[Openstack] Entities in OpenStack Auth

Eric Day eday at oddments.org
Wed Mar 2 19:49:55 UTC 2011

On Wed, Mar 02, 2011 at 07:43:08PM +0000, Glen Campbell wrote:
> According to the proposed API 1.1 spec, it *does* use an extra element in
> the path to indicate the account; this is (presumably) returned by the
> auth system:
> http://servers.api.openstack.org/v1.1/1234/servers/12
> Where "1234" is the account ID (actually a token, I believe) and "12" is
> the server ID. 
> See p. 5 of the latest API 1.1 doc.

Thanks, I saw Jorge pointed that out earlier as well. With that,
this discussion is more focused on how this maps to 'users' and
'projects' in nova and how to list servers (or any resource) across
multiple accounts.

> On 3/1/11 8:14 PM, "Eric Day" <eday at oddments.org> wrote:
> >For that query you would, but not all. If you want to create a new
> >instance for project1 you would:
> >
> >nova.openstack.org/v1.1/project1/servers
> >
> >Or if you wanted to reboot instance X in project1:
> >
> >nova.openstack.org/v1.1/project1/servers/X
> >
> >Note that the following resource is not the same as the last, since
> >justin wouldn't be the owner for instance X, project1 would be:
> >
> >nova.openstack.org/v1.1/justin/servers/X
> >
> >I think searches will always have special cases with filter options,
> >but for identifying a canonical URL for a resource, having the entity
> >name of the owner in there seems correct.
> >
> >The main thing I'm trying to figure out is whether to use an extra
> >entity in the path for new service URLs. Swift does and Nova does not,
> >and it would be nice to have some consistency. I see the benefits of
> >both, and in Swift's case it needs to for simple public URLs (where
> >there is no user context).
> >
> >-Eric

More information about the Openstack mailing list