[Openstack] Nova: Admin API blueprints
Vishvananda Ishaya
vishvananda at gmail.com
Wed Aug 31 00:41:36 UTC 2011
On Aug 30, 2011, at 5:22 PM, Nguyen, Liem Manh wrote:
> Thanks, Vish… Of course, now, I have more questions (naturally J):
>
> 1. So, if the Nova project/user objects go away, I assume the nova_auth_token middleware currently used for lazily creating Nova projects/users are not needed anymore?
Correct, the new middleware just sets the context, doesn't create keypairs.
> 2. Also, now that user/project operations are deprecated, how do we export the environment (novarc) for a particular user or project so that the euca* tools function?
Haven't solved this yet. It may have to be a manual process or external tool. Access and secret keys are stored in keystone with the new code, so it will have to get the data and then generate the creds.
> 3. Are the changes you mentioned in the Nova trunk already?
Yes
>
> Liem
>
> From: Vishvananda Ishaya [mailto:vishvananda at gmail.com]
> Sent: Tuesday, August 30, 2011 12:44 PM
> To: Nguyen, Liem Manh
> Cc: Glen Campbell; openstack at lists.launchpad.net
> Subject: Re: [Openstack] Nova: Admin API blueprints
>
> This is correct. Well, they are still there, but marked deprecated. One can still use the old user and project system by using the --use_deprecated_auth flag and using the modified middleware stack that is commented out in the default paste.ini file.
>
> Vish
>
>
> On Aug 30, 2011, at 11:37 AM, Nguyen, Liem Manh wrote:
>
>
> So, by the release of Diablo, the account and project operations from the nova-manage command won’t be there anymore, and things should be done via Keystone? I assume role will go away as well, since this is also covered by Keystone. Is this correct?
>
> Thanks,
> Liem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110830/0995372d/attachment.html>
More information about the Openstack
mailing list