Re: [openstack-dev] [TripleO] Strategy for recovering crashed nodes in the Overcloud?

2014-07-25 Thread Ladislav Smola
Hi, I believe you are looking for stack convergence in Heat. It's not fully implemented yet AFAIK. You can check it out here https://blueprints.launchpad.net/heat/+spec/convergence Hope it will help you. Ladislav On 07/23/2014 12:31 PM, Howley, Tom wrote: (Resending to properly start new

[openstack-dev] [TripleO] Strategy for recovering crashed nodes in the Overcloud?

2014-07-23 Thread Howley, Tom
(Resending to properly start new thread.) Hi, I'm running a HA overcloud configuration and as far as I'm aware, there is currently no mechanism in place for restarting failed nodes in the cluster. Originally, I had been wondering if we would use a corosync/pacemaker cluster across the

[openstack-dev] [TripleO] Strategy for recovering crashed nodes in the Overcloud?

2014-07-22 Thread Howley, Tom
Hi, I'm running a HA overcloud configuration and as far as I'm aware, there is currently no mechanism in place for restarting failed nodes in the cluster. Originally, I had been wondering if we would use a corosync/pacemaker cluster across the control plane with STONITH resources configured

Re: [openstack-dev] [TripleO] Strategy for recovering crashed nodes in the Overcloud?

2014-07-22 Thread Charles Crouch
- Original Message - Hi, I'm running a HA overcloud configuration and as far as I'm aware, there is currently no mechanism in place for restarting failed nodes in the cluster. Originally, I had been wondering if we would use a corosync/pacemaker cluster across the control plane