Open Stack

2016-07-28 22:31 GMT+08:00 Jay Pipes <jaypipes at gmail.com>:

> On 07/20/2016 11:25 PM, Alex Xu wrote:
>
>> One more for end users: Capabilities Discovery API, it should be 'GET
>> /resource_providers/tags'. Or a proxy API from nova to the placement
>> API....?
>>
>
> I would imagine that it should be a `GET
> /resource-providers/{uuid}/capabilities` call on the placement API, only
> visible to cloud administrators.
>
>
When the end-user request a capability which doesn't support by the cloud,
the end-user needs to wait for a moment after sent boot request due to we
use async call in nova, then he get an instance with error status. The
error info is no valid host. If this is the only way for user to discover
the capabilities in the cloud, that sounds bad. So we need an API for the
end-user to discover the Capabilities which are supported in the cloud, the
end-user can query this API before send boot request.


>
> Best,
> -jay
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160801/750ebbeb/attachment.html>