(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.1 2019-10-17T15:18:44+00:00 2019-10-17T15:18:44+00:00 Xiaofeng Wang xiaofengw@vmware.com 2019-10-17T15:18:44+00:00 urn:sha1:ecb501b84338f078be18c38c68c3ce87fed3584b Handle the special characters when reading VM Tools configure file. For example, the key and value may contain _, - and . etc. 2019-09-11T18:53:01+00:00 Xiaofeng Wang xiaofengw@vmware.com 2019-09-11T18:53:01+00:00 urn:sha1:45426d8d38a7224962867ba71f390cce653e0d17 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. 2019-07-16T13:09:38+00:00 Xiaofeng Wang xiaofengw@vmware.com 2019-07-16T13:09:38+00:00 urn:sha1:9c47c682b7aaa185c32a68f4dea8e23e9a2ef565 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 2018-12-03T18:43:21+00:00 Ryan Harper ryan.harper@canonical.com 2018-12-03T18:43:21+00:00 urn:sha1:cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6 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 2018-08-28T22:52:28+00:00 Pengpeng Sun pengpengs@vmware.com 2018-08-28T22:52:28+00:00 urn:sha1:9c35f9762028b8bf15cdcd6b42c0fafc233ddda3 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 2018-04-20T03:30:08+00:00 Scott Moser smoser@ubuntu.com 2018-04-20T03:30:08+00:00 urn:sha1:1081962eacf2814fea6f4fa3255c530de14e4a24 This enables warnings produced by pylint for unused variables (W0612), and fixes the existing errors. 2017-12-08T17:15:00+00:00 Maitreyee Saikia msaikia@vmware.com 2017-12-08T17:10:40+00:00 urn:sha1:ce33e423cde806a0590fec635778d62836e1bd37 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. 2017-09-08T04:21:30+00:00 Sankar Tanguturi stanguturi@vmware.com 2017-09-08T04:16:16+00:00 urn:sha1:a1dfdda2a2ae20fe026881980ddf7d16110f06e2 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 2017-08-15T15:33:50+00:00 Maitreyee Saikia msaikia@vmware.com 2017-08-15T15:33:50+00:00 urn:sha1:1f8183ff4750cc7f8798749987ef10912719544d 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. 2017-04-21T14:14:47+00:00 Joshua Powers josh.powers@canonical.com 2017-04-06T18:14:29+00:00 urn:sha1:5afe4cd0797a12d07ea19b9715b720d47bdea401 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.