XMLWordPrintable

    • Add consumer types in placement
    • 1
    • False
    • False
    • Committed
    • No Docs Impact
    • OSP-14490 - Large scale scheduling
    • openstack-nova-27.1.1-18.0.20230930093334.a869ab1.el9osttrunk
    • Committed
    • No impact
    • 67% To Do, 0% In Progress, 33% Done
    • Undefined
    • Technology Preview
    • Compute

      +++ This bug was initially created as a clone of Bug #1762355 +++

      Description of problem:

      Consumer types is a placement feature which is expected to be finished early in the U cycle and when it merges, it will be ready to consume by nova. Consumption of consumer types in nova would enable us to address two non-ideal behavior changes [1] that are present when:

      [quota]
      count_usage_from_placement = True

      The two behavior changes consuming placement consumer types would address are:

      1. "doubling" of quota usage (counted on both the source and the destination) for instances in VERIFY_RESIZE state

      2. "instances" quota usage being counted for instances in the ERROR state (note: historically instances, cores, and ram were counted against quota when in ERROR state but as of Train, when [quota]/count_usage_from_placement = True, cores and ram are not counted against quota when in ERROR state and only instances are still counted for ERROR state).

      [1] https://docs.openstack.org/nova/train/user/quotas.html#quota-usage-from-placement

      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
            rhos-dfg-compute
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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