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: I22dfeba18dc13ee159892f1a55fb1c76112bf53d
The allow-transfer is disabled by default in this change.
This option enable allow-transfer in 'options' config.
Closes-Bug: #2003829
Change-Id: I7b45848d902550b75695f53b75d62b8ce73ad326
* 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: I08d5503b3d49f35c812c5e503e8775e8b27044ce
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: If7ccdcaa900a3276c6e8eb124cdb0f605b20d6c3
* 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
These were pins to cope with supporting python 3.4. However,
layer-basic (as of [1]) now does the right thing in terms of getting the
correct versions of Jinja2 and MarkupSafe for the version of Ubuntu that
the charm is being built on:
1 - https://github.com/juju-solutions/layer-basic/pull/199
Change-Id: I29533d4794d6fb0e045893c934cb4920cacb408e
- 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
- Pin setuptools < 50.0 in src/wheelhouse.txt
Change-Id: I29b80b1e4797eb794c0e2611e732c376d99c270f
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: I1e798c9267085d50797b8988f50e99ac9184be33
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: Ie62d7878f7b952f35ca854cc36ee55b62af5f8c1
* 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: Ie263f9a14edfe9d3ffdaaff996bbe6e34def21c5
Pre-focal the service was called 'bind9'. On focal+ it is called
'named'. A previous commit [1] (also be me) didn't actually catch all of
the uses of bind9 as a service, so this concludes the set.
[1] Ida65c620fa81715d37e468217aea28f160cf31ee
Change-Id: Ifb5adfbb5a69a9b12ef9fb7c214b192642d11344
Closes-Bug: #1929770
Pre-focal the service was called 'bind9'. On focal+ it is called
'named'. This patch introduces a number of changes to make this
possible:
* Modify existing charm class "DesignateBindCharm" to include a check
to see if the distro version is "focal" or higher; if so switch
the service name to 'named'.
Change-Id: Ida65c620fa81715d37e468217aea28f160cf31ee
Closes-Bug: #1929770
This charms.openstack PatchHelper class is a better version of the
Helper class in test_lib_charm_openstack_designate_bind.py as it allows
patching by fully qualified class string. This simplifies the patching
in the tests.
Change-Id: I9a997550d58bd06c8a8af9752c0d418b4acbbbdd
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: I51d16d692b1456f157b54d35eec892c14946ea4d
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: Ic5d0d994cc3cbf5247bfd355c41793ea0b90f6cd
* 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: Iec68b0bda37b2139a9c8a2acdd59b3725e11b4cd
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I61f14b54f8c9208b072d7e998103fa63fcf806ca
* 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: If01db0736923dea0885c0fe6aa950a617d077750
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I9b10a9c9d8af2ff0a8074dbef0c43f91ae9cf200
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
Change-Id: Ie5b8bcc0a8aa553ade1d7d65ca45c5926c72baab
* 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
Change-Id: Ib9a01f611397ba6ba926cc8518e41f930b249fd7