~sankaraditya/cloud-init:topic-stanguturi-vmware-etc-hosts

Last commit made on 2017-09-14
Get this branch:
git clone -b topic-stanguturi-vmware-etc-hosts https://git.launchpad.net/~sankaraditya/cloud-init
Only Sankar Tanguturi can upload to this branch. If you are Sankar Tanguturi please log in for upload directions.

Branch merges

Branch information

Name:
topic-stanguturi-vmware-etc-hosts
Repository:
lp:~sankaraditya/cloud-init

Recent commits

a90b09b... by Sankar Tanguturi on 2017-09-14

  Do not set 'manage_etc_hosts' option.

  Check the comments in
  https://code.launchpad.net/~sankaraditya/cloud-init/+git/cloud-init/+merge/330608
  for more details. Decided not to set 'manage_etc_hosts' option.

7ac713d... by Sankar Tanguturi on 2017-09-11

  Modify /etc/hosts file for VMware Customization.

  Set manage_etc_hosts flag to True so that cloud-init will take
  care of updating /etc/hosts files accordingly.
  The NICS should be enabled before sending the 'SUCCESS' event to
  the underlying hypervisor. Made necessary changes.

a1dfdda... by Sankar Tanguturi on 2017-09-08

vmware customization: return network config format

For customizing the machines hosted on 'VMWare' hypervisor, the datasource
should return the 'network config' data in 'curtin' format.

This branch also fixes /etc/network/interfaces replacing the line
"source /etc/network/interfaces.d/*.cfg" which is incorrectly removed
when VMWare's Perl Customization Engine writes /etc/network/interfaces.

Modify the code to read the customization configuration and return the
converted data.

Added few tests.

LP: #1675063

922c3c5... by Scott Moser on 2017-09-07

Ec2: only attempt to operate at local mode on known platforms.

This change makes the DataSourceEc2Local do nothing unless it is on
actual AWS platform. The motivation is twofold:

a.) It is generally safer to only make this function available to Ec2
clones that explicitly identify themselves to the guest. (It also
gives them a reason to supply identification code to cloud-init.)

b.) On non-intel OpenStack platforms ds-identify would enable both the Ec2
and OpenStack sources. That is because there is not good data (such as
dmi) to positively identify the platform. Previously that would be fine
as OpenStack would run first and be successful. The change to add Ec2Local
meant that an Ec2 now runs first.

The best case for 'b' would be a slow down as attempts at the Ec2 metadata
service time out. The discovered case was worse.

Additionally we add a simple check for datatype of 'network' in the
metadata before attempting to read it.

LP: #1715128

409918f... by Scott Moser on 2017-08-29

Use /run/cloud-init for tempfile operations.

During boot, the usage of /tmp is not safe. In systemd systems,
systemd-tmpfiles-clean may run at any point and clear out a temp file
while cloud-init is using it. The solution here is to use
/run/cloud-init/tmp.

LP: #1707222

dcbb901... by Scott Moser on 2017-09-05

ds-identify: Make OpenStack return maybe on arch other than intel.

OpenStack Nova identifies itself only to Intel guests.
Make ds-identify return 'MAYBE' for OpenStack on non-intel arches.

An unnecessary change here is to rename the 'policy_nodmi' kwarg
to 'policy_no_dmi' in the related unit tests.

LP: #1715241

5582e4a... by Chad Smith on 2017-09-06

tests: mock missed openstack metadata uri network_data.json

This missed mock in test_openstack resulted in a costly unit test timeout.

LP: #1714376

a3649e0... by Lars Kellogg-Stedman on 2017-09-05

relocate tests/unittests/helpers.py to cloudinit/tests

This moves the base test case classes into into cloudinit/tests and
updates all the corresponding imports.

653c0b4... by Joshua Powers on 2017-09-01

tox: add nose timer output

This adds the output of the nose timer plugin to the py3 environment to
tox. This will print out the 10 longest running tests and automatically
turn tests longer than 1 second "red" after the coverage output.

fa266bf... by Scott Moser on 2017-09-01

upstart: do not package upstart jobs, drop ubuntu-init-switch module.

The ubuntu-init-switch module allowed the use to launch an instance that
was booted with upstart and have it switch its init system to systemd and
then reboot itself. It was only useful for the time period when Ubuntu was
transitioning to systemd but only produced images using upstart.

Also, do not run setup with --init-system=upstart. This means that by
default, debian packages built with packages/bddeb will not have upstart
unit files included. No other removal is done here.