(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux 2019-01-23T12:23:09+00:00 2019-01-23T12:23:09+00:00 Scott Moser smoser@ubuntu.com 2018-12-20T23:51:09+00:00 urn:sha1:ee6bb34376e1814a91fc513a811b059b04260d4c ovf_vmware_transport_guestinfo is not currently tested. It used '$1' instead of '$out' when checking for xml content in the output of vmware-rpctool. 2019-01-23T12:22:33+00:00 Scott Moser smoser@ubuntu.com 2018-12-20T17:22:45+00:00 urn:sha1:d7952d075666122f480f0a5820ac01dfbaa7da1a This adds support for reading OVF information over the 'com.vmware.guestInfo' tranport. The current implementation requires vmware-rpctool be installed in the system. LP: #1807466 2018-11-27T21:39:42+00:00 Scott Moser smoser@ubuntu.com 2018-11-27T21:39:42+00:00 urn:sha1:530850f971e36f4b0ef216cec9d889a99474ca0e When deploying an OVA, at least some versions of vmware attach a cdrom with an ISO9660 filesystem label of 'OVF ENV'. This was seen on Vmware vCenter Server, 6.0.0, 2776510. In order to accomplish this we had to change the content of the DI_ISO9660_DEVS variable to be comma delimited rather than space delimited. 2018-09-14T21:12:17+00:00 Scott Moser smoser@ubuntu.com 2018-09-14T21:12:17+00:00 urn:sha1:bb60f61bfcd92465f4076e8d8abbb486cf6bbcf1 There was a typo in the doc string at the top of ds-identify (disable -> disabled). That is fixed here as well as adding some better examples on content in /etc/cloud/ds-identify.cfg. 2018-08-17T20:25:31+00:00 Scott Moser smoser@ubuntu.com 2018-08-17T20:25:31+00:00 urn:sha1:aaffd59431fe05932a66016db941fe197c4e7620 This adds a Oracle specific datasource that functions with OCI. It is a simplified version of the OpenStack metadata server with support for vendor-data. It does not support the OCI-C (classic) platform. Also here is a move of BrokenMetadata to common 'sources' as this was the third occurrence of that class. 2018-05-22T14:07:59+00:00 Scott Moser smoser@ubuntu.com 2018-05-22T14:07:59+00:00 urn:sha1:b4ae0e1fb8a48a83ea325cf032eb1acb196ee31c SuSE builds were not getting a PATH set in generator's environment. This may seem like mis-configuration on the system, but caused ds-identify to fail to find blkid (or any other program). The change here just ensures that we get /sbin /usr/sbin /bin /usr/bin into the PATH when main is run. LP: #1771382 2018-05-15T17:38:20+00:00 Scott Moser smoser@ubuntu.com 2018-05-15T17:38:20+00:00 urn:sha1:0d7ee5592621d09699d079945ffd6febf16669b2 In playing with a SmartOS container I found that ds-identify did not identify the container there as a container. Systemd-detect-virt identifies it as 'container-other'. Also here are tests for ds-identify for the SmartOS platform identification, and some indentation fixes in ds-identify. 2018-05-10T02:08:53+00:00 Scott Moser smoser@ubuntu.com 2018-05-10T02:08:53+00:00 urn:sha1:bde30070ec5f20aeb4d48cee8cf6c49b900ee311 We had two calls to is_ds_enabled, and the debug message looked something like this: is_ds_enabled returned 1: ConfigDrive NoCloud Now instead we have just one call, and the debug message like: is_ds_enabled(IBMCloud) = true 2018-05-08T17:59:33+00:00 Scott Moser smoser@ubuntu.com 2018-05-08T17:59:33+00:00 urn:sha1:4c1af5c7eb8db67f51f35130e13157a735256d2b This fixes warnings reported by shellcheck at 0.4.6. The complaints that we are ignoring globally (top of the file) are:  2015: Note that A && B || C is not if-then-else. C may run if A is true.  2039: In POSIX sh, 'local' is undefined.  2162: read without -r will mangle backslashes.  2166: Prefer [ p ] && [ q ] as [ p -a q ] is not well defined. Most of the complaints were just noise, but a few unused variables were reported and fixed. Related shellcheck issues opened: - https://github.com/koalaman/shellcheck/issues/1191 - https://github.com/koalaman/shellcheck/issues/1192 - https://github.com/koalaman/shellcheck/issues/1193 - https://github.com/koalaman/shellcheck/issues/1194 2018-04-30T19:21:51+00:00 Scott Moser smoser@ubuntu.com 2018-04-30T19:21:51+00:00 urn:sha1:11172924a48a47a7231d19d9cefe628dfddda8bf Ubuntu images on IBMCloud for 16.04 have some seed data in /var/lib/cloud/data/seed/nocloud-net. In order to have systems with IBMCloud enabled, we modified ds-identify detection to skip that seed if the system was on IBMCloud. That change did not consider the fact that IBMCloud might not be in the datasource list. There was similar logic in the ConfigDrive datasource in ds-identify and the datasource itself. Config drive is now updated to only check and avoid IBMCloud if IBMCloud is enabled. The check in ds-identify for nocloud was dropped. If a user provides a nocloud seed on IBMCloud, then that can be used. This means that systems running Xenial will continue to get their old datasources. LP: #1766401