<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware, branch current</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=current</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=current'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2022-02-08T14:49:00+00:00</updated>
<entry>
<title>Fix IPv6 netmask format for sysconfig (#1215)</title>
<updated>2022-02-08T14:49:00+00:00</updated>
<author>
<name>Harald</name>
<email>hjensas@redhat.com</email>
</author>
<published>2022-02-08T14:49:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=b97a30f0a05c1dea918c46ca9c05c869d15fe2d5'/>
<id>urn:sha1:b97a30f0a05c1dea918c46ca9c05c869d15fe2d5</id>
<content type='text'>
This change converts the IPv6 netmask from the network_data.json[1]
format to the CIDR style, &lt;IPv6_addr&gt;/&lt;prefix&gt;.

Using an IPv6 address like ffff:ffff:ffff:ffff:: does not work with
NetworkManager, nor networkscripts.

NetworkManager will ignore the route, logging:
  ifcfg-rh: ignoring invalid route at \
    "::/:: via fd00:fd00:fd00:2::fffe dev $DEV" \
    (/etc/sysconfig/network-scripts/route6-$DEV:3): \
    Argument for "::/::" is not ADDR/PREFIX format

Similarly if using networkscripts, ip route fail with error:
  Error: inet6 prefix is expected rather than \
    "fd00:fd00:fd00::/ffff:ffff:ffff:ffff::".

Also a bit of refactoring ...

cloudinit.net.sysconfig.Route.to_string:
* Move a couple of lines around to reduce repeated code.
* if "ADDRESS" not in key -&gt; continute, so that the
  code block following it can be de-indented.
cloudinit.net.network_state:
* Refactors the ipv4_mask_to_net_prefix, ipv6_mask_to_net_prefix
  removes mask_to_net_prefix methods. Utilize ipaddress library to
  do some of the heavy lifting.

LP: #1959148</content>
</entry>
<entry>
<title>Adopt Black and isort (SC-700) (#1157)</title>
<updated>2021-12-16T02:16:38+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-12-16T02:16:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf'/>
<id>urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf</id>
<content type='text'>
Applied Black and isort, fixed any linting issues, updated tox.ini
and CI.
</content>
</entry>
<entry>
<title>VMware: source /etc/network/interfaces.d/* on Debian</title>
<updated>2021-11-18T21:58:06+00:00</updated>
<author>
<name>chengcheng-chcheng</name>
<email>63850735+chengcheng-chcheng@users.noreply.github.com</email>
</author>
<published>2021-11-18T21:58:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=3c6b594b90b0647f398f41962def45fd0953ce5b'/>
<id>urn:sha1:3c6b594b90b0647f398f41962def45fd0953ce5b</id>
<content type='text'>
For Debian, the network configure file was named
/etc/network/interfaces.d/50-cloud-init, not the 50-cloud-init.cfg,
related to
https://github.com/canonical/cloud-init/blob/62721ae71057530e41779ff02ce578b7b802a60f/cloudinit/distros/debian.py#L56
the static IP customization on Debian will fail owing to
"source /etc/network/interfaces.d/*.cfg".
This change will fix this issue.

LP: #1950136</content>
</entry>
<entry>
<title>[VMware] Support cloudinit raw data feature (#691)</title>
<updated>2021-01-13T23:18:28+00:00</updated>
<author>
<name>xiaofengw-vmware</name>
<email>42736879+xiaofengw-vmware@users.noreply.github.com</email>
</author>
<published>2021-01-13T23:18:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=11630044d235e0c6e1ffd2b12ff8906613ccdac6'/>
<id>urn:sha1:11630044d235e0c6e1ffd2b12ff8906613ccdac6</id>
<content type='text'>
This feature will modify VMware datasource to read from meta data and user data which are specified by VMware vSphere user. If meta data/user data are found in cloud-init configuration directory, datasource will parse the meta data/network and user data from the configuration file, otherwise it will continue to parse them from traditional customization configuration file as before. The supported meta data file is in json or yaml format.</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/marekm72/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>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/marekm72/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>cloudinit: remove global disable of pylint W0107 and fix errors (#489)</title>
<updated>2020-07-15T14:26:12+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-07-15T14:26:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=4fe576516d65feda17ba78e9265a8e494a195e7b'/>
<id>urn:sha1:4fe576516d65feda17ba78e9265a8e494a195e7b</id>
<content type='text'>
* cloudinit: remove global disable of pylint W0107 and fix errors

This includes removing a test class which contained no tests but wasn't
detected as empty because of an errant pass statement.

* .pylintrc: update disable comment to match arguments</content>
</entry>
<entry>
<title>When tools.conf does not exist, running cmd "vmware-toolbox-cmd config get deployPkg enable-custom-scripts", the return code will be EX_UNAVAILABLE(69), on this condition, it should not take it as error. (#413)</title>
<updated>2020-06-09T16:20:47+00:00</updated>
<author>
<name>chengcheng-chcheng</name>
<email>63850735+chengcheng-chcheng@users.noreply.github.com</email>
</author>
<published>2020-06-09T16:20:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=c6d09af67626c2f2241c64c10c9e27e8752ba87b'/>
<id>urn:sha1:c6d09af67626c2f2241c64c10c9e27e8752ba87b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Move subp into its own module. (#416)</title>
<updated>2020-06-08T16:49:12+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2020-06-08T16:49:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=3c551f6ebc12f7729a2755c89b19b9000e27cc88'/>
<id>urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88</id>
<content type='text'>
This was painful, but it finishes a TODO from cloudinit/subp.py.

It moves the following from util to subp:
  ProcessExecutionError
  subp
  which
  target_path

I moved subp_blob_in_tempfile into cc_chef, which is its only caller.
That saved us from having to deal with it using write_file
and temp_utils from subp (which does not import any cloudinit things now).

It is arguable that 'target_path' could be moved to a 'path_utils' or
something, but in order to use it from subp and also from utils,
we had to get it out of utils.</content>
</entry>
<entry>
<title>VMWware: support to update guest info gc status if enabled (#261)</title>
<updated>2020-03-26T16:31:04+00:00</updated>
<author>
<name>xiaofengw-vmware</name>
<email>42736879+xiaofengw-vmware@users.noreply.github.com</email>
</author>
<published>2020-03-26T16:31:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=1fefeef92fd1881b21e124b83f2adefd3e014087'/>
<id>urn:sha1:1fefeef92fd1881b21e124b83f2adefd3e014087</id>
<content type='text'>
</content>
</entry>
</feed>
