(Created page with "This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images.") |
No edit summary |
||
Line 1: | Line 1: | ||
This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images. | This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images. | ||
- configure DHCP, renew dhcp leases | |||
- configure with cloud-init | |||
- configure with traditional RH-ecosystem ifcfg-eth0 file (log warnings for unsupported options) | |||
Questions! | |||
- Q: any need to support more than one interface? | |||
- Q: if single interface, should we standardize on "eth0"" | |||
- Q: dns configuration? | |||
- Q: support static IP (via cloud-init?) |
Revision as of 19:01, 19 August 2015
This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images.
- configure DHCP, renew dhcp leases
- configure with cloud-init
- configure with traditional RH-ecosystem ifcfg-eth0 file (log warnings for unsupported options)
Questions!
- Q: any need to support more than one interface? - Q: if single interface, should we standardize on "eth0"" - Q: dns configuration? - Q: support static IP (via cloud-init?)