On 3/1/11 6:11 PM, Eric Day wrote:
[ ... trimmed ... ]
For the OpenStack API, we need something a bit different from what we
have today. We currently have no way of passing in a project name,
so I propose we add an "entity" element to the path name (just like
Swift does). For example, instead of "/v1.0/servers/1", it would be
"/v1.0/entity/servers/1", where entity can represent an account (like
swift), project (like current nova), or even a user entity (deployments
where projects or accounts are not used). Our window for OpenStack
API changes is still open as it's still under heavy development,
and I think this path addition will provide more functionality and
a consistent structure across services (glance and burrow will be
using an account or "entity" in the path as well).
FYI: the multitenant blueprint, which I will be proposing for merge
later today or early tomorrow, does just this to pass the project name in.
--
--
-Monsyne Dragon
work: 210-312-4190
mobile 210-441-0965
google voice: 210-338-0336
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is
prohibited.
If you receive this transmission in error, please notify us immediately by
e-mail
at ab...@rackspace.com, and delete the original message.
Your cooperation is appreciated.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
