<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/sources/helpers/vmware, branch crux</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=crux</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2018-12-03T18:43:21+00:00</updated>
<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/vyos/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/vyos/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>
<entry>
<title>pylint: pay attention to unused variable warnings.</title>
<updated>2018-04-20T03:30:08+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-04-20T03:30:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=1081962eacf2814fea6f4fa3255c530de14e4a24'/>
<id>urn:sha1:1081962eacf2814fea6f4fa3255c530de14e4a24</id>
<content type='text'>
This enables warnings produced by pylint for unused variables (W0612),
and fixes the existing errors.
</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>vmware customization: return network config format</title>
<updated>2017-09-08T04:21:30+00:00</updated>
<author>
<name>Sankar Tanguturi</name>
<email>stanguturi@vmware.com</email>
</author>
<published>2017-09-08T04:16:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a1dfdda2a2ae20fe026881980ddf7d16110f06e2'/>
<id>urn:sha1:a1dfdda2a2ae20fe026881980ddf7d16110f06e2</id>
<content type='text'>
For customizing the machines hosted on 'VMWare' hypervisor, the datasource
should return the 'network config' data in 'curtin' format.

This branch also fixes /etc/network/interfaces replacing the line
"source /etc/network/interfaces.d/*.cfg" which is incorrectly removed
when VMWare's Perl Customization Engine writes /etc/network/interfaces.

Modify the code to read the customization configuration and return the
converted data.

Added few tests.

LP: #1675063
</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>pylint: fix all logging warnings</title>
<updated>2017-04-21T14:14:47+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-04-06T18:14:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5afe4cd0797a12d07ea19b9715b720d47bdea401'/>
<id>urn:sha1:5afe4cd0797a12d07ea19b9715b720d47bdea401</id>
<content type='text'>
This will change all instances of LOG.warn to LOG.warning as warn
is now a deprecated method. It will also make sure any logging
uses lazy logging by passing string format arguments as function
parameters.
</content>
</entry>
<entry>
<title>Fixed Misc issues related to VMware customization.</title>
<updated>2017-01-17T16:27:07+00:00</updated>
<author>
<name>Sankar Tanguturi</name>
<email>stanguturi@vmware.com</email>
</author>
<published>2016-09-06T21:51:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=8ddb57149281ba2658696f19c1eb96e7769381e4'/>
<id>urn:sha1:8ddb57149281ba2658696f19c1eb96e7769381e4</id>
<content type='text'>
- staticIPV4 property can be either None or a valid Array. Need to
  check for None before accessing the ip address.
- Modified few misc. log messages.
- Added a new log message while waiting for the customization config file.
- Added support to configure the maximum amount of time to wait for the
  customization config file.
- VMware Customization Support is provided only for DataSourceOVF class and
  not for any other child classes. Implemented a new variable
  vmware_customization_supported to check whether the 'VMware Customization'
  support is available for a specific datasource or not.
- Changed the function get_vmware_cust_settings to get_max_wait_from_cfg.
- Removed the code that does 'ifdown and iup' in NIC configurator.
</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>
</feed>
