<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/doc/rtd/topics/datasources, branch 20.3</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.3</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.3'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2020-08-13T19:19:22+00:00</updated>
<entry>
<title>doc/rtd/topics/datasources/ovf.rst: fix doc8 errors (#533)</title>
<updated>2020-08-13T19:19:22+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-08-13T19:19:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=545b1c778a036aa973d98aa08453a15f3f872b5a'/>
<id>urn:sha1:545b1c778a036aa973d98aa08453a15f3f872b5a</id>
<content type='text'>
Plus a minor formatting improvement.</content>
</entry>
<entry>
<title>VMware: Support parsing DEFAULT-RUN-POST-CUST-SCRIPT (#441)</title>
<updated>2020-07-21T15:52:29+00:00</updated>
<author>
<name>xiaofengw-vmware</name>
<email>42736879+xiaofengw-vmware@users.noreply.github.com</email>
</author>
<published>2020-07-21T15:52:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=995f8adf00509e5d2aefc9f0680c3c4894ae6666'/>
<id>urn:sha1:995f8adf00509e5d2aefc9f0680c3c4894ae6666</id>
<content type='text'>
Add support for VMware's vCD configuration setting DEFAULT-RUN-POST-CUST-SCRIPT.
When set True, it will default vms to run post customization scripts if the VM has not been configured in VMTools with "enable-custom-scripts" set False.

Add datasource documentation with a bit more context about this interaction on VMware products.

With this fix, the behavior will be:
 * If VM administrator doesn't want others to execute a script on this VM,  VMtools can set "enable-custom-scripts" to false from the utility "vmware-toolbox-cmd".
 * If VM administrator doesn't set value to "enable-custom-scripts", then by default this script is disabled for security purpose.
 * For VMware's vCD product , the preference is to enable the script if "enable-custom-scripts" is not set. vCD will generate a configuration file with "DEFAULT-RUN-POST-CUST-SCRIPT" set to true. This flag works for both VMware customization engine and cloud-init.</content>
</entry>
<entry>
<title>Add mention of vendor-data to no-cloud format documentation (#470)</title>
<updated>2020-07-02T12:52:26+00:00</updated>
<author>
<name>Landon Kirk</name>
<email>landonaddison@yahoo.com</email>
</author>
<published>2020-07-02T12:52:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e31f7fe43aa8f352097c4bb3e97fc3acca8a26b7'/>
<id>urn:sha1:e31f7fe43aa8f352097c4bb3e97fc3acca8a26b7</id>
<content type='text'>
Also add landon912 to .github-cla-signers</content>
</entry>
<entry>
<title>Fix broken link to OpenStack metadata service docs (#467)</title>
<updated>2020-07-02T12:32:15+00:00</updated>
<author>
<name>Matt Riedemann</name>
<email>mriedem.os@gmail.com</email>
</author>
<published>2020-07-02T12:32:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ac422e764af04df799ddad0449da72909e5d1eb1'/>
<id>urn:sha1:ac422e764af04df799ddad0449da72909e5d1eb1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix link to the MAAS documentation (#442)</title>
<updated>2020-06-19T13:25:25+00:00</updated>
<author>
<name>Paride Legovini</name>
<email>paride.legovini@canonical.com</email>
</author>
<published>2020-06-19T13:25:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=615fe62c0927e68349a1cd602c169eb699684f50'/>
<id>urn:sha1:615fe62c0927e68349a1cd602c169eb699684f50</id>
<content type='text'>
LP: #1883666</content>
</entry>
<entry>
<title>Document CloudStack data-server well-known hostname (#399)</title>
<updated>2020-06-09T15:18:29+00:00</updated>
<author>
<name>Gregor Riepl</name>
<email>onitake@gmail.com</email>
</author>
<published>2020-06-09T15:18:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e52ec4ebb8042e3be8c409252f6bbeb1fd767ee2'/>
<id>urn:sha1:e52ec4ebb8042e3be8c409252f6bbeb1fd767ee2</id>
<content type='text'>
* Document CloudStack data-server well-known hostname
* Document fallback to default gateway
* Add onitake to CLA signers list</content>
</entry>
<entry>
<title>DataSourceNoCloud/OVF: drop claim to support FTP (#333)</title>
<updated>2020-04-28T14:34:10+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-04-28T14:34:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f5e1d67bf6faf400749ca192c3394c3356b2654e'/>
<id>urn:sha1:f5e1d67bf6faf400749ca192c3394c3356b2654e</id>
<content type='text'>
I don't believe this has ever been supported, looking at the git
history, but it certainly isn't at the moment.

LP: #1875470</content>
</entry>
<entry>
<title>YAML align indent sizes for docs readability  (#323)</title>
<updated>2020-04-22T18:38:15+00:00</updated>
<author>
<name>Tak Nishigori</name>
<email>nishigori.tak@gmail.com</email>
</author>
<published>2020-04-22T18:38:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1b049e6e51a9ac1ca02bf33629ede5c47c5b1941'/>
<id>urn:sha1:1b049e6e51a9ac1ca02bf33629ede5c47c5b1941</id>
<content type='text'>
This proposal has been aligned in a human readable.

    There are no changes to this except for spac
    The indentation size is not specifically defined in the YAML RFC
        $ make yaml has passed on my-machine

I set the indentation size to the largest number of articles in the repository (dictionary: 2)

(And also include nishigori as a CLA signer.)</content>
</entry>
<entry>
<title>Identify SAP Converged Cloud as OpenStack</title>
<updated>2020-03-26T21:15:37+00:00</updated>
<author>
<name>Silvio Knizek</name>
<email>killermoehre@gmx.net</email>
</author>
<published>2020-03-26T21:15:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=7f9f33dbb08bacaa49244e857847400ad8a67ad4'/>
<id>urn:sha1:7f9f33dbb08bacaa49244e857847400ad8a67ad4</id>
<content type='text'>
add SAP Converged Cloud as cloud provider</content>
</entry>
<entry>
<title>ec2: render network on all NICs and add secondary IPs as static (#114)</title>
<updated>2020-03-18T19:33:37+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2020-03-18T19:33:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6600c642af3817fe5e0170cb7b4eeac4be3c60eb'/>
<id>urn:sha1:6600c642af3817fe5e0170cb7b4eeac4be3c60eb</id>
<content type='text'>
Add support for rendering secondary static IPv4/IPv6 addresses on
any NIC attached to the machine. In order to see secondary IP
addresses in Ec2 IMDS network config, cloud-init now reads metadata
version 2018-09-24. Metadata services which do not support the Ec2
API version will not get secondary IP addresses configured.

In order to discover secondary IP address config, cloud-init now
relies on metadata API Parse local-ipv4s, ipv6s,
subnet-ipv4-cidr-block and subnet-ipv6-cidr-block metadata keys to
determine additional IPs and appropriate subnet prefix to set for a
nic.

Also add the datasource config option apply_full_imds_netork_config
which defaults to true to allow cloud-init to automatically configure
secondary IP addresses. Setting this option to false will tell
cloud-init to avoid setting up secondary IP addresses.

Also in this branch:
 - Shift Ec2 datasource to emit network config v2 instead of v1.

LP: #1866930</content>
</entry>
</feed>
