~raharper/cloud-init:ubuntu/devel/newupstream-20180914

Last commit made on 2018-09-14
Get this branch:
git clone -b ubuntu/devel/newupstream-20180914 https://git.launchpad.net/~raharper/cloud-init
Only Ryan Harper can upload to this branch. If you are Ryan Harper please log in for upload directions.

Branch merges

Branch information

Name:
ubuntu/devel/newupstream-20180914
Repository:
lp:~raharper/cloud-init

Recent commits

d418088... by Ryan Harper

releasing cloud-init version 18.3-44-g84bf2482-0ubuntu1

be7f59a... by Ryan Harper

update changelog (New upstream snapshot 18.3-44-g84bf2482).

e6933f2... by Ryan Harper

merge from upstream/master at 18.3-44-g84bf2482

84bf248... by Scott Moser

bash_completion/cloud-init: fix shell syntax error.

A syntax error creeped in with commit c7555762f3a3.

12066fc... by Scott Moser

EphemeralIPv4Network: Be more explicit when adding default route.

On OpenStack based OVH public cloud, we got DHCP response with
  fixed-address 54.36.113.86;
  option subnet-mask 255.255.255.255;
  option routers 54.36.112.1;

The router clearly is not on the subnet. So 'ip' would fail when
we tried to add the default route.
The solution here is to add an explicit route on that interface
to the router and then add the default route.

Also add 'bgpovs' to the list of 'physical' types for OpenStack
network configuration. That type is used on OVH public cloud.

LP: #1792415

4361e0e... by Scott Moser

OpenStack: support reading of newer versions of metdata.

Mark as supported for reading some newer versions of openstack metadata:
 2016-06-30 : Newton one
 2016-10-06 : Newton two
 2017-02-22 : Ocata
 2018-08-27 : Rocky

c75c582... by Scott Moser

OpenStack: fix bug causing 'latest' version to be used from network.

Cloud-init was reading a list of versions from the OpenStack metadata
service (http://169.254.169.254/openstack/) and attempt to select the
newest known supported version. The problem was that the list
of versions was not being decoded, so we were comparing a list of
bytes (found versions) to a list of strings (known versions).

LP: #1792157

c755576... by Chad Smith

user-data: jinja template to render instance-data.json in cloud-config

Allow users to provide '## template: jinja' as the first line or their
#cloud-config or custom script user-data parts. When this header exists,
the cloud-config or script will be rendered as a jinja template.

All instance metadata keys and values present in
/run/cloud-init/instance-data.json will be available as jinja variables
for the template. This means any cloud-config module or script can
reference any standardized instance data in templates and scripts.

Additionally, any standardized instance-data.json keys scoped below a
'<v#>' key will be promoted as a top-level key for ease of reference in
templates. This means that '{{ local_hostname }}' is the same as using the
latest '{{ v#.local_hostname }}'.

Since instance-data is written to /run/cloud-init/instance-data.json, make
sure it is persisted across reboots when the cached datasource opject is
reloaded.

LP: #1791781

0e8a1bc... by Ryan Harper

releasing cloud-init version 18.3-39-g757247f9-0ubuntu1

344f69a... by Ryan Harper

update changelog (New upstream snapshot 18.3-39-g757247f9).