Last commit made on 2019-08-22
Get this branch:
git clone -b ubuntu/xenial https://git.launchpad.net/~chad.smith/cloud-init
Only Chad Smith can upload to this branch. If you are Chad Smith please log in for upload directions.

Branch merges

Branch information


Recent commits

c8452b9... by Chad Smith 20 hours ago

releasing cloud-init version 19.2-21-ge6383719-0ubuntu1~16.04.1

0e89e35... by Chad Smith 21 hours ago

update changelog (New upstream snapshot 19.2-21-ge6383719).

a3ccba2... by Chad Smith 19 hours ago

debian/cloud-init.templates: enable Exoscale cloud

377002c... by Chad Smith 21 hours ago

update changelog.

fec46db... by Chad Smith 21 hours ago

refresh patches against origin/master commit e6383719

refresh patches against origin/master commit e6383719:

140bf42... by Chad Smith 21 hours ago

merge from origin/master at 19.2-21-ge6383719

e638371... by Chad Smith 22 hours ago

ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA

Emit a script allowing cloud-init to set linux/nvidia/latelink
debconf selection to true. This avoids having to call
debconf-set-selections and allows cloud-init to pre-confgure
linux-restricted-modules to link NVIDIA drivers to the running kernel.

Cloud-init loads this debconf template and sets the value to true in the
debconf database by sourcing debconf's /usr/share/debconf/confmodule and
uses db_x_loadtemplatefile to register cloud-init's setting for

LP: #1840080

3e99827... by Florian Müller <email address hidden> on 2019-08-20

Add missing #cloud-config comment on first example in documentation.

Since this is the first code snippet some users might see,
they could end up in the same situation like me today
when they wonder why their yaml user config is not
working at all.

8587870... by Chad Smith on 2019-08-19

ubuntu-drivers: emit latelink=true debconf to accept nvidia eula

To accept NVIDIA EULA, cloud-init needs to emit latelink=true debconf
setting to the linux-restricted-modules package to allow NVIDIA
drivers to properly link to the running kernel.

LP: #1840080

2c52e6e... by Dan Watkins on 2019-08-19

DataSourceOracle: prefer DS network config over initramfs

The Oracle platform provides networking configuration from two sources:

* the primary interface configuration comes from the initramfs, because
  Oracle instance all iSCSI boot
* secondary interface configuration comes from an IMDS accessed over

As we need to combine these two sources of network configuration, the
default "prefer initramfs config over data source config" behaviour
isn't appropriate; we would never get the IMDS interfaces via that
route. Instead, the Oracle data source has code to combine these two
sources, so we prefer its network configuration over the initramfs

(This is not appropriate default behaviour, because _in general_ data
sources won't know how to merge initramfs-provided configuration into
their provided configuration, so switching this order for all data
sources would result in initramfs configuration being discarded on any
data source that implements network_config.)