Question on "openstack resource provider allocation" commond

Bug #1761039 reported by Yikun Jiang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
placement-osc-plugin
Opinion
Undecided
Unassigned

Bug Description

Now we have four commands about allocation

* resource provider allocation delete
* resource provider allocation set
* resource provider allocation show

and map to API:

    '/allocations/{consumer_uuid}': {
        'GET': allocation.list_for_consumer,
        'PUT': allocation.set_allocations_for_consumer,
        'DELETE': allocation.delete_allocations,
    },

But I just think why these are NOT defined as:
* resource allocation delete
* resource allocation set
* resource allocation show

Because we have a list for provider:
    '/resource_providers/{uuid}/allocations': {
        'GET': allocation.list_for_resource_provider,
    },

If we want to add support for this API, maybe using ``resource provider allocation show`` is more suitable in here

So, I just wanna sure is there some special consideration on here.

Revision history for this message
Matt Riedemann (mriedem) wrote :

There probably wasn't much thought put into this at first because everything started as 'openstack resource provider ...' and the allocation CLI was probably just following that pattern, but it arguably could have been 'openstack resource consumer allocation ...' etc.

Changed in placement-osc-plugin:
status: New → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.