Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add metalctl section to MEP14 #223

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add metalctl section to MEP14 #223

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/src/development/proposals/MEP14/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ So far, the following components have been identified as requiring changes:
- metal-images

More components are likely to be added to the list during processing.
For DNS and NTP servers it should be possible to provide default values within a partition. They can either be inherited from machines and firewalls or overwritten with own ones.

## pixiecore

Expand All @@ -22,4 +23,8 @@ If using a self-deployed NTP server, also the metal-hammer need to be configured

Configurations for the `metal-images` are different for machines and firewalls.

## metalctl

In order to pass DNS and NTP servers to partitions and machines while creating them, the flags `dnsservers` and `ntpservers` need to be added.

The implementation of this MEP will make metal-stack possible to create and maintain machines without requiring an internet connection.