* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* Locked requirements using pip-compile:
* existing (test-)requirements.txt ->
(test-)requirements.in
* pip-compile to *-py3[8|10].txt using python3.8
and python3.10.
* Updated tox.ini to use the appropriate merged
requirements-*.txt files.
* Removal of lunar from metadata, charmcraft.yaml
osci.yaml, tests.yaml and associated bundles.
* Locked libs and tests to stable/bobcat branches for:
* charm-helpers
* charms.openstack
* zaza
* zaza-openstack-tests
The API service needs to listen on all IP addresses to allow different
haproxy frontends reach it out.
By default the service binds to 127.0.0.1, and binding it to
options.service_listen_info.watcher_api.ip prevents the assess_status()
code to succeed, this is a common pattern[0]
This change expands the testing bundles to deploy a fully functional
cloud and run the testing class WatcherTests which uses the
vm_workload_consolidation strategy[0].
- Add charmcraft.yaml to build the charm using charmcraft-2.2
- Add osci.yaml to run CI jobs on zosci
- Align tox.ini and src/tox.ini with the rest of the charms
- Add testing bundles jammy-zed, jammy-antelope and lunar-antelope. The
other bundles are dropped
- Clean up requirements.txt removing unneeded dependencies
- Update metadata.yaml to declare jammy and lunar only
- Use generic zuul job templates
- Add src/wheelhouse.txt
- Install python3-apt instead of python-apt
- Drop pip.sh
- Drop unneeded pining from test-requirements.txt
