an in the orchestration layer.
--
Stephen Turner
-Original 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 th
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, I think we should focus on documenting this change properly
so folks are aware they need to change their setup. I wrote some
documentation already that I'll port to 4.
I'm sorry to come late to this thread, but I only picked it up from Remi's blog
post [*] over the weekend.
I'm certainly not going to defend the way this change came in under the radar,
but speaking as a member of the XenServer development team, I wouldn't want to
go back to the old behaviour.
> > XenServer 6.0.2.!
> > Can somebody give 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: Die
et: 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
> to such a major change.
>
> When I put my "Opera
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 e
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 wrote:
> Thanks for starting this thread Remi.
>
> From my
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 failu
