<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware/imc/config.py, branch rolling</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=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2021-12-16T02:16:38+00:00</updated>
<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/vyos/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] 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/vyos/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>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>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/vyos/vyos-cloud-init.git/commit/?id=1fefeef92fd1881b21e124b83f2adefd3e014087'/>
<id>urn:sha1:1fefeef92fd1881b21e124b83f2adefd3e014087</id>
<content type='text'>
</content>
</entry>
<entry>
<title>VMware: Support for user provided pre and post-customization scripts</title>
<updated>2017-12-08T17:15:00+00:00</updated>
<author>
<name>Maitreyee Saikia</name>
<email>msaikia@vmware.com</email>
</author>
<published>2017-12-08T17:10:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=ce33e423cde806a0590fec635778d62836e1bd37'/>
<id>urn:sha1:ce33e423cde806a0590fec635778d62836e1bd37</id>
<content type='text'>
In the VMware customization workflow, we have some options for the user
to upload scripts for additional customization. Based on user request,
those custom scripts can be either run before regular customization or
after. For post customization scripts, we decide whether to run the scripts
just after customization or post system reboot.
</content>
</entry>
<entry>
<title>vcloud directory: Guest Customization support for passwords</title>
<updated>2017-08-15T15:33:50+00:00</updated>
<author>
<name>Maitreyee Saikia</name>
<email>msaikia@vmware.com</email>
</author>
<published>2017-08-15T15:33:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1f8183ff4750cc7f8798749987ef10912719544d'/>
<id>urn:sha1:1f8183ff4750cc7f8798749987ef10912719544d</id>
<content type='text'>
This feature enables the following VMware VCloud Director functionality:
1. Setting admin password
2. Expire password.
3. Set admin password and expire.

Password configuration is triggered only as part of a full
recustomization, that happens either on first power on or when
"poweron and full recustomization" is selected. Full customization
flow is determined by marker files. Unique marker ids are
generated when full recustomization is requested. And marker file based
on these marker ids help to determine if we need to execute the above
configuration.
</content>
</entry>
<entry>
<title>LICENSE: Allow dual licensing GPL-3 or Apache 2.0</title>
<updated>2016-12-22T22:04:28+00:00</updated>
<author>
<name>Jon Grimm</name>
<email>jon.grimm@canonical.com</email>
</author>
<published>2016-11-22T23:09:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b2a9f33616c806ae6e052520a8589113308f567c'/>
<id>urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c</id>
<content type='text'>
This has been a recurring ask and we had initially just made the change to
the cloud-init 2.0 codebase.  As the current thinking is we'll just
continue to enhance the current codebase, its desirable to relicense to
match what we'd intended as part of the 2.0 plan here.

- put a brief description of license in LICENSE file
- put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0
- simplify the per-file header to reference LICENSE
- tox: ignore H102 (Apache License Header check)

Add license header to files that ship.
Reformat headers, make sure everything has vi: at end of file.

Non-shipping files do not need the copyright header,
but at the moment tests/ have it.
</content>
</entry>
<entry>
<title>run flake8 instead of pyflakes in tox.  expect tests/ to pass flake8.</title>
<updated>2016-05-12T20:43:11+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2016-05-12T20:43:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4ba4df2f00ab1763920280f76e2b4497898858af'/>
<id>urn:sha1:4ba4df2f00ab1763920280f76e2b4497898858af</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix up a ton of flake8 issues</title>
<updated>2016-05-12T17:56:26+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@gmail.com</email>
</author>
<published>2016-05-12T17:56:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=f11827aee59cf2678c3d2a157218a3fe2831f5c2'/>
<id>urn:sha1:f11827aee59cf2678c3d2a157218a3fe2831f5c2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>  Fixed all the review comments from Daniel.</title>
<updated>2016-01-20T02:24:54+00:00</updated>
<author>
<name>Sankar Tanguturi</name>
<email>stanguturi@stanguturi-rhel</email>
</author>
<published>2016-01-20T02:24:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=415c45a2b9b66603e672e8ea54cee8f40a19abd1'/>
<id>urn:sha1:415c45a2b9b66603e672e8ea54cee8f40a19abd1</id>
<content type='text'>
  Added a new file i.e. nic_base.py which will be used a base calls for all
  NIC related configuration.
  Modified some code in nic.py.
</content>
</entry>
</feed>
