[pve-devel] [PATCH ifupdown2] allow address on vlan aware bridge
Alexandre DERUMIER
aderumier at odiso.com
Mon Jun 18 13:00:31 CEST 2018
> I don't known if we could update pve-common management to cleanup current
> config,
>>yes. it's compatible, so why not?
> or make a post-install script in ifupdown2 to update config ?
>>We only require this if we cannot support reading both formats.
Ok thanks. Indeed, it's working with both ifupdown/ifupdown2.
But I don't known how to update config (transparently) for users ? (This don't need /etc/network/interfaces.new and reboot)
----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "Wolfgang Bumiller" <w.bumiller at proxmox.com>, "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 18 Juin 2018 12:06:36
Objet: Re: [pve-devel] [PATCH ifupdown2] allow address on vlan aware bridge
comments below
> On June 18, 2018 at 10:52 AM Alexandre DERUMIER <aderumier at odiso.com> wrote:
>
>
> BTW,
>
> They are 2 configs changes needed
>
> for bond:
>
> currently we use
>
> slaves eth0 eth1.
>
>
> classic ifupdown support also "bond-slaves eth0 eth1" since debian squeeze.
>
> ifupdown2 support only "bond-slaves".
>
>
>
> for vlan aware bridge:
> our ifupdown script "bridgevlan", add bridge-vids 2-4094 if it's not defined
> by default.
>
> but ifupdown2 need to be explicitly defined
>
>
>
> I don't known if we could update pve-common management to cleanup current
> config,
yes. it's compatible, so why not?
> or make a post-install script in ifupdown2 to update config ?
We only require this if we cannot support reading both formats.
> Not sure what is the best way ?
More information about the pve-devel
mailing list