Author: Corey Bryant
Author Date: 2023-11-09 16:00:01 UTC

Update octavia.conf auth config for bobcat

As noticed in bobcat testing, the [service_auth] section requires
more configuration than it did in the past. Additionally, as noted
in I686cfdef78de927fa4bc1921c15e8d5853fd2ef9, Octavia will no longer
take the authentication settings for Neutron from the [service_auth]
as a fallback. It will instead require them to be in the [neutron]
section. However, [service_auth] settings will still be used for
other services like Nova and Glance.

This change adds auth config options to the [service_auth] and
[neutron] sections, moves the auth_section config option to the
[keystone_authtoken] section, and sets the auth_section config
option to point to the [service_auth] section.

Closes-Bug: #2043095
Related-Bug: #2043129
Change-Id: I290f543827d63bb685209d615c9f448c2ff9d31e
(cherry picked from commit f76d066df5330d8b8dd47ddc54abbb41e6f78bc2)

Author: Corey Bryant
Author Date: 2023-11-09 16:00:01 UTC

Update octavia.conf auth config for bobcat

As noticed in bobcat testing, the [service_auth] section requires
more configuration than it did in the past. Additionally, as noted
in I686cfdef78de927fa4bc1921c15e8d5853fd2ef9, Octavia will no longer
take the authentication settings for Neutron from the [service_auth]
as a fallback. It will instead require them to be in the [neutron]
section. However, [service_auth] settings will still be used for
other services like Nova and Glance.

This change adds auth config options to the [service_auth] and
[neutron] sections, moves the auth_section config option to the
[keystone_authtoken] section, and sets the auth_section config
option to point to the [service_auth] section.

Closes-Bug: #2043095
Related-Bug: #2043129
Change-Id: I290f543827d63bb685209d615c9f448c2ff9d31e

Author: Samuel Walladge
Author Date: 2022-09-21 05:06:17 UTC

Wait for management interface IP to be assigned

There can be a delay between the interface being created,
and an IP address getting assigned,
which previously caused a race condition where
the config could be rendered before the IP address was ready
resulting in the health manager bind_ip to be empty.

This ensures that the IP address will be ready before continuing,
which will ensure that the config rendering will not happen until ready,
and the configure-resources action will only return once it's all done.

Closes-Bug: #1961088
Change-Id: I2cae5f0e307c8cd14f1831f3416d890ad604b705
(cherry picked from commit d8d8963667cb620370e2c424dbe668460ab99ff1)

Author: Samuel Walladge
Author Date: 2022-09-21 05:06:17 UTC

Wait for management interface IP to be assigned

There can be a delay between the interface being created,
and an IP address getting assigned,
which previously caused a race condition where
the config could be rendered before the IP address was ready
resulting in the health manager bind_ip to be empty.

This ensures that the IP address will be ready before continuing,
which will ensure that the config rendering will not happen until ready,
and the configure-resources action will only return once it's all done.

Closes-Bug: #1961088
Change-Id: I2cae5f0e307c8cd14f1831f3416d890ad604b705
(cherry picked from commit d8d8963667cb620370e2c424dbe668460ab99ff1)

Author: Samuel Walladge
Author Date: 2022-09-21 05:06:17 UTC

Wait for management interface IP to be assigned

There can be a delay between the interface being created,
and an IP address getting assigned,
which previously caused a race condition where
the config could be rendered before the IP address was ready
resulting in the health manager bind_ip to be empty.

This ensures that the IP address will be ready before continuing,
which will ensure that the config rendering will not happen until ready,
and the configure-resources action will only return once it's all done.

Closes-Bug: #1961088
Change-Id: I2cae5f0e307c8cd14f1831f3416d890ad604b705
(cherry picked from commit d8d8963667cb620370e2c424dbe668460ab99ff1)

Author: Alex Kavanagh
Author Date: 2023-08-17 15:28:50 UTC

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

Change-Id: Id883860c21bff001e693760a0535fd427e9c6d18

Author: Alex Kavanagh
Author Date: 2023-08-17 12:55:52 UTC

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

Change-Id: I1f7368e2851402d67f71f69590d1be6c8ddd25e3

Author: Edward Hope-Morley
Author Date: 2023-08-22 14:16:54 UTC

Rebuild with support for service_type

Bumps versions of interface-keystone and layer-openstack
Adds bindep.txt to get CI working

Related-Bug: #1965967
Change-Id: I85123351a04cf4c4d22683967307ac1b38196e21

Author: Corey Bryant
Author Date: 2023-01-13 20:06:41 UTC

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: I4c24236c44003e1af4a3510bdd99f13ae8a9caa0

Author: Corey Bryant
Author Date: 2023-01-13 20:06:03 UTC

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: Ibce01340a6821f47e5b99f1e59ddd632d6170147

Author: Hua Zhang
Author Date: 2021-05-01 00:32:21 UTC

Delete hm port on unit removal

JUJU_DEPARTING_UNIT will be set in leader unit as well when removing one
unit, so update_controller_ip_port_list can use it to delete hm port and
update neutron ip list. Besides, cluster.{connected,available} will be
set by interface-openstack-ha when relation-{broken,departed} is changed,
so update_controller_ip_port_list will also have a change to run.
In other words, as long as update_controller_ip_port_list is triggered
for various reasons, the cleanup will be completed.

NOTE: also resolve cherry-pick conflict with the commit f235f68f,
remove pinning pyparsing package as it is already updated in
sec/build.lock and remove Func-Test-Pr

Closes-Bug: 1915512
Change-Id: I88c61b8d2d0b573df7df071ed7978e83b6803c5c
(cherry picked from commit cc292d72e2cb47366e093490c5319503f86d93ec)
Signed-off-by: Zhang Hua <joshua.zhang@canonical.com>

Author: Alex Kavanagh
Author Date: 2022-01-18 17:21:15 UTC

Update build.lock for moved nrpe-external-master interface

The original repository for the npre-external-master repository was
removed and was re-uploaded [1]. This changed the commit hash for the
build.lock. This patch updates the commit hash to point to the head of
the new repository main branch as it hasn't changed since 2017.

[1] - https://github.com/juju/layer-index/pull/120

Change-Id: I43443d6fb37769f76991d2ab0ede6bd5abfc47ee

Author: Alex Kavanagh
Author Date: 2022-01-18 17:21:15 UTC

Update build.lock for moved nrpe-external-master interface

The original repository for the npre-external-master repository was
removed and was re-uploaded [1]. This changed the commit hash for the
build.lock. This patch updates the commit hash to point to the head of
the new repository main branch as it hasn't changed since 2017.

[1] - https://github.com/juju/layer-index/pull/120

Change-Id: I43443d6fb37769f76991d2ab0ede6bd5abfc47ee

Author: Alex Kavanagh
Author Date: 2022-01-18 17:21:15 UTC

Update build.lock for moved nrpe-external-master interface

The original repository for the npre-external-master repository was
removed and was re-uploaded [1]. This changed the commit hash for the
build.lock. This patch updates the commit hash to point to the head of
the new repository main branch as it hasn't changed since 2017.

[1] - https://github.com/juju/layer-index/pull/120

Change-Id: I43443d6fb37769f76991d2ab0ede6bd5abfc47ee

Author: Aurelien Lourot
Author Date: 2021-05-03 10:30:52 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Update test bundles to point to openstack-charmers.

Change-Id: If3c89a76b58aa24496c19464856eb45df2cb28ae

Author: Aurelien Lourot
Author Date: 2021-02-10 19:16:24 UTC

Updates for stable branch creation 21.01

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 branch.
Switch to using stable zaza-openstack-tests branch.

Change-Id: I3057ab1e5919184ac2c4632c4b713f07239de455

Author: Aurelien Lourot
Author Date: 2020-11-02 10:51:01 UTC

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.

Change-Id: I947f4aa6adc458c8a5cf9c9f3b81e9cd8d3765d4

Author: Nobuto Murata
Author Date: 2020-08-03 06:29:07 UTC

Set up health_manager processes based on worker-multiplier

Properly limit the number of processes with worker-multiplier instead of
spawning as many workers as available CPU threads.

Change-Id: I7f42e131d7de4a58a926b634950969e6f406bb10
Closes-Bug: #1889731
(cherry picked from commit 4ed5caf77e675bbfc98cc5f1e45bcfa250bfab16)

Author: David Ames
Author Date: 2020-05-21 16:58:47 UTC

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.

Change-Id: Iaf98cfa742815c84e963f62ba3de813b696057a9

Author: David Ames
Author Date: 2020-04-28 21:18:19 UTC

Rebuild reactive APIs for layer-basic regression

Fix regression in layer-basic which failed to unpack new dependencies
properly during the upgrade-charm hook.

Github Issue: #166
Closes Bug: #1875496

Change-Id: I26eaf7ae50fe528b7ab0bf5182aa1ed82b97cb7e

Author: David Ames
Author Date: 2019-10-24 19:27:39 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch to using stable charm-helpers branch.

Change-Id: I6f9d6ffe6fffdfeee280ecbd4b4ec86581f4efa6

Author: Frode Nordahl
Author Date: 2019-08-14 06:11:35 UTC

Pin stable charm to ``charms.openstack`` stable branch

Change-Id: I2af6e9e30d7e3fd2315739134b459c6286dd324f

Author: Chris MacNaughton
Author Date: 2019-05-24 12:52:24 UTC

Backport Zaza reconfiguration

By splitting up Zaza from the openstack-charms specific tests,
we can more easily guarantee test stability, while not harming
out ability to improve on the testing library during a cycle.

This change backports the zaza namespace change landing, and
adds a stable branch of the zaza-openstack-charms project to
the test-dependencies.

Change-Id: Ib641db1bbddedd86d85ba096e45032e1a7dc641c

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:31:03 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.