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: I75d4112af25ae1980e9901b35325c798040e7294
In a multi-region shared keystone deployment, we must set the
os_region_name config option. Without it, Masakari will try to connect
to the wrong API endpoints when it needs to talk to other services.
Closes-Bug: #2042924
Change-Id: I31ae1e011354fc9ded114babcb92f366256fadea
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
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: I0dbd4f5ce3d922a2f7c84e710d4faa276718debc
* 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
* Add libpython3-dev to allow the charm to be built. This
fixes a missing dependency with Cython
Change-Id: If0beacfe04b08ea7460dd241d2247f2afa002652
Ensure the RabbitMQ oslo.messaging section is used in all templates;
this configures SSL options when deployed in TLS secured configurations
with RabbitMQ.
Change-Id: I0821304b3f0e586e3a868e3c95294a688bae085a
Closes-Bug: 2007567
* 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: I5bf1b2a030c08461bc42c1e686af6220738ed98c
- 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: I59ab3d2fa63b534296c5a703322e9aa3e061bff5
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: Iee0101df1f2a943f3da8ad8b5719bdaa031af151
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: I55ccb5548917c8431b0080c956bec5543d31a9a3
When RabbitMQ is deployed in HA mode the transport_url parameter of
masakari must reference all RabbitMQ instances. Previously it
referenced only one. Now uses the configuration from the base OpenStack
layer
Closes-Bug: #1950331
Change-Id: Iea9d4f2484b82c22939a258e7f9faa3030a9bd1e
When the certificates relation is unspecified with the
configure_tls method invocation, the masakari endpoints
seem to ignore the update to TLS. This change specifies
the relation which causes the endpoints to update correctly.
Closes-Bug: #1935986
Change-Id: Ib1a6ca1ddf64950ff13cf3a8904d9848710d96a5
Without this fix deployment fails with
ERROR cannot deploy bundle: cannot add unit for
application "masakari": acquiring machine to host
unit "masakari/0": cannot assign unit "masakari/0"
to machine 12: series does not match
Change-Id: Ib436e8916cb31fe049bc0a641fbd29fda2e0f260
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: Ic8d988993a52beb8c647f242860c4793610a6c92
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I101b9666f9d1e4a032a12edc5d5178f829e9ba1c
* 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: I05d305bbac9d81549208787e847a71c4aa75baee
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: Iacceaa4946c468ac5b5062ff6ee04835c833be62
* 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: Ie167177b18f4bd9043d31f741f323dfd0cbe970a
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I5ff54ca310c121869e39fc0f720cc31a3af92e98
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
The func test pr is to test/verify the reap instances change in zaza.
func-test-pr: https://github.com/openstack-charmers/zaza/pull/411
Change-Id: I744bd6f88c88ef30754bcf947c5379334b24631a
Adds config options to configure the notification expiration time
as well as how frequent to check for expired notifications.
Change-Id: I9607f01a800baded37cfc23b6bc9f8e6aecc2d74
Closes-Bug: #1773765
* 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: If79d772f8c843db4c2440dc5209bf8954ed72e05
The Masakari API service need to be TLS-terminated. This patch applies the
ssl_ options in render_config function.
Change-Id: I0acdaaf4ab6eb150d0d562cd978601726456d035
Closes-Bug: #1889787
Charmhelper sync to pick up the fix to the AMQP context.
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: I998a24697f93e5a8ad1eeabfd19b86ed631fa2fc
Closes-Bug: #1796886
Alex Kavanagh