Multiple Interfaces and IPs not detected in AWS VPC
Bug #1153626 reported by
Michael Hale
This bug affects 17 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I booted a c1.medium with ami-3fec7956, 2 interfaces and 2 IPs per interface. I expected the 4 IPs to be configured on the instance when I logged in, however only the primary interface had a single IP assigned.
DHCP does not seem to support multiple IPs per interface so the alias IPs will probably need to be statically assigned based on the EC2 meta-data API (http://
Additionally since network interfaces, and their IPs, can be moved between running instances in VPC, any solution should detect hot-plug events and not just setup things at boot time.
Related branches
~chad.smith/cloud-init:feature/ec2-secondary-nics
On hold
for merging
into
cloud-init:master
- Server Team CI bot: Approve (continuous-integration)
- cloud-init Commiters: Pending requested
-
Diff: 463 lines (+210/-75)3 files modifiedcloudinit/sources/DataSourceEc2.py (+47/-15)
doc/rtd/topics/datasources/ec2.rst (+3/-0)
tests/unittests/test_datasource/test_ec2.py (+160/-60)
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: |
added: ec2-images removed: ec2 |
To post a comment you must log in.
Thanks for taking the time to open a bug and make ubuntu better.
When multiple interfaces and IPs first came out, I looked at this, but yours is the first request for this.
I agree, I'd like to have a udev hook that would fire on interface adaded and then determine if it was in EC2, and if so, hit the EC2 metadata service and configure the device. That'd be smooth.
I'm more than happy to review and help out, but its not something that will be high priority on my plate at the moment.