From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] address flexibility
Date: Wed, 27 Aug 2025 14:30:05 +0000 [thread overview]
Message-ID: <912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com> (raw)
In-Reply-To: <m2cy8i3q6p.wl-randy@psg.com>
>>
>>i build new proxmox nodes in the lab on a lab network. i do the
>>debian
>>part in the lab and then the proxmox part in the destination rack
>>because i am not confident that proxmox install does not bind to /
>>embed
>>the ip address on which it is installed.
>>
>>am i being too cautious. can in build a node, then ship to rack,
>>change
>>/etc/hosts, network config, etc., and then join the cluster?
yes, no problem
_______________________________________________
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:[~2025-08-27 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 18:15 Randy Bush
2025-08-27 14:30 ` DERUMIER, Alexandre [this message]
2025-08-27 14:32 ` Miguel Tudela via pve-user
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=912e37adbc53f89115d2f3543aa1d11366ff8eef.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.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