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

[WIP] providers: add experimental initrd network bootstrap #362

Closed
wants to merge 3 commits into from

Conversation

lucab
Copy link
Contributor

@lucab lucab commented Feb 20, 2020

DRAFT: it is unclear whether we want to provide RHCOS/FCOS on Classic instances, due to overall limitations of Classic infrastructure. Implementation here is complete though, and manually tested.


This adds initial/experimental support for bootstrapping the network
in the initrd. It is meant to support weird cloud providers where
DHCP is not available or not usable.
This feature is currently reachable as a dedicated exp rd-net-bootstrap
subcommand.
The first provider where this logic is required is ibmcloud-classic.

This adds initial/experimental support for bootstrapping the network
in the initrd. It is meant to support weird cloud providers where
DHCP is not available or not usable.
This feature is currently reachable as a dedicated `exp rd-net-bootstrap`
subcommand.
The first provider where this logic is required is `ibmcloud-classic`.
@lucab
Copy link
Contributor Author

lucab commented Aug 13, 2020

Status update: we aren't shipping RHCOS/FCOS to ibmcloud-classic in the end, so this PR is likely not going anywhere.

There is still the larger topic of bringing up the network from a config-drive. I'm not fully convinced Afterburn should go there, I'm currently feeling that NM may be able to take care of that better.

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

Successfully merging this pull request may close these issues.

None yet

1 participant