On Fri, Jun 14, 2013 at 08:37:02AM -0500, [email protected] wrote:
> Definitely, true for community branch.
> +1 of documenting known issues both in code and on wiki (or whatever is
> appropriate place)
Instead of documenting this I would prefer if the glance barclamp did not
silently change the use_keystone value to false if no keystone proposal is
found. But would require the user to explicitly change that value. I suspect
that in most case when the user tries to deploy glance before keystone it's by
mistake and not by intention.
If use_keystone is still true when saving the proposal with no keystone
proposal present, we can still error out in validate_proposal_after_save()
without doing any harm.
This whole discussion is IMO pretty similar to the silent fallback to sqlite
when no mysql/postgresql was deployed. Which luckily was fixed meanwhile.
regards,
Ralf
_______________________________________________
Crowbar mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
