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

Re: NoCloud cloud-init datasource



On Tue, Feb 9, 2016 at 10:36 PM, Cliff Rowley <cliffrowley@gmail.com> wrote:
Straight libvirt/kvm (hence my push for the NoCloud datasource!)
Right, so we can see why there is a mismatch.

I'll leave it the right peeps on this list to comment, however I think what we ideally want to provide is a generic kvm image (in fact not necessarily specific to kvm; just call it a generic image) that only has NoCloud enabled. I think there is room to add in extra datasources (http://cloudinit.readthedocs.org/en/latest/topics/datasources.html) as long as they don't inhibit the boot process and gracefully degrade without delay.

A generic KVM image with NoCloud would be fine with me.  I'm happy building my own images too (have just built one with NoCloud enabled to "see what happens"), but as an end user what I'd really like is to be able to pull and cache an official image.

Its hard to cater for everything no matter how many different types of images you provide, however I'd just like to flag that Ubuntu do this pretty well.

They do, but not without problems - I had some issues with the interfaces configuration in their image (it tries to use both /etc/interfaces and /etc/interfaces.d/* - unsuccessfully).  I guess then init specific images is probably a good thing after all.
Right, I'm not sure if this is related to your problem there but it could be. Change in linux and udev means that network interfaces may not be predictable (which many have argued that is ironic considering the aim of the change).

For example this instead of eth0 depending where you run the image too:

#! /bin/sh
cat <<EOF> /etc/network/interfaces.d/eno16780032.cfg
# The primary network interface
auto eno16780032
iface eno16780032 inet dhcp
EOF


If the 'generic' image is configured for eth0 you won't have networking.

Reply to: