DevConf.US 2022

Edge is a space that has all of the buzz right now but for some of us that came from customers to Red Hat from retail and energy verticals it is nothing new… EXCEPT the technology has caught up to some of the needs we had 20 years ago as well as we are seeing a convergence of IT and OT with the introduction of millions of low cost IOT devices.

In this session we will talk about how to: Build and deploy a factory for deploying and managing RHEL for Edge (rpm-ostree) devices using OpenShift
Building Ansible Automation Platform using OpenShift Gitops on OpenShift
Managing devices via Ansible Automation Platform
Using the Ansible Automation Platform to manage the deployment of the OS
Lifecycle the application running in podman as a systemd service using Ansible Automation Platform to manage them at scale.
Declarative and imperative systems and how you need both in order do have completely automated gitops deployments

Audience Takeaways and Ecosystem Benefits:
How people are doing large scale deployments of containerized applications at the edge on small form factor devices at low cost of ownership
Understanding of gitops in imperative and declarative use cases

Imperative vs Declarative Brief(excerpt):
In GitOps, we make a distinction between declarative and imperative systems. The commonly accepted distinction goes as follows:
Imperative Automation defines the steps to execute in order to reach the desired solution.
Declarative Automation defines the desired end state of the automation.
In general, declarative automation systems are considered better because they do more for the user - they abstract more of the automation task by forcing users to consider an end state rather than worry about the details of how to reach that end state (or at least tell users and operators why they cannot). Kubernetes classifies itself as a declarative system.