[pve-devel] [PATCH common 1/1] Fix #545: Allow descriptive names for network bridges and bonds

[Dominic Jäger]

Changing \d to \w was simply the quickest way to adress the bug report. I've already heard some people here speaking favorably about the idea of an alias/custom description, but no final decision has been made as far as I know.

> Alexandre DERUMIER <aderumier at odiso.com> hat am 6. Juni 2019 um 07:54 geschrieben:
>
> ifupdown2 already support "alias" option on interfaces
> 
> auto eth0
> iface eth0
>     alias "my super long string of description"
> 
> 
> I was planning to use that for vnet too. (keeping vnet(\d+) as interface id, and add a custom description).
> 
> What do you think about this ?
> 
> 
> ----- Mail original -----
> De: "Fabian Grünbichler" <f.gruenbichler at proxmox.com>
> À: "pve-devel" <pve-devel at pve.proxmox.com>
> Envoyé: Mercredi 5 Juin 2019 11:25:47
> Objet: Re: [pve-devel] [PATCH common 1/1] Fix #545: Allow descriptive names for network bridges and bonds
> 
> On Wed, May 15, 2019 at 11:49:30AM +0200, Dominic Jäger wrote: 
> > Allowing more descriptive names for network bridges and bonds makes 
> > their identification easier. 
> 
> 
> per our discussion, maybe this + labels/comments on interfaces could 
> get a v2? ;) 
> 
> > Signed-off-by: Dominic Jäger <d.jaeger at proxmox.com> 
> > --- 
> > - if ($iface =~ m/^bond\d+$/) { 
> > + if ($iface =~ m/^bond\w+$/) {