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: I5549fc5d72659dd3434543d13001101af3b613f2
* 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: I8cf89d0abcc196a83fbb8088b730ee74f774f6ee
* 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: Ie43538cc39e2115275802b328c9145df5955beb8
- 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: I909c4299c94edbf2ba7d2052c1642d04902878f7
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: Icf3da0aa6e1820b10f211eb5ab779ff5d3d3f394
* 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: I4d6b684a1257cc6bbb703b4a98d90e9f71972d9f
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ib7a6e24d74a8bb76eb20d101c5b621e05d0cc153
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby supporto.
hisute-wallaby test is disabled (moved to dev) due to [1].
[1] https://github.com/juju-solutions/layer-basic/issues/194
Change-Id: I218b3da58865add03ef1fd39988127f7ca0a2666
* 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: I01d014e6e735bdf368df2b7254b563b961eaf226
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I7491d754ed327f3b8604f04db7847541f2d56251
* 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: I335b204f7ca8888a0fc5e2465580c2ebbe24d2b0
The existing comment in the code expresses the correct intent:
"fetch current secret-id, if any, from relation with barbican principle"
but then attempts to retrieve the secret-id from the vault
relation.
Change-Id: Ie2694ba38e08fd9e864bf9d8fa0b63f0e185b8bd
Closes-Bug: #1871981
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
- sync tox.ini
- sync requirements.txt and test-requirements.txt
- Remove vault HA in functional tests as etcd/easyrsa were not included.
In order to have a faster gate, the HA on vault is dropped and it will
be tested in the vault gate test and other scenario tests.
Change-Id: I2eacde1d08734c32731df3dfa43da738871792a8
- 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: I964b9608ab3b8a81352cc56eb1176e360aae9d9e
Changes to tests to deploy barbican and vault with haclustering.
It now deploys 3 units of vault and barbican, together with hacluster
for both applications.
Overlay added to ensure all tests run in HA.
DocImpact
Closes-Bug: #1876107
Implements: High availability testing
Change-Id: Ia7abdc682fd583e15feba68fc11cdb89ab7c41ff
Pin the version of hvac for a consistent response type. Use the adpater
to get response code and json data.
Closes Bug: #1871981
Change-Id: Ia8517a75e7bc20f751eca83aaa84728cc62edee6
The hvac.Client post response is no longer an object with status_code and json
encoded data. It is a dictionary.
Change-Id: I1cacc8deda005cdbb2290d5ae821e4870608a41a
Since the relation with vault maybe contain more than one
token and we have no way to know if they are valid, we
support trying them all until we get a good one and raise
the error only if we tried them all unsuccessfully and
have no current secret-id otherwise return current
secret-id.
Change-Id: I2ee5ffe5d53e874efb3fabc6a880bf95b00a44f9
Partial-Bug: #1849323
This project already has disco-stein tests enabled, but since these
changes are part of a batch change on all the charms, I am keeping
the same title for all.
Changes for barbican-vault:
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
Change-Id: Icb0fadfaa140d0fd295b432a867794f9ec7edcf5
Also explicitly set ``include_system_packages`` to False.
While that setting is now the a default we consume from
``layer-basic`` it is more clear for the causual reader
of the charm source code.
Remove redundant entries from ``wheelhouse.txt``.
Change-Id: I076da27fd1ab30bc945e1f8474231a1064a5b61c
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I2c09f48895043bb73e5c32d986ecf38212d81cd7
Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.
As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.
For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135
Change-Id: I29304997cdbe3987fb0e55d3ea67b20550653704
This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again
Change-Id: Ic4d52185874ae5fc467de401ad91112f6fb84ee9
This change adds in zaza.openstack, as well as changing the
branch target of zaza to a branch with zaza.openstack
removed, allowing us to validate the new library
Change-Id: I72e19b9dafa712395c18c756e1304a812597c8a6
Alex Kavanagh