Hi Henrique,
On Sat, Mar 29, 2014 at 12:36 AM, Henrique Truta < [email protected]> wrote: > Hi all! > > I've been working on a prototype of Domains in Nova. In that prototype the > user is now able to do the following API calls with a domain scoped token: > > GET v2/domains/{domain_id}/servers: Lists servers which projects belong to > the given domain > GET v2/domains/{domain_id}/servers/{server_id}: Gets details from the > given server > DELETE v2/domains/{domain_id}/servers/{server_id}: Deletes the given server > POST v2/domains/{domain_id}/servers/{server_id}/action: Reboots the given > server > > Could you help me test these functionalities and review the code? > > I think it would be very useful if you could fill out the nova specs template for this change: https://github.com/openstack/nova-specs/blob/master/specs/template.rst It's still sort of in beta, but in this case the REST API section would be very helpful now in allowing us to separate review of the design first and get that right before tackling the review of the implementation. Is the domain referred to here the keystone domain? If so why do we need a separate resource path rather than just rely on the domain supplied through the token or ? Note that the tenant_id in the resource path is ignored in V2 and doesn't exist at all in the V3 API. Regards, Chris > The code can be found in my github repo ( > https://github.com/henriquetruta/nova) on the domains-prototype branch. > > Thanks! > > -- > -- > Ítalo Henrique Costa Truta > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
