These core services, when integrated together, offer the functionality necessary for managing our fleet of device edge devices. A virtual machine template to deploy virtual machines from which we can build our images.A virtualization platform such as Red Hat OpenShift Virtualization (formerly container-native virtualization).A pipeline technology we’ll be using Red Hat OpenShift Pipelines.An instance of Ansible automation controller to drive our automation and leverage existing automation.Management of local storage for retaining our composed images, databases, etc.An image registry to store our edge images as we compose them.Now that we understand some of the why, let's move forward and lay out what components we will be using in this single-node OpenShift "edge manager in a box." The core set of services we’ll be consuming are: Operators are genuinely a great way to reduce the barrier of entry when it comes to installing services and components in OpenShift.Device Edge images are really just YAML files that should be maintained in Git, which gives us a clear path to infrastructure as code (IaC) and proper continuous integration/continuous deployment ( CI/CD) all within OpenShift Container Platform.Since it's OpenShift, the SNO concept can be graduated to a large cluster to meet the capacity needs of a production environment.Having all the components in a single OpenShift node provides a quick and easy way to prove out a concept.Having all the components in a single-node OpenShift (SNO) cluster makes it a great way to have a one-stop experience.Why use OpenShift on a single node?īefore we begin, let us step back and ask: Why do this? Well, there are a variety of reasons:
SHIFT TECHNOLOGIES EARNING FULL
Keep in mind that you can apply these same concepts to a 3-node compact and full OpenShift cluster as well.
SHIFT TECHNOLOGIES EARNING HOW TO
This article details how to go about building this configuration on a single-node OpenShift cluster. OpenShift, in a sense, helps make managing devices at the edge simpler and cost-effective. In addition, OpenShift manages many of these services via an Operator, meaning a non-technical team doesn’t need to understand all the specific details about the service. One of those components, the scheduler, enables these services to be efficiently co-located onto a single platform. Red Hat OpenShift includes an abundance of technologies out of the box that are necessary for effectively managing a fleet of devices at the edge.
0 kommentar(er)
