This change fixes an issue that when the charm-designate is
related to two different designate-bind applications, the same
rndc key file is used for the two different applications.
We fix this by writing an rndc_key_file per application rather than in
a single rndc.key file for all the units.
Closes-Bug: #1995975
Change-Id: I5dafeb2b4dcf9549260081d3674038f836d29f0f
Signed-off-by: David Negreira <david.negreira@canonical.com>
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: I466bebb1bf7574b21ed5db45e88ad1801df767c9
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: I380e012bee8c415aaf1929d06d64552319d6356b
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: I2836aadfe6b9a035c6838b144e3f65436e4c184e
* 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: I3f9c253a89906b8f1dde4f60f1fdc30119a8d31c
This change add several configuration options to enable HTTP checks
to the HAProxy configuration, instead of the default TCP connection
checks (which continue to be the default).
Closes-Bug: #1880610
Change-Id: Ibadd5648cdf69eef42b05e29772dcae9897d668b
Before, the update-status hook would run many handlers
that would have been normally done only during
configuration changes.
Consequently it creates an impact on the service and
apply changes every time the hook is triggered, which is
in most deployments every 5 minutes.
This prevents the DNS zones managed by Designate to be
updated constantly and potentially avoid race conditions
within designate components.
Closes-bug: #2003528
Change-Id: I0d4fea182da1316c0c30c143e64fcd2ca682afff
Currently, the charm ignores the use-internal-endpoints config
option that is being inherited from the Openstack Layer. This
patch adds a check to ensure that the internal endpoint is exposed
if this is set to True.
Closes-bug: #1995188
Change-Id: I48a04ac619204ba109d87ca05de7cbe308592486
The functional test bundles specify that the mysql and rabbit
services should use the openstack-origin reference field, but this
is not actually relevant to the rabbit/mysql charms (e.g. it doesn't
make sense to install rabbit from cloud:jammy-zed as rabbit is from
the distro).
Change-Id: I50693d6e85b2ce427ff184555cdfae66096f3f6c
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.
Change-Id: I1bf4aac08cf7388fec4550d40887a8df45927589
* 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: I2c98ab0f82aa6d6d0a43365cee04d6da34a39ce4
As per the bug report, designate-mdns service appear to restart multiple time.
This patch disable the service until the configuration has been rendered.
Closes-Bug: #1925233
Change-Id: Ib9843bda9c6967ce50cec8d721079bd70f7f3040
Added NRPE checks to detect when upstream DNS servers
are unreachable. We had a case where a customer changed
settings on their DNS servers which caused an outage.
The added check will allow our alerting to capture
cases where the upstream DNS servers become unreachable.
One service check is generated for each value found
in the 'nameservers' charm config params. The checks
use the 'check_dns' command with a host value of
'canonical.com', and each command checks a corresponding
nameserver value from the 'nameservers' config params. All
other optional flags for 'check_dns' are using the default
values.
Closes-bug: #1850216
Change-Id: Iea601977851d5c4ea2b9b79071d94b2385637d57
- 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: I3b005253025fa7ba2b0cdb918fe4134c44316cf0
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: I8768cf21899108de80aa9f6cb7da9a91b91cdf9f
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: I7b12f467e329e2693e4c7349f328133a1ec3cb00
The configuration option nameserver expects each value to have a dot (.)
at the end, currently when this dot is missing the servers creation
fail, the error doesn't bubble up. On the neutron-api charm adds the dot
automatically when it's missing in the dns-domain config option, this
change makes the Designate charm behave in the same way.
Change-Id: If335c9b5b1b2adca3e39fa4f1d182dfbe362f874
Closes-Bug: #1952656
* drop trusty/xenial metadata and function tests
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: Icf909b3d01fdf374ab172fca2766fadd112b40bf
With this patch managed_resource_email can be set via charm
with juju config managed-resource-email = email@domain.com
functional for auto generated SOA records. that came from
Floating IP.
Closes-Bug: #1940864
Change-Id: I9f55564316fdb559481909dd7b196ef8fd9fe612
With this patch will allow to set the configuartion parameter
managed_resource_tenant_id that is required on some setups.
Closes-Bug: #1926659
Change-Id: Id76b798ef23f528f3440b6b33ce4bb9b4e680b0d
When shared-db is rejoined the charm will reconfigure the DB IFF DB
related flags are cleared.
Change-Id: Ieb575d6aa220f10c519425f1e1a6f59e29c512f1
Closes-Bug: #1887265