This was now just a matter of doing the clickity click on all hosts. They're now using the dedicated vlan.

I've added a bridge vmbr443 to all hypervisors.

I wanted to rename the bridges on the proxmox hosts to something clearer (like vmbr-staging) but it turns out that proxmox only supports bridges named /vmbr\d+/. Ugh.

(the VLAN id for the staging vlan is 443).

In T1872#44251, @rdicosmo wrote:

Is this now done? If that's the case this ticked should be closed.

Is this now done? If that's the case this ticked should be closed.

A priori, everything is done on sesi's side, as asked by @olasd, last ticket entries excerpt:

sesi asked for some more details about the hardware to propagate that vlan too.
I just replied, so hopefully, that should converge soon.

Most of the relevant commits use the 192.168.128.0/24 address space.

An email asking more details has been received or clarification.
P485 is the draft for the answer.

I'll rework the git history and split the diffs in multiple smaller ones.

we really want this first staging vm to live in a dedicated /24 instead of prod's one (192.168.100.0/24),

• init-template: Update documentation about some more needed steps
• prepare-workstation: Fix instructions
• gateway: Instantiate the staging gateway
• storage0: Use the gateway for that node
• staging: Work around the puppet agent non standard exit code
• storage: Push dependency on gateway provisioning

• staging: Add gateway node
• staging: Update macaddress to new one

we really do not want this hardocoded MAC address,