Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-19555

QE testing for unified limits oslo.limit endpoint discovery in 18.0

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • openstack-nova
    • QE testing for unified limits oslo.limit endpoint discovery in 18.0
    • False
    • False
    • RHOSSTRAT-985Enable unified limits oslo.limit endpoint discovery in 18.0
    • Not Selected
    • ?
    • ?
    • To Do
    • ?
    • rhos-workloads-compute
    • ?
    • 100% To Do, 0% In Progress, 0% Done

      Currently, there is a manual step required when configuring unified limits on 18.0 to set the endpoint ID in the nova.conf for nova-api and nova-conductor services, for example:

      [oslo_limit]
      endpoint_id = <Nova API endpoint ID>
      

      This is documented in:

      https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/configuring_the_compute_service_for_instance_creation/assembly_configuring-unified-limits_scheduling-and-placement#proc_enabling-unified-limits_scheduling-and-placement

      With this change (oslo.limit endpoint discovery), it is no longer necessary to do the manual configuration step.

      One way to verify this would be to remove the Nova endpoint_id related code from:

      https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/blob/main/playbooks/podified/hooks/nova-unified-limits-enable.yaml

      and verify the CI job still passes.

              rhn-gps-jparker James Parker
              mwitt@redhat.com melanie witt
              rhos-workloads-compute
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: