yahoo-eng-team team mailing list archive

[Chad Smith <1709772@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In EC2 clouds, the only way to determine whether an instance is
configured for IPv6 is by querying the metadata service. In order to
query metadata to determine network configuration, DataSourceEc2 needs
to configure the network with dhcp and then query the datasource.

Add optional functionality for DataSourceEc2 to query metatadata sevice
in init-local timeframe using dhcp.

** Affects: cloud-init
     Importance: Medium
     Assignee: Chad Smith (chad.smith)
         Status: Fix Committed

** Changed in: cloud-init
       Status: New => In Progress

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
     Assignee: (unassigned) => Chad Smith (chad.smith)

** Merge proposal linked:
   https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/328241

** Changed in: cloud-init
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1709772

Title:
  EC2 datasource moved to init-local stage

Status in cloud-init:
  Fix Committed

Bug description:
  In EC2 clouds, the only way to determine whether an instance is
  configured for IPv6 is by querying the metadata service. In order to
  query metadata to determine network configuration, DataSourceEc2 needs
  to configure the network with dhcp and then query the datasource.

  Add optional functionality for DataSourceEc2 to query metatadata
  sevice in init-local timeframe using dhcp.

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