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: I39a01c3d9ca695ef1947b2038d706f41b9f9bdc9
Enabled by default since this branch only supports jammy where the
kernel and ovn are new enough to support this flag. This will eliminate
the need for a more complex change or the use of a dedicated opt-in
config option.
For more details, please refer to
I089f95b40803a6cd5e01990acacd599ced3bbd91
Closes-Bug: #1947391
Change-Id: Icc05980b4bc9184ba4e52722c6c11abfcfc0d58c
This option enables configuration of overlay package
repository for installation of OVN packages that are
not available in default distribution repository.
Expected behavior:
* New deployments will use default overlay for
their series.
* Setting this option to "distro" allows new
deployment that does not use overlay repository
* Existing deployments that are upgraded to this
version of the charm won't automatically apply
repository overlay and will keep using their
current defaults.
Closes-Bug: #1992770
Change-Id: I20789f637c9443bd274df5f91522f9e2ce973164
When neutron-api-plugin-ovn charm is upgraded (juju refresh ...) some configuration parameters in ml2_conf.ini may have also updated.
It was observed that sometime those changes are not taken in to account by neutron service because it was not restarted after file content modification.
This change introduces rising of “restart-trigger” key on neutron-plugin relation databag when upgrade-charm event is generated.
With every new “charm-upgrade” event value for “restart-trigger” is updated: f.e. “restart-trigger cf2697c8-f5f0-44b5-8dae-32d893fb209c”.
Principal charm “neutron-api” has implemented logic which triggers neutron service restart as soon as “restart-trigger” key value is changed.
Closes-Bug: #2019798
Change-Id: Ia1f48d86330d6e357ae3b35ce28bbb036788ac4a
Upstream Neutron has declared that the neutron-dynamic-routing service
plugin is now supported when OVN L3 service plugin and mechanism driver
are in use.
https://review.opendev.org/c/openstack/neutron/+/8640514d1a7bd0bc
This change removes the NDR plugin from the filter so that the plugin
is enabled.
Change-Id: Ic101d8c9fd7a674103ea53fe0b56d3c3f315595c
Due to new install dependencies for urllib3, this charm has been
converted to a binary charm so that the build dependencies are resolved
at charm build, rather than charm install.
Note: the 23.04 binary charm build fails due to missing support in
charmcraft [1], but this should be addressed soon.
[1] https://github.com/canonical/charmcraft/issues/1104
Closes-Bug: #2019540
Change-Id: I0834ddf7d63bf7f7d59a122bc07f007abffb5f3f
* 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
* Add libpython3-dev to allow the charm to be built. This
fixes a missing dependency with Cython
* Remove wheelhouse pin of flit_core to avoid install hook
failure.
* Rename overlay file to local-charm-overlay.yaml.j2 to avoid
need for release-sepcific symlink overlay files.
Change-Id: I14ec64542f3a51adf9b32c6c2687023762f3210d
Changes:
- Add jammy-zed.yaml.j2
- Add kinetic-zed.yaml.j2
- Drop unused overlays (symlinks to ha.j2)
- Drop 'source' key from mysql-innodb-cluster and rabbitmq-server
Change-Id: I566431adce5fa0823247b10e2828f4f7e961faa6
* 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: I3cc0af8443ecf62589c88d4e924cb633c419e87f
Sqlalchemy 1.4 dropped support for RowProxy and Row now behaves like a
tuple. This causes row and column iteration to fail using the RowProxy
semantics as the iteration methods are no longer there. Fix this by
checking which method needs to be used. This is necessary for backwards
compatibility with the Xena release for the Yoga branch.
Closes-Bug: #1968647
Change-Id: I6a4adbd87bd59ad3a4b0a8cef187d82f4e128084
- 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: I064f4d30c4df8c5004cd30139dbed61d7775d19a
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: Icad049b5d152306be943c9c7177bbf751b48ddb0
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: I62e4e03f73db6e4ddd10b8d221a2ae8fda0a4290
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: I94aced6559e0e354b8042b5728e4cb756082de1b
This fixes an install hook failure caused by a conflict
between setuptools 41.6.0 and importlib_metadata by pinning
importlib_metadata to the last version that supported that
version of setuptools.
Closes-Bug: #1948967
Change-Id: Ic8376be8f1ef157dbfa13bd34ba51389cc472bb9
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: I53c243eac27a21948cc60b9f11125faec3f3ec36
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I3fdd311848691e01d8e78d68cf2091628a2447f8
* 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: Ie9ddc1992ba988f1b75ea92f686ed485effd610f
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I28a12f26e11bcd619318df176c9279c4326026e9
* 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: Ib87fe046bac26dabc915f14ce8651daa63deecce
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I633253f9660087cd988c02c6d74c4a615b58162f
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: I064d38d207b6dc6e7c8fd64facb2105f88ea23ce
* 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: I9c96f6170e1ff0ac123bccc6fe3faf7a576e5a7b