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: I0a38c624cc501b22c19ec69f4e50d6fbf5f3a24b
Patch out charmhelpers.osplatform.get_platform() and
charmhelpers.core.host.lsb_release() globally in the unit tests to
insulate the unit tests from the platform that the unit tests are being
run on.
Change-Id: Ifda8aa2675b4a756109254f62b9a600c42679cac
Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.
When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.
Change-Id: I2f0e316697aef630a321c6fca1553d337b04ddf6
* 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: Id4b79992d0a5220fa8013da03656e6b676d27967
This patch adds kinetic to the metadata.yaml and ensures
that a run-on base for 22.10 is added in the
charmcraft.yaml
Change-Id: I9107920cf997f6537b722e1bc4db9188fa966019
* 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: I782ea5c502b7bc0eb9941c7eb8d4b830f07b218a
- 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
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/751
Change-Id: Ia285c2d834cd0b9ab97fc944370172631995b83f
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: I8a57a9ae84668d67dd29dd819152716b366461a4
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: I315a7941cd6c5eaea698657af122adb221f5647f
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Sync libraries.
hisute-wallaby test is disabled (moved to dev) due to [1] as bundle may
reference a reactive charm.
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: Ib3056ce7f712514b035d9af95a6a6ac7f834531c
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ic5760af94bbc62f33ac5202711857b8a65f2600f
The 'hirsute' key in c-h/core/host_factory/ubuntu.py:
UBUNTU_RELEASES had been missed out, and is needed for
hirsute support in many of the charms. This sync is to
add just that key. See also [1]
Note that this sync is only for classic charms.
[1] https://github.com/juju/charm-helpers/pull/598
Change-Id: Ica9283d49eb57e127471bdfa8847fa0ea37d580f
It's not currently possible to upgrade to the
cinder-ceph way of doing things with a cloud
that relates cinder and ceph-mon directly.
Drive-by: Apply README template
Related-Bug: #1727184
Change-Id: Iec6caa0ba778fb3a17aba0fea357b05f68ee22be
* 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: If7594a71715a0c8ea268ceb9a576f54d85c8200c
Previously, we didn't have a control over volume_backend_name other than
the default app name in the Juju model. A common backend name to
multiple backends with the same character is useful because those can be
treated as a single virtual backend associated with a single volume
type.
Change-Id: I4b57f7979837d21a1b116007f3da707ee154792b
Closes-Bug: #1884511
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Iaf475b79232e651b5f236a6e6a36e54005fa9e2d
The network-get --primary-address juju-info fails on pre-2.8.?
versions of juju. This results in a NoNetworkBinding error.
Fallback to unit_get() if that occurs for local_address().
Change-Id: I7deee35df63f8f17bc1da5c4f303bef9f227bb9b
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: I9f252f378e4c76e6c44acf3e8a690cb39a299d30
* Re-trigger `ceph_access_joined` from `ceph_replication_device_changed`.
Without this, we could end up with incomplete `ceph-access` relation
if `ceph_access_joined` is executed before `ceph_replication_device_changed`.
* Seed `replication-device-secret-uuid` early in `config-changed`, to make
sure that it's set if `storage_backend` is executed before `ceph_access_joined`.
* Set `secret_uuid` as part of the `replication_device` config in the backend
config. Without this, Nova won't be able to access the proper secret for
the Cinder Ceph volumes, after a failover.
Change-Id: Ic023d05d5d17a663e1719de393bdd15f18a40484
* 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: I20570a90789e3d36339aa0bd4305e32af1226dfc
The new config option is applied only to the broker request to
create the charm replicated pool.
Co-authored-by: Marius Oprin <moprin@cloudbasesolutions.com>
Change-Id: I6bf9544af02d0622b8f714da97b5dbcf49d1d1af
This is required to get the updated broker request handler
containing the new rbd-mirroring-mode flag.
Change-Id: Ia4c1e9741ae8eab2e41d7ba4e4615475914c43e5
When assessing the charms status check that the current
ceph broker request has been complete. If it has not
put the charm in a 'waiting' state and update the status
message.
Change-Id: Iaaa2021a86b7e360f3255a52b27a49ef859beecd
Closes-Bug: #1899918