(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2021-12-16T02:16:38+00:00 2021-12-16T02:16:38+00:00 James Falcon james.falcon@canonical.com 2021-12-16T02:16:38+00:00 urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf Applied Black and isort, fixed any linting issues, updated tox.ini and CI. 2021-12-02T14:51:26+00:00 James Falcon james.falcon@canonical.com 2021-12-02T14:51:26+00:00 urn:sha1:cf38c2cbc5875813fbb9858f45e5b95789b7ffea GCE currently fetches metadata after network has come up. There's no reason we can't fetch at init-local time, so update GCE to fetch at init-local time to be more performant and consistent with other datasources. 2021-10-22T18:38:08+00:00 vteratipally 67723486+vteratipally@users.noreply.github.com 2021-10-22T18:38:08+00:00 urn:sha1:6cf9dc870f69f8d910388193a4a59474117915b7 In some of the cases, the system-product-name is just google. This is useful incase of nocloud where we use the disk to load the datasource 2021-09-21T04:53:05+00:00 vteratipally 67723486+vteratipally@users.noreply.github.com 2021-09-21T04:53:05+00:00 urn:sha1:e27c30748e88409b1646a552f994edf9ed9d017e Add retries to DatasourceGCE when connecting to GCE. Sometimes when the trying to fetch the metadata, cloud-init fails and the fallback datasource NoCloud is used which is not expected. Add retries to ensure loading of the data source. 2020-11-02T20:41:11+00:00 Scott Moser smoser@brickies.net 2020-11-02T20:41:11+00:00 urn:sha1:0af1ff1eaf593c325b4f53181a572110eb016c50 This just separates the reading of dmi values into its own file. Some things of note: * left import of util in dmi.py only for 'is_container' It'd be good if is_container was not in util. * just the use of 'util.is_x86' to dmi.py * open() is used directly rather than load_file. 2020-06-02T15:24:29+00:00 Joshua Powers josh.powers@canonical.com 2020-06-02T15:24:29+00:00 urn:sha1:5f7825e22241423322dbe628de1b00289cf34114 Remove extra spaces after a ',' 2019-08-09T17:11:05+00:00 Rick Wright rickw@google.com 2019-08-09T17:11:05+00:00 urn:sha1:155847209e6a3ed5face91a133d8488a703f3f93 This adds an empty publish_host_keys() method to the default datasource that is called by cc_ssh.py. This feature can be controlled by the 'ssh_publish_hostkeys' config option. It is enabled by default but can be disabled by setting 'enabled' to false. Also, a blacklist of key types is supported. In addition, this change implements ssh_publish_hostkeys() for the GCE datasource, attempting to write the hostkeys to the instance's guest attributes. Using these hostkeys for ssh connections is currently supported by the alpha version of Google's 'gcloud' command-line tool. (On Google Compute Engine, this feature will be enabled by setting the 'enable-guest-attributes' metadata key to 'true' for the project/instance that you would like to use this feature for. When connecting to the instance for the first time using 'gcloud compute ssh' the hostkeys will be read from the guest attributes for the instance and written to the user's local known_hosts file for Google Compute Engine instances.) 2018-03-20T22:37:36+00:00 Chad Smith chad.smith@canonical.com 2018-03-20T22:37:36+00:00 urn:sha1:685f9901b820a457912959bdd4f389835e965524 DataSource.get_hostname call signature changed to allow for metadata_only parameter. The metadata_only=True parameter is passed to get_hostname during init-local stage in order to set the system hostname if present in metadata prior to initial network bring up. Fix subclasses of DataSource which have overridden get_hostname to allow for metadata_only param. LP: #1757176 2018-03-01T22:39:16+00:00 Scott Moser smoser@ubuntu.com 2018-03-01T22:39:16+00:00 urn:sha1:40e77380e036a24fafe91a63d0cdefada4312348 Last set of changes to GCE datasource broke reading of user-data unless the user had base64 encoded their user-data and also set user-data-encoding to 'base64'. This fixes the issue. LP: #1752711 2018-01-24T01:12:32+00:00 Max Illfelder illfelder@google.com 2018-01-24T01:12:32+00:00 urn:sha1:2d781c6a3e27433b7fa993cd54b269ceb74e10b2 The behavior changes and improvements include: - Only import keys into the default user that contain the name of the default user ('ubuntu', or 'centos') or that contain 'cloudinit'. - Use instance or project level keys based on GCE convention. - Respect expiration time when keys are set. Do not import expired keys. - Support ssh-keys in project level metadata (the GCE default). As part of this change, we also update the request header when talking to the metadata server based on the documentation: https://cloud.google.com/compute/docs/storing-retrieving-metadata#querying LP: #1670456, #1707033, #1707037, #1707039