[ovirt-users] Update Self-Hosted-Engine - Right Way?

[Taste-Of-IT]

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/allinone/
> [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 at 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 at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users [1]
>  _______________________________________________
>  Users mailing list
>  Users at 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/allinone/
> [3] http://www.ovirt.org/documentation/how-to/hosted-engine/
> [4]
> http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/