* 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: I2c98ab0f82aa6d6d0a43365cee04d6da34a39ce4
- Add 22.04 to charmcraft.yaml
- Update metadata to include jammy
- Remove impish from metadata
- Update osci.yaml to include py3.10 default job
- Modify tox.ini to remove py35,py36,py37 tox target and add py310
target.
- ensure that the openstack-origin is yoga
Change-Id: I3b005253025fa7ba2b0cdb918fe4134c44316cf0
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: Ic1d783ea841da5ffe331006af1ceeacf06dbcbb7
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I35600c4b7d60e0f03bc05e78cd1279a3b165e355
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I5b232af01089555cbb80869ceee1e4bab90a79ea
Render configs always needs the cluster relation if it is available.
There is logic in OpenStackAPIRelationAdapters that checks to see if
this unit is alone. If it is it creates a 'cluster' namespace and
populates it with data specific to this node. If this unit has peers
then OpenStackAPIRelationAdapters populates the cluster namespace with
PeerHARelationAdapter *if* a cluster relation has been passed in. If
the unit has peers but the Peer relation has *not* been passed in
there is no cluster namespace and rendering of config that relies on
it (namely haproxy) fails.
To fix this, check if the relation exists and if it does add it to
the list of relations used to render configs
Change-Id: I6f34c28411db957d0b55155b8671bf981084bb6b