This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I191a4ac0c66f2e5d36cc941d5eb2809408a89320
* 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: I493cb80145fe91163d011bc78f30e84f317142de
Also clean up pre-existing pep8 violations in the
files/* dir which was previously not covered by lint testing.
Also clean-up mocking issues around apt-pkg replacements in the
unit tests.
Also fix py35 issue with enabled_manager_modules() function in the
charmhelpers library (see
https://github.com/juju/charm-helpers/pull/387).
Also fix the functional tests bundles so they actually test the
version of OpenStack that the bundle indicates.
Change-Id: I2c8d84fadc11311c622dd308c4694496872dc157
This commit adds some unit testing to the helper libraries
as well as amulet testing for the charm itself
Change-Id: I13ff38655773521592c81bb5a6847a516abd943a
Add charmhelpers.contrib.hardening and calls to install,
config-changed, upgrade-charm and update-status hooks. Also
add new config option to allow one or more hardening
modules to be applied at runtime.
Change-Id: If3e20565b1917828cb9fa2cf00b93bd13c1db00f
resources e.g. pools as opposed to creating them
themselves. This hopefully simplifies the logic at
the client side and reduces the risk of race
conditions by shifting execution to the ceph
charm itself. Backwards-compatibility with
clients that don't want to/yet support this approach
is maintained.
Alex Kavanagh