From: Dimitri Alexandris <d.alexandris@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] allow-ovs vs auto
Date: Wed, 3 Mar 2021 19:06:54 +0200 [thread overview]
Message-ID: <CAOWoYHpwOsMqcdbNh+81ErsOmAUJVhAjijAGtHZx56e=MGH3sw@mail.gmail.com> (raw)
In-Reply-To: <048e4a73b9243606c94656180c00d0f9735a5346.camel@odiso.com>
All of my proxmox (5) have allow-ovs in every vmbr.
On Wed, Mar 3, 2021 at 11:16 AM <aderumier@odiso.com> wrote:
> if you use ifupdown2, it'll use "auto ..."
>
> this is because ifupdown2 is able to manage relationship.
>
> The web interface will setup correct configuration for you if you use
> ifupdown2 or ifupdown1.
>
>
>
>
> Le mardi 02 mars 2021 à 12:23 +0800, Hongyi Zhao a écrit :
> > If I create an OVS Bridge with the Autostart option using pve's web
> > interface, the following configuration will be generated:
> >
> > auto vmbr0
> > iface vmbr0 inet manual
> > ovs_type OVSBridge
> >
> > OTOH, the examples given on the wiki website
> > <https://pve.proxmox.com/wiki/Open_vSwitch> use the following format:
> >
> > allow-ovs vmbr0
> > iface vmbr0 inet manual
> > ovs_type OVSBridge
> >
> > So, I want to know if the "allow-ovs" and "auto" keywords are
> > equivalent in the context for my above scenario. Any hints will be
> > appreciated.
> >
> > Regards
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2021-03-03 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGP6POL6n3zJ+fcys_uAiBgFsAn7saF4D1V=fiCjDGY=13sThQ@mail.gmail.com>
2021-03-03 9:16 ` aderumier
2021-03-03 17:06 ` Dimitri Alexandris [this message]
2021-03-04 0:24 ` Hongyi Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOWoYHpwOsMqcdbNh+81ErsOmAUJVhAjijAGtHZx56e=MGH3sw@mail.gmail.com' \
--to=d.alexandris@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox