<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit, branch 20.4</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.4</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2020-11-24T17:38:50+00:00</updated>
<entry>
<title>Release 20.4 (#686)</title>
<updated>2020-11-24T17:38:50+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-11-24T17:38:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=47f4229ebcef9f83df8b549bb869a2dbf6dff17c'/>
<id>urn:sha1:47f4229ebcef9f83df8b549bb869a2dbf6dff17c</id>
<content type='text'>
Bump the version in cloudinit/version.py to 20.4 and
update ChangeLog.

LP: #1905440</content>
</entry>
<entry>
<title>Ability to hot-attach NICs to preprovisioned VMs before reprovisioning (#613)</title>
<updated>2020-11-23T15:04:05+00:00</updated>
<author>
<name>aswinrajamannar</name>
<email>39812128+aswinrajamannar@users.noreply.github.com</email>
</author>
<published>2020-11-23T15:04:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a4d0feb050e32277a218e45bfb6a496d26ff46d0'/>
<id>urn:sha1:a4d0feb050e32277a218e45bfb6a496d26ff46d0</id>
<content type='text'>
Adds the ability to run the Azure preprovisioned VMs as NIC-less and
then hot-attach them when assigned for reprovision.

The NIC on the preprovisioned VM is hot-detached as soon as it reports
ready and goes into wait for one or more interfaces to be hot-attached.
Once they are attached, cloud-init gets the expected number of NICs (in
case there are more than one) that will be attached from IMDS and waits
until all of them are attached. After all the NICs are attached,
reprovision proceeds as usual.</content>
</entry>
<entry>
<title>Support configuring SSH host certificates. (#660)</title>
<updated>2020-11-20T20:59:51+00:00</updated>
<author>
<name>Jonathan Lung</name>
<email>lungj@users.noreply.github.com</email>
</author>
<published>2020-11-20T20:59:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=66b4be8b6da188a0667bd8c86a25155b6f4f3f6c'/>
<id>urn:sha1:66b4be8b6da188a0667bd8c86a25155b6f4f3f6c</id>
<content type='text'>
Existing config writes keys to /etc/ssh after deleting files matching
a glob that includes certificate files. Since sshd looks for
certificates in the same directory as the keys, a host certificate
must be placed in this directory. This update enables the certificate's
contents to be specified along with the keys.

Co-authored-by: jonathan lung &lt;lungj@heresjono.com&gt;
Co-authored-by: jonathan lung &lt;jlung@kepler.space&gt;</content>
</entry>
<entry>
<title>cc_resizefs on FreeBSD: Fix _can_skip_ufs_resize (#655)</title>
<updated>2020-11-19T22:19:16+00:00</updated>
<author>
<name>Mina Galić</name>
<email>me+git@igalic.co</email>
</author>
<published>2020-11-19T22:19:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=12ef7541c2d0c6b2cd510f95fda53ca9c8333064'/>
<id>urn:sha1:12ef7541c2d0c6b2cd510f95fda53ca9c8333064</id>
<content type='text'>
On FreeBSD, if a UFS has trim: (-t) or MAC multilabel: (-l) flag, resize
FS fail, because the _can_skip_ufs_resize check gets tripped up by the
missing options.

This was reported at FreeBSD Bugzilla: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250496 and as
LP: #1901958

Rather than fixing the parser as in the patches proposed there (and
attempted in #636) this pull-request rips out all of it, and simplifies
the code.  We now use `growfs -N` and check if that returns an error. If
it returns the correct kind of error, we can skip the resize, because we
either are at the correct size, or the filesystem in question is broken
or not UFS. If it returns the wrong kind of error, we just re-raise it.

LP: #1901958</content>
</entry>
<entry>
<title>DataSourceAzure: push dmesg log to KVP (#670)</title>
<updated>2020-11-19T18:38:27+00:00</updated>
<author>
<name>Anh Vo</name>
<email>anhvo@microsoft.com</email>
</author>
<published>2020-11-19T18:38:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=73e704e3690611625e3cda060a7a6a81492af9d2'/>
<id>urn:sha1:73e704e3690611625e3cda060a7a6a81492af9d2</id>
<content type='text'>
Pushing dmesg log to KVP to help troubleshoot VM boot issues</content>
</entry>
<entry>
<title>DataSourceAzure: update password for defuser if exists (#671)</title>
<updated>2020-11-19T05:35:46+00:00</updated>
<author>
<name>Anh Vo</name>
<email>anhvo@microsoft.com</email>
</author>
<published>2020-11-19T05:35:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=eea754492f074e00b601cf77aa278e3623857c5a'/>
<id>urn:sha1:eea754492f074e00b601cf77aa278e3623857c5a</id>
<content type='text'>
cc_set_password will only update the password for the default user if
cfg['password'] is set. The existing code of datasource Azure will fail
to update the default user's password because it does not set that
metadata. If the default user doesn't exist in the image, the current
code works fine because the password is set during user create and
not in cc_set_password</content>
</entry>
<entry>
<title>Azure helper: Increase Azure Endpoint HTTP retries (#619)</title>
<updated>2020-11-18T18:02:56+00:00</updated>
<author>
<name>Johnson Shi</name>
<email>Johnson.Shi@microsoft.com</email>
</author>
<published>2020-11-18T18:02:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6df0230b1201d6bed8661b19d8f3758797635377'/>
<id>urn:sha1:6df0230b1201d6bed8661b19d8f3758797635377</id>
<content type='text'>
Increase Azure Endpoint HTTP retries to handle
occasional platform network blips.

Introduce a common method http_with_retries
in the azure.py helper, which will serve as
the common HTTP request handler for
all HTTP requests with the Azure endpoint.
This method has builtin retries and
reporting diagnostics logic.</content>
</entry>
<entry>
<title>DataSourceAzure: send failure signal on Azure datasource failure (#594)</title>
<updated>2020-11-18T17:34:04+00:00</updated>
<author>
<name>Johnson Shi</name>
<email>Johnson.Shi@microsoft.com</email>
</author>
<published>2020-11-18T17:34:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=d807df288f8cef29ca74f0b00c326b084e825782'/>
<id>urn:sha1:d807df288f8cef29ca74f0b00c326b084e825782</id>
<content type='text'>
On systems where the Azure datasource
is a viable platform for crawling metadata,
cloud-init occasionally encounters fatal
irrecoverable errors during the crawling
of the Azure datasource.

When this happens, cloud-init crashes,
and Azure VM provisioning would fail.
However, instead of failing immediately,
the user will continue seeing provisioning
for a long time until it times out with
"OS Provisioning Timed Out" message.

In these situations, cloud-init should
report failure to the Azure datasource
endpoint indicating provisioning failure.
The user will immediately see provisioning
terminate, giving them a much better
failure experience instead of pointlessly
waiting for OS provisioning timeout.</content>
</entry>
<entry>
<title>test_persistence: simplify VersionIsPoppedFromState (#674)</title>
<updated>2020-11-18T16:11:58+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-11-18T16:11:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=96d21dfbee308cd8fe00809184f78da9231ece4a'/>
<id>urn:sha1:96d21dfbee308cd8fe00809184f78da9231ece4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cli: add --system param to allow validating system user-data on a machine (#575)</title>
<updated>2020-11-18T14:23:44+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2020-11-18T14:23:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f680114446a5a20ce88f3d10d966811a774c8e8f'/>
<id>urn:sha1:f680114446a5a20ce88f3d10d966811a774c8e8f</id>
<content type='text'>
Allow root user to validate the userdata provided to the launched
machine using `cloud-init devel schema --system`</content>
</entry>
</feed>
