lp:~smoser/cloud-init/trunk.improve-wait

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~cloud-init-dev/cloud-init/trunk at revision 1190

Dimitri John Ledkov (community): Approve on 2016-03-29

Martin Pitt (community): Approve on 2016-03-29

cloud-init Commiters: Pending requested 2016-03-28

Diff: 33 lines (+5/-8)

1 file modified

udev/cloud-init-wait (+5/-8)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1190. By Scott Moser on 2016-03-28

improve how cloud-init-wait waits

since we run from a udev event, this is sufficient.
udev settle will exit when either of
 a.) the file exists
 b.) the udev event queue has all been processed.

Since cloud-init-wait is being run as a udev event, 'b' cannot
be satisfied until it finishes. Thus, this essentially becomes a
inotify based wait for the file /run/cloud-init/network-config-ready
and no loops are needed.

1189. By Scott Moser on 2016-03-24

support network configuration in cloud-init --local

this allows 'cloud-init --local' to fully run before networking comes up.
By doing so, we can now cleanly apply networking to the new system.

This adds support for reading ConfigDrive network configuration
and also from NoCloud. The support is only present for ubuntu/debian
at the current time. Other distros will follow.

Also ability to specify network configuration on kernel command line
via either ip= or network-config=<base64>.

1188. By Scott Moser on 2016-03-22

quickly check to see if the previous instance id is still valid

This adds a check in cloud-init to see if the existing (cached)
datasource is still valid. It relies on support from the Datasource
to implement 'check_instance_id'. That method should quickly determine
(if possible) if the instance id found in the datasource is still valid.

This means that we can still notice new instance ids without
depending on a network datasource on every boot.

I've also implemented check_instance_id for the superclass and for
sources:
  DataSourceAzure (check dmi data)
  DataSourceConfigDrive (check dmi data)
  DataSourceNocloud (check the seeded data or kernel command line)
  DataSourceOpenstack (check dmi data)

1187. By Scott Moser on 2016-03-18

debian packaging: adjust build-depends for xenial

python3 support was moved out of pyflakes into python3-pyflakes.
Adjust the package to build on trusty where python3-pyflakes was
not present and also on xenial where it is.

Note, this does mean that sbuild now requires '--resolve-alternatives'.
That is how it is used on launchpad but is not the default in sbuild.

1186. By Scott Moser on 2016-03-17

Send proper SUCCESS / FAILED events to the underlying VMware hypervisor.

Added code to customize timezone.
Added few utility functions to send events to the VMware hypervisor.
Re-factored the code little bit.
Added code to send SUCCESS event when customization succeeds.
Added code to send FAILED event if any error occurs during customization.

1185. By Scott Moser on 2016-03-14

fix ssh_pwauth behavior to function as documented.

Add option checking for ssh_pwauth to bring behavior inline with the
description cloud-config.txt example.

Previously, setting 'ssh_pwauth' to 'unchanged' or '' would result
in an empty value for PasswordAuthentication when it should have
simply not been modified.

1184. By Scott Moser on 2016-03-14

doc/ add new logo to rtd (read the docs) docs.

1183. By Scott Moser on 2016-03-14

doc: document that volume label must be 'cidata' NocCloud datasource.

1182. By Scott Moser on 2016-03-14

some systemd cleanups

 generator:
  * write to directory /run/cloud-init/ rather than /run
  * read from /proc/1/cmdline for the command line if inside a container

 cloud-init-local.service: now run fully before any networking comes up.
 cloud-init.service: run before network-online.target and after
    networking.service. This ends up meaning other things that require
    network-online.target will run after cloud-init.service, but
    cloud-init.service will still have networking.

    The 'networking.service' is ifupdown specific. Further changes would
    be needed for other networking systems (networkd for example)

1181. By Scott Moser on 2016-03-14

change return value for dmi data of all \xff to be ""

Previously we returned a string of "." the same length as the dmi field.
That seems confusing to the user as "." would seem like a valid response
when in fact this value should not be considered valid.

So now, in this case, return empty string.