cloud-init

~b1sandmann/cloud-init:migrate-lp-to-github

  1. Git
  2. lp:~b1sandmann/cloud-init
  3. migrate-lp-to-github
Last commit made on 2021-03-03
Get this branch:
git clone -b migrate-lp-to-github https://git.launchpad.net/~b1sandmann/cloud-init
Only Jens Sandmann can upload to this branch. If you are Jens Sandmann please log in for upload directions.

Branch merges

Branch information

Name:
migrate-lp-to-github
Repository:
lp:~b1sandmann/cloud-init

Recent commits

ef8b3cb... by Jens Sandmann

lp-to-git-users: adding B1Sandmann

Mapped from b1sandmann

3be6663... by Thomas Stringer

Add flexibility to IMDS api-version (#793)

Add flexibility to IMDS api-version by having both a desired IMDS
api-version and a minimum api-version. The desired api-version will
be used first, and if that fails it will fall back to the minimum
api-version.

62f7a8b... by Paride Legovini

Fix the TestApt tests using apt-key on Xenial and Hirsute (#823)

* Xenial issue

The `apt-key finger` format changed since Xenial. Sample Xenial output:

pub 4096R/991BC93C 2018-09-17
      Key fingerprint = F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B

Sample Focal output:

pub rsa4096 2016-04-12 [SC]
      EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796

What didn't change is the format of the key fingerprint, which should be
enough to ensure that the right key is in place across all the supported
releases.

* Hirsute issue

TestApt::test_ppa_source also fails on Hirsute because of a difference
in how the PPA keys are added. On Focla this command:

  add-apt-repository ppa:simplestreams-dev/trunk

install /etc/apt/trusted.gpg.d/simplestreams-dev_ubuntu_trunk.gpg, while
on Hirsute the file is names simplestreams-dev-ubuntu-trunk.gpg. The
filename is part of the `apt-key finger` output, and this the test
fails. Only checking for the presence of the key fingerprint in apt-key
also covers this case.

LP: #1916629

a10838a... by vwoodst

doc: remove duplicate "it" from nocloud.rst (#825)

2757333... by Kristian Klausen <email address hidden>

archlinux: Use hostnamectl to set the transient hostname (#797)

hostname (inetutils) isn't installed per default on arch, so switch
to hostnamectl which is installed per default (systemd).

402d98e... by Dermot Bradley

cc_keys_to_console.py: Add documentation for recently added config key (#824)

PR #811 added a new config key, emit_keys_to_console, but didn't update the
documentation for mention it.

695c4f8... by Toshi Aoyama <email address hidden>

Update cc_set_hostname documentation (#818)

It is distro dependent whether hostname or fqdn is used

d873b9d... by Dan Watkins

Release 21.1 (#820)

Bump the version in cloudinit/version.py to 21.1 and
update ChangeLog.

LP: #1916540

a64b738... by Johnson Shi

Azure: Support for VMs without ephemeral resource disks. (#800)

Changes:
* Only merge in default Azure cloud ephemeral disk configs
during DataSourceAzure._get_data() if the ephemeral disk
exists.
* DataSourceAzure.address_ephemeral_resize() (which is
invoked in DataSourceAzure.activate() should only set up
the ephemeral disk if the disk exists.

Azure VMs may or may not come with ephemeral resource disks
depending on the VM SKU. For VM SKUs that come with
ephemeral resource disks, the Azure platform guarantees that
the ephemeral resource disk is attached to the VM before
the VM is booted. For VM SKUs that do not come with
ephemeral resource disks, cloud-init currently attempts
to wait and set up a non-existent ephemeral resource
disk, which wastes boot time. It also causes disk setup
modules to fail (due to non-existent references to the
ephemeral resource disk).

udevadm settle is invoked by cloud-init very early in boot.
udevadm settle is invoked very early, before
DataSourceAzure's _get_data() and activate() methods.

Within DataSourceAzure's _get_data() and activate() methods,
the ephemeral resource disk path should exist if the
VM SKU comes with an ephemeral resource disk.
The ephemeral resource disk path should not exist if the
VM SKU does not come with an ephemeral resource disk.

LP: #1901011

e384a54... by Michael Hudson-Doyle

cc_keys_to_console: add option to disable key emission (#811)

Specifically:

ssh:
  emit_keys_to_console: false

We also port the cc_keys_to_console cloud tests to the new integration
testing framework, and add a test for this new option.

LP: #1915460