Re: [ovirt-users] Update Self-Hosted-Engine - Right Way?
Hello Simon, i am new with oVirt, but are you sure, that this is the way for the self-hosted-engine? Because i have no commands with hosted-***. As far as i understand the engine runs in self-hosted-engine on same host and therefore there is no way to enter the vm with engine and set it to maintenance mode.?! Regards Taste Am 2016-03-04 10:24, schrieb Simone Tiraboschi:
On Fri, Mar 4, 2016 at 9:57 AM, Taste-Of-IT <kontakt@taste-of-it.de> wrote:
Hello,
i want to Update my oVirt as Self-Hosted-Engine on CentOS 7. The way i whould do is as follow and i want to know if this is the right recommended way.
Please follow this: http://www.ovirt.org/documentation/how-to/hosted-engine/#Upgrade_Hosted_Engi... [2]
Ensure to take care to put hosted-engine in global maintenance mode before upgrading the engine VM otherwise the HA agent could reboot it (since it detects that the engine is not responsive) in the middle of the upgrade with potentially really bad results.
1. shutdown all virtual machines (can i do this from GUI, or should it better be done inside the VMs?) 2. yum update "ovirt-engine-setup*" 3. yum update 4. engine-setup 5. follow questions and hope all is updated correct...
Is that all or should i do some other stepps before or between this?
thx Taste _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users [1]
Links: ------ [1] http://lists.ovirt.org/mailman/listinfo/users [2] http://www.ovirt.org/documentation/how-to/hosted-engine/#Upgrade_Hosted_Engi...
Hello Simon,
i am new with oVirt, but are you sure, that this is the way for the self-hosted-engine? Because i have no commands with hosted-***. As far as i understand the engine runs in self-hosted-engine on same host and therefore there is no way to enter the vm with engine and set it to maintenance mode.?! If you have only one host and it sounds like it then upgrading is a bit different. hosted-engine command is available on the HOST. Just shutdown all VM's, either way will work if you have ovirt-guest-agent running inside the VM's
On 4-3-2016 10:44, Taste-Of-IT wrote: place hosted-engine in maintenance mode (hosted-engine --set-maintenance --mode=global) ssh, use vnc, into engine yum upgrade if you want to upgrade the system too, else running engine-setup will update only ovirt components. shutdown the engine. yum upgrade your host, reboot your host, once back up, disable maintenance mode (replace global with none) ha-agent and ha-broker will start the engine for you. Joop
What I just tested on a lab environment of mine is this below Starting situation is single host with CentOS 7.2 and SH Engine on CentOS 7.2 deployed from appliance Version is 3.6.2. Both are updated up to 26/01/16 nad there are 3 VMs running - shutdown Vms - move host to global maintenance On host: hosted-engine --set-maintenance --mode=global - upgrade engine VM both from 3.6.2 to 3.6.3 and update its CentOS packages with: On SH Engine: yum update "ovirt-engine-setup*" yum update engine-setup - reboot engine VM and verify correct access to web admin gui You can verify its console status at this time with something like this run on host side: hosted-engine --add-console-password --password=mypwd /bin/remote-viewer vnc://localhost:5900 & NOTE: it seems that nc remote-viewer command doesn't survive the reboot... you have to reconnect - verify oVirt version is right and all is ok, eg starting a VM and accessing its console; then shutdown again the VM - move the host to local maintenance On host: hosted-engine --set-maintenance --mode=local - update Host On engine VM: shutdown -h now NOTE: I think this step about engine VM shouldn't be necessary in case of multi host environment. Simply you should go host by host with these steps up to completing upgrade of your hosts. On host: yum update reboot - Exit maintenance On host: hosted-engine --set-maintenance --mode=none - Verify engine VM starts and access to web admin gui is ok - Start your VMs and verify all is ok I have just done this and all is ok: all storage domains (ISO, NFS and hosted_storage) are up and able to start and manage VMs The only "problem" I have seeing is that in Hosts tab, the host is still marked for some minutes with a box and tip says "Update available". But then it goes away (no event regarding this on events pane... just wait).. HIH, Gianluca On Fri, Mar 4, 2016 at 11:19 AM, Joop <jvdwege@xs4all.nl> wrote:
Hello Simon,
i am new with oVirt, but are you sure, that this is the way for the self-hosted-engine? Because i have no commands with hosted-***. As far as i understand the engine runs in self-hosted-engine on same host and therefore there is no way to enter the vm with engine and set it to maintenance mode.?! If you have only one host and it sounds like it then upgrading is a bit different. hosted-engine command is available on the HOST. Just shutdown all VM's, either way will work if you have ovirt-guest-agent running inside the VM's
On 4-3-2016 10:44, Taste-Of-IT wrote: place hosted-engine in maintenance mode (hosted-engine --set-maintenance --mode=global) ssh, use vnc, into engine yum upgrade if you want to upgrade the system too, else running engine-setup will update only ovirt components. shutdown the engine. yum upgrade your host, reboot your host, once back up, disable maintenance mode (replace global with none) ha-agent and ha-broker will start the engine for you.
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hello, sorry that i repeat it, but i dont have the command hosted-engine... Is it possible that we talk about different kind of installations? Please check yours because i only have the self-hosted engine installed. Thx Am 2016-03-04 12:08, schrieb Gianluca Cecchi:
What I just tested on a lab environment of mine is this below
Starting situation is single host with CentOS 7.2 and SH Engine on CentOS 7.2 deployed from appliance Version is 3.6.2. Both are updated up to 26/01/16 nad there are 3 VMs running
- shutdown Vms
- move host to global maintenance On host: hosted-engine --set-maintenance --mode=global
- upgrade engine VM both from 3.6.2 to 3.6.3 and update its CentOS packages with: On SH Engine: yum update "ovirt-engine-setup*" yum update engine-setup
- reboot engine VM and verify correct access to web admin gui You can verify its console status at this time with something like this run on host side: hosted-engine --add-console-password --password=mypwd /bin/remote-viewer vnc://localhost:5900 &
NOTE: it seems that nc remote-viewer command doesn't survive the reboot... you have to reconnect
- verify oVirt version is right and all is ok, eg starting a VM and accessing its console; then shutdown again the VM
- move the host to local maintenance On host: hosted-engine --set-maintenance --mode=local
- update Host On engine VM: shutdown -h now NOTE: I think this step about engine VM shouldn't be necessary in case of multi host environment. Simply you should go host by host with these steps up to completing upgrade of your hosts.
On host: yum update reboot
- Exit maintenance On host: hosted-engine --set-maintenance --mode=none
- Verify engine VM starts and access to web admin gui is ok
- Start your VMs and verify all is ok
I have just done this and all is ok: all storage domains (ISO, NFS and hosted_storage) are up and able to start and manage VMs
The only "problem" I have seeing is that in Hosts tab, the host is still marked for some minutes with a box and tip says "Update available". But then it goes away (no event regarding this on events pane... just wait)..
HIH, Gianluca
On Fri, Mar 4, 2016 at 11:19 AM, Joop <jvdwege@xs4all.nl> wrote:
Hello Simon,
i am new with oVirt, but are you sure, that this is the way for
self-hosted-engine? Because i have no commands with hosted-***. As far as i understand the engine runs in self-hosted-engine on same host and therefore there is no way to enter the vm with engine and set it to maintenance mode.?! If you have only one host and it sounds like it then upgrading is a bit different. hosted-engine command is available on the HOST. Just shutdown all VM's, either way will work if you have ovirt-guest-agent running inside the VM's
On 4-3-2016 10:44, Taste-Of-IT wrote: the place hosted-engine in maintenance mode (hosted-engine --set-maintenance --mode=global) ssh, use vnc, into engine yum upgrade if you want to upgrade the system too, else running engine-setup will update only ovirt components. shutdown the engine. yum upgrade your host, reboot your host, once back up, disable maintenance mode (replace global with none) ha-agent and ha-broker will start the engine for you.
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users [1]
Links: ------ [1] http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 4-3-2016 23:48, Taste-Of-IT wrote:
Hello, sorry that i repeat it, but i dont have the command hosted-engine... Is it possible that we talk about different kind of installations? Please check yours because i only have the self-hosted engine installed. Are you talking about the all-in-one setup?
Please list the ovirt packages on both the VM and the host. (rp -aq | grep ovirt | sort) Joop
Hello Joop, yes the correct wording is all-in-one and thats why i cant enter this command on the vm for the host inside the vm but on the engine which is the host too :), but the command rp is unknown on CentOS 7.2 as min install. Am 2016-03-06 21:19, schrieb Joop:
On 4-3-2016 23:48, Taste-Of-IT wrote:
Hello, sorry that i repeat it, but i dont have the command hosted-engine... Is it possible that we talk about different kind of installations? Please check yours because i only have the self-hosted engine installed. Are you talking about the all-in-one setup?
Please list the ovirt packages on both the VM and the host. (rp -aq | grep ovirt | sort)
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Ah ok. So you previously installed an All-in-One setup following something like these instructions: http://www.ovirt.org/develop/release-management/features/integration/allinon... But this feature is deprecated in 3.6 and it should be dropped in 4.0 And you want to migrate this single host installation to an hosted-engine one, that for a clean new install should be done with something like this: http://www.ovirt.org/documentation/how-to/hosted-engine/ In your case you have to migrate and follow something similar to this: http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine... but I think it is not so simple if you have at the end only one host to use.... You could export your VMs and the re-import them after migration and scratch of your hypevisor. What Joop suggested is the rpm command (adding a final "m" to rp) But I think that actually you are on All-in-one where the engine mgmt part is installed on the same machine that acts as the hypervisor. Try to read the migration doc I pointed out and see if you can adapt it to your environment (I don't know which 3.x version it is...) HIH, Gianluca On Sun, Mar 6, 2016 at 9:53 PM, Taste-Of-IT <kontakt@taste-of-it.de> wrote:
Hello Joop,
yes the correct wording is all-in-one and thats why i cant enter this command on the vm for the host inside the vm but on the engine which is the host too :), but the command rp is unknown on CentOS 7.2 as min install.
Am 2016-03-06 21:19, schrieb Joop:
On 4-3-2016 23:48, Taste-Of-IT wrote:
Hello, sorry that i repeat it, but i dont have the command hosted-engine... Is it possible that we talk about different kind of installations? Please check yours because i only have the self-hosted engine installed.
Are you talking about the all-in-one setup?
Please list the ovirt packages on both the VM and the host. (rp -aq | grep ovirt | sort)
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hello Gianluca, yes i installed the All-in-One Solution. I know the fact, that it will deprecated in Version 4.0, but my company is so small that it actually would not be profitable to use min 3 Server (2 ovirt and 1 for storage). i also have to migrate from another solution which doesnt support the free version realy good. So oVirt all-in-one seems to me a good option, actually, and i hope while lots of people use that, that the developer will have over version 4.0 a similar solution. as far as i know the support until 4.0 is still there for all-in-one and the date for release not public. so it could be at end of the year or later ... maybe ... Ok back to the topic. No i want to migrate, i simply want to Update from 3.6.2 to 3.6.3. Actually i do these: - in WebGUI Admin Portal i set the Host to Maintenance Mode - # yum check-update - # yum update - # engine-setup - run through config Options - in WebGUI run Upgrade for the Host - after successfull Upgrade i set the Host back to active These Steps seems in my test to work, but is that the right way for All-in-One ? Many thx Taste Am 2016-03-06 22:16, schrieb Gianluca Cecchi:
Ah ok. So you previously installed an All-in-One setup following something like these instructions: http://www.ovirt.org/develop/release-management/features/integration/allinon... [2]
But this feature is deprecated in 3.6 and it should be dropped in 4.0
And you want to migrate this single host installation to an hosted-engine one, that for a clean new install should be done with something like this: http://www.ovirt.org/documentation/how-to/hosted-engine/ [3]
In your case you have to migrate and follow something similar to this: http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine... [4]
but I think it is not so simple if you have at the end only one host to use.... You could export your VMs and the re-import them after migration and scratch of your hypevisor.
What Joop suggested is the rpm command (adding a final "m" to rp)
But I think that actually you are on All-in-one where the engine mgmt part is installed on the same machine that acts as the hypervisor. Try to read the migration doc I pointed out and see if you can adapt it to your environment (I don't know which 3.x version it is...)
HIH, Gianluca
On Sun, Mar 6, 2016 at 9:53 PM, Taste-Of-IT <kontakt@taste-of-it.de> wrote:
Hello Joop,
yes the correct wording is all-in-one and thats why i cant enter this command on the vm for the host inside the vm but on the engine which is the host too :), but the command rp is unknown on CentOS 7.2 as min install.
Am 2016-03-06 21:19, schrieb Joop: On 4-3-2016 23:48, Taste-Of-IT wrote: Hello, sorry that i repeat it, but i dont have the command hosted-engine... Is it possible that we talk about different kind of installations? Please check yours because i only have the self-hosted engine installed. Are you talking about the all-in-one setup?
Please list the ovirt packages on both the VM and the host. (rp -aq | grep ovirt | sort)
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users [1]
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users [1]
Links: ------ [1] http://lists.ovirt.org/mailman/listinfo/users [2] http://www.ovirt.org/develop/release-management/features/integration/allinon... [3] http://www.ovirt.org/documentation/how-to/hosted-engine/ [4] http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine...
participants (3)
-
Gianluca Cecchi -
Joop -
Taste-Of-IT