These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal. They do NOT lock the charms
down, and don't change the testing branches to stable branches.
Change-Id: Ieb68946379d497db3ac385513c528b852dba88cd
* Voting was turned on for jammy-antelope in the
project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
is turned on in individual charms
* Kinetic-zed bundles/tests are removed
Change-Id: I37c5aff2d71eae71015d1a1986fb73f64b864a94
When creating Openstack VMs the user has to specify the image it wants
to use. sstream-mirror-glance adds a date to the image name, so they
always have to recheck which is the current latest image.
This commit adds the `set_latest_property` configuration to include
--set-latest-property to sstream-mirror-glance command line argument.
When --set-latest-property is given sstream-mirror-glance will set the
recently synced image with the `latest=true` property and then remove
the `latest` property from all the os_version/architecture matching
images.
Configure bundles to fetch simplestreams snap from edge channel
Closes-bug: #1933130
Change-Id: Idf78294db7abb8c81d637086e8142782bf1dd36f
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/853
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: Iff2f3d0e011b47d895136ab7376f0e7d9c3955fb
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: I2b4ecddd0aa8b7dfcb3cf739a2f52ef93dc7ecf2
* drop xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I248d0c92e64692127e2a53a8cffc2efe56a8d790
The functionality of use_swift where a local apache2 instance was set up
for metadata was deprecated for removal and this change actually removes
this. However, the option itself can still be used as an indicator
whether Swift is intended to be used for simplestreams metadata or not.
If the usage is explicitly requested, the charm but Swift endpoints are
not yet present, the charm will now will set the unit state to
maintenance in addition to local logging that was done previously.
Swift presence checking is now endpoint-based instead of being
service-based (no use for the case where endpoints are not set up while
the service is in the catalog).
The lack of swift presence is also ignored for the purposes of
generating proxy setting context - if the endpoint is not there there is
not point in trying to generate NO_PROXY rules for it.
This change also makes test bundles use ceph as a storage medium for
glance since out of space errors were encountered during testing as the
glance unit was running out of space for image storage.
Closes-Bug: #1942047
Closes-Bug: #1934563
Closes-Bug: #1938069
Change-Id: I6519b1449806ad19ee4545501bc4631c9f8e535f
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Sync libraries.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I2a09dc92ae59ed43c87c3c24def1240c117482fd
Using a swift endpoint to store simplestreams data is more
typical than using the webserver on the gss charm itself.
Switch all tests to use this approach and refresh all bundles
to be consistent in layout.
Change-Id: I36e3faa4c202ded602620aa606ce6c13d9ab699a
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/335
Drop support for sending sync status messages to a RMQ exchange.
This was used by conjure-up which is no longer maintained so
drop the supporting code, metadata and options and remove
RabbitMQ from all test bundles.
Change-Id: I504508a64e50a9d331f6c5d69b292d9ccc20da3d
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/321
Switch over to using the new simplestreams snap instead of using
the largely unmaintained packaging in distro (and various PPA's).
This drops direct integration with the simplestreams codebase
in preference to just calling the sstream-mirror-glance command
with the correct parameters.
This commit includes refactoring of 'custom_properties' handling
which was actually broken - there was no loading of the yaml
formatted list, which was probably overkill, so the option now
takes a space separated list of key=value pairs, for example:
custom_properties="hw_firmware_type=uefi hw_vif_multiqueue_enabled=true"
Fix version comparison in script wrapper.
Drop Trusty support - snaps on Trusty are awkward requiring new
kernel versions and trusty support was only retained for upgrade
purposes anyway.
Drop unsupported Xenial OpenStack versions.
Fixup CA cert handling to use any charm installed CA cert (including
that provided via the certificates relation) and install cert
to snap compatible location for simplestreams to use.
Add basic action to perform image sync on demand an refactor
the glance simplestreams sync wrapper to work within a hook
context to support the action.
Disable automatic scheduling of image syncs by default as this
tends to be racey during deployment resulting in images being
synced to glance unit local storage.
Add bionic-ussuri bundle and make it the default smoke test.
Deprecate source and key options - no longer required for
deployment with snap.
Change-Id: I730df6b7f5955ddfeea5b8de15490ac083823f5a
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/321
Added support for charm to install py3 packages
Fixed gss script to run on both py2 and py3
Added the ability for the script wrapper to get the distro version
so the gss script can be launched with the right python binary.
focal-ussuri test bundle added and smoke/dev tests changed to focal-ussuri
charmhelpers sync
-----
LP related bug: #1853456
Change-Id: I161d8a0fa9787f0d5409f7bf386c22d98aae0a64
This patch migrate tests from Amulet to Zaza, and Python3 only.
SSL is enabled for all bundles with charm-vault, except trusty, which is
not supported by vault.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/55
Partial-Bug: 1828424
Change-Id: I4dacf33d3ab4dedbbe62a36b1b2ce5606e51d234
Signed-off-by: Joe Guo <guoqiao@gmail.com>
The bundle disco-stein was in the dev bundles because
a bug with the Python 3.7 syntax prevented the success of
the deployment of HA clusters. This bug is fixed, we can
reintegrate disco-stein in the gate bundles.
Other small additions:
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
LP Related-Bug: #1823718
Change-Id: I37308917d3bb31a7c53fce6a10addf95a85bb2b5
When use_swift=False in addition to syncing images into glance, also
host the product streams metadata using apache.
Change-Id: I6aad2fee3670f575014d0845f3bd7aae6fa06785
Closes-Bug: #1840830
Also switch the func test to use charm-helpers in a venv,
removing tests/charmhelpers to be in line with the other
charms.
Change-Id: I8c83bf1fb35b10438cc87fd0b8c86cb5a4846a72
This patch enables SSL to be used with glance-simplestreams-sync.
The ssl_ca option allows a base64 encoded PEM CA certificate to be
used with g-s-s such that the keystone and glance HTTPS sessions are
verified using that certificate.
A new basic_deployment_ssl.py is introduced that just verifies that the
gss charm can get gss to perform a sync; this verifies that gss can
communicate with https versions of keystone and glance.
Note that the simplestreams package also requires a change for SSL to
function properly. As simplestreams doesn't seem to use PyPi, the
version from the git master will need to be used.
Change-Id: Idcdcb2c933a92a558e729aeb718b58d4077621a7
Closes-Bug: #1802407
Add a tactical change which is already merged into charm-helpers.
This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.
Reference:
4835c6c167
Change-Id: Ia211f4990e80496c1f47489b7c9679d38d586da5
The charm does in fact set workload status. But not with a "ready" message.
Check for "Sync completed" workload status before continuing with further
tests. This workload message alone indicates the health and functionality of
the gsss charm.
The test for glance services is orthogonal to testing the gsss charm. Removed
it.
The premise of this functional test is to be a black-box
functional check: can the charm sync an image? If so,
job-done, move along.
Other explicit checks which came along with legacy charm
tests have proven to be brittle and of little value in
catching actual, meaningful issues. As such, remove those
introspections.
Alex Kavanagh