9:20 a.m.
Hi,
We need to update/reboot the NFS server on wich the hosted engine is
installed. This server also hosts a couple of extra storage domains
(ISO, Export and a iScsi domain). I'm wondering if this procedure is
complete for an oVirt 4.0 installation :
1-set the environment to global maintenance
2-set the extra domains to maintenance mode
3-shutdown the hosted engine
4-update/reboot the storage server
5-reboot the hosted engine
6-reactivate extra domains
7-disable global maintenance mode
I'm wondering what's happening after step 4 and how ovirt will react
when the NFS storage disapear and come back.
11:13 a.m.
On Mon, Jan 23, 2017 at 4:20 PM, Claude Duropcher <
claude.durocher(a)cptaq.gouv.qc.ca> wrote:
Hi,
We need to update/reboot the NFS server on wich the hosted engine is
installed. This server also hosts a couple of extra storage domains (ISO,
Export and a iScsi domain). I'm wondering if this procedure is complete for
an oVirt 4.0 installation :
1-set the environment to global maintenance
2-set the extra domains to maintenance mode
3-shutdown the hosted engine
4-update/reboot the storage server
5-reboot the hosted engine
6-reactivate extra domains
7-disable global maintenance mode
I'm wondering what's happening after step 4 and how ovirt will react when
the NFS storage disapear and come back.
ovirt-ha-agent will try to reconnect the shared storage if hosted-engine
for all the time; depending on different factors, sanlock will fail
updating the hosted-engine lease ans this can bring the watchdog to reboot
the host.
Setting also local maintenance mode on the involved hosts is a good idea.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:51 a.m.
This is a multi-part message in MIME format.
--------------A983AC3C9C3F782E21725053
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Simone, thanks for replying,
According to the documentation, global mode seems to be a superset of=20
local mode. Does setting to local mode maintenance on all hosts in the=20
cluster really bring any benefits?
*
|global| - All high-availability agents in the cluster are disabled
from monitoring the state of the engine virtual machine. The global
maintenance mode must be applied for any setup or upgrade operations
that require the engine to be stopped, such as upgrading to a later
version of oVirt.
*
|local| - The high-availability agent on the host issuing the
command is disabled from monitoring the state of the engine virtual
machine. The host is exempt from hosting the engine virtual machine
while in local maintenance mode; if hosting the engine virtual
machine when placed into this mode, the engine will be migrated to
another host, provided there is a suitable contender. The local
maintenance mode is recommended when applying system changes or
updates to the host.
Le 2017-01-23 =C3=A0 12:13, Simone Tiraboschi a =C3=A9crit :
On Mon, Jan 23, 2017 at 4:20 PM, Claude Duropcher=20
<claude.durocher(a)cptaq.gouv.qc.ca=20
<mailto:claude.durocher@cptaq.gouv.qc.ca>> wrote:
Hi,
We need to update/reboot the NFS server on wich the hosted engine
is installed. This server also hosts a couple of extra storage
domains (ISO, Export and a iScsi domain). I'm wondering if this
procedure is complete for an oVirt 4.0 installation :
1-set the environment to global maintenance
2-set the extra domains to maintenance mode
3-shutdown the hosted engine
4-update/reboot the storage server
5-reboot the hosted engine
6-reactivate extra domains
7-disable global maintenance mode
I'm wondering what's happening after step 4 and how ovirt will
react when the NFS storage disapear and come back.
ovirt-ha-agent will try to reconnect the shared storage if=20
hosted-engine for all the time; depending on different factors,=20
sanlock will fail updating the hosted-engine lease ans this can bring=20
the watchdog to reboot the host.
Setting also local maintenance mode on the involved hosts is a good ide=
a.
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
--------------A983AC3C9C3F782E21725053
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dutf-8"
http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<p>Simone, thanks for replying,<br>
</p>
<p>According to the documentation, global mode seems to be a
superset of local mode. Does setting to local mode maintenance on
all hosts in the cluster really bring any benefits?<br>
</p>
<ul>
<li>
<p><code>global</code> - All high-availability agents in the
cluster are disabled from monitoring the state of the engine
virtual machine. The global maintenance mode must be applied
for any setup or upgrade operations that require the engine to
be stopped, such as upgrading to a later version of oVirt.</p>
</li>
<li>
<p><code>local</code> - The high-availability agent on the host
issuing the command is disabled from monitoring the state of
the engine virtual machine. The host is exempt from hosting
the engine virtual machine while in local maintenance mode; if
hosting the engine virtual machine when placed into this mode,
the engine will be migrated to another host, provided there is
a suitable contender. The local maintenance mode is
recommended when applying system changes or updates to the
host.</p>
</li>
</ul>
<div class=3D"moz-cite-prefix">Le 2017-01-23 =C3=A0 12:13, Simone
Tiraboschi a =C3=A9crit=C2=A0:<br>
</div>
<blockquote
cite=3D"mid:CAN8-ONr-24f1dp9UzSc6+oDmfdj2Fm+o7vdCM7ZMjagXszQk3w@mail.gmai=
l.com"
type=3D"cite">
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Mon, Jan 23, 2017 at 4:20 PM,
Claude Duropcher <span dir=3D"ltr"><<a
moz-do-not-send=3D"true"
href=3D"mailto:claude.durocher@cptaq.gouv.qc.ca"
target=3D"_blank">claude.durocher(a)cptaq.gouv.qc.ca</a>&gt=
;</span>
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
We need to update/reboot the NFS server on wich the hosted
engine is installed. This server also hosts a couple of
extra storage domains (ISO, Export and a iScsi domain).
I'm wondering if this procedure is complete for an oVirt
4.0 installation :<br>
<br>
1-set the environment to global maintenance<br>
<br>
2-set the extra domains to maintenance mode<br>
<br>
3-shutdown the hosted engine<br>
<br>
4-update/reboot the storage server<br>
<br>
5-reboot the hosted engine<br>
<br>
6-reactivate extra domains<br>
<br>
7-disable global maintenance mode<br>
<br>
I'm wondering what's happening after step 4 and how ovirt
will react when the NFS storage disapear and come back.<br>
<br>
</blockquote>
<div><br>
</div>
<div>ovirt-ha-agent will try to reconnect the shared storage
if hosted-engine for all the time; depending on different
factors, sanlock will fail updating the hosted-engine
lease ans this can bring the watchdog to reboot the host.</=
div>
<div>Setting also local maintenance mode on the involved
hosts is a good idea.</div>
<div><br>
</div>
<div>=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<wbr>_________________<br>
Users mailing list<br>
<a moz-do-not-send=3D"true"
href=3D"mailto:Users@ovirt.org"
target=3D"_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send=3D"true"
href=3D"http://lists.ovirt.org/mailman/listinfo/users"
rel=3D"noreferrer"
target=3D"_blank">http://lists.ovirt.o=
rg/mailman<wbr>/listinfo/users</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------A983AC3C9C3F782E21725053--
2:32 a.m.
On Mon, Jan 23, 2017 at 6:51 PM, Claude Duropcher <
claude.durocher(a)cptaq.gouv.qc.ca> wrote:
Simone, thanks for replying,
According to the documentation, global mode seems to be a superset of
local mode. Does setting to local mode maintenance on all hosts in the
cluster really bring any benefits?
No, not really: they are different and global is not superset of local.
global maintenance mode is needed if you need to do maintenance on the
engine VM, no host will restart the engine VM. local maintenance mode is if
you need to do maintenance or upgrade a single host.
-
global - All high-availability agents in the cluster are disabled from
monitoring the state of the engine virtual machine. The global maintenance
mode must be applied for any setup or upgrade operations that require the
engine to be stopped, such as upgrading to a later version of oVirt.
-
local - The high-availability agent on the host issuing the command is
disabled from monitoring the state of the engine virtual machine. The host
is exempt from hosting the engine virtual machine while in local
maintenance mode; if hosting the engine virtual machine when placed into
this mode, the engine will be migrated to another host, provided there is a
suitable contender. The local maintenance mode is recommended when applying
system changes or updates to the host.
Le 2017-01-23 à 12:13, Simone Tiraboschi a écrit :
On Mon, Jan 23, 2017 at 4:20 PM, Claude Duropcher <
claude.durocher(a)cptaq.gouv.qc.ca> wrote:
> Hi,
>
> We need to update/reboot the NFS server on wich the hosted engine is
> installed. This server also hosts a couple of extra storage domains (ISO,
> Export and a iScsi domain). I'm wondering if this procedure is complete for
> an oVirt 4.0 installation :
>
> 1-set the environment to global maintenance
>
> 2-set the extra domains to maintenance mode
>
> 3-shutdown the hosted engine
>
> 4-update/reboot the storage server
>
> 5-reboot the hosted engine
>
> 6-reactivate extra domains
>
> 7-disable global maintenance mode
>
> I'm wondering what's happening after step 4 and how ovirt will react when
> the NFS storage disapear and come back.
>
>
ovirt-ha-agent will try to reconnect the shared storage if hosted-engine
for all the time; depending on different factors, sanlock will fail
updating the hosted-engine lease ans this can bring the watchdog to reboot
the host.
Setting also local maintenance mode on the involved hosts is a good idea.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
2889
days inactive
2890
days old
3 comments
2 participants
participants (2)
-
Claude Duropcher -
Simone Tiraboschi