[sles-beta] SLES12 network interface names

[urs.frey at post.ch]

Hi Olaf

>Okay, this makes sense, and I think this should not be too hard to address.
>Let's see what we can come up with.

Thank you very much.
Meanwhile I am trying to get around by setting net.ifnames=0 as Kernel Parameter.

Best regards

Urs Frey                                              
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX     : ++41 (0)58 667 30 07 
E-Mail:   urs.frey at post.ch


-----Ursprüngliche Nachricht-----
Von: Olaf Kirch [mailto:okir at suse.de] 
Gesendet: Monday, March 24, 2014 4:04 PM
An: Frey Urs, IT222
Cc: sles-beta at lists.suse.com
Betreff: Re: AW: [sles-beta] SLES12 network interface names

On Monday 24 March 2014 15:57:34 urs.frey at post.ch wrote:
> Hi Olaf
> 
> >So, will vmware leave at least the MAC address intact?
> 
> Yes unless the type of driver changes in the VM client config, e.g.from
>  Intel to vmxnet3, the MAC keeps being the same. But this is a different
>  story.
> 
> See, my concern is, that I usually have to install a server remotely
>  without having seen the HW before. The only thing I have, is the MAC I can
>  get either by API from the HP Proliant ILO remote console, or by API from
>  the VMware Vspere client configuration.
> 
> In both cases I then need to "translate" the MAC of the first interface in
>  the list to some name to generate my autoinst.xml In my case the first
>  interface in the list is cabled and has an open Firewall as setup
>  interface for network setup.

Okay, this makes sense, and I think this should not be too hard to address.
Let's see what we can come up with.

Olaf
-- 
Neo didn't bring down the Matrix. SOA did. (soafacts.com)
--------------------------------------------
Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir at suse.com)
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)