-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration tests for COS integration for OpenStack #277
Integration tests for COS integration for OpenStack #277
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed until helpers/lxd.py
, cool stuffs!
@yanksyoon I think you can merge this, when you approve it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for the changes!
Overview
Follow-up to #266 to provide integration tests running on the openstack cloud.
An integration test related to COS and repo policy compliance will be provided in a follow-up PR.
The OpenStack tests are not yet included in the CI, as there is another PR working on getting Openstack to work on the CI: #269
This PR does also refactor the helper modules. Due to parallel development on the openstack integration tests, the other integration tests have not been tested to see if they still work and this will need to be investigated in a follow-up.
The openstack applicable tests are marked now with an
openstack
pytest mark.This PR also fixes/adds:
Rationale
Add integration tests to ensure proper functioning.
Juju Events Changes
n/a
Module Changes
A separate package has been introduced and the helper modules have been placed there. There is a module for LXD and Openstack that contains cloud specific code. An interface
InstanceHelper
has been defined which is implemented for both clouds. It is required to handle cloud specific helper code asrun_in_instance' or
ensure_one_runner' or `get_runner_name'.The
test_charm_metrics_{success,failure}
tests have been adapted and the openstack applicable tests are marked with anopenstack
mark.Beyond that:
openstack_manager
: Now writes ssh key with correct permission and ubuntu useropenstack_userdata.j2
: Fix case where write_post_metrics function is not called on non-zero exit code of previous commandLibrary Changes
Checklist
src-docs
urgent
,trivial
,complex
)