8:48 p.m.
--_000_EF26FC1776F7FF46BFC072393EFD13A29A4E1FSERV070corpeldora_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi all,
Currently there is an option in the "vdc_options" table which indicates the=
operating systems that do not support NIC hotplug. I think it would be a b=
etter idea to use the osinfo properties file to enable or disable NIC hotpl=
ugging, since in this file an operating system can inherit properties from =
another one. The main idea is to disable NIC hotplugging in PPC64 VMs, but =
listing explicitly every ppc64 os in "HotPlugUnsupportedOsList" config valu=
e does not look like a clean way to do so. Do you agree with this? Should t=
his parameter be included in the osinfo properties file?
Thanks,
Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa
--_000_EF26FC1776F7FF46BFC072393EFD13A29A4E1FSERV070corpeldora_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40" <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft
Word 14 (filtered medium)" <style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" / </xml><![endif]--><!--[if gte mso
9]><xml <o:shapelayout
v:ext=3D"edit" <o:idmap v:ext=3D"edit"
data=3D"1" /
</o:shapelayout></xml><![endif]--
</head <body lang=3D"PT-BR"
link=3D"blue" vlink=3D"purple" <div
class=3D"WordSection1" <p
class=3D"MsoNormal"><span lang=3D"EN-US">Hi all,<br <br Currently there is an option in the
"vdc_options" table which ind=
icates the operating systems that do not support NIC hotplug. I think it wo=
uld be a better idea to use the osinfo properties file to enable or disable=
NIC hotplugging, since in this file an operating
system can inherit properties from another one. The main idea is to disabl=
e NIC hotplugging in PPC64 VMs, but listing explicitly every ppc64 os in &q=
uot;HotPlugUnsupportedOsList" config value does not look like a clean =
way to do so. Do you agree with this? Should
this parameter be included in the osinfo properties
file?<o:p></o:p></span=
></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p
class=3D"MsoNormal">Thanks,<o:p></o:p></p <p class=3D"MsoNormal">Leonardo Bianconi/Vitor
de Lima/Gustavo Pedrosa<o:p>=
</o:p></p </div </body
</html
--_000_EF26FC1776F7FF46BFC072393EFD13A29A4E1FSERV070corpeldora_--
9:08 a.m.
Hi Gustavo,
----- Original Message -----
From: "Gustavo Frederico Temple Pedrosa"
<gustavo.pedrosa(a)eldorado.org.br>
To: engine-devel(a)ovirt.org
Sent: Monday, September 9, 2013 8:48:25 PM
Subject: [Engine-devel] Question about HotPlug
Hi all,
Currently there is an option in the "vdc_options" table which indicates the
operating systems that do not support NIC hotplug. I think it would be a
better idea to use the osinfo properties file to enable or disable NIC
hotplugging, since in this file an operating system can inherit properties
from another one. The main idea is to disable NIC hotplugging in PPC64 VMs,
but listing explicitly every ppc64 os in "HotPlugUnsupportedOsList" config
value does not look like a clean way to do so. Do you agree with this?
Should this parameter be included in the osinfo properties file?
The hotplug capability of the OS refers also to disk hotplug in addition to
vnics hotplug.
The VmCommand.isOsSupportingHotPlug() handles the logic of the operating systems
that don't support hotplug.
+1 for moving it as a parameter in the osinfo-defaults.properties for the relevant
os.
Thanks,
Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
10:42 a.m.
On 09/10/2013 10:08 AM, Moti Asayag wrote:
Hi Gustavo,
----- Original Message -----
> From: "Gustavo Frederico Temple Pedrosa"
<gustavo.pedrosa(a)eldorado.org.br>
> To: engine-devel(a)ovirt.org
> Sent: Monday, September 9, 2013 8:48:25 PM
> Subject: [Engine-devel] Question about HotPlug
>
>
>
> Hi all,
>
> Currently there is an option in the "vdc_options" table which indicates
the
> operating systems that do not support NIC hotplug. I think it would be a
> better idea to use the osinfo properties file to enable or disable NIC
> hotplugging, since in this file an operating system can inherit properties
> from another one. The main idea is to disable NIC hotplugging in PPC64 VMs,
> but listing explicitly every ppc64 os in "HotPlugUnsupportedOsList" config
> value does not look like a clean way to do so. Do you agree with this?
> Should this parameter be included in the osinfo properties file?
The hotplug capability of the OS refers also to disk hotplug in addition to
vnics hotplug.
The VmCommand.isOsSupportingHotPlug() handles the logic of the operating systems
that don't support hotplug.
+1 for moving it as a parameter in the osinfo-defaults.properties for the relevant
os.
+1
I'd also separate between hotplugdisk/nic
(and from what i hear, for some operations like cpu/ram, we'll need to
distinguish between hotplug and hot unplug, but this can wait for them)
>
>
>
> Thanks,
>
> Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
11:31 a.m.
On Tue 10 Sep 2013 11:42:36 AM IDT, Itamar Heim wrote:
On 09/10/2013 10:08 AM, Moti Asayag wrote:
> Hi Gustavo,
>
> ----- Original Message -----
>> From: "Gustavo Frederico Temple Pedrosa"
>> <gustavo.pedrosa(a)eldorado.org.br>
>> To: engine-devel(a)ovirt.org
>> Sent: Monday, September 9, 2013 8:48:25 PM
>> Subject: [Engine-devel] Question about HotPlug
>>
>>
>>
>> Hi all,
>>
>> Currently there is an option in the "vdc_options" table which
>> indicates the
>> operating systems that do not support NIC hotplug. I think it would
>> be a
>> better idea to use the osinfo properties file to enable or disable NIC
>> hotplugging, since in this file an operating system can inherit
>> properties
>> from another one. The main idea is to disable NIC hotplugging in
>> PPC64 VMs,
>> but listing explicitly every ppc64 os in "HotPlugUnsupportedOsList"
>> config
>> value does not look like a clean way to do so. Do you agree with this?
>> Should this parameter be included in the osinfo properties file?
>
> The hotplug capability of the OS refers also to disk hotplug in
> addition to
> vnics hotplug.
>
> The VmCommand.isOsSupportingHotPlug() handles the logic of the
> operating systems
> that don't support hotplug.
>
> +1 for moving it as a parameter in the osinfo-defaults.properties for
> the relevant
> os.
+1
I'd also separate between hotplugdisk/nic
(and from what i hear, for some operations like cpu/ram, we'll need to
distinguish between hotplug and hot unplug, but this can wait for them)
>
>
+1 whats the namespace you had in mind for it?
e.g.
os.{id}.hotplugSupported.network.value = true
or an existing devices namespace is also an option:
os.{id}.devices.network.hotplugSupport.value = true
>>
>>
>>
>> Thanks,
>>
>> Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa
>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
3:16 p.m.
Thank you all !
Roy, we will use your second suggestion, thank you very much.
-----Original Message-----
From: Roy Golan [mailto:rgolan@redhat.com]
Sent: terça-feira, 10 de setembro de 2013 06:32
To: Itamar Heim
Cc: Gustavo Frederico Temple Pedrosa; engine-devel(a)ovirt.org; Moti Asayag
Subject: Re: [Engine-devel] Question about HotPlug
On Tue 10 Sep 2013 11:42:36 AM IDT, Itamar Heim wrote:
> On 09/10/2013 10:08 AM, Moti Asayag wrote:
>> Hi Gustavo,
>>
>> ----- Original Message -----
>>> From: "Gustavo Frederico Temple Pedrosa"
>>> <gustavo.pedrosa(a)eldorado.org.br>
>>> To: engine-devel(a)ovirt.org
>>> Sent: Monday, September 9, 2013 8:48:25 PM
>>> Subject: [Engine-devel] Question about HotPlug
>>>
>>>
>>>
>>> Hi all,
>>>
>>> Currently there is an option in the "vdc_options" table which
>>> indicates the operating systems that do not support NIC hotplug. I
>>> think it would be a better idea to use the osinfo properties file to
>>> enable or disable NIC hotplugging, since in this file an operating
>>> system can inherit properties from another one. The main idea is to
>>> disable NIC hotplugging in
>>> PPC64 VMs,
>>> but listing explicitly every ppc64 os in
"HotPlugUnsupportedOsList"
>>> config
>>> value does not look like a clean way to do so. Do you agree with this?
>>> Should this parameter be included in the osinfo properties file?
>>
>> The hotplug capability of the OS refers also to disk hotplug in
>> addition to vnics hotplug.
>>
>> The VmCommand.isOsSupportingHotPlug() handles the logic of the
>> operating systems that don't support hotplug.
>>
>> +1 for moving it as a parameter in the osinfo-defaults.properties for
>> the relevant
>> os.
>
> +1
> I'd also separate between hotplugdisk/nic (and from what i hear, for
> some operations like cpu/ram, we'll need to distinguish between
> hotplug and hot unplug, but this can wait for them)
>
>>
>>
+1 whats the namespace you had in mind for it?
e.g.
os.{id}.hotplugSupported.network.value = true
or an existing devices namespace is also an option:
os.{id}.devices.network.hotplugSupport.value = true
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Leonardo Bianconi/Vitor de Lima/Gustavo Pedrosa
>>>
>>> _______________________________________________
>>> Engine-devel mailing list
>>> Engine-devel(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
3884
days inactive
3885
days old
4 comments
4 participants
participants (4)
-
Gustavo Frederico Temple Pedrosa -
Itamar Heim -
Moti Asayag -
Roy Golan