I'm using cloud-init on CentOS, but would really like this functionality
as well. For the time being, I'll be trying to reuse the upstream AWS
pieces.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
We're using a variant Alessandro's work to configure out instances.
https://github.com/instacart/ubuntu-ec2net
Reboot doesn't seem to refresh the interfaces list -- maybe there is
another event hook that we need? I'm not terribly familiar with udev but
would love to see this ironed out and ready
I'm attaching ec2-utils-0.4-1.19.amzn1.src.rpm as I retrieved it with:
get_reference_source -p ec2-net-utils
from inside ami-83e4bcea (amazon/amzn-ami-pv-2013.09.1.x86_64-ebs) today.
The license per spec file and headers is 'Apache License 2.0'.
** Attachment added:
adding also as a tarball of the rpmbuild dir after rpm -Uvh (jsut for
convenience).
** Attachment added: tarball of rpmbuild after install of
ec2-utils-0.4-1.19.amzn1.src.rpm
Fixed some bugs. New version here
https://github.com/ademaria/ubuntu-ec2net
--
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
Hi Forest,
looking at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-
eni.html#ec2-net-utils
DHCP script
Whenever the network interface receives a new DHCP lease, this script queries
the instance metadata for Elastic IP addresses. For each Elastic IP address, it
adds a rule to the
Hi,
I have actually adapted the files from the Amazon AMI which are working just
fine.
There is also an ansible file which tells where the files should be dropped.
You might need to adjust a few things but it should all be working
There is only a problem with this bug
Re-uploading attachment as solution
** Attachment added: Re-uploading attachment as solution
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1153626/+attachment/3925065/+files/bug_1153626.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:~lfaraone/+junk/configure-interfaces
--
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
Forest,
Thanks for the link. I hadn't seen that utility. It does appear to be doing
basically what I was suggesting.
--
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
Sure. The part that stood out to me was refreshes secondary IP
addresses during DHCP lease renewal. I haven't examined Amazon's code,
but that description reads like it solves the problem of automatically
configuring additional IP addresses without requiring additional network
interfaces.
--
I'm in a similar situation: An ec2 instance with just one network
interface, to which I have assigned a secondary IP address.
This bit from the AWS docs is interesting:
If you are using Amazon Linux, the ec2-net-utils package can take care
of this step for you. It configures additional network
** Changed in: cloud-init
Status: New = Triaged
** Changed in: cloud-init
Importance: Undecided = Medium
--
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:
Adding notes from IRC:
* use 'manual eth1' to avoid cloud-init blocking on boot waiting for interfaces
* /etc/network/interfaces originates from a hardcoded file in the image
* cloud-init places /etc/cloud/on-ec2 (or similar) flag file
* on interface add/remove have a rule that fires, checks ec2
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
Scott, thanks for the reply. This is not something I need at the moment,
but it does seem like a good way for me to perhaps learn more about
Ubuntu network configuration and udev rules. I did a bit of digging and
found the following files which seem relevant:
/lib/udev/write_net_rules
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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
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,
18 matches
Mail list logo
