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

Unified Limits Integration in Nova

XMLWordPrintable

    • Unified Limits Integration in Nova
    • False
    • False
    • OSPRH-811Red Hat OpenStack 18.0 Greenfield Deployment
    • Committed
    • No Docs Impact
    • OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
    • openstack-nova-27.1.1-18.0.20230930093334.a869ab1.el9ost
    • Committed
    • No impact
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      .Use of Identity service (Keystone) unified limits in the Compute service (nova)

      This RHOSO release supports Identity service unified limits in the Compute service. Unified limits centralize management of resource quota limits in the Identity service (Keystone) and enable flexibility for users to manage quota limits for any Compute service resource being tracked in the Placement service.
      Show
      .Use of Identity service (Keystone) unified limits in the Compute service (nova) This RHOSO release supports Identity service unified limits in the Compute service. Unified limits centralize management of resource quota limits in the Identity service (Keystone) and enable flexibility for users to manage quota limits for any Compute service resource being tracked in the Placement service.
    • Technology Preview
    • Done
    • Rejected

      Description of problem:

      Support for keystone unified limits in nova
      for centralized quota and resource limits.

      The work on unified limtis has been ongoing for several cycles.
      https://review.opendev.org/#/c/602201/
      to move that effort forword requires a multi cycle investment

      While much work has been done to simplify how quotas are implemented in
      Nova, there are still some major usability issues for operators with
      the current system:

      • We don't have consistent support for limit/quota hierarchy across OpenStack
      • Requiring operators to set limits individually in each service
        (i.e. Cinder, Nova, Neutron, etc)
      • Nova's existing quotas don't work well with Ironic
      • No support for custom Resource Class quotas (includes "per flavor" quotas)
      • Confusion when API defined quota limits override any changes made to the
        configuration
      • Some Nova quotas are unrelated to resource consumption, causing confusion

      Transitioning to use Keystone's unified limits, via oslo.limit, will help fix
      these issues.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:
      1.
      2.
      3.

      Actual results:

      Expected results:

      Additional info:

            mwitt@redhat.com melanie witt
            jira-bugzilla-migration RH Bugzilla Integration
            James Parker James Parker
            rhos-dfg-compute
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 4 days, 2 hours
                4d 2h
                Remaining:
                Remaining Estimate - 4 days, 2 hours
                4d 2h
                Logged:
                Time Spent - Not Specified
                Not Specified