On Mon, Mar 26, 2012 at 2:48 AM, Deepak Garg wrote:
> Thanks, I will keep this in mind.
>
> a. when this is well thought out, you may include it in Community Projects
> b. Here's CLI auth bp sent to Netstack list in case you are catching
> up with emails: http://wiki.openstack.org/QuantumCliAuth
On Fri, Mar 30, 2012 at 12:35 AM, Deepak Garg wrote:
> Thanks Rohit for taking out time to go through the bp.
>
> Keystone may be implementing some caching but in case when the user
> has stored the Username credentials as env vars and he is using the
> quantum cli again and again, we wouldn't lik
Ok, so to summarize, this is my understanding of how things will work
moving forward:
- it seems that all of nova-manage is going away in Folsom (this is a nova
team decision). Many of the calls will be replaced with nova "admin API"
calls.
- in Folsom, we are removing the requirement that all qu
Regarding caching:
As of today, caching strategies vary a lot between projects although
they are a valid candidate for openstack-common. I don't see it being
done in short term.
My proposal is to ping openstack-common folks and see if we can
include the basic auth code there and when other project
Hi.
Salvatore actually had a branch to merge plugins.ini with quantum.conf a
while back, but we kept delaying because we felt that we were too close to
a milestone release.
Here's the change-set: https://review.openstack.org/#change,1415
I think that patch could now be simplified, as for Folsom I
This is my understanding as well.
I reckon that removing the need for using nova-manage for Quantum networks
should also make unnecessary moving network-related nova-manage operations to
nova CLI.
The 'admin user' authentication for Nova <-> Quantum interactions should be
good enough in many c
Deepak,
Thanks for submitting this blueprint.
I think it looks very good, and I have only a couple of minor points:
1) --endpoint_url: don't we have already a mechanism for specifying the quantum
service uri?
2) 401 error: I think it should include the case of invalid credentials too,
leaving
7 matches
Mail list logo
