Outcome Overview

This Outcome establishes GitOps as the standardized, supported, and scalable approach for Day 1 (deployment) and Day 2 (ongoing management, updates, and maintenance) operations of Red Hat OpenStack Services on OpenShift (RHOSO) environments. By integrating RHOSO with OpenShift's ecosystem and Red Hat automation products (like ArgoCD, OpenShift Pipelines), we will deliver a controlled, secure, and highly automated solution for managing one or multiple RHOSO environments. This directly contributes to strategic goals around customer operational efficiency, scalability of complex deployments, and consistency across enterprise cloud environments, making RHOSO deployments less cumbersome, faster to recover from incidents, and significantly reducing configuration drift and operational overhead.

Crucially, this Outcome also includes the development of a supported, GitOps-driven automation workflow and documentation to enable the smooth, consistent, and repeatable in-place upgrade path from existing Red Hat OpenStack Platform (RHOSP) 17.1 environments to the new RHOSO 18 architecture. This work directly addresses the need to accelerate customer migration to the RHOSO architecture by providing a controlled, auditable, and automated adoption mechanism, immediately proving the value of GitOps practices to our existing RHOSP customer base.

Success Criteria

What is the success criteria for this strategic outcome?  Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

• Standardized Automation: A documented, supported, and repeatable GitOps-based workflow exists for the initial deployment and full lifecycle management (updates, rollbacks) of RHOSO across typical enterprise environments (Dev, Stage, Prod).
• Migration Acceleration: A supported GitOps-driven procedure for the automated, controlled upgrade/adoption from RHOSP 17.1 to RHOSO 18 is documented, validated, and made available to customers.
• Operational Consistency: Cloud administrators can verify and enforce configuration consistency across multiple RHOSO environments by referencing a single Git repository as the source of truth, minimizing configuration drift.
• Scalability Enablement: The solution simplifies the management of multiple or large RHOSO environments, addressing the current challenge of increasing complexity with scale.
• Customer Adoption Readiness: Comprehensive user documentation, guides, and reference architectures are available and promoted to enable customers and field teams to successfully adopt the GitOps workflow for RHOSO deployment and management.

Expected Results (what, how, when)

Post Completion Review – Actual Results

After completing the work (as determined by the "when" in Expected Results above), list the actual results observed / measured during Post Completion review(s).

• Time-to-Deployment (TTD) Reduction: [Actual measurement]

• Upgrade Success Rate: [Actual measurement]

• Configuration Drift Incidents (CDI): [Actual measurement]

• Adoption Rate and Feedback: [Actual measurement/summary of feedback]

• Time to Rollback (TTR): [Actual measurement]