<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/systemd/vyos-config-cloud-init.service, branch 1.3.6</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/marekm72/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-1x.git/atom?h=1.3.6</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-1x.git/atom?h=1.3.6'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-1x.git/'/>
<updated>2023-05-04T19:41:40+00:00</updated>
<entry>
<title>cloud-init: T5190: Added Cloud-init pre-configurator</title>
<updated>2023-05-04T19:41:40+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2023-05-04T19:41:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-1x.git/commit/?id=748199b10df112cba0821703001c0307e325bd90'/>
<id>urn:sha1:748199b10df112cba0821703001c0307e325bd90</id>
<content type='text'>
Added a new service that starts before Cloud-init, waits for all network
interfaces initialization, and if requested by config, checks which interfaces
can get configuration via DHCP server and creates a corresponding Cloud-init
network configuration.

This protects from two situations:

* when Cloud-init tries to get meta-data via eth0 (default and fallback variant
for any data source which depends on network), but the real network is connected
to another interface
* when Cloud-init starts simultaneously with udev and initializes the first
interface to get meta-data before it is renamed to eth0 by udev
</content>
</entry>
</feed>
