* 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: I01ea27e6bbde4ebaaf3d8efdd89d9d7cfe04ee2b
* 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: I3cc0af8443ecf62589c88d4e924cb633c419e87f
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
This patch also drops the impish bundle and unused overlay
bundles.
Change-Id: I85d45fd390eccfef2fbdcd9de96b7b7cf01483f4
This change puts the specified key/value config-flags into
the [DEFAULT] section of the config file rather than the [api]
section, as they were supposed to be in the [DEFAULT] section.
Additionally, this change switches to using the config-flags
support from charms.openstack.
Closes-Bug: #1986943
Change-Id: I77a35c074e234c3bdfa78800b05ee770492e0694
The config flags are a comma-seperated list of keys and values.
This enables an operator to pass arbitrary configuration into
the masakari-monitors configuration.
Closes-Bug: #1941650
Change-Id: I3571bf7dfcb092ce5d04f439806e9a25465e16c5
- 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: I0c34ec81953fc00d5b51b14ba80092f666577d18
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: Ida2665d20845e20b51f3270870ad9cf55a824921
This corresponds to the upstream change titled:
"Use hostname to avoid clash with section".
This avoids a clash with the section of the same name.
An ussuri masakarimonitors.conf template is added that
uses the hostname config option. The base template continues
to use the host config option for older release, inline with
upstream.
This change also updates tox.ini, src/tox.ini, and adds pip.sh
from centrally managed release-tools.
Closes-Bug: #1941643
Change-Id: I4b5b528cf24477746bf7ff6ffedfef0b13d91816
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: I13057e3e6544c8024d39c611ec8bdbbec387da6a
* 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: I07b01cf8f2762a918b0f55ac90a6173f56bf9406
The Masakari process monitor is explicitly outside the scope of
what we chose to enable when the original charm development was
done for Masakari.
Drop installation of the process monitor package and related
templates and configuration.
Drive-by fixup of requirements for older Pythons.
Related-Bug: 1941623
Change-Id: Id883c117e73e71842fbe7a96e0471b37e999020f
Upstream process_list.yaml.sample, which was likely
a source for the charm version, has slightly different
binaries paths. This patch provides correct systemd service
names and binaries locations for the masakari-process-monitor
service.
Closes-Bug: #1941644
Change-Id: Ic209723fe7bfdf030310cf8a3e5607caf6a73853
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: Ibc09d03ed16847fa81c50487b8c7ded9d87b90e3
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Id3cc6895c0a6c1e631dbbe925c01d05582ea5b7e
* 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: I9ba14524ddea4b0a0a63171abfa38b9e1bb1b2b5
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I8623128fd878d22b4b89c1316eb8c1c9234304b6
* 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: Ibc4a8b508697208e1be4be0548df1cdcf92a472c
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: Ia8767f0d7ba14e7d830c323fb81d02fc29b7c3af
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: I59a13af81392a35c647fe01d2c14745ed84121f8
* 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: If009ba69de6463374b3c929d8888b90595ebb91b
If use-internal-endpoints is set to true then reflect that in
the masakari monitors config file.
Change-Id: I26ad45ff0fa4088a4b0a0f64d031bb805af45a78
Closes-Bug: 1895657
Masakari monitors looks up the masakari endpoint in the keystone
catalogue, to do this it needs to know the region it should be
targetting. To achieve this this change adds the region config
option.
Change-Id: Idb593ee8017252d0cd21dd58ee6d662536eba5a4
Closes-Bug: 1895656
Also remove jinja2 from wheelhouse.txt as is a duplicate
and due to improvements in charm build it now causes the
build to fail.
Change-Id: I62f5315c32cfc014ef8a8581ca5f977ec6114263