Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-167

Octavia Adoption

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rhos-18.0.17 FR 5
    • None
    • Octavia LBaaS
    • None
    • RHOSSTRAT-904Reach Feature Complete Status for the Red Hat OpenStack Services on OpenShift 18.0 Adoption Process
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 17% To Do, 50% In Progress, 33% Done
    • rhos-connectivity-vans
    • Enhancement
    • Hide
      .Adoption of combined Networker/Controller nodes

      Adoption of RHOSP 17.1 environments that use the RHOSO Load-balancing service (octavia) are verified to work as documented in _link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/adopting_a_red_hat_openstack_platform_17.1_deployment/index[Adopting a Red Hat OpenStack Platform17.1 deployment]_.
      Show
      .Adoption of combined Networker/Controller nodes Adoption of RHOSP 17.1 environments that use the RHOSO Load-balancing service (octavia) are verified to work as documented in _link: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/adopting_a_red_hat_openstack_platform_17.1_deployment/index [Adopting a Red Hat OpenStack Platform17.1 deployment]_.
    • Done

      Feature Overview
      This feature defines the procedure and outlines the tooling necessary to adopt a Director-deployed Octavia Control Plane service from Red Hat OpenStack Platform (RHOSP) 17.1 into Red Hat OpenStack Services on OpenShift (RHOSO) 18. Octavia is the load balancing service for OpenStack, providing scalable and highly available load balancing for applications. The adoption process involves migrating the Octavia control plane while ensuring that existing configurations, load balancers, and listener configurations are preserved and continue to function seamlessly in the new RHOSO environment.

       

      Acceptance criteria:

      1. Successful adoption from 17.1 director deployed RHOSP to RHOSO

      Definition Done:
      1. Document all the limitations encountered while testing/adoption this feature
      2) Document "adoption guide" for this feature (if required)
      3) All QE test should have been automated, executed and passed in CI

              lavraham Lilach Avraham
              pnavarro@redhat.com Pedro Navarro Perez
              Gurpreet Singh Gurpreet Singh
              Edu Alcaniz Edu Alcaniz
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: