<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Gianluca,<div class=""><br class=""></div><div class="">I forgot to mention that you need to ensure that systemd knows that the new file exists. You should likely run `systemctl daemon-reload` after creating/modifying your custom systemd files. You can see that the After directive is combined from both files. Check it out by running `systemctl show vdsmd.service | grep After`</div><div class=""><br class=""></div><div class="">It makes sense to make further changes to ensure that NFS stops last, but I haven't looked into that yet.</div><div class="">:-)<br class=""><div class="">
<div id="signature" class=""><br class="">Cheers,<br class="">Gervais<br class=""><br class=""><br class=""></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Oct 3, 2016, at 7:22 AM, Gianluca Cecchi <<a href="mailto:gianluca.cecchi@gmail.com" class="">gianluca.cecchi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="webkit-block-placeholder"></div><p dir="ltr" class="">Il 28/Set/2016 21:09, "Gervais de Montbrun" <<a href="mailto:gervais@demontbrun.com" class="">gervais@demontbrun.com</a>> ha scritto:<br class="">
><br class="">
> Hi Gianluca,<br class="">
><br class="">
> Instead of editing the system's built in systemd configuration, you can do the following...<br class="">
><br class="">
> Create a file called /etc/systemd/system/ovirt-ha-broker.service<br class="">
><br class="">
>> # My custom ovirt-ha-broker.service config that ensures NFS starts before ovirt-ha-broker.service<br class="">
>> # thanks Gervais for this tip! :-)<br class="">
>><br class="">
>> .include /usr/lib/systemd/system/ovirt-ha-broker.service<br class="">
>><br class="">
>> [Unit]<br class="">
>> After=nfs-server.service<br class="">
><br class="">
><br class="">
> Then disable and enable ovirt-ha-broker.service (systemctl disable ovirt-ha-broker.service ; systemctl enable ovirt-ha-broker.service) and you should see that it is using your customized systemd unit definition. You can see that systemd is using your file by running systemctl status ovirt-ha-broker.service. You'll see something like "Loaded: loaded (/etc/systemd/system/ovirt-ha-broker.service;" in the output.<br class="">
><br class="">
> Your file will survive updates and therefore always wait for nfs to start prior to starting. You can do the same for your other customizations.<br class="">
><br class="">
> Cheers,<br class="">
> Gervais<br class="">
><br class="">
><br class="">
><br class="">
>> On Sep 28, 2016, at 1:31 PM, Gianluca Cecchi <<a href="mailto:gianluca.cecchi@gmail.com" class="">gianluca.cecchi@gmail.com</a>> wrote:<br class="">
>><br class="">
>> On Sun, Sep 4, 2016 at 10:54 AM, Yedidyah Bar David <<a href="mailto:didi@redhat.com" class="">didi@redhat.com</a>> wrote:<br class="">
>>><br class="">
>>> On Sat, Sep 3, 2016 at 1:18 PM, Gianluca Cecchi<br class="">
>>> <<a href="mailto:gianluca.cecchi@gmail.com" class="">gianluca.cecchi@gmail.com</a>> wrote:<br class="">
>>> > Hello,<br class="">
>>> > how do the two modes apply in case of single host?<br class="">
>>> > During an upgrade phase, after having upgraded the self hosted engine and<br class="">
>>> > leaving global maintenance and having checked all is ok, what is the correct<br class="">
>>> > mode then to put host if I want finally to update it too?<br class="">
>>><br class="">
>>> The docs say to put hosts to maintenance from the engine before upgrading them.<br class="">
>>><br class="">
>>> This is (also) so that VMs on them are migrated away to other hosts.<br class="">
>>><br class="">
>>> With a single host, you have no other hosts to migrate VMs to.<br class="">
>>><br class="">
>>> So you should do something like this:<br class="">
>>><br class="">
>>> 1. Set global maintenance (because you are going to take down the<br class="">
>>> engine and its vm)<br class="">
>>> 2. Shutdown all other VMs<br class="">
>>> 3. Shutdown engine vm from itself<br class="">
>>> At this point, you should be able to simply stop HA services. But it<br class="">
>>> might be cleaner to first set local maintenance. Not sure but perhaps<br class="">
>>> this might be required for vdsm. So:<br class="">
>>> 4. Set local maintenance<br class="">
>>> 5. Stop HA services. If setting local maintenance didn't work, perhaps<br class="">
>>> better stop also vdsm services. This stop should obviously happen<br class="">
>>> automatically by yum/rpm, but perhaps better do this manually to see<br class="">
>>> that it worked.<br class="">
>>> 6. yum (or dnf) update stuff.<br class="">
>>> 7. Start HA services<br class="">
>>> 8. Check status. I think you'll see that both local and global maint<br class="">
>>> are still set.<br class="">
>>> 9. Set maintenance to none<br class="">
>>> 10. Check status again - I think that after some time HA will decide<br class="">
>>> to start engine vm and should succeed.<br class="">
>>> 11. Start all other VMs.<br class="">
>>><br class="">
>>> Didn't try this myself.<br class="">
>>><br class="">
>>> Best,<br class="">
>>> --<br class="">
>>> Didi<br class="">
>><br class="">
>><br class="">
>> Hello Didi,<br class="">
>> I would like to leverage the update I have to do on 2 small different lab environments to crosscheck the steps suggested.<br class="">
>> They are both single host environments with self hosted engine.<br class="">
>> One is 4.0.2 and the other is 4.0.3. Both on CentoS 7.2<br class="">
>> I plan to migrate to the just released 4.0.4<br class="">
>><br class="">
>> One note: in both environments the storage is NFS and is provided by the host itself, so a corner case (for all hosted_storage domain, main data domain and iso storage domain).<br class="">
>> I customized the init scripts, basically for start phase of the server and to keep in count of the NFS service, but probably something has to be done for stop too?<br class="">
>><br class="">
>> 1) In /usr/lib/systemd/system/ovirt-ha-broker.service<br class="">
>><br class="">
>> added in section [Unit]<br class="">
>><br class="">
>> After=nfs-server.service<br class="">
>><br class="">
>> The file is overwritten at update so one has to keep in mind this<br class="">
>><br class="">
>> 2) also in vdsmd.service changed <br class="">
>> from:<br class="">
>> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \<br class="">
>> supervdsmd.service sanlock.service vdsm-network.service<br class="">
>><br class="">
>> to:<br class="">
>> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \<br class="">
>> supervdsmd.service sanlock.service vdsm-network.service \<br class="">
>> nfs-server.service<br class="">
>><br class="">
>> Do you think any order setup I have to put in place related to NFS service and oVirt services stop?<br class="">
>><br class="">
>> _______________________________________________<br class="">
>> Users mailing list<br class="">
>> <a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">
>> <a href="http://lists.ovirt.org/mailman/listinfo/users" class="">http://lists.ovirt.org/mailman/listinfo/users</a><br class="">
><br class="">
></p><p dir="ltr" class="">Nice! I'm going to try and see.<br class="">
Any particular dependency I should add for shutdown order due to the fact that my host is also the NFS server providing data stores?<br class="">
Do I need to set up nfs stop only after a particular ovirt related service?<br class="">
Thanks,<br class="">
Gianluca<br class="">
</p>
</div></blockquote></div><br class=""></div></div>
</body></html>