OpenStack Magnum Charm

charm-magnum:stable/victoria

  1. Git
  2. lp:charm-magnum
  3. stable/victoria
Last commit made on 2023-09-11
Get this branch:
git clone -b stable/victoria https://git.launchpad.net/charm-magnum

Branch merges

Branch information

Name:
stable/victoria
Repository:
lp:charm-magnum

Recent commits

42260c7... by Jesper Schmitz Mouridsen

Add cluster-user-trust config option

Clusters created with the option cloud_provider_enabled or
registry_enabled set to true, or volumer_driver set to 'cinder' need
this flag set to True as well to instruct Magnum to assign trust to the
cluster user.

This option defaults to False due to security concerns (see
https://bugs.launchpad.net/bugs/cve/2016-7404 )

[0] https://docs.openstack.org/magnum/latest/user/index.html#cloud-provider-enabled

Closes-Bug: #1996237
Change-Id: I393030fa0da244ba5928482c8ef4e75e53f1a7b3
(cherry picked from commit 29260ddf8ae040e6319732a21ece4cca96196a5f)

8a00c08... by Alex Kavanagh

[victoria] 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/830
Closes-Bug: #2028683

Change-Id: I7083110054b0e15855b7ef6c4709cac332e6f199

a300350... 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: Ic49a95729332d2de591e9d9538a7d692f08442c8

f2db683... by Alex Kavanagh

Pin build.lock for all layers to the commit hash

The build.lock branch points to master which means that the layer is not
locked. Lock the layers to the commit hash instead.

Closes-Bug: #1990062
Change-Id: If9d56a78ef5c888eb451bdfa1f8fbd98697b1c14

63540b4... by Alex Kavanagh

Migrate charm charmhub for stable/victoria

- start from stable/victoria branch
- Do charmcraft, osci, zuul changes
- Modify libs to point to stable/victoria for:
  - charmhelpers
  - charms.openstack (as needed)
  - zaza & zaza.openstack.tests
- Remove unsupported test bundles
- migration bundles to charmhub.io (ch: prefix + channels)
- Build on 20.04 amd64
- Run on 20.04 amd64, s390x, ppc64el, arm64

Change-Id: I3952c3959992e1c043c1f0334331f6921660f288

c6e4753... by Alex Kavanagh

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: I51735fa54a494328d8d48950f6a56704712f947f

a8629bc... by Alex Kavanagh

21.10 - Update requirements.txt - pin cffi 1.14.6

* On stable/21.10 branch
* Pin cffi 1.14.6 in requirements.txt used in charm build
  for py35 compatability.

Change-Id: I12187b43e323091ef6034ab475bde3c58985e397

f0df853... by Alex Kavanagh

21.10 - Stable cut of charms for testing period

* use stable/21.10 libraries
* use zaza/zaza-openstack-tests at stable/21.10
* build.lock files for reactive charms
* bundles refer to ~openstack-charms candidate channel
* update tox/pip.sh to ensure setuptools<50.0.0

Change-Id: I05b2ba0832eca097cabdf166700542ac070cd629

a4208dc... by Aurelien Lourot

Sync release-tools

In order to fix ResolutionImpossible on tox invocation.

https://github.com/openstack-charmers/release-tools/issues/151
https://github.com/openstack-charmers/release-tools/pull/152

Change-Id: I015bc4d424407b9f9ca831181a6cdf398b91fc4d

c6076f9... by Zuul <email address hidden>

Merge "Add impish to metadata.yaml"