8:42 p.m.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B23BF82AUSP01DAG0201_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
greetings,
we are talking about possibly upgrading our cisco gear tonight, and this wi=
ll affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest VLA=
Ns are going thru, ad then afterwards rebooting the switch that all ovirtmg=
mt connections are in? how will the ovirt environment behave with loss of =
network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or stories =
of similar experiences would be appreciated.
thanks,
jonathan
________________________________
This is a PRIVATE message. If you are not the intended recipient, please de=
lete without copying and kindly advise us by e-mail of the mistake in deliv=
ery. NOTE: Regardless of content, this e-mail shall not operate to bind SKO=
POS to any order or other contract unless pursuant to explicit written agre=
ement or government initiative expressly permitting the use of e-mail for s=
uch purpose.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B23BF82AUSP01DAG0201_
Content-Type: text/html; charset="us-ascii"
Content-ID: <DDEF291004EAE1438F023D0301605A8E(a)collaborationhost.net Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
</head <body
style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif" <div>greetings,</div <div><br
</div <div>we are talking about
possibly upgrading our cisco gear tonight, and th=
is will affect our ovirt environment.</div
<div><br </div <div>what can i expect if i were to reboot first the
switch that all VMgues=
t VLANs are going thru, ad then afterwards rebooting the switch that all ov=
irtmgmt connections are in? how will the ovirt environment behave wit=
h loss of network connectivity for a
couple minutes?</div <div><br </div
<div>the iscsi network is not going to be affected. any information
o=
r stories of similar experiences would be appreciated.</div <div><br
</div <div>thanks,</div <div>jonathan</div
<br <br
<hr <font color=3D"Gray"
face=3D"Arial" size=3D"1">This is a PRIVATE message. I=
f you are not the intended recipient, please delete without copying and kin=
dly advise us by e-mail of the mistake in delivery. NOTE: Regardless of con=
tent, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit wri=
tten agreement or government initiative expressly permitting the use of e-m=
ail for such purpose.</font </body </html
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B23BF82AUSP01DAG0201_--
12:04 p.m.
Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
greetings,
we are talking about possibly upgrading our cisco gear tonight, and this
will affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest
VLANs are going thru, ad then afterwards rebooting the switch that all
ovirtmgmt connections are in? how will the ovirt environment behave
with loss of network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or
stories of similar experiences would be appreciated.
thanks,
jonathan
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2:39 p.m.
This is a multi-part message in MIME format.
--------------020402080306010409060609
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From experience, I would shutdown the ovirt engine before you do any
work related to networking. The VMs will keep running w/o the engine
available, you're simply unable to add/remove/failover VMs, etc. The
VDSM running on the host will be unable to get instructions to "kill"
any VMs as the engine is already "down" :) ...
hope it helps!
alex
On 03/24/2013 10:04 AM, Lior Vernia wrote:
Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
> greetings,
>
> we are talking about possibly upgrading our cisco gear tonight, and this
> will affect our ovirt environment.
>
> what can i expect if i were to reboot first the switch that all VMguest
> VLANs are going thru, ad then afterwards rebooting the switch that all
> ovirtmgmt connections are in? how will the ovirt environment behave
> with loss of network connectivity for a couple minutes?
>
> the iscsi network is not going to be affected. any information or
> stories of similar experiences would be appreciated.
>
> thanks,
> jonathan
>
>
> ------------------------------------------------------------------------
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind SKOPOS to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use
> of e-mail for such purpose.
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------020402080306010409060609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Tahoma">From experience, I
would
shutdown the ovirt engine before you do any work related to
networking. The VMs will keep running w/o the engine available,
you're simply unable to add/remove/failover VMs, etc. The VDSM
running on the host will be unable to get instructions to "kill"
any VMs as the engine is already "down" :) ... <br>
<br>
hope it helps!<br>
alex<br>
<br>
<br>
<br>
</font></font><br>
On 03/24/2013 10:04 AM, Lior Vernia wrote:
<blockquote cite="mid:514ECFC4.4010600@redhat.com"
type="cite">
<pre wrap="">Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
</pre>
<blockquote type="cite">
<pre wrap="">greetings,
we are talking about possibly upgrading our cisco gear tonight, and this
will affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest
VLANs are going thru, ad then afterwards rebooting the switch that all
ovirtmgmt connections are in? how will the ovirt environment behave
with loss of network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or
stories of similar experiences would be appreciated.
thanks,
jonathan
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
</body>
</html>
--------------020402080306010409060609--
3:12 p.m.
+1, better solution than mine (safer, simpler), thank you Alex. Do still
keep in mind the possible trouble with thin provisioning.
On 24/03/13 14:39, Alex Leonhardt wrote:
From experience, I would shutdown the ovirt engine before you do any
work related to networking. The VMs will keep running w/o the engine
available, you're simply unable to add/remove/failover VMs, etc. The
VDSM running on the host will be unable to get instructions to "kill"
any VMs as the engine is already "down" :) ...
hope it helps!
alex
On 03/24/2013 10:04 AM, Lior Vernia wrote:
> Hello Jonathan,
>
> First of all let me apologize for not being more responsive, seems like
> you got the worse end of time difference.
>
> Now, in case the question is still relevant:
>
> 1. Rebooting the first switch won't cause any damage. The VMs will lose
> connectivity on the VLANs, but they should still be manageable through
> oVirt and run normally on their hosts.
>
> 2. Rebooting the second one could prove more troublesome. Firstly, as a
> preemptive measure I would advise that you not have any VMs running on
> your host marked as SPM at the moment of reboot, if possible - there's
> risk that VMs running on your SPM will be shut down violently when it
> loses connectivity (or the moment it regains connectivity). Also, if any
> of your VMs have thin provisioning defined and they exhaust their
> storage during downtime, they'll run into trouble; but as far as I know
> they should be okay if they're not running processes that can suddenly
> demand a lot more storage. That's as far as possible damage goes.
> Besides that, when the switch comes back up, some components (host, data
> domain) might appear as non-operational or down, and you might have to
> reactivate them manually from the webadmin console.
>
> Hope this helps.
>
> Yours, Lior Vernia.
>
> On 21/03/13 20:42, Jonathan Horne wrote:
>> greetings,
>>
>> we are talking about possibly upgrading our cisco gear tonight, and this
>> will affect our ovirt environment.
>>
>> what can i expect if i were to reboot first the switch that all VMguest
>> VLANs are going thru, ad then afterwards rebooting the switch that all
>> ovirtmgmt connections are in? how will the ovirt environment behave
>> with loss of network connectivity for a couple minutes?
>>
>> the iscsi network is not going to be affected. any information or
>> stories of similar experiences would be appreciated.
>>
>> thanks,
>> jonathan
>>
>>
>> ------------------------------------------------------------------------
>> This is a PRIVATE message. If you are not the intended recipient, please
>> delete without copying and kindly advise us by e-mail of the mistake in
>> delivery. NOTE: Regardless of content, this e-mail shall not operate to
>> bind SKOPOS to any order or other contract unless pursuant to explicit
>> written agreement or government initiative expressly permitting the use
>> of e-mail for such purpose.
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
3:42 p.m.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B6CF21DAUSP01DAG0201_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Ah, thank you much lior and alex.
I believe this also answers my other thread, that is is ok to reboot the ma=
nagement server at any time? (I have another thread about how sluggish mine=
is running lately, and id like to get it rebooted soon before I go on vaca=
tion).
Thanks again!
jonathan
From: Alex Leonhardt [mailto:alex.tuxx@gmail.com]
Sent: Sunday, March 24, 2013 7:40 AM
To: Lior Vernia
Cc: Jonathan Horne; users(a)ovirt.org
Subject: Re: [Users] rebooting physical network that ovirt is attached to
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
________________________________
This is a PRIVATE message. If you are not the intended recipient, please de=
lete without copying and kindly advise us by e-mail of the mistake in deliv=
ery. NOTE: Regardless of content, this e-mail shall not operate to bind SKO=
POS to any order or other contract unless pursuant to explicit written agre=
ement or government initiative expressly permitting the use of e-mail for s=
uch purpose.
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B6CF21DAUSP01DAG0201_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<style <!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black}
span.HTMLPreformattedChar
{font-family:Consolas;
color:black}
span.EmailStyle19
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-- </style
</head <body bgcolor=3D"white"
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" <div class=3D"WordSection1" <p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt; font-family:"C=
alibri","sans-serif"; color:#1F497D">Ah, thank you much
lior=
and alex.</span></p <p
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;
font-family:"C=
alibri","sans-serif";
color:#1F497D"> </span></p <p
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;
font-family:"C=
alibri","sans-serif"; color:#1F497D">I believe this
also ans=
wers my other thread, that is is ok to reboot the management server at any =
time? (I have another thread about how sluggish mine is
running lately, and id like to get it rebooted soon before I go on vacatio=
n).</span></p <p
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;
font-family:"C=
alibri","sans-serif";
color:#1F497D"> </span></p <p
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;
font-family:"C=
alibri","sans-serif"; color:#1F497D">Thanks
again!</span></p=
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt; font-family:"C=
alibri","sans-serif";
color:#1F497D">jonathan</span></p <p
class=3D"MsoNormal"><span style=3D"font-size:11.0pt;
font-family:"C=
alibri","sans-serif";
color:#1F497D"> </span></p
<div <div style=3D"border:none;
border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in" <p
class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;
font-family:&quo=
t;Tahoma","sans-serif";
color:windowtext">From:</span></b><s=
pan style=3D"font-size:10.0pt;
font-family:"Tahoma","sans-se=
rif"; color:windowtext"> Alex Leonhardt [mailto:alex.tuxx@gmail.com]
<br <b>Sent:</b> Sunday, March 24, 2013 7:40
AM<br <b>To:</b> Lior
Vernia<br <b>Cc:</b> Jonathan
Horne; users(a)ovirt.org<br <b>Subject:</b> Re:
[Users] rebooting physical network that ovirt is attach=
ed to</span></p </div </div <p
class=3D"MsoNormal"> </p <p
class=3D"MsoNormal"><span style=3D"font-size:10.0pt;
font-family:"T=
ahoma","sans-serif"">From experience, I would shutdown
the o=
virt engine before you do any work related to networking. The VMs will keep=
running w/o the engine available, you're simply unable
to add/remove/failover VMs, etc. The VDSM running on the host will be unab=
le to get instructions to "kill" any VMs as the engine is already=
"down" :) ...
<br <br hope it helps!<br alex<br
<br <br
<br </span><br On 03/24/2013 10:04 AM, Lior Vernia wrote: </p <pre>Hello Jonathan,</pre
<pre> </pre
<pre>First of all let me apologize for not being more responsive, seems lik=
e</pre <pre>you got the worse end of
time difference.</pre <pre> </pre <pre>Now, in case the question is still
relevant:</pre <pre> </pre <pre>1. Rebooting the first switch won't cause any
damage. The VMs will los=
e</pre <pre>connectivity on the
VLANs, but they should still be manageable through=
</pre <pre>oVirt and run normally on
their hosts.</pre <pre> </pre <pre>2. Rebooting the second one could prove more
troublesome. Firstly, as =
a</pre <pre>preemptive measure I
would advise that you not have any VMs running on=
</pre <pre>your host marked as SPM
at the moment of reboot, if possible - there's=
</pre <pre>risk that VMs running on
your SPM will be shut down violently when it<=
/pre <pre>loses connectivity (or the moment it regains
connectivity). Also, if a=
ny</pre <pre>of your VMs have thin
provisioning defined and they exhaust their</pre=
<pre>storage during downtime, they'll run into
trouble; but as far as I kno=
w</pre <pre>they should be okay if
they're not running processes that can suddenly=
</pre <pre>demand a lot more
storage. That's as far as possible damage goes.</pre=
<pre>Besides that, when the switch comes back up, some
components (host, da=
ta</pre <pre>domain) might appear as
non-operational or down, and you might have to=
</pre <pre>reactivate them manually
from the webadmin console.</pre <pre> </pre <pre>Hope this helps.</pre <pre> </pre
<pre>Yours, Lior Vernia.</pre
<pre> </pre
<pre>On 21/03/13 20:42, Jonathan Horne wrote:</pre <blockquote style=3D"margin-top:5.0pt;
margin-bottom:5.0pt" <pre>greetings,</pre <pre> </pre
<pre>we are talking about possibly upgrading our cisco gear tonight, and th=
is</pre <pre>will affect our ovirt
environment.</pre <pre> </pre <pre>what can i expect if i were to reboot first the
switch that all VMgues=
t</pre <pre>VLANs are going thru, ad
then afterwards rebooting the switch that all=
</pre <pre>ovirtmgmt connections are
in? how will the ovirt environment beh=
ave</pre <pre>with loss of network
connectivity for a couple minutes?</pre
<pre> </pre
<pre>the iscsi network is not going to be affected. any information
o=
r</pre <pre>stories of similar
experiences would be appreciated.</pre
<pre> </pre
<pre>thanks,</pre <pre>jonathan</pre <pre> </pre
<pre> </pre
<pre>----------------------------------------------------------------------=
--</pre <pre>This is a PRIVATE
message. If you are not the intended recipient, plea=
se</pre <pre>delete without copying
and kindly advise us by e-mail of the mistake i=
n</pre <pre>delivery. NOTE:
Regardless of content, this e-mail shall not operate t=
o</pre <pre>bind SKOPOS to any order
or other contract unless pursuant to explicit=
</pre <pre>written agreement or
government initiative expressly permitting the us=
e</pre <pre>of e-mail for such
purpose.</pre <pre> </pre <pre> </pre
<pre>_______________________________________________</pre <pre>Users mailing list</pre <pre><a
href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a></pre <pre><a
href=3D"http://lists.ovirt.org/mailman/listinfo/users">http:...
.ovirt.org/mailman/listinfo/users</a></pre
<pre> </pre
</blockquote
<pre>_______________________________________________</pre <pre>Users mailing list</pre <pre><a
href=3D"mailto:Users@ovirt.org">Users@ovirt.org</a></pre <pre><a
href=3D"http://lists.ovirt.org/mailman/listinfo/users">http:...
.ovirt.org/mailman/listinfo/users</a></pre
</div <br
<hr <font color=3D"Gray"
face=3D"Arial" size=3D"1">This is a PRIVATE message. I=
f you are not the intended recipient, please delete without copying and kin=
dly advise us by e-mail of the mistake in delivery. NOTE: Regardless of con=
tent, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit wri=
tten agreement or government initiative expressly permitting the use of e-m=
ail for such purpose.</font </body </html
--_000_9BE6F493F83A594DA60C45E6A09DC5AC2B6CF21DAUSP01DAG0201_--
From experience, I would shutdown the ovirt engine before you do any
work r=
elated to networking. The VMs will keep running w/o the engine available,
y=
ou're simply unable to add/remove/failover VMs, etc. The VDSM running on th=
e host will be unable to get instructions to "kill" any VMs as the engine i=
s already "down" :) ...
hope it helps!
alex
On 03/24/2013 10:04 AM, Lior Vernia wrote:
Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
greetings,
we are talking about possibly upgrading our cisco gear tonight, and this
will affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest
VLANs are going thru, ad then afterwards rebooting the switch that all
ovirtmgmt connections are in? how will the ovirt environment behave
with loss of network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or
stories of similar experiences would be appreciated.
thanks,
jonathan
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org
4:21 p.m.
Hello Jonathan,
Having taken a look at the other thread, your original assumption was
correct - aside from NFS, your nodes and VMs should generally be fine
during a reboot (again, excluding cases as I mentioned for thin
provisioning).
As for the NFS services your server is providing, I'm no expert when it
comes to storage, so my best advice would be to wait for someone on the
other thread to give you a definite answer (also it sounds like there's
a bigger issue weighing on your server, causing it to be sluggish).
However, if you're pressed for time - I think you should be fine as long
as you detach the NFS domains in an orderly fashion before you take the
server down for a reboot, and then reattach them when it's back up. As
far as I know (and again I'm no expert), both of these domains aren't
critical most of the time; ISO domains are critical when you have VMs
accessing them (during installation and such), and export domains when
you're moving VMs around.
Also, you might want to try IRC to see if someone more knowledgeable
than me might answer you in real time: irc://irc.oftc.net/ovirt.
Yours, Lior.
On 24/03/13 15:42, Jonathan Horne wrote:
Ah, thank you much lior and alex.
I believe this also answers my other thread, that is is ok to reboot the
management server at any time? (I have another thread about how sluggish
mine is running lately, and id like to get it rebooted soon before I go
on vacation).
Thanks again!
jonathan
*From:*Alex Leonhardt [mailto:alex.tuxx@gmail.com]
*Sent:* Sunday, March 24, 2013 7:40 AM
*To:* Lior Vernia
*Cc:* Jonathan Horne; users(a)ovirt.org
*Subject:* Re: [Users] rebooting physical network that ovirt is attached to
From experience, I would shutdown the ovirt engine before you do any
work related to networking. The VMs will keep running w/o the engine
available, you're simply unable to add/remove/failover VMs, etc. The
VDSM running on the host will be unable to get instructions to "kill"
any VMs as the engine is already "down" :) ...
hope it helps!
alex
On 03/24/2013 10:04 AM, Lior Vernia wrote:
Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
greetings,
we are talking about possibly upgrading our cisco gear tonight, and this
will affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest
VLANs are going thru, ad then afterwards rebooting the switch that all
ovirtmgmt connections are in? how will the ovirt environment behave
with loss of network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or
stories of similar experiences would be appreciated.
thanks,
jonathan
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
4:40 p.m.
>
>
> I believe this also answers my other thread, that is is ok to reboot the
> management server at any time? (I have another thread about how sluggish
> mine is running lately, and id like to get it rebooted soon before I go
> on vacation).
>
dont reboot the whole server - just restart the jboss
cheers
6:34 p.m.
This is a multi-part message in MIME format.
--------------090902060900070102080309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
if only export and iso domains are on the ovirt engine host, you're
usually good to just reboot, when the engine is back up and running,
you'll have to manually re-attach the domains back to the data centre...
alex
On 03/24/2013 02:21 PM, Lior Vernia wrote:
Hello Jonathan,
Having taken a look at the other thread, your original assumption was
correct - aside from NFS, your nodes and VMs should generally be fine
during a reboot (again, excluding cases as I mentioned for thin
provisioning).
As for the NFS services your server is providing, I'm no expert when it
comes to storage, so my best advice would be to wait for someone on the
other thread to give you a definite answer (also it sounds like there's
a bigger issue weighing on your server, causing it to be sluggish).
However, if you're pressed for time - I think you should be fine as long
as you detach the NFS domains in an orderly fashion before you take the
server down for a reboot, and then reattach them when it's back up. As
far as I know (and again I'm no expert), both of these domains aren't
critical most of the time; ISO domains are critical when you have VMs
accessing them (during installation and such), and export domains when
you're moving VMs around.
Also, you might want to try IRC to see if someone more knowledgeable
than me might answer you in real time: irc://irc.oftc.net/ovirt.
Yours, Lior.
On 24/03/13 15:42, Jonathan Horne wrote:
> Ah, thank you much lior and alex.
>
>
>
> I believe this also answers my other thread, that is is ok to reboot the
> management server at any time? (I have another thread about how sluggish
> mine is running lately, and id like to get it rebooted soon before I go
> on vacation).
>
>
>
> Thanks again!
>
> jonathan
>
>
>
> *From:*Alex Leonhardt [mailto:alex.tuxx@gmail.com]
> *Sent:* Sunday, March 24, 2013 7:40 AM
> *To:* Lior Vernia
> *Cc:* Jonathan Horne; users(a)ovirt.org
> *Subject:* Re: [Users] rebooting physical network that ovirt is attached to
>
>
>
> From experience, I would shutdown the ovirt engine before you do any
> work related to networking. The VMs will keep running w/o the engine
> available, you're simply unable to add/remove/failover VMs, etc. The
> VDSM running on the host will be unable to get instructions to "kill"
> any VMs as the engine is already "down" :) ...
>
> hope it helps!
> alex
>
>
>
>
> On 03/24/2013 10:04 AM, Lior Vernia wrote:
>
> Hello Jonathan,
>
>
>
> First of all let me apologize for not being more responsive, seems like
>
> you got the worse end of time difference.
>
>
>
> Now, in case the question is still relevant:
>
>
>
> 1. Rebooting the first switch won't cause any damage. The VMs will lose
>
> connectivity on the VLANs, but they should still be manageable through
>
> oVirt and run normally on their hosts.
>
>
>
> 2. Rebooting the second one could prove more troublesome. Firstly, as a
>
> preemptive measure I would advise that you not have any VMs running on
>
> your host marked as SPM at the moment of reboot, if possible - there's
>
> risk that VMs running on your SPM will be shut down violently when it
>
> loses connectivity (or the moment it regains connectivity). Also, if any
>
> of your VMs have thin provisioning defined and they exhaust their
>
> storage during downtime, they'll run into trouble; but as far as I know
>
> they should be okay if they're not running processes that can suddenly
>
> demand a lot more storage. That's as far as possible damage goes.
>
> Besides that, when the switch comes back up, some components (host, data
>
> domain) might appear as non-operational or down, and you might have to
>
> reactivate them manually from the webadmin console.
>
>
>
> Hope this helps.
>
>
>
> Yours, Lior Vernia.
>
>
>
> On 21/03/13 20:42, Jonathan Horne wrote:
>
> greetings,
>
>
>
> we are talking about possibly upgrading our cisco gear tonight, and this
>
> will affect our ovirt environment.
>
>
>
> what can i expect if i were to reboot first the switch that all VMguest
>
> VLANs are going thru, ad then afterwards rebooting the switch that all
>
> ovirtmgmt connections are in? how will the ovirt environment behave
>
> with loss of network connectivity for a couple minutes?
>
>
>
> the iscsi network is not going to be affected. any information or
>
> stories of similar experiences would be appreciated.
>
>
>
> thanks,
>
> jonathan
>
>
>
>
>
> ------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
>
> delete without copying and kindly advise us by e-mail of the mistake in
>
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
>
> bind SKOPOS to any order or other contract unless pursuant to explicit
>
> written agreement or government initiative expressly permitting the use
>
> of e-mail for such purpose.
>
>
>
>
>
> _______________________________________________
>
> Users mailing list
>
> Users@ovirt.org<mailto:Users@ovirt.org>
>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> _______________________________________________
>
> Users mailing list
>
> Users@ovirt.org<mailto:Users@ovirt.org>
>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> ------------------------------------------------------------------------
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind SKOPOS to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use
> of e-mail for such purpose.
--------------090902060900070102080309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Tahoma">if only export and
iso domains
are on the ovirt engine host, you're usually good to just
reboot, when the engine is back up and running, you'll have to
manually re-attach the domains back to the data centre...<br>
<br>
alex<br>
<br>
</font></font><br>
On 03/24/2013 02:21 PM, Lior Vernia wrote:
<blockquote cite="mid:514F0BD3.1@redhat.com" type="cite">
<pre wrap="">Hello Jonathan,
Having taken a look at the other thread, your original assumption was
correct - aside from NFS, your nodes and VMs should generally be fine
during a reboot (again, excluding cases as I mentioned for thin
provisioning).
As for the NFS services your server is providing, I'm no expert when it
comes to storage, so my best advice would be to wait for someone on the
other thread to give you a definite answer (also it sounds like there's
a bigger issue weighing on your server, causing it to be sluggish).
However, if you're pressed for time - I think you should be fine as long
as you detach the NFS domains in an orderly fashion before you take the
server down for a reboot, and then reattach them when it's back up. As
far as I know (and again I'm no expert), both of these domains aren't
critical most of the time; ISO domains are critical when you have VMs
accessing them (during installation and such), and export domains when
you're moving VMs around.
Also, you might want to try IRC to see if someone more knowledgeable
than me might answer you in real time: <a class="moz-txt-link-freetext"
href="irc://irc.oftc.net/ovirt">irc://irc.oftc.net/ovirt<...;.
Yours, Lior.
On 24/03/13 15:42, Jonathan Horne wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ah, thank you much lior and alex.
I believe this also answers my other thread, that is is ok to reboot the
management server at any time? (I have another thread about how sluggish
mine is running lately, and id like to get it rebooted soon before I go
on vacation).
Thanks again!
jonathan
*From:*Alex Leonhardt [<a class="moz-txt-link-freetext"
href="mailto:alex.tuxx@gmail.com">mailto:alex.tuxx@gmail.com</a>]
*Sent:* Sunday, March 24, 2013 7:40 AM
*To:* Lior Vernia
*Cc:* Jonathan Horne; <a class="moz-txt-link-abbreviated"
href="mailto:users@ovirt.org">users@ovirt.org</a>
*Subject:* Re: [Users] rebooting physical network that ovirt is attached to
From experience, I would shutdown the ovirt engine before you do any
work related to networking. The VMs will keep running w/o the engine
available, you're simply unable to add/remove/failover VMs, etc. The
VDSM running on the host will be unable to get instructions to "kill"
any VMs as the engine is already "down" :) ...
hope it helps!
alex
On 03/24/2013 10:04 AM, Lior Vernia wrote:
Hello Jonathan,
First of all let me apologize for not being more responsive, seems like
you got the worse end of time difference.
Now, in case the question is still relevant:
1. Rebooting the first switch won't cause any damage. The VMs will lose
connectivity on the VLANs, but they should still be manageable through
oVirt and run normally on their hosts.
2. Rebooting the second one could prove more troublesome. Firstly, as a
preemptive measure I would advise that you not have any VMs running on
your host marked as SPM at the moment of reboot, if possible - there's
risk that VMs running on your SPM will be shut down violently when it
loses connectivity (or the moment it regains connectivity). Also, if any
of your VMs have thin provisioning defined and they exhaust their
storage during downtime, they'll run into trouble; but as far as I know
they should be okay if they're not running processes that can suddenly
demand a lot more storage. That's as far as possible damage goes.
Besides that, when the switch comes back up, some components (host, data
domain) might appear as non-operational or down, and you might have to
reactivate them manually from the webadmin console.
Hope this helps.
Yours, Lior Vernia.
On 21/03/13 20:42, Jonathan Horne wrote:
greetings,
we are talking about possibly upgrading our cisco gear tonight, and this
will affect our ovirt environment.
what can i expect if i were to reboot first the switch that all VMguest
VLANs are going thru, ad then afterwards rebooting the switch that all
ovirtmgmt connections are in? how will the ovirt environment behave
with loss of network connectivity for a couple minutes?
the iscsi network is not going to be affected. any information or
stories of similar experiences would be appreciated.
thanks,
jonathan
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a
class="moz-txt-link-rfc2396E"
href="mailto:Users@ovirt.org"><mailto:Users@ovirt.org></a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a
class="moz-txt-link-rfc2396E"
href="mailto:Users@ovirt.org"><mailto:Users@ovirt.org></a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind SKOPOS to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
</pre>
</blockquote>
</blockquote>
</body>
</html>
--------------090902060900070102080309--
4262
days inactive
4265
days old
7 comments
4 participants
participants (4)
-
Alex Leonhardt -
Jonathan Horne -
Lior Vernia -
Tom Brown