[FFe] ec2 add support for configuring secondary NICs and secondary ipv4 and ipv6 addresses
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
Chad Smith |
Bug Description
Ec2's IMDS metadata reports network configuration for any secondary IPv4 and IPv6 addresses that have been created and attached to any NIC associated with an instance.
cloud-init currently only renders network config on the primary NIC (eth0).
Cloud-init should add network configuration for an additional attached NICs beyond the primary eth0 as well as add static IP configuration for any secondary IPv4 of IPv6 addresses present on each NIC.
This avoids forcing the manual network configuration onto the end-user or image creator after initial system boot for secondary NICs or IP addresses.
To obtain this data from Ec2 IMDS, cloud-init needs to crawl Ec2 metadata version 2018-09-24, if present, to obtain lists of secondary ip addresses from metadata keys "ipv6s" and "local-ipv4s".
Combined with the keys "subnet-
"subnet-
To retain original behavior of stable ubuntu releases, ensure this automatic secondary IP address configuration can also be disabled.
This code change will only impact Ec2 datasources launched on Focal and
can be optionally disabled in an image if undesired.
description: | updated |
description: | updated |
description: | updated |
summary: |
- [FFe] ec2 add support for configuring secondary ipv4 and ipv6 addresses + [FFe] ec2 add support for configuring secondary NICs and secondary ipv4 + and ipv6 addresses |
description: | updated |
description: | updated |
An upstream pull request has been created that should address this bug /github. com/canonical/ cloud-init/ pull/114
https:/