<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div>i mean HOST's(not guest) ethernet.</div><div>Consistent Network Device Naming&nbsp; is what i proposal.</div><div>if someone is working on implementing &nbsp;it in ovirt?</div><div>&nbsp;</div><div>thanks<br><br><br><br></div><div></div><div id="divNeteaseMailCard"></div><div></div><pre><br>At&nbsp;2013-03-27&nbsp;15:23:18,"Antoni&nbsp;Segura&nbsp;Puimedon"&nbsp;&lt;asegurap@redhat.com&gt;&nbsp;wrote:

&gt;If&nbsp;I&nbsp;understand&nbsp;correctly,&nbsp;it&nbsp;would&nbsp;be&nbsp;about&nbsp;the&nbsp;ability&nbsp;to&nbsp;use&nbsp;the

&gt;webadmin&nbsp;set&nbsp;names&nbsp;for&nbsp;the&nbsp;vnics,&nbsp;i.e.,&nbsp;to&nbsp;write&nbsp;udev&nbsp;rules.

&gt;

&gt;-----&nbsp;Original&nbsp;Message&nbsp;-----

&gt;&gt;&nbsp;From:&nbsp;"Mark&nbsp;Wu"&nbsp;&lt;wudxw@linux.vnet.ibm.com&gt;

&gt;&gt;&nbsp;To:&nbsp;"bigclouds"&nbsp;&lt;bigclouds@163.com&gt;

&gt;&gt;&nbsp;Cc:&nbsp;arch@ovirt.org

&gt;&gt;&nbsp;Sent:&nbsp;Wednesday,&nbsp;March&nbsp;27,&nbsp;2013&nbsp;1:52:42&nbsp;AM

&gt;&gt;&nbsp;Subject:&nbsp;Re:&nbsp;proposal:supply&nbsp;a&nbsp;way&nbsp;to&nbsp;allow&nbsp;to&nbsp;change&nbsp;ethernet&nbsp;name.

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;On&nbsp;03/26/2013&nbsp;08:13&nbsp;PM,&nbsp;bigclouds&nbsp;wrote:

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;hi,all

&gt;&gt;&nbsp;i&nbsp;take&nbsp;the&nbsp;liberty&nbsp;of&nbsp;proposal&nbsp;a&nbsp;feature,&nbsp;give&nbsp;admin&nbsp;the&nbsp;opportunity

&gt;&gt;&nbsp;to&nbsp;change&nbsp;ethernet&nbsp;name.

&gt;&gt;&nbsp;my&nbsp;reasones:

&gt;&gt;&nbsp;1.modern&nbsp;server&nbsp;has&nbsp;several&nbsp;ethernets,but&nbsp;traditional&nbsp;ethernet&nbsp;naming

&gt;&gt;&nbsp;scheme&nbsp;is&nbsp;hard&nbsp;for&nbsp;people&nbsp;to&nbsp;know&nbsp;what&nbsp;its&nbsp;name&nbsp;represent.

&gt;&gt;&nbsp;2.sometime&nbsp;ethernet&nbsp;name&nbsp;is&nbsp;unpredictable&nbsp;.for&nbsp;example&nbsp;ifc-xxxx&nbsp;is

&gt;&gt;&nbsp;lost,&nbsp;having&nbsp;to&nbsp;change&nbsp;a&nbsp;n&nbsp;ew&nbsp;ethernet&nbsp;card.&nbsp;all&nbsp;those&nbsp;can&nbsp;lead

&gt;&gt;&nbsp;confusion.

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;Are&nbsp;you&nbsp;talking&nbsp;about&nbsp;the&nbsp;same&nbsp;problem&nbsp;resolved&nbsp;by&nbsp;biosdevname

&gt;&gt;&nbsp;developed&nbsp;by&nbsp;Dell?

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;You&nbsp;could&nbsp;take&nbsp;a&nbsp;look&nbsp;at&nbsp;the&nbsp;following&nbsp;links&nbsp;to&nbsp;confirm&nbsp;it.

&gt;&gt;&nbsp;http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf

&gt;&gt;&nbsp;https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;Mark

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;thanks

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;_______________________________________________

&gt;&gt;&nbsp;Arch&nbsp;mailing&nbsp;list&nbsp;Arch@ovirt.org

&gt;&gt;&nbsp;http://lists.ovirt.org/mailman/listinfo/arch

&gt;&gt;&nbsp;

&gt;&gt;&nbsp;_______________________________________________

&gt;&gt;&nbsp;Arch&nbsp;mailing&nbsp;list

&gt;&gt;&nbsp;Arch@ovirt.org

&gt;&gt;&nbsp;http://lists.ovirt.org/mailman/listinfo/arch

&gt;&gt;&nbsp;

&gt;_______________________________________________

&gt;Arch&nbsp;mailing&nbsp;list

&gt;Arch@ovirt.org

&gt;http://lists.ovirt.org/mailman/listinfo/arch

</pre></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>