(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=cla 2017-12-05T22:05:29+00:00 2017-12-05T22:05:29+00:00 Scott Moser smoser@brickies.net 2017-12-05T22:05:29+00:00 urn:sha1:47016791ca5e97d80e45d3f100bc4e5d0b88627d This groups up each test platform into its own directory rather than having files spread between four different directories for one platform. Platforms tend to be worked on one at a time and so having the platforms together makes more sense than apart. 2017-11-29T20:26:38+00:00 Scott Moser smoser@brickies.net 2017-11-29T20:26:38+00:00 urn:sha1:88368f9851b29dddb5a12e4b21868cbdef906c5c The NoCloudKVMImage.execute() would modify the image in /srv/citest that meant that after the first time you ran a test, the image was dirty. The change here is to make the image operate on a qcow backed image. Also modify Snapshot to then copy the qcow rather than creating another chained qcow. The reason being that the image might go away or change after the snapshot has been returned. Also * drop use of 'override_templates' which was only relevant to LXD. * NoCloudKVM.create_image() returned an instance before now it has create_instance which creates an instance. * NoCloudKVMInstance has a 'disk' attribute separate from 'name' 2017-09-14T18:53:55+00:00 Joshua Powers josh.powers@canonical.com 2017-07-11T21:28:11+00:00 urn:sha1:376168e251a1d4f2ee3643fed6092b8907f057ec The NoCloud KVM platform includes: * Downloads daily Ubuntu images using streams and store in /srv/images * Image customization, if required, is done using mount-image-callback otherwise image is untouched * Launches KVM via the xkvm script, a wrapper around qemu-system, and sets custom port for SSH * Generation and inject an SSH (RSA 4096) key pair to use for communication with the guest to collect test artifacts * Add method to produce safe shell strings by base64 encoding the command Additional Changes: * Set default backend to use LXD * Verify not running script as root in order to prevent images from becoming owned by root * Removed extra quotes around that were added when collecting the cloud-init version from the image * Added info about each release as previously the lxd backend was able to query that information from pylxd image info, however, other backends will not be able to obtain the same information as easily 2017-06-08T22:24:17+00:00 Wesley Wiedenmeier wesley.wiedenmeier@gmail.com 2017-06-08T22:23:31+00:00 urn:sha1:76d58265e34851b78e952a7f275340863c90a9f5 Massive update to clean up and greatly enhance the integration testing framework developed by Wesley Wiedenmeier. - Updated tox environment to run integration test 'citest' to utilize pylxd 2.2.3 - Add support for distro feature flags - add framework for feature flags to release config with feature groups and overrides allowed in any release conf override level - add support for feature flags in platform and config handling - during collect, skip testcases that require features not supported by the image with a warning message - Enable additional distros (i.e. centos, debian) - Add 'bddeb' command to build a deb from the current working tree cleanly in a container, so deps do not have to be installed on host - Adds a command line option '--preserve-data' that ensures that collected data will be left after tests run. This also allows the directory to store collected data in during the run command to be specified using '--data-dir'. - Updated Read the Docs testing page and doc strings for pep 257 compliance 2016-12-22T22:41:39+00:00 Wesley Wiedenmeier wesley.wiedenmeier@gmail.com 2016-12-22T22:27:37+00:00 urn:sha1:f53fc46aa732e3b29991b3e5e39da31a722945ee The adds in end-to-end testing of cloud-init. The framework utilizes LXD and cloud images as a backend to test user-data passed in. Arbitrary data is then captured from predefined commands specified by the user. After collection, data verification is completed by running a series of Python unit tests against the collected data. Currently only the Ubuntu Trusty, Xenial, Yakkety, and Zesty releases are supported. Test cases for 50% of the modules is complete and available. Additionally a Read the Docs file was created to guide test writing and execution.