← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1661797] Re: identify lxd-nova platform to enable Openstack datasource

 

This bug was fixed in the package cloud-init -
0.7.9-23-g0df21b6-0ubuntu1

---------------
cloud-init (0.7.9-23-g0df21b6-0ubuntu1) zesty; urgency=medium

  * New upstream snapshot.
    - support nova-lxd by reading platform from environment of pid 1.
      (LP: #1661797)
    - ds-identify: change aarch64 to use the default for non-dmi systems.
      that default is to enable cloud-init even if no datasources are
      explicitly found.
    - Remove style checking during build and add latest style checks to tox
      [Joshua Powers] (LP: #1652329)
    - code-style: make master pass pycodestyle (2.3.1) cleanly.

 -- Scott Moser <smoser@xxxxxxxxxx>  Thu, 09 Feb 2017 13:18:47 -0500

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  identify lxd-nova platform to enable Openstack datasource

Status in cloud-init:
  Fix Committed
Status in nova-lxd:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in nova-lxd package in Ubuntu:
  Confirmed

Bug description:
  nova-lxd uses the Openstack Network metadata service.

  In an effort to avoid polling metadata services in cloud-init we will disable
  attempts to reach the MD without positive identification of the cloud.

  We need to be able to positively identify that the container we are running
  inside should have access to an openstack metadata service so we can
  safely assume it will be there.

  How can we positively identify that a container is running in nova-lxd?
  Is there anything in the environment (possibly pid 1 environ?) that we
  can look at?

  One way I could see doing t his would be for lxd-nova to put
     CLOUD_PLATFORM='openstack-nova'
  inside the pid 1 environment.  then cloud-init can look at /proc/1/environ
  and pick that out.

  Open to other ideas, and would love it if there was something we could
  do.

  Related bugs
   bug 1660385: Alert user of Ec2 Datasource on lookalike cloud
   bug 1661797: identify lxd-nova platform to enable Openstack datasource
   bug 1661693: identify brightbox platform to enable Ec2 datasource
   bug 1663304: identify openstack kvm platform on arm64

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


References