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

[Scott Moser]

Marking fix-released in nova-lxd  in zesty.

** Description changed:

  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
+  bug 1663304: identify openstack kvm platform on arm64
+  bug 1668313: [SRU] mitaka point release

** Changed in: nova-lxd (Ubuntu Zesty)
       Status: Confirmed => Fix Released

** Changed in: nova-lxd (Ubuntu Yakkety)
       Status: Confirmed => In Progress

** Changed in: nova-lxd (Ubuntu Xenial)
       Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova-lxd in Ubuntu.
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:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in nova-lxd source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed
Status in nova-lxd source package in Yakkety:
  In Progress
Status in cloud-init source package in Zesty:
  Fix Released
Status in nova-lxd source package in Zesty:
  Fix Released

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
   bug 1668313: [SRU] mitaka point release

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