cloud-init should allow pre-seeding of ec2 datasource:Ec2:metadata_urls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
it would be best if cloud-init supported pre-seeding of the ec2 metadata url.
This way, something coordinating the installation could cleanly specify through a preseed the location of the metadata url.
It might also make sense to be able to pre-seed 'manual_
manual_cache_clean: True
datasource:
Ec2:
metadata_urls: [ http://
where the path was a uuid or something, and on subsequent boots cloud-init would not need that url to be present.
Note, though, that 'manual_
Related branches
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: rls-p-tracking |
Changed in cloud-init (Ubuntu): | |
assignee: | nobody → Scott Moser (smoser) |
status: | New → In Progress |
This bug was fixed in the package cloud-init - 0.6.3~bzr539- 0ubuntu1
--------------- bzr539- 0ubuntu1) precise; urgency=low
cloud-init (0.6.3~
* New upstream snapshot. :http:: Pipeline- Depth via remove- defaults) , then seed package ca-certificates to not cloud-init. postinst: address population of apt_pipeline cloud-init. postinst: support configuring cloud-init maas-metadata- url and init/maas- credentials. (LP: #942061) cloud-init. postinst: support for (LP: #924375)
* add ability to configure Acquire:
cloud-config setting 'apt_pipelining' (LP: #942061)
* if cloud-config settings removed default certificats
(
install new ones on upgrade.
* run-parts now uses internal implementation rather than
separate command.
* add MaaS datasource (LP: #942061)
* debian/
setting on installation.
* debian/
maas datasource via preseed values cloud-init/
cloud-
* debian/
-- Scott Moser <email address hidden> Fri, 09 Mar 2012 16:37:01 -0500