Configure networking based on EC2 metadata source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Scott Moser | ||
Bug Description
EC2 metadata[1] presents information regarding network devices (mac, name, etc) that would be useful to consume. Chiefly we could match the network device names surfaced in the EC2 UIs (eth0, eth2...) rather than using our own enumeration at boot.
A method to detemermine if we are on an instance in EC2 as been published[2] as part of their documentation so we can now do this in the EC2 datasource without impacting clouds that have copied that datasource.
The work done for DO datasource[3] would be applicable here as a model.
[1] http://
[2] http://
[3] https:/
Related branches
- Scott Moser: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 182 lines (+135/-0)2 files modifiedcloudinit/sources/DataSourceEc2.py (+38/-0)
tests/unittests/test_datasource/test_ec2.py (+97/-0)
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Please be aware of Bug #1637252. On sysconfig based-systems, cloud-init blows up during boot. This is also known as https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1389530