Forgot to readd the ML to CC... Sorry,
Lennart
--
Lennart Poettering, Red Hat
--- Begin Message ---
On Thu, 18.06.15 22:03, Florian Koch ([email protected]) wrote:
> >> Now if you use similar names for conatiners, like
> >>
> >> com.$company.$devision.$name1
> >> com.$company.$devision.$name2
> >> com.$company.$devision.$name3
> >>
> >> the network device name handling is broken.
> >>
> >> I tryed to prefix the machinename with a uuid (uuidgen) but the the
> >> names are to long.
> >>
> >> Why not using a 11 Caracter uuid / random for network interface
> >> names, and avoid all the naming trouble?
> >
> > Well, because we want to keep things easy to grok for users. If you
> > type "ip link" and see the container names for the veth links, then
> > that's certainly a lot more useful than seeing some random
> > gibberish....
>
> that is totally understandable, but what is with macvlan interfaces?
> these are not shown in ip link (they are moved to the container
> namespace)
> The macvlan are my main Problem , we do not use veth interfaces.
Hmm, not sure I follow: the macvlan ones exist inside the container
namespace only (modulo a short time window during container setup),
and hence don't have to carry unique names across the whole
system. It's completely OK if we have an interface by the same name
every single container...
The reason I named ned macvlan interfaces like the ifaces they are
generated from is to help admins understand the relation...
Lennart
--
Lennart Poettering, Red Hat
--- End Message ---
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
