[Bug 1153626] Re: Multiple Interfaces and IPs not detected in AWS VPC

Michael Hale mike at hales.ws
Tue Mar 19 04:34:38 UTC 2013


My current thinking is that a udev rule will need to have a RUN hook
that updates /etc/network/interfaces or at a minimum runs the
appropriate ip commands based on what is discovered in the EC2 metadata
service. It seems like updating /etc/network/interfaces would be good
since ifup/ifdown rely on its configuration. According to the VPC docs
(http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-
eni.html#detach_eni) it appears that eth0 can *not* be removed from a
running instance while eth1 may be removed or added while the machine is
running. However, it is unclear if additional VIPs can be added to eth0
while the instance is running. I'm not sure how changes to the available
IPs would be detected without polling the meta-data service.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1153626

Title:
  Multiple Interfaces and IPs not detected in AWS VPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions



More information about the Ubuntu-server-bugs mailing list