Open Stack

To be fair, we test only the subset that is set via devstack on the stable
side. That should be a common subset, but it is far from fully
comprehensive. Nova has over 600 config variables, so additional tooling
here would be goodness.

Sean Dague
http://dague.net
On Nov 18, 2013 7:35 AM, "Dan Smith" <dms at danplanet.com> wrote:

> > Another issue that we might want to try and solve with this (and imho
> > another reason to keep the framework for this in oslo) is that we might
> > want to make these update aware, and allow for some graceful degradation
> > or something similar when for example an updated service is stated with
> > an outdated config.
> >
> > Maybe Dan could weigh in on this?
>
> Well, AFAIK, we require config compatibility between subsequent
> versions, so there really shouldn't be anything to report. It might be
> useful to report, when running the havana tool against an
> upgraded-from-grizzly config which things are deprecated though.
>
> We already test that the config upgrade works in the grenade test in the
> gate, so there really shouldn't be any degredation experienced by the
> user after an upgrade...
>
> --Dan
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131118/c8436e31/attachment.html>