Red Hat OpenStack tightens OpenShift Kubernetes integration

Crimson Hat has introduced Crimson Hat OpenStack System 16.two, an update to Crimson Hat’s infrastructure-as-a-assistance platform that offers tighter integration with the company’s OpenShift Kubernetes container procedure.

With the new integration, buyers of each platforms can operate VM-based and container-based purposes in parallel with improved community potential, protection characteristics, storage, and efficiency, Crimson Hat said on October thirteen. OpenStack 16.two is out there by the Crimson Hat Consumer Portal via a Crimson Hat subscription.

Precise abilities in OpenStack 16.two involve:

• Overall flexibility to operate VMs and cloud-indigenous purposes in parallel. “Bare metal” efficiency is presented via integration with OpenShift.
• An extended lifecycle letting for continual characteristic updates devoid of disruption or opportunity downtime.
• New components possibilities which include Intel Xeon scalable processors. People can establish hybrid clouds in a fashion that suits them, factoring in main architecture to components offloading with smartNICs.
• Storage has been designed easier by aggregating a range of distributors and formats.
• For edge connectivity and software availability, availability zone awareness is presented via Open Virtual Networking (OVN). Operators can set up nodes in teams, based on a geographic site, electricity sources, and opportunity for downtime.

In other developments from Crimson Hat on October thirteen:

• The Crimson Hat establish of the Quarkus Kubernetes-indigenous Java framework provides continual tests and a new CLI eradicating the have to have for Gradle and Maven instructions. Also, the GUI has been up to date, offering visual representations of extensions and documentation, and Rest endpoints. New developer solutions, meanwhile, quickly link well-liked databases, information queues, and additional to purposes as they are designed.
• Crimson Hat OpenShift 4.9 and Crimson Hat State-of-the-art Cluster Management for Kubernetes two.4 had been unveiled, intended to provide for regularity in hybrid cloud networks. One-node OpenShift is highlighted for a tiny Kubernetes cluster. Previous OpenShift topologies have incorporated 3-node clusters and remote employee nodes.