<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers, 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-23T15:04:05+00:00</updated>
<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>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>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>azure: enable pushing the log to KVP from the last pushed byte  (#614)</title>
<updated>2020-11-04T19:51:16+00:00</updated>
<author>
<name>Moustafa Moustafa</name>
<email>momousta@microsoft.com</email>
</author>
<published>2020-11-04T19:51:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c86283f0d9fe8a2634dc3c47727e6218fdaf25e2'/>
<id>urn:sha1:c86283f0d9fe8a2634dc3c47727e6218fdaf25e2</id>
<content type='text'>
This allows the cloud-init log to be pushed multiple times during boot,
with the latest lines being pushed each time.</content>
</entry>
<entry>
<title>Fix not sourcing default 50-cloud-init ENI file on Debian (#598)</title>
<updated>2020-11-03T14:47:03+00:00</updated>
<author>
<name>WebSpider</name>
<email>WebSpider@users.noreply.github.com</email>
</author>
<published>2020-11-03T14:47:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=7978feb3af5846a1a2ac489cde83febe975b046d'/>
<id>urn:sha1:7978feb3af5846a1a2ac489cde83febe975b046d</id>
<content type='text'>
* Include both Ubuntu-style cfg file, and Debian-style directory in ENI
* Add WebSpider as contributor</content>
</entry>
<entry>
<title>cloudinit: move dmi functions out of util (#622)</title>
<updated>2020-11-02T20:41:11+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2020-11-02T20:41:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=0af1ff1eaf593c325b4f53181a572110eb016c50'/>
<id>urn:sha1:0af1ff1eaf593c325b4f53181a572110eb016c50</id>
<content type='text'>
This just separates the reading of dmi values into its own file.

Some things of note:
 * left import of util in dmi.py only for 'is_container'
   It'd be good if is_container was not in util.
 * just the use of 'util.is_x86' to dmi.py
 * open() is used directly rather than load_file.</content>
</entry>
<entry>
<title>Explicit set IPV6_AUTOCONF and IPV6_FORCE_ACCEPT_RA on static6 (#634)</title>
<updated>2020-10-29T14:05:42+00:00</updated>
<author>
<name>Eduardo Otubo</name>
<email>otubo@redhat.com</email>
</author>
<published>2020-10-29T14:05:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b46e4a8cff667c8441622089cf7d57aeb88220cd'/>
<id>urn:sha1:b46e4a8cff667c8441622089cf7d57aeb88220cd</id>
<content type='text'>
The static and static6 subnet types for network_data.json were
being ignored by the Openstack handler, this would cause the code to
break and not function properly.

As of today, if a static6 configuration is chosen, the interface will
still eventually be available to receive router advertisements or be set
from NetworkManager to wait for them and cycle the interface in negative
case.

It is safe to assume that if the interface is manually configured to use
static ipv6 address, there's no need to wait for router advertisements.
This patch will set automatically IPV6_AUTOCONF and IPV6_FORCE_ACCEPT_RA
both to "no" in this case.

This patch fixes the specific behavior only for RHEL flavor and
sysconfig renderer. It also introduces new unit tests for the specific
case as well as adjusts some existent tests to be compatible with the
new options. This patch also addresses this problem by assigning the
appropriate subnet type for each case on the openstack handler.

rhbz: #1889635
rhbz: #1889635

Signed-off-by: Eduardo Otubo otubo@redhat.com</content>
</entry>
<entry>
<title>azure: clean up and refactor report_diagnostic_event (#563)</title>
<updated>2020-10-15T14:19:57+00:00</updated>
<author>
<name>Johnson Shi</name>
<email>Johnson.Shi@microsoft.com</email>
</author>
<published>2020-10-15T14:19:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3b05b1a6c58dfc7533a16f795405bda0e53aa9d8'/>
<id>urn:sha1:3b05b1a6c58dfc7533a16f795405bda0e53aa9d8</id>
<content type='text'>
This moves logging into `report_diagnostic_event`, to clean up its callsites.</content>
</entry>
<entry>
<title>cloudinit: remove unused LOG variables (#574)</title>
<updated>2020-09-16T13:53:09+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-09-16T13:53:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=22220e200a43f9a172e1abac93907b48d60d3ee0'/>
<id>urn:sha1:22220e200a43f9a172e1abac93907b48d60d3ee0</id>
<content type='text'>
Co-authored-by: Rick Harding &lt;rharding@mitechie.com&gt;</content>
</entry>
</feed>
