** Also affects: nova-lxd
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: nova-lxd
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** 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
+ 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'
+ 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 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
--
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:
Confirmed
Status in nova-lxd:
Confirmed
Status in cloud-init 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1661797/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
