Proposal policy question below.. Judd Maltin 1-917-882-1270 I have suffering to learn compassion once and once again.
On Jun 13, 2013 12:56 PM, "Vincent Untz" <[email protected]> wrote: > > Le jeudi 13 juin 2013, à 12:22 -0400, Judd Maltin a écrit : > > Sigh. > > > > I see what you mean about out-of-order keystone -> swift deployments. > > The user would have to re-deploy swift. Seems logical. Wouldn't they > > get to the Swift barclamp page, see that they have a keystone option, > > and then back out and go apply a keystone proposal? > > We can make this easier: if we don't care about non-keystone usage, we > can make it impossible to create a swift proposal if there's no keystone > proposal. I like the ability to deploy things out of order. I wanna bump this to Rob or Victor for comment. We would want to alert the user, though, surely. > > > I also see what you mean about Glance and Keystone. That's a *bad > > thing* if the glance service isn't registered at all in keystone, as > > nova still needs to talk to it. That should be broken in two.. I'll > > have another look at the code. > > I just think it's easier to always use keystone in glance ;-) I haven't tested using keystone and the glance file store. I'd hope that glance does not freak out when keystone auth_token is in the pipeline but is accessing files. What's your experience? > > Vincent > > -- > Les gens heureux ne sont pas pressés.
_______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
