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.

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

Split epoxy.ip= kernel parameter into multiple parameters #7

Open
stephen-soltesz opened this issue Dec 20, 2017 · 2 comments
Open

Comments

@stephen-soltesz
Copy link
Contributor

stephen-soltesz commented Dec 20, 2017

The current format for epoxy.ip= is borrowed from the kernel's built-in format for ip=, which comes from the nfs module. The ip= format has become an unofficial convention among fedora kickstart installations, as well as for some parts of coreos first-boot automation. However, this compact network configuration does not allow us to encode IPv6 addresses.

So, we should split the epoxy.ip= field into these new fields:

  • epoxy.ipv4=<address>,<netmask>,<gateway>
  • epoxy.ipv6=<address>,<netmask>,<gateway>
  • epoxy.interface=<name>[,<auto-conf?>,<other things>]
  • epoxy.hostname=<name>
@stephen-soltesz
Copy link
Contributor Author

Or, how about:

  • epoxy.ipv4=<address>/<mask>,<gateway>,<dns1>,<dns2>
  • epoxy.ipv6=<address>/<mask>,<gateway>,<dns1>,<dns2>

It becomes the responsibility of the receiving code to correctly parse and interpret the address and mask. This is more concise than the long-form netmask. And, probably more natural for ipv6.

@kokosta kokosta removed the backlog label Feb 3, 2018
@stephen-soltesz stephen-soltesz self-assigned this Mar 26, 2018
@stephen-soltesz
Copy link
Contributor Author

Configs & scripts that need to be updated to support the new form:

Configs:

  • stage1to2.ipxe
  • all kargs from later nextboot configs

Scripts:

  • stage2 rc.local
  • mlxupdate & ISO parameters
  • coreos generic network config

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

No branches or pull requests

3 participants