Codenames stopped at Train so this fills gap
all the way to Caracal as well as accounting
for releases that share the version. Where more
than one release shares the same version we set
the highest release as the named release for that
version to avoid unnecessary upgrades.
Closes-Bug: #1973303
Change-Id: I048921beb6aaa66563d83253efb6152caa315ba9
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: I97b3f9d3e810a7325f288e220e2d4c95c832eb39
This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].
[1] https://github.com/juju/charm-helpers/pull/824
Closes-Bug: #2028683
Change-Id: I000d9f2039ccab2ec5ef60cc3b55fe1d3201f8b6
* 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: I463ac3b04112941489a5211f75e8e24db0aa82e0
to the HAProxy configuration, instead of the default TCP connection
checks (which continue to be the default)
Closes-Bug: #1880610
Change-Id: If7841f710d0dfffdc7ee6b424cb77fc34aeae823
* 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: I1a250a0591c15971840bbd6130c7cff3822eed4f
- 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: Ic853bb3a98d1cafba9304cf19ff2c4ecb1df1104
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
Change-Id: Ie6e4716482a1043d4936b1343b1050fc88e54403
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.
Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I991fa5afc63c09fcb3f0982c08c815d5561b7f07
* drop xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: I8115cc36ef475786582be92d707a98d7f691dea1
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
hisute-wallaby test is disabled (moved to dev) due to [1].
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I4df3a7b4e1ab5aa7660424c4713f175df9f3f711
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Icb27ed77798c9a4c1389143d6b61fb5205983b16
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I3a9cafd1237777b4897badc8b0e00b598bcbc1e0
Rebuild gnocchi charm to pick up the charms.openstack change which
creates the ceph pool based upon the name of the application deployed
rather than the name 'gnocchi'.
Closes-Bug: #1918821
Change-Id: Ic57c75a77fe0e6c9b9f37003a0f4f6af87e3bdf9
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Ia7ef1f933d765981ab8075223728471c51751576
* 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: If3e84c2dd4db8643b6f3c61426fdc5ffa455faf2
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I8273f8cca5f7abf3945d6e0c653da62a3f6623cc
Ensures that haproxy.cfg is written with the correct
space address for peer backends.
Related-Bug: #1912505
Change-Id: I725daa9d346cbc8f49f76bbecdbd7aaff275b881
Includes updates to charmhelpers/charms.openstack for cert_utils
and unit-get for the install hook error on Juju 2.9
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I0bf71eae53cdce8f109d40b6428f4a3e19061117
* charm-helpers sync for classic charms
* rebuild for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure master branch for charms.openstack
- ensure master branch for charm-helpers
Change-Id: I11b97634ce279047658b399718b1f4b1cc51e548
Ceph Bluestore Compression is a post-deploy configurable option
and allowing to update the broker request is required. Drop code
that gates the sending of pool broker request, the original issue
has been fixed in the interface code and it is now safe to call
multiple times.
Unpin flake8, fix minor lints.
Change-Id: Ib8a209fffddc882c4b42a620f284a0d0504a749f
* 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: Icf6ef2ae4b845f4dc612a5d949144eb5c11030b1