Virtualization isn’t going away any time soon.

Alongside the ever-growing need to modernize and move towards a more elastic, agile, and scalable cloud native infrastructure, many organizations also need to run, maintain, and in a lot of cases grow their traditional virtualization environment.

As a leader in cloud infrastructure, with Red Hat OpenStack Platform and Red Hat OpenShift, Red Hat is in a unique position to offer an integrated approach for customers to enjoy the best of both worlds.  How exactly? Let's see!

Red Hat OpenStack Platform Director Operator: What is it?

Director Operator is a Kubernetes Operator-backed deployment method which leverages Kubernetes CRDs, Multus 2nd  interfaces, Metal3, Red Hat OpenShift Virtualization and TripleO-Ansible to provide a hybrid deployment solution for both container native workloads and traditional VMs side by side. This deployment methodology will future-proof the workload infrastructure for container-native applications while having it host the traditional VMs with Red Hat OpenStack Platform.

image2-Aug-17-2023-09-02-29-3089-PM

Since the Director Operator is not a net new installer but rather uses TripleO Heat, it maintains the traditional director templating structure, but with a twist! Now said templates are being consumed by a configmap called by a CRD to generate from the Ansible content that will be deployed on the target nodes.

The controller nodes are based on OpenShift Virtualization VMs and are provisioned by calling the ctlplne CRD while the compute nodes andHCI Nodes are being called by the compute provision CRD from the OpenShift Cluster Metal3 inventory. Since, this inventory is shared with the OpenShift infrastructure and the bare metal nodes in it can be repurposed to expand either the OpenStack cluster or the OpenShift cluster if needed.

The Deployment Flow steps using OpenStack Director Operator

image3-Aug-17-2023-09-02-04-8407-PM

Once the deployment finishes the environment will look like this:

image1-Aug-17-2023-09-02-17-0924-PM

 

  1. Red Hat OpenStack Platform has a 5 year long life cycle for which our customers plan critical workloads and certifications that are tied to both an API and host operating system (RHEL).
  2. In most use cases, the Red Hat OpenStack Platform dataplane is being used to run critical applications which cannot tolerate multiple downtimes. Even if the host OpenShift infrastructure is being updated, the workloads will continue to run without interference.

Join us for the next blog in this series in which we will explore the set-by-step guide on how to deploy a Red Hat OpenStack Platform director operator OpenStack cloud.