yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

I wonder why an openstack project would not configure images built to
run on openstack to use the openstack metadata service.  Is there a
reason?  Generally speaking I think it should perform much better as the
openstack metadata service is often quite slow.  Cloud-init crawls the
metadata service and on openstack that will take probably 6 requests
while EC2 will take several more.  (Openstack provides lots of data in
json format in a single payload while Ec2 provides individual bits in
individual urls).

All that said, I'll consider it a bug that if you have only 1 or 2 entries
in the datasource list that Ec2 strict should be assumed.


** Also affects: cloud-init
   Importance: Undecided
       Status: New

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

** Changed in: cloud-init
       Status: New => Confirmed

** Tags added: dsid

-- 
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/1683038

Title:
  Need to convince cloud-init we really want Ec2 datasource

Status in cloud-init:
  Confirmed
Status in diskimage-builder:
  Fix Released

Bug description:
  cloud-init was recently changed to be more selective about the types
  of data source it wants to access.  See https://bugs.launchpad.net
  /cloud-init/+bug/1660385.  In particular, when it is run on a non-EC2
  cloud and sees EC2 metadata, it recently started to print annoying
  warnings to the user.

  When we add the "Ec2" datasource to images, we should also generate a
  workaround that suppresses the warning.  According to the warning
  itself, this can be achieved by adding a file
  /etc/cloud/cloud.cfg.d/99-ec2-datasource.cfg that says

    #cloud-config
    datasource:
     Ec2:
      strict_id: false

  An alternative would be to live with the warnings, and hope that DIB
  users select other datasources in preference of Ec2, for example
  OpenStack and/or ConfigDrive.

  Another option would be to convince the cloud-init developers that
  OpenStack clouds can be expected to provide the Ec2 metadata service,
  and that there's no need to issue warnings about that.

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