From: nada <nada@verdnatura.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] PVE 7 - upgrade to ifupdown2
Date: Thu, 27 Jul 2023 08:20:58 +0200 [thread overview]
Message-ID: <9cdaee916a179c2658aa41689c72e906@verdnatura.es> (raw)
In-Reply-To: <mailman.15.1690388504.335.pve-user@lists.proxmox.com>
hi Alessio
yes, you need just install ifupdown2 at ALL nodes
and after that you may just try to change some comment
of one of yours net
via webGUI at node > system > network >
after that you'll see diff and just do Apply...
NadaMac
On 2023-07-26 18:21, Alessio Cecchi via pve-user wrote:
> Hi,
> we have upgrade a PVE cluster from 5.4 to 6.4 and now to 7.4. Before to
> upgrade to PVE 8 I would like to switch to ifupdown2.
> What is the right procedure to upgrade to ifupdown2 and the steps to
> pay attention to?
> Is sufficient to migrate all VM from the node and do "apt install
> ifupdown2" one node after another?
> Should I update somethings in /etc/network/interfaces (we are using
> bond+bridge+VLAN)?
> Thanks
> --
> Alessio Cecchi
> Postmaster @http://www.qboxmail.it
> https://www.linkedin.com/in/alessice
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
parent reply other threads:[~2023-07-27 6:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.15.1690388504.335.pve-user@lists.proxmox.com>]
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=9cdaee916a179c2658aa41689c72e906@verdnatura.es \
--to=nada@verdnatura.es \
--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