cloud-init-dev team mailing list archive
-
cloud-init-dev team
-
Mailing list archive
-
Message #01709
[Merge] ~wesley-wiedenmeier/cloud-init:integration-testing into cloud-init:master
The proposal to merge ~wesley-wiedenmeier/cloud-init:integration-testing into cloud-init:master has been updated.
Description changed to:
integration-testing updates
- enable additional distros
- allow use of either pylxd 2.1.3 or 2.2.3
- detected at runtime during instance.execute()
- when using 2.1.3, the test suite will not have proper
error handling during setup phase, as 2.1.3 does not
return command exit codes. this is adequate for use on
jenkins until the fix for 2.2 is merged in upstream
- refactor image setup code
- improve error handling throughout
- change behavior of --upgrade setup_image to only
upgrade cloud-init
- add --upgrade-all setup_image flag to upgrade all
packages on system
- clean up detection of cloud-init version
- output cloud-init version at end of setup_image
- use 'yum install' rather than 'yum update' in
setup_image.upgrade in case cloud-init not installed
- update help in setup_image args
- clean up image config
- new image config format allows finer control over
platform specific image config, with less verbosity
- clean up handling of image config throughout platform
- added additional releases and distros
- re-ordered releases.yaml in order of release date, and
added EOL comments for future reference
- allow image config to override setup options with
'setup_overrides'
- allow image config to specify preserving base images
for lxd
- allow using images from images.linuxcontainers.org for
releases other than ubuntu
- improve waiting for system to boot
- separated out determining if the system has booted from
determining if cloud-init has finished
- do not wait for cloud-init during setup phases, as it
may not be installed
- use 'systemctl is-system-running' or 'runlevel'
depending on init system
- poll for system ready inside the image rather than
through instance.execute() to make pylxd too many open
files error take longer to strike
- clean up code for handling waiting
- update lxd image metadata and templates if necessary
- many lxd images that do not come with cloud-init
installed do not have the necessary templates to write
a nocloud seed into the image
- if necessary, export image, extract metadata, add new
template scripts, and import as new image
- add new tox environments to run tests
- new versions of pylxd only available through pip on
xenial, best to avoid using pip outside a venv
- environments 'citest_old_pylxd' and 'citest' provide
entry points into the cli, allowing use of any test
commands, using pylxd 2.1.3 and 2.2.3 respectively
For more details, see:
https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/308218
--
Your team cloud init development team is requested to review the proposed merge of ~wesley-wiedenmeier/cloud-init:integration-testing into cloud-init:master.
References