[ovirt-users] Maintenance GUI vs CLI

[Yedidyah Bar David]

On Tue, Mar 14, 2017 at 2:31 PM, Marcin Kruk <askifyouneed at gmail.com> wrote:
> So if the maintenance mode from the GUI is necessary to upgrade host, how to
> launch it from the CLI on that host?

Generally speaking, it should be doable using the api/sdk.
I don't know the details. If you have many hosts, you might
want to try the upgrade manager:

http://www.ovirt.org/develop/release-management/features/engine/upgrademanager/

>
> 2017-03-14 11:30 GMT+01:00 Yedidyah Bar David <didi at redhat.com>:
>>
>> On Tue, Mar 14, 2017 at 12:12 PM, Marcin Kruk <askifyouneed at gmail.com>
>> wrote:
>> > What is the difference between:
>>
>> There are two different notions of host maintenance:
>>
>> 1. in the engine, meaning the engine will migrate away VMs from
>> this host, not start new ones on it, etc. This applies to all
>> hosts, not just hosted-engine ones
>>
>> 2. in ovirt-hosted-engine-ha, the high availability daemons.
>> Here it means similar things, but applies only to the hosted
>> engine vm, and is maintained in the HE shared storage (not in
>> the engine db).
>>
>> > host CLI command:  hosted-engine --vm-maintenance --mode=local
>>
>> This one does (2.).
>>
>> > and
>> > RHVEM gui click action:  Hosts -> <hostname> -> Maintenance?
>>
>> In the past, this did only (1.), but now it does both.
>>
>> See also:
>>
>>
>> https://www.ovirt.org/develop/release-management/features/engine/self-hosted-engine-maintenance-flows/
>> https://bugzilla.redhat.com/show_bug.cgi?id=1047649
>> https://bugzilla.redhat.com/show_bug.cgi?id=1277646
>>
>> Best,
>> --
>> Didi
>
>



-- 
Didi