* Update charm-designate from branch 'master'
to a8152b789c0f1e0b2847b8619abe6199a2e1b3ca
- Merge "separate rndc.key file per application"
- separate rndc.key file per application
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>
* Update charm-designate from branch 'master'
to d875ad61f061a708c64aee9cf1397b992c5077ce
- Updates for caracal tox.ini
Update the tox.ini file(s) to use the constraints file from
zaza-openstack-tests.
Change-Id: I6f21a215e8149880c0e16ed747f1fc378359189e
* Update charm-designate from branch 'master'
to 5790a8052a8105fc84af01b9b2b3550324acca59
- Updates for caracal testing support
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
* Update charm-designate from branch 'master'
to 14f11a18120d6ea6a9866d2d51953b54166cb375
- Ensure get_requests_for_local_unit doesn't fail on incomplete relation
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
* Update charm-designate from branch 'master'
to 73a39d4c148a303df403a7be2099663d22c24a42
- Add docs key and point at Discourse
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
* Update charm-designate from branch 'master'
to b657a63abdb1990ece815805d2d3e1632f66afa4
- Enable jammy-antelope voting and drop kinetic-zed tests
* 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
* Update charm-designate from branch 'master'
to 6711b12054e2da999bf7f606344f6bb9af2768b7
- Add support for HAProxy L7 checks
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
* Update charm-designate from branch 'master'
to f84cee2634e6d9605fd154be40f2c04426eba01e
- Prevent update-status to run unrequired handlers
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
* Update charm-designate from branch 'master'
to 8a4940bbb108124246ad3ae830964cf58dfc9ec3
- Add check to expose internal endpoints
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
* Update charm-designate from branch 'master'
to f87d01015bebbc7758612f27082f4108ceb94a7d
- Use the default source origin for mysql & rabbit
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
* Update charm-designate from branch 'master'
to 66c5f42350449f77e8518665cec9c052bc6d17c3
- Build separately for each supported series and use binary builds
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
* Update charm-designate from branch 'master'
to 1dc253a0980134b16c80b29bf194796d118c353a
- Ensure services are not started while unit paused
Closes-Bug: #1983594
Change-Id: Ib05687d0146fee7609f36ca8692dafe0082846bc
* Update charm-designate from branch 'master'
to 13211f092c57577a39cd0429e723faae3f1efe4e
- Add Kinetic and Zed support
* 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
* Update charm-designate from branch 'master'
to 1fef3793f5b4f089969a746ba8be33972ef58f10
- Disable designate-mdns service until the configuration has been rendered
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
* Update charm-designate from branch 'master'
to fc616b48c072f1dd425ff53f39f2f9a4163c2468
- Merge "Add *.charm to gitignore"
- Add *.charm to gitignore
This patch adds *.charm to the .gitignore to ensure that any built
artifacts are ignored.
Change-Id: Iedd404a0d075e80857d0f9517fae49679a52dad1
* Update charm-designate from branch 'master'
to 3fce0cb6c0618d37631bee48a4bcea9bae7a96c7
- Add NRPE service checks for upstream DNS
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
* Update charm-designate from branch 'master'
to b53106c7140dccfe941683e4ecf71fe18ef3dc0a
- Merge "Updates to enable jammy and finalise charmcraft builds"
- Updates to enable jammy and finalise charmcraft builds
- 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
* Update charm-designate from branch 'master'
to dc2b12cc330775d17fdaf2cab525fa99d1376dce
- Update to build using charmcraft
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
* Update charm-designate from branch 'master'
to f6121b5691db3080510b9a3339e604c00e16ab8a
- Use unittest.mock instead of mock
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
* Update charm-designate from branch 'master'
to 81c8cbf4a60de9dcc454cdc8717d67ad31f55ea2
- Add final dot when missing in nameservers
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
* Update charm-designate from branch 'master'
to 1e7035e2f0bf3100aabccb639c92be7eef0d5b0d
- Merge "Additional test updates"
- Additional test updates
* 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
* Update charm-designate from branch 'master'
to ff985f9111fd12e624745f7398b5e5f9c55ab06f
- Merge "Allow Set managed_resource_email on designate config."
- Allow Set managed_resource_email on designate config.
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
* Update charm-designate from branch 'master'
to 0e1e3e89b6b62ef49b0e72ee435123eec1830a3d
- Allow set managed_resource_tenant_id.
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
* Update charm-designate from branch 'master'
to 3ae0be599b4433919e3db6526a26070fea536db5
- Add NRPE checks for services
Adds the nrpe-external-master layer and checks for services managed by
this charm.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/436
Change-Id: Ice5eada838626059f8cb2c427f7b9b0884317660
Closes-Bug: #1897809
Related-Bug: #1933643
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
* Update charm-designate from branch 'master'
to 6734b495fdaf5e42a0082847e9aca583a57f9f41
- Merge "Moving to OFTC"
- Moving to OFTC
Change-Id: I863b565efd26ad1e22fd48562d08df5676ee3779
Signed-off-by: Nicolas Bock <nicolas.bock@canonical.com>
* Update charm-designate from branch 'master'
to 4e9d4756a2003859d668e7233fc3e38e0c72c390
- Clear shared-db.setup when departing shared-db
When shared-db is rejoined the charm will reconfigure the DB IFF DB
related flags are cleared.
Change-Id: Ieb575d6aa220f10c519425f1e1a6f59e29c512f1
Closes-Bug: #1887265
* Update charm-designate from branch 'master'
to ed1c6c502123c5be64954f8b4cb43b131f5aa236
- rebuild - restore c-h proxy env vars for add-apt-repository
Change-Id: Ibf5f1b4d284b9040740ad24d442ee4a46cb69db4
* Update charm-designate from branch 'master'
to 852d0a4d32c23aa1367f19967bcde60833ffd326
- Test bundles for focal-wallaby and hirsute-wallaby
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: I327cf71fe81a1808b7ca08bd190ee2423f3beff3
* Update charm-designate from branch 'master'
to 334cd15ee66a92b00af8bcad512a725dcd8ed59d
- Updates to flip all libraries back to master
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I03364083cf79a0c2d0dabb7eca1f28ac9bde4063
* Update charm-designate from branch 'master'
to be3dd9ccbcaea00264d6a4cfe3d0bbb1bab11db7
- Add wallaby package version
Change-Id: Ie687140212c48df6fc6e717efcbcc848388c063f
* Update charm-designate from branch 'master'
to 68c99e78d56a6f596a35ed7b45706ba9b6291640
- 21.04 libraries freeze for charms on master branch
* 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: I3cd7f19cfcaa23b46b2a064490ead713ed587789
* Update charm-designate from branch 'master'
to 2cbaedab44293351192e9ac2eb9982dc4d902f08
- Add hirsute and remove trusty from metadata.yaml
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I5bf5f91ce065e54bcca4333527a5fe497d8ebf70
* Update charm-designate from branch 'master'
to ac39378132dbe4809b78e4ec374c25efe3cf05ca
- Merge "Add new osci.yaml"
- Add new osci.yaml
This change is preparatory to migration Ubuntu OpenStack CI
from Jenkins to Zuul
Change-Id: I16e82e0f295a9c0f6f21e4ff343e2f1afda1d82d
* Update charm-designate from branch 'master'
to 4a54e9b3e54e911519357e9f352e351e973be260
- Updates to pin charm-tools to 2.8.3
* 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: Ic1d783ea841da5ffe331006af1ceeacf06dbcbb7
* Update charm-designate from branch 'master'
to 38c8fc48d2e04d19d7da5973b0911fdbcacb45b4
- Rebuild to use charm-tools pre 2.8 release
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I35600c4b7d60e0f03bc05e78cd1279a3b165e355
* Update charm-designate from branch 'master'
to 0cad21f0c2187508f3970e0c95f8c57cac7e33d5
- Rebuild with udpated charm-tools 2.8.2
Validate the newest version of charm-tools: 2.8.2
https://github.com/juju/charm-tools/pull/598
Change-Id: I73d998cc700eec024e74378f61de4acf82465238
* Update charm-designate from branch 'master'
to 03e00fb23514d8be3da782c5e5210b4a61aced22
- Rebuild for haproxy address bug 1912505
Ensures that haproxy.cfg is written with the correct
space address for peer backends.
Related-Bug: #1912505
Change-Id: Ic333d7722435e483f8bcd10892167ed923f0885a
Zuul