[Users] Nic names : always start by eth0

Hello, I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ? If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules) Thanks, Regards, Grégoire

Hi You have toremove HWADDR value from theifcfg-ethX and rules string from /etc/udev/rules.d/70-persistent-net.rules files. It'll work fine if you have only one NIC per machine. -- Best regards, Pavel Zhukov Software Maintenance Engineer RHCE, RHCVA Tel: +420.532294671 mailto:pzhukov@redhat.com On Tue, 30 Jul 2013, gregoire.leroy@retenodus.net wrote: | Hello, | | I have an ovirt cluster which runs CentOS VM. I have a template to | create VM. On this template, there are two interfaces, eth0 and | eth1. | When I create a VM using this template, the new interfaces are named | eth2 and eth3. It can be pretty annoying and I would like to know if | it would be possible to always start by eth0 ? | | If I remember the discussion on IRC, it would be necessary to clean | old udev rules (in centos it seems to be | /etc/udev/rules.d/70-persistent-net.rules) | | Thanks, | Regards, | Grégoire | _______________________________________________ | Users mailing list | Users@ovirt.org | http://lists.ovirt.org/mailman/listinfo/users

Hi, The easiest way is to remove 70-persistent-net.rules in your master-vm, remove HWADDR-strings from ifcfg-eth* friles, shut it down and create the template. Btw, also remove your ssh-keys in your template to create unique ones for each vm... Regards, René On Tue, 2013-07-30 at 14:59 +0200, gregoire.leroy@retenodus.net wrote:
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules)
Thanks, Regards, Grégoire _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 07/30/2013 04:13 PM, René Koch (ovido) wrote:
Hi,
The easiest way is to remove 70-persistent-net.rules in your master-vm, remove HWADDR-strings from ifcfg-eth* friles, shut it down and create the template. Btw, also remove your ssh-keys in your template to create unique ones for each vm...
will cloud-init solve this one?
Regards, René
On Tue, 2013-07-30 at 14:59 +0200, gregoire.leroy@retenodus.net wrote:
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules)
Thanks, Regards, Grégoire _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "\"René \"Koch (ovido)\"\"" <r.koch@ovido.at> Cc: "gregoire leroy" <gregoire.leroy@retenodus.net>, users@ovirt.org, "Omer Frenkel" <ofrenkel@redhat.com>, "Michal Skrivanek" <mskrivan@redhat.com>, "Greg Padgett" <gpadgett@redhat.com> Sent: Tuesday, July 30, 2013 9:46:22 PM Subject: Re: [Users] Nic names : always start by eth0
On 07/30/2013 04:13 PM, René Koch (ovido) wrote:
Hi,
The easiest way is to remove 70-persistent-net.rules in your master-vm, remove HWADDR-strings from ifcfg-eth* friles, shut it down and create the template. Btw, also remove your ssh-keys in your template to create unique ones for each vm...
will cloud-init solve this one?
we should add an ability to send a user script that cloud-init will run, then basically user could put any configuration he would like. this is not available currently, but i'm pretty sure supported by cloud-init.
Regards, René
On Tue, 2013-07-30 at 14:59 +0200, gregoire.leroy@retenodus.net wrote:
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules)
Thanks, Regards, Grégoire _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi AFAIK This is more a CentOS- than an oVirt-issue. CentOS behaves identically on vSphere. If I remember correctly, this is due to the fact that the MAC-address of the virtual NIC has to change, when you create a VM from a template. CentOS however keeps the MAC address of the template and just adds the new MAC, which then of course becomes eth1. --SMG ----- Original Message -----
From: "gregoire leroy" <gregoire.leroy@retenodus.net> To: users@ovirt.org Sent: Tuesday, July 30, 2013 7:59:35 AM Subject: [Users] Nic names : always start by eth0
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules)
Thanks, Regards, Grégoire _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi AFAIK This is more a CentOS- than an oVirt-issue. CentOS behaves identically on vSphere. If I remember correctly, this is due to the fact that the MAC-address of the virtual NIC has to change, when you create a VM from a template. CentOS however keeps the MAC address of the template and just adds the new MAC, which then of course becomes eth1. --SMG ----- Original Message -----
From: "gregoire leroy" <gregoire.leroy@retenodus.net> To: users@ovirt.org Sent: Tuesday, July 30, 2013 7:59:35 AM Subject: [Users] Nic names : always start by eth0
Hello,
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules)
Thanks, Regards, Grégoire _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

gregoire.leroy@retenodus.net wrote:
I have an ovirt cluster which runs CentOS VM. I have a template to create VM. On this template, there are two interfaces, eth0 and eth1. When I create a VM using this template, the new interfaces are named eth2 and eth3. It can be pretty annoying and I would like to know if it would be possible to always start by eth0 ?
If I remember the discussion on IRC, it would be necessary to clean old udev rules (in centos it seems to be /etc/udev/rules.d/70-persistent-net.rules) Just use sys-unconfig which will wipe all machine specific data, like network/root pw/ and then make it into a template. On each clone the machine will need network/root pw/ etc.
Joop
participants (8)
-
gregoire.leroy@retenodus.net
-
Itamar Heim
-
Joop
-
Omer Frenkel
-
Pavel Zhukov
-
René Koch (ovido)
-
Sven M. Geschke
-
Sven M. Geschke