I see a distinction between disabling user-supplied metadata, and not
automatically injecting /etc/network/interfaces or ssh_key if we're relying
on cloud-init to populate that info.
On Thu, Feb 23, 2012 at 1:01 PM, Dan Prince <email address hidden> wrote:
> Hi Justin,
>
> Would something like this work:
>
> https://review.openstack.org/#change,4430
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/939798
>
> Title:
> Injection should not happen with metadata service
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> I'm trying out the "official" way to do injection of keys etc.
>
> It looks like if I specify an SSH key, and I'm using the metadata
> service, the key is still injected into the image; it also doesn't
> look like there's a flag to turn that off.
>
> I think there should be a flag "no_inject" or similar.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/939798/+subscriptions
>
Looks good to me!
I see a distinction between disabling user-supplied metadata, and not interfaces or ssh_key if we're relying
automatically injecting /etc/network/
on cloud-init to populate that info.
On Thu, Feb 23, 2012 at 1:01 PM, Dan Prince <email address hidden> wrote:
> Hi Justin, /review. openstack. org/#change, 4430 /bugs.launchpad .net/bugs/ 939798 /bugs.launchpad .net/nova/ +bug/939798/ +subscriptions
>
> Would something like this work:
>
> https:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Injection should not happen with metadata service
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> I'm trying out the "official" way to do injection of keys etc.
>
> It looks like if I specify an SSH key, and I'm using the metadata
> service, the key is still injected into the image; it also doesn't
> look like there's a flag to turn that off.
>
> I think there should be a flag "no_inject" or similar.
>
> To manage notifications about this bug go to:
> https:/
>