Categories

• Generic.

  Generic software used with platforms

  865
  Topics
  877
  Posts

  

  There's the console in the bottom right corner of the browser window you will see the version. Check in the config.xml file. $ cd /var/lib/jenkins $ grep -i version config.xml <?xml version='1.1' encoding='UTF-8'?> <version>2.138.1</version> There's also the jenkins cli. Note: For demo purposes there's no authorization setup. $ java -jar jenkins-cli.jar -s http://localhost:8080/ version 2.138.1
• Cloud Platforms

  Cloud Platforms

  158
  Topics
  159
  Posts

  

  This is the demo application as shown in: https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html The previous steps to follow before running this demo application are as follows: How do i setup the pre-reqs for eks - aws kubernetes service? How do i install linux kubectl for aws eks - aws kubernetes? How do i install the go programming language on linux? How do i install the aws-iam-authenticator for aws eks? How do i create an aws eks cluster using the cli? How do i configure kubectl for aws eks? How do i add worker nodes to an aws eks cluster? How do i enable worker nodes to join my eks cluster? If you want to see the code for each kubernetes object view the raw github URL in a browser or use curl e.g: $ curl https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/guestbook-controller.json Create the Redis master replication controller. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/redis-master-controller.json replicationcontroller "redis-master" created Create the Redis master service. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/redis-master-service.json service "redis-master" created Create the Redis slave replication controller. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/redis-slave-controller.json replicationcontroller "redis-slave" created Create the Redis slave service. kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/redis-slave-service.json service "redis-slave" created Create the guestbook replication controller. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/guestbook-controller.json replicationcontroller "guestbook" created Create the guestbook service. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/v1.10.3/examples/guestbook-go/guestbook-service.json service "guestbook" created Query the services in your cluster and wait until the External IP column for the guestbook service is populated. $ kubectl get services -o wide Open the URL in a browser to see the guestbook application.
• Linux.

  Redhat, Ubuntu, Centos, SUSE & all Linux Operating Systems

  2406
  Topics
  2410
  Posts

  

  $ snap changes ID Status Spawn Ready Summary 66 Done today at 03:24 PDT today at 03:24 PDT Auto-refresh snap "wine-platform-i386" 67 Done today at 04:14 PDT today at 04:14 PDT Remove "notepad-plus-plus" snap 68 Done today at 04:15 PDT today at 04:15 PDT Install "notepad-plus-plus" snap
• Unix

  Solaris, HP-UX & AIX

  2439
  Topics
  2439
  Posts

  

  Link: https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXIEXP1131 There is HPE product called HP-UX Internet Express for HP-UX 11i v3, which has a number of open source tools, one of which is sudo. The information on whether you need a license for downloading the software depot is not forthcoming and not easy to find on their website. The product appears to free, but as it is open source not support is provided.
• Virtualization - Containers - Hardware Partitioning

  Virtual Platforms & Containers

  358
  Topics
  363
  Posts

  

  A liveness command to check the health of an application. It all very well having the container running in a pod but application checks need to be in place too. Let's break down the code below: create a container running the busybox image get it to execute command to create file wait 30 seconds remove the file (to trigger simulate a failure) wait 300 seconds. apiVersion: v1 kind: Pod metadata: labels: test: liveness name: liveness-exec spec: containers: - name: liveness image: k8s.gcr.io/busybox args: - /bin/sh - -c - touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600 livenessProbe: exec: command: - cat - /tmp/healthy initialDelaySeconds: 3 periodSeconds: 5 Create the pod. $ kubectl create -f livenesscmd.yaml Looking at the events, you can see the pod being creating going into a unhealthy state, and then starting a new container. $ kubectl describe pod liveness Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 1m default-scheduler Successfully assigned liveness-exec to minikube Normal SuccessfulMountVolume 1m kubelet, minikube MountVolume.SetUp succeeded for volume "default-token-fpffp" Warning Unhealthy 33s (x3 over 43s) kubelet, minikube Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory Normal Pulling 2s (x2 over 1m) kubelet, minikube pulling image "k8s.gcr.io/busybox" Normal Pulled 2s (x2 over 1m) kubelet, minikube Successfully pulled image "k8s.gcr.io/busybox" Normal Created 2s (x2 over 1m) kubelet, minikube Created container Normal Killing 2s kubelet, minikube Killing container with id docker://liveness:Container failed liveness probe.. Container will be killed and recreated. Normal Started 1s (x2 over 1m) kubelet, minikube Started container As well as the Liveness command, there are two other types of Liveness checks, Liveness HTTP Request and TCP Liveness Probe.
• Learn

  Learn New Things

  115
  Topics
  115
  Posts

  

  Man page for systemd(1), init(1) - systemd system and service manager Man page for systemd.special(7) - Special systemd units $ systemctl list-unit-files --type=service You can also list units by type. $ systemctl list-units --type=device The type of units are: The following unit types are available: 1. Service units, which start and control daemons and the processes they consist of. For details see systemd.service(5). 2. Socket units, which encapsulate local IPC or network sockets in the system, useful for socket-based activation. For details about socket units see systemd.socket(5), for details on socket-based activation and other forms of activation, see daemon(7). 3. Target units are useful to group units, or provide well-known synchronization points during boot-up, see systemd.target(5). 4. Device units expose kernel devices in systemd and may be used to implement device-based activation. For details see systemd.device(5). 5. Mount units control mount points in the file system, for details see systemd.mount(5). 6. Automount units provide automount capabilities, for on-demand mounting of file systems as well as parallelized boot-up. See systemd.automount(5). 7. Snapshot units can be used to temporarily save the state of the set of systemd units, which later may be restored by activating the saved snapshot unit. For more information see systemd.snapshot(5). 8. Timer units are useful for triggering activation of other units based on timers. You may find details in systemd.timer(5). 9. Swap units are very similar to mount units and encapsulate memory swap partitions or files of the operating system. They are described in systemd.swap(5). 10. Path units may be used to activate other services when file system objects change or are modified. See systemd.path(5). 11. Slice units may be used to group units which manage system processes (such as service and scope units) in a hierarchical tree for resource management purposes. See systemd.slice(5). 12. Scope units are similar to service units, but manage foreign processes instead of starting them as well. See systemd.scope(5). Units are named as their configuration files. Some units have special semantics. A detailed list is available in systemd.special(7).
• News

  News from various vendors

  6725
  Topics
  6725
  Posts

  

  <p>The OpenSSL Management Committee (OMC) on behalf of the OpenSSL Project would like to formally express its thanks to the following organisations for agreeing to sponsor the next FIPS validation effort: Akamai Technologies, Blue Cedar, NetApp, Oracle, VMware.</p> <p>Four weeks ago, the OpenSSL team gathered with many of the organisations sponsoring the next FIPS module for a face-to-face meeting in Brisbane, Australia.</p> <p>We got a great deal accomplished during that week. Having most of the fips-sponsor organisations in the same location helps ensure that we are all on the same page for the decisions we need to make going forward.</p> <!-- more --> <p>The fips-sponsor gathering (hosted by Oracle, Brisbane) involved a diverse group of people:</p> <p><img src="https://www.openssl.org/blog/images/2018-08-27-fips-sponsors.png" title="" ></p> <p>It has been more than seven years since the commencement of the previous FIPS140 module work and many things have changed during that time, both in terms of requirements of the Cryptographic Module Validation Program (CMVP) and the OpenSSL code base.</p> <p>For the current validation effort, input and assistance from a small group (the five fips-sponsors) is essential to achieving the outcomes of the project in this area - a validated module that is usable by itself and can also form the foundation for other companies to perform their own validations for any areas where there are specific requirements outside the general scope.</p> <p>As the project moves from high-level design to detailed design, prototyping, development, testing, documentation and quality assurance, we plan to make information available to the OpenSSL community for review and comment - as the next FIPS140 module will be substantially different to the previous approaches.</p> <p>We are mindful of the end-of-life date for OpenSSL-1.0.2 (31-Dec-2019) and the end-of-life (sunset date) of the existing OpenSSL FIPS Object Object (29-Jan-2022) and our objective remains to have a validated cryptographic module in place well before 31-Dec-2019.</p><br/><br/><a href="https://www.openssl.org/blog/blog/2018/09/25/fips/">https://www.openssl.org/blog/blog/2018/09/25/fips/</a>
• Notebook
  88
  Topics
  88
  Posts

  

  Link: https://en.wikipedia.org/wiki/Unix_time A lot of us do not know what epoch means? In this context the definition is: A point of time distinguished by a particular event or state of affairs; a memorable date. It is the number of seconds passed since beginning of 00:00:00 UTC Thursday 1, January 1970 minus the number of leap seconds. This applies to all Unix-like systems.
• Hall Of Fame

  Famous People In Information Technology

  7
  Topics
  7
  Posts

  

  Links: https://en.wikipedia.org/wiki/Jon_Postel Obituary post on RFC's by Vint Cerf: https://www.rfc-editor.org/rfc/pdfrfc/rfc2468.txt.pdf Jon Postel (1943 - 1998), For 3 decades RFC Editor, Involvement protocols which made The Internet possible, protocols like SMTP & TCP/IP are very much a part of The Modern Internet. He also the founder of the Internet Assigned Numbers Authority (IANA). Then later, a key figure in the Internet Corporation for Assigned Names and Numbers (ICANN) "An Internet Pioneer!" Jonathan Bruce Postel. a.k.a "God Of The Internet" by the media. "The Internet should not be managed by any government, national or multinational." "Group discussion is very valuable; group drafting is less productive."
• Comments & Feedback

  Got a question? Ask away!
  1
  Topics
  1
  Posts

  

  Hello. This area is for comments and feedback about the services & website only.