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
* 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
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
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
This patch also add a fix in dragent to handle train version.
Change-Id: I8babe05c1754ee6a327ba9db1fe4b76e65d620df
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: Ib54af6ee5ea51839b67e8f5f131e279abe24bf85
Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.
As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.
For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135
Change-Id: I87c8649d83dd19eeaea17f2a209993cece723983
Ensure "rabbit_use_ssl" is specified in the [oslo_messaging_rabbit]
config section instead of "ssl" for Ocata, since "ssl" was not yet
introduced.
This is fixed by using section-oslo-messaging-rabbit for pike and
above rather than ocata and above, and using section-rabbitmq-oslo
for ocata.
Change-Id: I9209a3cdc9b52a918621ad2c328e67aa616f18d6
Closes-Bug: #1838696
Add ``py3`` target to tox.ini for developer friendliness
Update unit tests to use ``charms.openstack`` unit test helers.
Change-Id: I4752d8e776491f934cd5c1232166933a9ba17746
Partial-Bug: #1837379
This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again
Change-Id: If00d8883005aaf3bcab1277250644a2d97412d32
This change adds in zaza.openstack, as well as changing the
branch target of zaza to a branch with zaza.openstack
removed, allowing us to validate the new library
Change-Id: I2b5e3d946c7f9387b39c0c27143f68280c9c99c6
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Clean up test-requirements.txt
Change-Id: Ibf4d82ed84856806d008083ad983e6ac431b8b2a
Drop charm specific code to build the oslo.messaging
transport_url; this is now provided as part of
charms.openstack.
Change-Id: I1a9bcf7bc57b99326cae618df06930ae3990fab0
Closes-Bug: 1817672
The charm was failing to setup enough SSL configuration to communicate
with rabbitmq when rabbitmq uses SSL. This led to Bug:#1807233.
The change and its dependencies guarantees the charm will setup all the
configuration and certificates required for communication with rabbitmq
and SSL.
Depends-On: I6bb56a59cd65310d644aa25ae203996b22ec4b4e
Change-Id: Id78aba7766e045003ad5661ca31d6a6de57d704a
Closes-Bug: #1807233
Alex Kavanagh