(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained 2022-02-03T22:05:02+00:00 2022-02-03T22:05:02+00:00 James Falcon james.falcon@canonical.com 2022-02-03T22:05:02+00:00 urn:sha1:aa47ec0ce020c56afb4308476a3b85254f15569d As part of IN_PLACE testing, /etc/cloud/cloud.cfg.d get overwritten by what's in the source tree. This can cause problems when the directory is mounted in, because tests need the ability to modify files in /etc/cloud. Attempting to 'lxc file push' instead will fail on LXD VMs because the LXD agent isn't available yet. If such functionality is desired, one can temporarily use the 'lxd_setup' mark while writing a test and push the files manually. 2022-02-03T04:38:56+00:00 Chad Smith chad.smith@canonical.com 2022-02-03T04:38:56+00:00 urn:sha1:6ed3c5dfcd9392784d2199224ac7d28d1abfdf7b Since lxc bind mounts will be read-only as nobody:nogroup we don't want to bind mount /etc/cloud/cloud.cfg.d into the instance because some tests add artifacts to /etc/cloud/cloud.cfg.d. Also make LXD push_file pull_file methods assert that the file transfer was a success, otherwise we miss the root-cause for test failures. This resulted in failed Jenkins runs in test_lxd_discovery with a symptom of NoCloud being detected instead of LXD datasource. The root-case was that instance.file_push failed due to permission errors for root on the bind mounted /etc/cloud/cloud.cfg.d. Also bump pycloudlib commitish to get Azure Jammy image support. 2022-02-03T03:14:52+00:00 James Falcon james.falcon@canonical.com 2022-02-03T03:14:52+00:00 urn:sha1:b64b7d8ceb0e7bdb7cc9839c238798622c5b9682 * Include CI and Fixtures sections in integration test docs * Incorporate additional variable annotations * Remove unnecessary IntegrationInstance subclasses * Move setup_image teardown into its fixture 2022-01-19T23:43:05+00:00 Paride Legovini paride.legovini@canonical.com 2022-01-19T23:43:05+00:00 urn:sha1:4c7d159c3efe39860d3c01bf680ba686b87adb77 Dailies are always available for stable releases and the devel release. Moreover testing against dailies will warn us earlier about issues. 2022-01-18T15:10:36+00:00 James Falcon james.falcon@canonical.com 2022-01-18T15:10:36+00:00 urn:sha1:62f82651f2c29db5934f16afcb9f1e522f90588a https://pycloudlib.readthedocs.io/en/latest/configuration.html#configuration 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-11-01T20:43:05+00:00 Chad Smith chad.smith@canonical.com 2021-11-01T20:43:05+00:00 urn:sha1:773765346ba543987aa64a1119fa760f0b1cbb6f Add DataSourceLXD which knows how to talk to the dev-lxd socket to obtain all instance metadata API: https://linuxcontainers.org/lxd/docs/master/dev-lxd. This first branch is to deliver feature parity with the existing NoCloud datasource which is currently used to intialize LXC instances on first boot. Introduce a SocketConnectionPool and LXDSocketAdapter to support performing HTTP GETs on the following routes which are surfaced by the LXD host to all containers: http://unix.socket/1.0/meta-data http://unix.socket/1.0/config/user.user-data http://unix.socket/1.0/config/user.network-config http://unix.socket/1.0/config/user.vendor-data These 4 routes minimally replace the static content provided in the following nocloud-net seed files: /var/lib/cloud/nocloud-net/{meta-data,vendor-data,user-data,network-config} The intent of this commit is to set a foundation for LXD socket communication that will allow us to build network hot-plug features by eventually consuming LXD's websocket upgrade route 1.0/events to react to network, meta-data and user-data config changes over time. In the event that no custom network-config is provided, default to the same network-config definition provided by LXD to the NoCloud network-config seed file. Supplemental features above NoCloud datasource: surface all custom instance data config keys via cloud-init query ds which aids in discoverability of features/tags/labels as well as conditional #cloud-config jinja templates operations based on custom config options. TBD: better cloud-init query support for dot-delimited keys 2021-09-01T14:23:55+00:00 Shreenidhi Shedi 53473811+sshedi@users.noreply.github.com 2021-09-01T14:23:55+00:00 urn:sha1:58c2de4c97de6cfa6edbf5319641f2ef71284895 Using flake8 inplace of pyflakes Renamed run-pyflakes -> run-flake8 Changed target name to flake8 in Makefile With pyflakes we can't suppress warnings/errors in few required places. flake8 is flexible in that regard. Hence using flake8 seems to be a better choice here. flake8 does the job of pep8 anyway. So, removed pep8 target from Makefile along with tools/run-pep8 script. Included setup.py in flake8 checks 2021-07-02T23:01:58+00:00 James Falcon therealfalcon@gmail.com 2021-07-02T23:01:58+00:00 urn:sha1:36aeb49cb966d6ab576d4ce7cd2e815079c541a3 test_upgrade.py was outputting a ton of stuff that had to be manually collected and verified. This commit adds more assertions to the test and outputs directly to the logs rather than separate files. 2021-06-15T02:37:15+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2021-06-15T02:37:15+00:00 urn:sha1:59a3d84562a0fdeb16a4a566371294790d110ad4