cloud-init should allow pre-seeding of ec2 datasource:Ec2:metadata_urls

[Scott Moser]

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_cache_clean'. Then, you could essentially pre-seed cloud-config that looked like:

manual_cache_clean: True
datasource:
 Ec2:
  metadata_urls: [ http://192.168.1.131:80/abcdefg ]

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_cache_clean' is less important here, because you could easily have cloud-config or cloud-init data served by the metadata service populate that value in /etc/cloud/cloud.cfg.d.

[Launchpad Janitor (janitor)]

This bug was fixed in the package cloud-init - 0.6.3~bzr539-0ubuntu1

---------------
cloud-init (0.6.3~bzr539-0ubuntu1) precise; urgency=low

  * New upstream snapshot.
    * add ability to configure Acquire::http::Pipeline-Depth via
      cloud-config setting 'apt_pipelining' (LP: #942061)
    * if cloud-config settings removed default certificats
      (remove-defaults), then seed package ca-certificates to not
      install new ones on upgrade.
    * run-parts now uses internal implementation rather than
      separate command.
    * add MaaS datasource (LP: #942061)
  * debian/cloud-init.postinst: address population of apt_pipeline
    setting on installation.
  * debian/cloud-init.postinst: support configuring cloud-init
    maas datasource via preseed values cloud-init/maas-metadata-url and
    cloud-init/maas-credentials. (LP: #942061)
  * debian/cloud-init.postinst: support for (LP: #924375)
 -- Scott Moser <email address hidden> Fri, 09 Mar 2012 16:37:01 -0500