: [DISCUSS] XenServer and HA: the way forward
Hi all,
Since CloudStack 4.4 the implementation of HA in CloudStack was changed to
use the XenHA feature of XenServer. As of 4.4, it is expected to have XenHA
enabled for the pool (not for the VMs!) and so XenServer will be the one to
elect a new
Message-
From: Remi Bergsma [mailto:r...@remi.nl]
Sent: 28 May 2015 12:53
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] XenServer and HA: the way forward
Hi Stephen,
Thanks for getting in touch!
First of all, good to hear we agree that this change wasn't done in a nice way.
For now
@cloudstack.apache.org
Subject: [DISCUSS] XenServer and HA: the way forward
Hi all,
Since CloudStack 4.4 the implementation of HA in CloudStack was changed to use
the XenHA feature of XenServer. As of 4.4, it is expected to have XenHA enabled
for the pool (not for the VMs!) and so XenServer
: [DISCUSS] XenServer and HA: the way forward
Hi all,
Thanks for pointing me to the proposal, Koushik. Too bad no one responded
to such a major change.
When I put my Operations hat on, I see several issues. First of all,
there was no mention of this change in the release notes. Not as a new
feature
-Ursprüngliche Nachricht-
Von: Remi Bergsma [mailto:r...@remi.nl]
Gesendet: Dienstag, 5. Mai 2015 12:36
An: dev@cloudstack.apache.org
Betreff: Re: [DISCUSS] XenServer and HA: the way forward
Hi all,
Thanks for pointing me to the proposal, Koushik. Too bad no one responded
The below is the proposal for switching to XenServer HA.
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201403.mbox/%3c83f77ff1bd50194ab65afa5479d082a71e4...@sjcpex01cl02.citrite.net%3E
On 04-May-2015, at 9:03 PM, Tim Mackey tmac...@gmail.com wrote:
Thanks for starting this thread
2015 08:12
An: dev@cloudstack.apache.org
Betreff: Re: [DISCUSS] XenServer and HA: the way forward
The below is the proposal for switching to XenServer HA.
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201403.mbox/%3c83f77ff1bd50194ab65afa5479d082a71e4...@sjcpex01cl02.citrite.net%3E
Hi all,
Thanks for pointing me to the proposal, Koushik. Too bad no one responded
to such a major change.
When I put my Operations hat on, I see several issues. First of all,
there was no mention of this change in the release notes. Not as a new
feature, nor as a bug that was fixed. How do we
more information on this?
Mit freundlichen Grüßen / With kind regards,
Swen Brüseke
-Ursprüngliche Nachricht-
Von: Remi Bergsma [mailto:r...@remi.nl]
Gesendet: Dienstag, 5. Mai 2015 12:36
An: dev@cloudstack.apache.org
Betreff: Re: [DISCUSS] XenServer and HA: the way forward
Hi all
Hi all,
Since CloudStack 4.4 the implementation of HA in CloudStack was changed to
use the XenHA feature of XenServer. As of 4.4, it is expected to have XenHA
enabled for the pool (not for the VMs!) and so XenServer will be the one to
elect a new pool master, whereas CloudStack did it before.
Thanks for starting this thread Remi.
From my perspective the pros of simply enabling XenServer HA are:
- automatic election of pool master in the event of hardware failure
- automatic fencing of a host in the event of dom0 corruption
- automatic fencing of a host in the event of heartbeat
11 matches
Mail list logo
