I don't use XenServer maintenance mode until after CloudStack has put the Host
in maintenance mode.
When you initiate maintenance mode from the host rather than CloudStack the db
does not know where the VM's are and your UUID's get jacked.
CS is your brains not the hypervisor.
Maintenance in C
CloudStack should always do the migration of VM's not the Hypervisor.
That's not true. You can safely migrate outside of CloudStack as the power
report will tell CloudStack where the vms live and the db gets updated
accordingly. I do this a lot while patching and that works fine on 6.2 and 6.5.
No guys,as the article wrote, my first action was to put in Maintenance
Mode the Pool Master INSIDE CS; "It is vital that you upgrade the XenServer
Pool Master first before any of the Slaves. To do so you need to empty the
Pool Master of all CloudStack VMs, and you do this by putting the Host into
i don't know what do the maintenance mode in CS but if it put in maintenance
also the pool master this article is wrong!
Davide Pala
Infrastructure Specialist
Gesca srl
Via degli Olmetti, 18
00060 Formello (Roma)
Office: +39 06 9040661
Fax: +39 06 9040
E-mail: [email protected]
Web:
Hi all,
There is nothing better than looking at the source code.
After the VM migration (or restart for LCX ?!), when the host is put in
maintenance mode, for Xenserver it will remove a tag called “cloud”.
On Sat, Jan 2, 2016 at 7:38 PM, Davide Pala wrote:
> i don't know what do the maintenanc
So i dont know anything about cloud on xenserver and for this reason i think
the cloudstack dont put in maintenance xenserver pool master
Inviato dal mio dispositivo Samsung
Messaggio originale
Da: Rafael Weingärtner
Data: 02/01/2016 22:48 (GMT+01:00)
A: [email protected]
That is true it is not putting the host in maintenance. Not just the
master, but any XenServer host.
The question is, should it? If so, we should open a Jira ticket.
On Sat, Jan 2, 2016 at 9:18 PM, Davide Pala wrote:
> So i dont know anything about cloud on xenserver and for this reason i
> thi
No. The upgrade must be done with a cold reboot without the maintenance. XS
pool master mist be the master again when it boot
Inviato dal mio dispositivo Samsung
Messaggio originale
Da: Rafael Weingärtner
Data: 03/01/2016 00:25 (GMT+01:00)
A: [email protected]
Ogg
until we use "xe pool-designate-new-master", the master of the pool will
not change.
Unless, you have configured the HA features in your XenServer Pool/cluster,
the reboot of the master may trigger a change of master server.
Bottom line: today, the code does not change the master server of a
XenS
Hi Alessandro,
Without seeing the logs, or DB, it will be hard to diagnose the issue. I've
seen something similar in the past, where the XenServer host version isnt
getting updated in the DB, as part of the XS upgrade process. That caused
CloudStack to use the wrong hypervisor resource to try conne
10 matches
Mail list logo
