[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#826954: cloud.debian.org: NoCloud datasource not enabled in Debian 8.5 image



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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,
Cheers,

Thomas Goirand (zigo)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXWxL6AAoJENQWrRWsa0P+/UQP/02YLcDQNQQ2POhC/t5cXOOF
I7Z36LpgAYBjXyqdtdAamK8Rt2PWlGkvVufWU8JyfabCwjPtGQeAYEIXT6oojchv
X/EpMOoCXoHZJXj6EzwdbM9IXVEQJ4GQ4t7AOgZW5NgoPu2+d9BHsbvdonuVUsDY
jKQu3jVYPrl+tis6IXAulG0jJgeYA47P72vkIu2IT88pB+2FM2sfv3+YixLs5CC+
rFLBcwNoaqLzmn0EW5SynDjHmpubx+cIue058Y3o/gJfm74vUTy0AbJZL/j/ejcC
vWZwQBKeVMuQU/b3+W5f9PHAa8wkm3w7lhZNmgVJU+fNJr2/JhGEE+ZZM+DHoUk7
HURhorDW7lFdzfv/5zaQyk1pVvUjNna+qcwwIpyY1TkKKAv4UomORRkrzZSN9Z8w
9AeT9oq+3EZcgdGHNckAW4FpeZhMrayoCanW+ieIOXlvHqiSHYMjSKStszR/ic25
PTai7PHuP+Jqe4hGkJDKPhK3kh8KeJUKUTonga05h3Ndg9cEt5ilQIM/qprRfotc
dWpm7a+3i/q7TeEctq+Sh/ZdS+QYY+yhgfgLZ7MV1aqM1l7J63ONA2Jk0LEOjRxM
JFqqgDaA2pFcq1NzlOicnpUCx4G7K1E2wbNN1aHSM4Mzg1zogRm8DpQd3H0OSNrc
kt25VowLiRReNPg7CO2/
=IQsj
-----END PGP SIGNATURE-----


Reply to: