< Cloud
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
- Q: dns configuration? | - Q: dns configuration? | ||
- Q: support static IP (via cloud-init?) | - Q: support static IP (via cloud-init?) | ||
Several use cases in EC2 involve instances with multiple network interfaces and occasionally multiple addresses on a single interface. I do not believe all of those need to be configured automatically, but it ought to remain possible for a user/script/etc to make network configuration changes that persist across reboots. | |||
[[User:Gholms|Gholms]] ([[User talk:Gholms|talk]]) 05:49, 27 August 2015 (UTC) | |||
Revision as of 05:49, 27 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?)
Several use cases in EC2 involve instances with multiple network interfaces and occasionally multiple addresses on a single interface. I do not believe all of those need to be configured automatically, but it ought to remain possible for a user/script/etc to make network configuration changes that persist across reboots.