IBM/Red Hat/Fedora Leftovers

-
IBM Keeps OpenShift Up To Speed On Power Systems - IT Jungle
For more than two years now, as we have previously reported, there have been a number of ways to bring Kubernetes container control to the Power Systems platform, including Docker Enterprise Edition, IBM Cloud Private, and Red Hat OpenShift. In the wake of the Red Hat acquisition, it is pretty clear that OpenShift will be the container environment of choice on IBM System z and Power Systems machines on premises and on these machines as well as X86 iron deployed on the IBM Cloud.
To that end, we find in announcement letter 220-439 that IBM’s Red Hat unit has ported its OpenShift Container Platform, 4.6 release to Power Systems iron. The reason that this does not happen automagically is that Red Hat OpenShift is not based on the stock Red Hat Enterprise Linux distribution, but rather the CoreOS Linux, a streamlined variant of Linux that can be upgraded while active that Red Hat acquired a couple of years back. (If you want to know more about CoreOS, I covered it extensively at The Next Platform, my other day job.) It takes a little extra time to make sure CoreOS works on Power chips. If customers want to mix and match KVM virtualization with Kubernetes containers, they have to buy a proper RHEL license for their machines. (Why IBM doesn’t just bundle RHEL, perhaps a single partition only, by default on Power9 systems already is beyond me. Set it up so companies can start playing with containers for free.) Anyway, OpenShift Container Platform is sold with licenses that span two cores at a time. In addition, the OpenShift distro can run various IBM Cloud Paks, which are containerized packages of IBM middleware and other open source systems software and applications.
-
Devfiles and Kubernetes cluster support in OpenShift Connector 0.2.0 extension for VS Code [Ed: Red Hat working to promote Microsoft proprietary software with surveillance]
We are pleased to announce that the new release of the OpenShift Connector extension for Visual Studio Code (VS Code) is now available. The 0.2.0 release offers new features for rapidly developing and deploying code on Kubernetes and Red Hat OpenShift clusters. OpenShift Connector now supports component deployment using devfiles, leveraging odo 2.0 command-line interface under the hood.
With this release, the extension now supports connecting to vanilla Kubernetes clusters and includes a new option for creating OpenShift 4 clusters locally via Red Hat CodeReady Containers (CRC). In this article, we introduce these new features and present the workflow for using CodeReady Containers with OpenShift Connector 0.2.0.
-
Podman with capabilities on Fedora - Fedora Magazine
Containerization is a booming technology. As many as seventy-five percent of global organizations could be running some type of containerization technology in the near future. Since widely used technologies are more likely to be targeted by hackers, securing containers is especially important. This article will demonstrate how POSIX capabilities are used to secure Podman containers. Podman is the default container management tool in RHEL8.
-
Obtain previous Job ID in Ansible Tower Workflow
Ansible Tower allows you to create Workflows, which enable you to create complex workflows by putting together multiple Ansible Playbooks. Ansible Tower Workflows can have some simple logics, such as run different Ansible Playbooks based on the outcome (success or failure) of a previous Ansible Playbook run. Sometimes, though, you need to have more information about a previous Ansible Playbook run than just the outcome.
I recently found myself in a situation where I had an Ansible Tower Workflow with two Ansible Playbooks into it, where the first one was performing specific tasks. The second one needed to get and process the output of the first Ansible Playbook. Since Ansible Tower provides an API to fetch an Ansible Playbook run output, this part is trivial if you know the Job ID that Ansible Tower assigned to that specific run. Looking around, I’ve not found much information on how to retrieve the Job ID of a different Job, so I looked at the various APIs and found this solution, which I’m going to share with you today. I’ve not found much information about getting another Job ID because it is usually a bad practice to do such a thing and that very often you can achieve the same goal in a much cleaner way. This better option, though, was not present in my case. Due to many constraints I had in this project, this was the best way I’ve found, even if I’ve tried - at least mentally - many other ways before accepting that this was the only one in my case.
-

- Login or register to post comments
Printer-friendly version- 3223 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

EMPLOYERS Modernizes Digital Transformation with Red Hat
EMPLOYERS Modernizes Digital Transformation with Red Hat