lp:~smoser/cloud-init/trunk.new-ds
- Get this branch:
- bzr branch lp:~smoser/cloud-init/trunk.new-ds
Branch merges
Branch information
Recent revisions
- 1215. By Scott Moser
-
Paths: fix instance path if datasource's id has a '/'.
If the datasource's instance id contained a '/' then the instance_id path
would not be as expected under /var/lib/cloud/instances /instance_ id. - 1214. By Scott Moser
-
Config Drive: fix check_instance_id signature.
After reboot cloud-init would fail as the previously pickled object
would have a check_instance_id signature but it didn't match expected - 1212. By Scott Moser
-
network: do not write interface as 'auto' from ip= on command line.
When ip= on the kernel command line defines the networking, set
those network devices to be manually controlled, instead of 'auto'.The reason for this is that if they're marked as 'auto':
a.) a second attempt will be made to ifup them.
b.) they'll be brought down on shutdown'b' is problematic on network root filesystem.
Also this picks up 2 changes from curtin's net module:
- Cleanup newline logic so we always have a clean '\n\n' between stanza
- Add a unittest to validate bonding network config render, specifically
when to emit auto $iface for dependent bond slaves. - 1211. By Scott Moser
-
apply networking less often
Do not apply networking configuration whenever a previous datasource
has been loaded from disk and found to be valid (via positive
return 'check_instance_id' or user configuration of manual_cache_clean) . This effectively means that we apply fallback networking only once
per instance rather than every boot on any datasource with
'check_instance_id' implemented. - 1210. By Scott Moser
-
networking: no longer delete eth0.cfg on debian/ubuntu
Ubuntu cloud images in created a file during build that
would interfere with cloud-init's discovered or rendered networking.
To avoid the issues, cloud-init was deleting
/etc/network/interfaces. d/eth0. cfg . The build process no longer creates this file.
However, to address any existing files cloud-init will still remove
the file if it has known content and warn otherwise. - 1209. By Scott Moser
-
fallback net config: do not consider devices starting with 'veth'
Just skip devices that are named veth*.
The fix here is to ignore lxd created devices, but any other veth
device that is created at this point in boot is probably not the
right interface to dhcp on.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~cloud-init-dev/cloud-init/trunk