yahoo-eng-team team mailing list archive

[OpenStack Infra <1621059@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/366789
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=eab8100b429a0b781b7a5322cecffeffa43d20d2
Submitter: Jenkins
Branch:    master

commit eab8100b429a0b781b7a5322cecffeffa43d20d2
Author: Chris Dent <cdent@xxxxxxxxxxxxx>
Date:   Wed Sep 7 14:27:24 2016 +0000

    [placement] add two ways to GET allocations
    
    Add two resources on the placement api for retrieving allocations.
    
    One, /resource_providers/{uuid}/allocations, returns all the
    allocations currently against this resource provider in this format:
    
        {'resource_provider_generation': GENERATION,
         'allocations':
            CONSUMER_ID_1: {
                'resources': {
                    'DISK_GB': 4,
                    'VCPU': 2
                }
            },
            CONSUMER_ID_2: {
                'resources': {
                    'DISK_GB': 6,
                    'VCPU': 3
                }
            }
        }
    
    Another, /allocations/{consumer_id}, returns all the allocations for
    the current consumer in this format:
    
        {'allocations':
          RP_UUID_1: {
            'generation': GENERATION,
            'resources': {
                'DISK_GB': 4,
                'VCPU': 2
            }
          },
          RP_UUID_2: {
              'generation': GENERATION,
              'resources': {
                  'DISK_GB': 6,
                  'VCPU': 3
              }
          }
        }
    
    The formats are eminently usable on the client side, by having a
    comparable dict reachable by a predictable key, but not self
    describing (we don't know that the keys are consumer ids or resource
    uuids).
    
    In the first format the descent into a resources key is to maintain
    parity with the second format and provide room for expansion.
    
    Change-Id: I69fbc4e9834ec6dc80dacf43f8fd9dc6ec139006
    Closes-Bug: #1621059


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1621059

Title:
  placement api needs GET /resource_providers/{uuid}/allocations

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Somehow in the spec process this was overlooked but it is required for
  the resource tracker to effectively update allocation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1621059/+subscriptions