No pacemaker for os services, please. We'll be moving out neutron agents from pacemaker control in 8.0, other os services don't need it too.
E. 5 окт. 2015 г. 12:01 пользователь "Sergii Golovatiuk" < sgolovat...@mirantis.com> написал: > Good morning gentlemen! > > Alex raised very good question. Thank you very much! We have 3 init > systems right now. Some services use SystemV, some services use upstart, > some services are under pacemaker. Personally, I would like to have > pacemaker as pid 1 to replace init [1]. However, I would like to remove > custom scripts as much as possible to leave only upstart/systemd classes > [2] only. That move will give fantastic flexibility to operators to control > their services. > > Concerning Haproxy checker, I think it should be done in different way. If > pacemaker/corosyunc has an issue the node should be fenced. > > Also, I would like to have pacemaker remote to control services on compute > nodes. It's very good replacement for monit. > > [1] https://www.youtube.com/watch?v=yq5nYPKxBCo > [2] > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-supported.html > > > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
