A bug was introduced when changing ceph-client to
an operator framework library that caused the
fallback application_name handling to present
a class name rather than a remote applicaiton name.
This change updates the handling to get at an
`app.name` rather than an `app`.
As a drive-by, this also allow-lists the fully-
qualified rename.sh.
Closes-Bug: #1995086
Change-Id: I57b685cb78ba5c4930eb0fa73d7ef09d39d73743
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1022
This unpinning is meant to solve the issues with tox 4.x breaking
all the virtualenv dependencies.
Change-Id: Ifc3381b2f2e4e41ebf6676080bf1831baffb0d42
This patchset changes a single action, 'change-osd-weight' so that
it's implemented with the operator framework.
Change-Id: Ia11885a2096b6e4b1ecda5caea38939e17098e1d
Add support for the metrics-endpoint relation. This allows relating
ceph-mon to prometheus-k8s which is being used in the COS Lite
observability stack. Upon relation, the ceph prometheus module will be
enabled and a corresponding scrape job configured for prometheus-k8s.
Drive-by test improvement for the utils module
Change-Id: Iaeee57aaa6f3678fdaef35f2582b4b4c974acb2a
This patchset implements the first rewrite of the charm using the
operator framework by simply calling into the hooks.
This change also includes functional validation about charm upgrades
from the previous stable to the locally built charm.
Fix tempest breakage for python < 3.8
Co-authored-by: Chris MacNaughton <chris.macnaughton@canonical.com>
Change-Id: I61308bb2900134ea163d9e92444066a3cb0de43d
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/849
This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.
Change-Id: I546438f1af6b3f779aa01e9ddd8c8ae7c3b7d063
* 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: I9c2419e39899f02e99b07d5dbd0b4cd0f51e03ba
Also fix for bug where the mgr daemon is not ready. A wait is
introduced if it is not ready before trying to assert pg-autotune.
Closes-Bug: #1848576
Change-Id: Ic3c1e1f7902f7e2052dc4cf432303f874369238d
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that python35-charm-jobs is retained since this charm is supported
on Xenial.
Change-Id: I51693cd7d535f2b5acb5ba118951f466ef7ac51f
Story: #2005924
Task: #34228
This technique was borrowed from the tox "cover" environment in
openstack/nova's tox.ini. This leverages the fact that stestr lets
you override the python executable via the PYTHON environment
variable. Doing this allows us to easily generate coverage for our
unit tests.
An important caveat is that this does not provide any coverage for
tests via zaza, amulet, etc. It is purely focused on the unit tests.
Note that this replaces the previous .coveragerc; coverage
configuration is instead pulled from tox.ini.
Change-Id: Idedc9707c2670825e2307ffacf40496d52f03d13
Make sure the exact python version is used for specific python
unit testing targets.
Update functional tests to include nova-cloud-controller.
Change-Id: I8d57719fce4f152a105d8a61c08b556873105708
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ia6790f1f07eca936ec8a3d7b9403ad439275eb25
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This stops leader_set from throwing backtraces, and instead logs the
error and continues as though the charm is not the leader (which is the
case when leader_set(...) fails).
Changed the py35 tox job to invoke py3 (to allow it to also test under
py3.6 on artful+).
Note that the pep8 check is still py27, so the additional # NOQA is
to handle Py2 not having FileNotFoundError.
Change-Id: Ic25d29983db9a0738d83e66de4673bb50594b599
As of pip 10.0, --allow-unverified is not permitted.
Use of the flag in this repo was previously used to force
installation of python-apt to accommodate certain unit tests.
The unverified package, python-apt, is no longer necessary
for test execution.
Related-Bug: #1760720
Change-Id: Ieb62ac460f605f5599206379b79075704a6fc3e9
Various changes to migrate the charm to work with Python 3. The tox.ini
has been modified to inlcude py35 and py36 targets for testing against
Python 3.5 (xenial, zesty), and Python 3.6 (artful+).
Change-Id: I009de528428aaca555b49f3fc17704dcf5f2a28c
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
Change-Id: I6efa2096237d8cbc6e869fc0f43dc622d4bea8e7
Related-Bug: #1659575
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: I75d0b5e0ff5ba3619e5f24567deb77c404b822cb
All OpenStack Charms now contain identical tox.ini files,
not to be modified or made unique within each charm repo.
This is to ensure consistency across charm repos in tox
target naming, approach and purpose, also giving the
charm dev and test experience additional consistency.
Also create empty dirs with .keep files where necessary.
Some classic charms have actions and/or lib dirs, and some
do not. In all classic charms, flake will now check those
dirs to ensure lint coverage of existing or future content.
Change-Id: I345e0b5f365bde8b7331a9dab53deb6984ec96cd
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.
Rename amulet tests inline with gate-* and dfs-* naming standards.
Update README to refer to functional testing section of the charm
guide.
Change-Id: I0d378cdffdc2eaa5c34578e85aba6acb7a47a41d
Avoid use of 'service --status-all' which is currently
broken on trusty for upstart managed daemons; the change
moves to detecting how the daemon is managed, and then
using upstart status XXX or the return code of service XXX
status to determine whether a process is running.
Fixes for IPv6 network address detection under Ubuntu
16.04 which changes the output format of the ip commands
slightly.
Update the version map to include 8.1.x as a Neutron
version for Mitaka.
Fixup mocking of apt during load of unit tests and ensure
that tox does not use any site packages, ensuring that
test execution is isolated from installed OS
Change-Id: I0f8d7cb2689f5e4c94390b324850e4e9b6e10eb5
Closes-Bug: 1581171
Closes-Bug: 1581598
Closes-Bug: 1580674
The new release of charm-tools no longer ships the charm
command; update minimum version requirement and switch
to using charm-proof instead, unblocking current pep8
failures across all charms.
Also pin the version of requests to 2.6.0 until theblues
(indirect dependency of charm-tools) sort out its
requirements versioning.
Change-Id: I29210e210b90aa81bf6ee9a020bd6de656750a77
This change will add two new actions to the ceph-mon charm. These
actions will allow the user to create and remove cache tiers from
existing pools. Both writeback and read only mode are supported.
Limitations of this patch include not having fine grain control
over the cache tier properties. Things like hit_set_count,
bloom filter control or cache sizing are not supported yet.
Change-Id: I5a37e79d0d23d35295a8ae97177c940af66b0485