Public bug reported: 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. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/924375 Title: cloud-init should allow pre-seeding of ec2 datasource:Ec2:metadata_urls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/924375/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
