Hi, I'm not sure if we should add the new state in this case, it looks like you can get this information dynamically, you already have the state of env which tells you that there are new ceph nodes, and there are no ready ceph nodes in the cluster hence you should install ceph-mon on the controllers.
The same for rabbitmq, if there is new controller, run rabbit reconfiguration on non-controllers nodes. Thanks, On Tue, Oct 7, 2014 at 6:14 PM, Dmitriy Shulyak <dshul...@mirantis.com> wrote: > Hi folks, > I want to discuss cluster reconfiguration scenarios, i am aware of 2 such > bugs: > > - ceph-mon not installed on controllers if cluster initially was deployed > without ceph-osd > - config with rabbitmq hosts not updated on non-controlles nodes after > additional controllers is added to cluster  > > In both cases we need to track node state and change it accordingly to > some event > (additonal ceph-osd, additional controller added to cluster, etc..). > I think that it is generic scenario and our api should support such > modifications. > > To track state of node we need to introduce new state - something in lines > of "requires_update". > And extend deployment selection logic to include nodes with this state, if > deploy action will be invoked. > > What do you think about such feature? I would be grateful for any other > cases. > >  https://bugs.launchpad.net/fuel/+bug/1368445 > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev