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
* 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
* 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
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
* 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
The update-status hook is supposed to be lightweight; prior to this
change the charm was running all of the handlers including a no-op
checking for upgrades to openstack. This patchset builds on the
depends-on patchset and gates the update-status hook against those
handlers. Note that update-status is handled using the default handler.
Depends-On: I7ca97db646ada95d7f5541ca4e2cf14013c0d7a6
Change-Id: I1e14e609567d00bed6e8bb755acabd08c1113469
Closes-Bug: #1824119
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: I02d740e1bfbd746385dabe551cd0f6058a28ebf6
We should increase concurrency using processes rather than threads
for the Gnocchi WSGI application, avoiding high memory consumption
over time under load.
A previous version of this change missed the newton specific version
of the apache configuration for gnocchi api.
Change-Id: Idb355dc5f5fa404140819f4b28940e9bbc1693e6
Closes-Bug: 1806008
If we try to render the Ceph configuration while
key is None, this raises an exception as it expects
a str
Change-Id: Ie1cc8252035336d377a63e8cf51600ec3a59412b
Closes-Bug: #1869989
Removing and adding back ceph-mon relation to gnocchi unit, the unit becomes
blocked. Since the flag ceph.create_pool.req.sent is already set, its not
triggered during subsequent add of ceph-mon relation. This makes the relation
inactive.
This patch resets the flag ceph.create_pool.req.sent based on the flags that
will be reset at ceph-client interface when relation is broken.
Change-Id: I3a1f4a0fa61c739c8e6d6581670438944dfcbc7c
Closes-Bug: #1856936
Alex Kavanagh