[openstack-dev] [fuel] What to do when a controller runs out of space
enikanorov at mirantis.com
Mon Oct 5 09:22:16 UTC 2015
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.
5 окт. 2015 г. 12:01 пользователь "Sergii Golovatiuk" <
sgolovatiuk at 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 . However, I would like to remove
> custom scripts as much as possible to leave only upstart/systemd classes
>  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.
>  https://www.youtube.com/watch?v=yq5nYPKxBCo
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev