charm-neutron-api:stable/yoga

Last commit made on 2023-08-17
Get this branch:
git clone -b stable/yoga https://git.launchpad.net/charm-neutron-api

Branch merges

Branch information

Name:
stable/yoga
Repository:
lp:charm-neutron-api

Recent commits

abc4fe3... by Alex Kavanagh

[yoga] Ensure get_requests_for_local_unit doesn't fail on incomplete relation

This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].

[1] https://github.com/juju/charm-helpers/pull/827
Closes-Bug: #2028683

Change-Id: I9b528cf5cac173d886828afcc188692819ca8f83

b635293... by Jadon Naas

Add docs key and point at Discourse

Add the 'docs' key and point it at a Discourse topic
previously populated with the charm's README contents.

When the new charm revision is released to the Charmhub,
this Discourse-based content will be displayed there. In
the absense of the this new key, the Charmhub's default
behaviour is to display the value of the charm's
'description' key.

Change-Id: Idb7ec6357e2ef7449cc77bff48d12102da72d822
(cherry picked from commit 3141e839a150dd440c0655e2d69ee41f2635453f)

ef2d636... by Corey Bryant

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: Ia4e3a15cfc2627d7e0d3adf4112e944e5ef7bd2e

77b4b89... by Alex Kavanagh

Update the bundles to use the stable track, edge risk for yoga

The bundles for the yoga channel currently point to "latest/edge"
channel for all the charms. This update points the charms to the
appropriate channel for the charm being used, either from ceph,
openstack, ovn or the misc tracks.

Change-Id: I265ac0886e854f90659f2fbbe256d2e0ae59928a

cf0d96b... by Alex Kavanagh

Updates for stable branch creation

- Set default branch for git review/gerrit.
- Switch tests to stable.
- Switch to using stable charm-helpers branch.
- Switch to using stable charm.openstack branch.
- Switch to using stable zaza, zaza-openstack-tests
  branch
- (reactive charms) Add build.lock file

Change-Id: I24172726ffb4b9484c914e4b69eda6b2d572127f

88c3c9d... by Alex Kavanagh

Updates to enable jammy and finalise charmcraft builds

- 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
- charmhelpers sync

Change-Id: I9e03f8032c4e66586feec2bbf5f07e93b89355cc

c435106... by Zuul <email address hidden>

Merge "Remove the charm artifact from the repository"

c411b90... by Nobuto Murata

Option to enable network-segment-range support

To let operators add an additional and optional service plugin into the
deployment configuration as "network_segment_range".
https://docs.openstack.org/neutron/latest/admin/config-network-segment-ranges.html

Closes-Bug: #1965229
Change-Id: Id0ac7c397874ad2c51935e8c0eab64f1ef4f6fd3

d810a84... by Alex Kavanagh

Remove the charm artifact from the repository

Change-Id: I9cdbd0433f9723b0af96668f24ce2e4c1870f3aa

1c88770... by Alex Kavanagh

Update to classic charms to build using charmcraft in CI

This update is to ensure that the Zuul Canonical CI builds the charm
before functional tests and ensure that that artifact is used for the
functional tests. This is to try to ensure that the charm that gets
landed to the charmhub is the same charm that was tested with.

Change-Id: I0febbbf7da990026b9578a3512c99539eb03bbc0