Skip to content

L3 only#282

Draft
majst01 wants to merge 4 commits into
mainfrom
layer-3-only
Draft

L3 only#282
majst01 wants to merge 4 commits into
mainfrom
layer-3-only

Conversation

@majst01

@majst01 majst01 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Description

DRAFT L3 only network

Please only review the Readme.md, the files in the ai folder where generated during the design process from AI and will be removed in the final MEP. I kept them only for reference during the review process.

Used AI-Tools ✨

  • Qwen3.6 used for generation of ideas in the ai folder.

@metal-robot metal-robot Bot added the area: documentation Affects the documentation area. label Jun 9, 2026
@metal-robot metal-robot Bot added this to Development Jun 9, 2026
@netlify

netlify Bot commented Jun 9, 2026

Copy link
Copy Markdown

Deploy Preview for metal-stack-io ready!

Name Link
🔨 Latest commit d505794
🔍 Latest deploy log https://app.netlify.com/projects/metal-stack-io/deploys/6a33fe195c6ca40009b4ffb0
😎 Deploy Preview https://deploy-preview-282--metal-stack-io.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread community/04-Proposals/MEP20/ai/mep-ra-slaac-boot.md
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md Outdated
Comment thread community/04-Proposals/MEP20/README.md Outdated

## metal-core

metal-core will need to support additional configuration templates for the boot vrf.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also install metal-core in a way that it also talks to metal-apiserver from within this boot-vrf which completely eliminates the need for weird routes on the switches

The L3 only boot and registration process can be described as follows:

- Every server will be scanned on a regular basis from the metal-bmc if there is IPXE is configured as boot iso payload. This is a additional task on the metal-bmc. metal-bmc already scans all servers on a regular basis to gather power metrics etc.
- If the boot iso is set to ipxe, the boot source override must be set to CDROM instead of PXE from network and a reboot must be triggered (migration to this approach, not when a machine is allocated).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we don't plan on removing support for the old PXE boot with this change, it could make sense to track the boot mode of each machine in metal-api. The migration step could then be triggered and tracked by metal-api.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: documentation Affects the documentation area.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

5 participants