(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-06-17T14:37:23+00:00 Mark Mercado mamercad@gmail.com 2021-06-17T14:37:23+00:00 urn:sha1:1243c5a1fc1f3546b40e48a2033a9abab546e40f The name "DigitalOcean" doesn't have a space in it; it's a single compound word written in Pascal case (upper camel case). 2020-06-30T18:19:38+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-06-30T18:19:38+00:00 urn:sha1:882f1a5f2d5bafd08e6900a2782c3affa67c9d86 As the first refactor PR, this also includes the initial structure for tests. LP: #1884619 2017-12-05T23:42:35+00:00 Chad Smith chad.smith@canonical.com 2017-12-05T23:42:35+00:00 urn:sha1:0cf6db3617e0cebeb89c4809396f84360827e96c Each DataSource subclass must define its own get_data method. This branch formalizes our DataSource class to require that subclasses define an explicit dsname for sourcing cloud-config datasource configuration. Subclasses must also override the _get_data method or a NotImplementedError is raised. The branch also writes /run/cloud-init/instance-data.json. This file contains all meta-data, user-data and vendor-data and a standardized set of metadata keys in a json blob which other utilities with root-access could make use of. Because some meta-data or user-data is potentially sensitive the file is only readable by root. Generally most metadata content types should be json serializable. If specific keys or values are not serializable, those specific values will be base64encoded and the key path will be listed under the top-level key 'base64-encoded-keys' in instance-data.json. If json writing fails due to other TypeErrors or UnicodeDecodeErrors, a warning log will be emitted to /var/log/cloud-init.log and no instance-data.json will be created. 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. 2016-12-22T22:04:28+00:00 Jon Grimm jon.grimm@canonical.com 2016-11-22T23:09:53+00:00 urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c 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. 2016-09-29T13:57:13+00:00 Ben Howard bh@digitalocean.com 2016-08-19T22:28:26+00:00 urn:sha1:9f83bb8e80806d3dd79ba426474dc3c696e19a41 On DigitalOcean, Network information is provided via Meta-data. It changes the datasource to be a local datasource, meaning it will run before fallback networking is configured. The advantage of that is that before networking is configured it can bring up a network device with ipv4 link-local and hit the metadata service that lives at 169.254.169.254 to find its networking configuration. It then takes down the link local address and lets cloud-init configure networking. The configuring of a network device to go looking for a metadata service is gated by a check of data in the smbios. This guarantees that the code will not run on another system. 2016-08-12T20:16:27+00:00 Ben Howard bh@digitalocean.com 2016-08-01T20:47:39+00:00 urn:sha1:bc2c3267549b9067c017a34e22bbee18890aec06 Per [1], DigitalOcean provides the metadata in multiple formats. The JSON document is the preferred endpoint. Changes: - Switch to the v1.json meta-data endpoint - Identify droplet identity from SMBIOS - Only poll for metadata when the instance is confirmed to be a droplet - Removal of hard-coded mirrors Additionally, centralize the gates on running 'dmidecode' on arm arches, and update tests to address. [1] https://developers.digitalocean.com/documentation/metadata/ 2016-05-12T17:56:26+00:00 Joshua Harlow harlowja@gmail.com 2016-05-12T17:56:26+00:00 urn:sha1:f11827aee59cf2678c3d2a157218a3fe2831f5c2 2016-03-04T06:45:58+00:00 Scott Moser smoser@ubuntu.com 2016-03-04T06:45:58+00:00 urn:sha1:8092805079d011093724d87e9485e5bf79479a72 Update make check target to run pep8 and run pyflakes or pyflakes3 depending on the value of 'PYVER'. This way the python3 build environment does not need python2 and vice versa. Also have make check run the 'yaml' test. tox: have tox run pep8 in the pyflakes