Backport the watcher support to zed. This involves the following:
* Update .gitreview file
* Update osci jobs in osci.yaml
* Update src/metadata.yaml to specify jammy/kinetic support, fix
descriptions
* Update src/test-requirments.yaml for stable/zed zaza branches
* Update test bundles to use zed
* Add override to specify the common cpu-model for migrations
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