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: Ie58f8722e4eeb06048084fd72c21f1fd614222af
The change includes modifications to bundles to set up components
necessary to spawn instances and provide actual connectivity to them. It
makes the testing more heavy but adds assurances that the data plane
works for the routes advertised by the NDR control plane.
The bundle changes also fix an issue that got in with the original OVN
bundles: manage-neutron-plugin-legacy-mode is set to True and the plugin
is determined to be OVS instead of OVN. The control plane for NDR still
worked but with a non-functioning ML2/ovs config causing OVN DBs to be
empty.
Func-Test-PR: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1076
Change-Id: Ie59b942a0800ce8dd979398f41ed2138472481f1
* OVN + NDR testing is possible as of Neutron 22.0.0 (2023.1 or
Antelope), see [1][2].
* Vault is added to non-OVN bundles as the tests.yaml file is shared
and uses a configure step for Vault
Important note: at the time of writing the OVN integration code in
Neutron does not have any use for `distributed` and `ha` router extra
attributes and whether distributed or centralized FIPs are used in OVN
is governed by the ovn/enable_distributed_floating_ip option which does
not operate at the per-router granularity and is global.
The docs have not been updated and still say [3] that OVN routers do not
expose `ha` or `distributed` attributes which are now there as of [1].
At the same time, the NDR implementation uses the `distributed`
attribute to determine whether to use the gateway port IP and treat FIPs
as centralized [4] and add a next-hop to the gateway port IP or not in
the advertised /32 routes. For routers with `distributed == True`,
NDR only attempts [5] to find ports with device owner
`'floatingip_agent_gateway'`. Therefore, when distributed FIPs are
enabled via ovn/enable_distributed_floating_ip, the `distributed` extra
attribute on a router is set to `False` and /32 routes are advertised
as centralized.
The distributed FIP case is currently not exercised by the current
bundles neither for ML2/ovs nor ML2/ovn. The current bundles only test
the control plane and route advertisement, not packet forwarding via
advertised next-hops.
[1] https://review.opendev.org/c/openstack/neutron/+/864051
[2] 4d1a7bd0bc
[3] cd66232c2b/doc/source/ovn/faq/index.rst (L16-L29)
[4] 513ea649be/neutron_dynamic_routing/db/bgp_db.py (L564)
[5] 513ea649be/neutron_dynamic_routing/db/bgp_db.py (L567-L580)
Change-Id: I21ba5d79ff100b839874a65e4ddd32f20dfb1311
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: I2bb3b81355a3bd9f6f055d1c66b038f4f0abfd0e
* switch to release-specific zosci functional tests
* switch to yoga zosci unit test job
* add py39
Change-Id: Ia7f9d5b00ac17636cb59280c78ffa60d815db832
These are the test bundles (and any associated changes) for
focal-wallaby and hirsute-wallaby support.
Change-Id: I6d21ce67b7d85811dc6b7f800ee5367a71fc3b98
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I3460aefa4931e7c90c690a6c077ff569c31bc0a3
* 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: Ie62670221edbd995c6a2d9256dba58105fb9c28e
This update adds the new hirsute Ubuntu release (21.04) and
removes trusty support (14.04 which is EOL at 21.04).
Change-Id: I35feba77b5fe2b0bb5b23d5bff02b3ea5d6c357f
* 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: I4ad9e3f8abb39a7e865d1db377da60335a47594d
Reverting to an earlier version of charm-tools to
resolve some building issues seen with latest 2.8.2
version.
Change-Id: I17ff809af5c11317f69a923163c2545a19ca4968
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: Ib0ae239fa70656318174d13b857aee6de7c67afc
* 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: I33b46b798a639ac38a265140fd383dee97415158
Also remove jinja2 from wheelhouse.txt as is a duplicate
and due to improvements in charm build it now causes the
build to fail.
Change-Id: I75a1f34cd3b1c31191c6022a2440216bcad18e3b
- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: I9df5207cd2ffe3efcf12e0ccd31f94e2b5436f08
Imports the dragnet module in the reactive handlers module to ensure
that the BaseOpenStackCharm.singleton is updated with a release_pkt
attribute
Change-Id: I99d091c21987d9fafba43754e69c5c3e24fa50ca