<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware, branch 20.3</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=20.3</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.3'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2020-07-21T15:52:29+00:00</updated>
<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>
<entry>
<title>guestcust_util: handle special characters in config file</title>
<updated>2019-10-17T15:18:44+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-10-17T15:18:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=ecb501b84338f078be18c38c68c3ce87fed3584b'/>
<id>urn:sha1:ecb501b84338f078be18c38c68c3ce87fed3584b</id>
<content type='text'>
Handle the special characters when reading VM Tools configure file.
For example, the key and value may contain _, - and . etc.
</content>
</entry>
<entry>
<title>VMWware: add option into VMTools config to enable/disable custom script.</title>
<updated>2019-09-11T18:53:01+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-09-11T18:53:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=45426d8d38a7224962867ba71f390cce653e0d17'/>
<id>urn:sha1:45426d8d38a7224962867ba71f390cce653e0d17</id>
<content type='text'>
VMWware customization already has support to run a custom script during
the VM customization. Adding this option allows a VM administrator to
disable the execution of customization scripts.  If set the script
will not execute and the customization status is set to
GUESTCUST_ERROR_SCRIPT_DISABLED.
</content>
</entry>
<entry>
<title>VMWare: Trigger the post customization script via cc_scripts module.</title>
<updated>2019-07-16T13:09:38+00:00</updated>
<author>
<name>Xiaofeng Wang</name>
<email>xiaofengw@vmware.com</email>
</author>
<published>2019-07-16T13:09:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=9c47c682b7aaa185c32a68f4dea8e23e9a2ef565'/>
<id>urn:sha1:9c47c682b7aaa185c32a68f4dea8e23e9a2ef565</id>
<content type='text'>
cloud-init does not trigger reboots of a VM therefore adding custom
scripts to rc.local does not execute the post scripts.  This patch
moves post-scripts into per-instance scripts dir and has cc_scripts
module run the post-scripts.

Also in this branch:
  - Remove the sh interpreter and execute the customization script
    directly.
  - Update the unit test.

LP: #1833192
</content>
</entry>
<entry>
<title>ovf: Fix ovf network config generation gateway/routes</title>
<updated>2018-12-03T18:43:21+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2018-12-03T18:43:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6'/>
<id>urn:sha1:cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6</id>
<content type='text'>
Move routes under the nic's subnet rather than use top-level
("global") route config ensuring all net renderers will provide the
configured route.

Also updated cloudinit/cmd/devel/net_convert.py:
 - Add input type 'vmware-imc' for OVF customization config files
 - Fix bug when output-type was netplan which invoked netplan
   generate/apply and attempted to write to
   /etc/netplan/50-cloud-init.yaml instead of joining with the
   output directory.

LP: #1806103
</content>
</entry>
<entry>
<title>VMWare: Fix a network config bug in vm with static IPv4 and no gateway.</title>
<updated>2018-08-28T22:52:28+00:00</updated>
<author>
<name>Pengpeng Sun</name>
<email>pengpengs@vmware.com</email>
</author>
<published>2018-08-28T22:52:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=9c35f9762028b8bf15cdcd6b42c0fafc233ddda3'/>
<id>urn:sha1:9c35f9762028b8bf15cdcd6b42c0fafc233ddda3</id>
<content type='text'>
The issue is when customize a VM with static IPv4 and without gateway, it
will still extend route list and will loop a gateways list which is None.
This fix is to make sure when no gateway is here, it will not extend route
list.

LP: #1766538
</content>
</entry>
</feed>
