(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.3 2020-08-25T15:21:18+00:00 2020-08-25T15:21:18+00:00 Paride Legovini paride.legovini@canonical.com 2020-08-25T15:21:18+00:00 urn:sha1:07104504ab5b30efd2d1f7a8c36effe18b8e5fe0 Changes: tox: bump the pylint version to 2.6.0 in the default run Fix pylint 2.6.0 W0707 warnings (raise-missing-from) 2020-08-25T03:48:21+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2020-08-25T03:48:21+00:00 urn:sha1:4068137e3ef048d3e2da56a8190f682eb19d501e This fixes a long delay during boot of some instances. For Azure instance types using SR-IOV via the Hyper-V netvsc network driver, two network interfaces are created that share the same MAC, but only the virtual device should be configured and used. Updating the netplan configuration to filter on the hv_netvsc driver prevents netplan from trying to figure both devices. LP: #1830740 2020-08-20T19:04:03+00:00 Moustafa Moustafa momousta@microsoft.com 2020-08-20T19:04:03+00:00 urn:sha1:d941c7f7846e0216873384044d20f4b6723697c5 Push the cloud-init.log file (Up to 500KB at once) to the KVP before reporting ready to the Azure platform. Based on the analysis done on a large sample of cloud-init.log files, Here's the statistics collected on the log file size: P50 P90 P95 P99 P99.9 P99.99 137K 423K 537K 3.5MB 6MB 16MB This change limits the size of cloud-init.log file data that gets dumped to KVP to 500KB. So for ~95% of the cases, the whole log file will be dumped and for the remaining ~5%, we will get the last 500KB of the cloud-init.log file. To asses the performance of the 500KB limit, 250 VM were deployed with a 500KB cloud-init.log file and the time taken to compress, encode and dump the entries to KVP was measured. Here's the time in milliseconds percentiles: P50 P99 P999 75.705 232.701 1169.636 Another 250 VMs were deployed with this logic dumping their normal cloud-init.log file to KVP, the same timing was measured as above. Here's the time in milliseconds percentiles: P50 P99 P999 1.88 5.277 6.992 Added excluded_handlers to the report_event function to be able to opt-out from reporting the events of the compressed cloud-init.log file to the cloud-init.log file. The KVP break_down logic had a bug, where it will reuse the same key for all the split chunks of KVP which results in overwriting the split KVPs by the last one when consumed by Hyper-V. I added the split chunk index as a differentiator to the KVP key. The Hyper-V consumes the KVPs from the KVP file as chunks whose key is 512KB and value is 2048KB but the Azure platform expects the value to be 1024KB, thus I introduced the Azure value limit. 2020-08-14T15:37:33+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-08-14T15:37:33+00:00 urn:sha1:2d3533b59c7bf00affbda9c2c94fb5f214ffcb11 2020-08-13T20:50:07+00:00 Johnson Shi Johnson.Shi@microsoft.com 2020-08-13T20:50:07+00:00 urn:sha1:c3556ae82dfb47d635344fcd78908f003648d6d2 This PR refactors Azure report ready code to include more robust tests and telemetry. 2020-08-13T19:38:37+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2020-08-13T19:38:37+00:00 urn:sha1:546617c449f2e973717191a07c243ec1b6bfc8da * v2 of the API is now default with fallback to v1. * Refactored the Oracle datasource to fetch version, instance, and vnic metadata simultaneously. 2020-08-10T19:11:23+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-08-10T19:11:23+00:00 urn:sha1:a6bb375aef93a31395af9ce0985c49ada9fb7139 The /opc/v1/ metadata endpoints[0] are universally available in Oracle Cloud Infrastructure and the OpenStack endpoints are considered deprecated, so we can refactor the data source to use the OPC endpoints exclusively. This simplifies the datasource code substantially, and enables use of OPC-specific attributes in future. [0] https://docs.cloud.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm 2020-08-07T15:19:09+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2020-08-07T15:19:09+00:00 urn:sha1:c068f992c3905d07732dafa6eb61c1ae3aa65916 Update DataSourceNoCloud and ds-identify to recognize LABEL_FATBOOT labels from blkid. Also updated associated tests. LP: #1841466 2020-07-22T16:51:01+00:00 Anh Vo anhvo@microsoft.com 2020-07-22T16:51:01+00:00 urn:sha1:d600f47e91b904243263358324c413c4f7e5cf50 DataSourceAzure: Gracefully handle the case of set hostname failure during provisioning 2020-07-21T15:52:29+00:00 xiaofengw-vmware 42736879+xiaofengw-vmware@users.noreply.github.com 2020-07-21T15:52:29+00:00 urn:sha1:995f8adf00509e5d2aefc9f0680c3c4894ae6666 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.