On 06/10/2016 11:35 PM, Clint Byrum wrote: > Excerpts from Thomas Goirand's message of 2016-06-10 21:20:30 +0200: >> On 06/10/2016 03:42 PM, Benjamin Drung wrote: >>> Package: cloud.debian.org >>> Severity: normal >>> >>> Hi, >>> >>> the cloud image debian-8.5.0-openstack-amd64.qcow2 [1] does not enable >> the >>> NoCloud datasource: >>> >>> --------<8--------- >>> root@debian:~# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg >>> # to update this file, run dpkg-reconfigure cloud-init >>> datasource_list: [ConfigDrive, Openstack, Ec2] >>> root@debian:~# dpkg-reconfigure cloud-init >>> root@debian:~# cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg >>> # to update this file, run dpkg-reconfigure cloud-init >>> datasource_list: [ NoCloud, AltCloud, CloudStack, ConfigDrive, Ec2, MA >> AS, OVF, GCE, None ] >>> --------<8--------- >>> >>> Please enable the NoCloud datasource (and maybe others). >> >> Hi, >> >> I can enable so many source, yes, but what would be the use case of them >> all? Isn't there is a drawback if I do activate all of the above >> mentioned sources? Or do you believe it's fine to just use all of that? >> >> Please let me know and I'll do as suggested, > > NoCloud is quite useful for making use of cloud-init when file-injection > is the only option for an image boot, but one wants to still use > cloud-init's features for some reason. > > Unlike some of the others that poll network addresses, this one is pretty > close to free. It just looks for a couple of files in /var. > > Ok, so would it be nice to do: datasource_list: [NoCloud, ConfigDrive, Openstack, Ec2] and then nothing else? Any other suggestion? Cheers, Thomas Goirand (zigo)
Attachment:
signature.asc
Description: OpenPGP digital signature