Author: Billy Olsen
Author Date: 2024-06-22 00:58:57 UTC

Add charmcraft 3 support

Update the charmcraft.yaml file to use base and platforms, only
allowing noble support.

- Update config to default to caracal.
- Update osci.yaml to use the charmcraft 3.x/beta
- Add noble/oracular to charmhelpers
- Drop non-noble tests

Change-Id: Iacb73d68810b10c7fa79971bf0165f7ea5c7412a

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit 3432ae7f02deb274aa222443faf83ce662bbaefc)
(cherry picked from commit 4bb231680306ca11be002a66201e2180d6e56609)
(cherry picked from commit c03ec8f984db7e1f709d15f346d4b4d6e4de2593)

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit 3432ae7f02deb274aa222443faf83ce662bbaefc)
(cherry picked from commit 4bb231680306ca11be002a66201e2180d6e56609)

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit 3432ae7f02deb274aa222443faf83ce662bbaefc)
(cherry picked from commit 4bb231680306ca11be002a66201e2180d6e56609)

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit 3432ae7f02deb274aa222443faf83ce662bbaefc)
(cherry picked from commit 4bb231680306ca11be002a66201e2180d6e56609)

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit 3432ae7f02deb274aa222443faf83ce662bbaefc)

Author: Danny Cocks
Author Date: 2024-04-16 05:43:59 UTC

Enable more recent DNS extensions (dns-integration-domain-keywords)

Since yoga, there have been two "additions" to the DNS extensions, which
simply build on top of the older ones. By changing the DNS extension to
be the latest (dns-integration-domain-keywords), all 4 extensions will
be activated:

- dns-integration (already included)
- dns-domain-ports (the previous default extension)
- subnet-dns-publish-fixed-ip
- dns-integration-domain-keywords

These extensions are required to enable replacement of keywords in DNS
entries and allow publishing fixed IPs without restrictions [1].

I have tested this on a local cluster and confirmed that the extensions
are enabled, and allow me to make use of the two new features.

[1] https://docs.openstack.org/designate/latest/user/neutron-integration.html

Closes-Bug: #2028163
Change-Id: I245cfe2f8fdb4d8ca325ade0c22771efa31b4bf2
(cherry picked from commit d48b2725f846633c015387eb112892670ab381d0)

Author: Diko Parvanov
Author Date: 2021-11-22 10:24:53 UTC

Adding uplink_status_propagation option

Add charm option uplink-status-propagation, which for releases >= stein
will add the ml2 plugin uplink_status_propagation, that enabled ports to
have the propagate_uplink_status attribute to allow instance VF to see the PF
link state change for SR-IOV ports.

Change-Id: I4f1ace630c74363057b0bbdbc759c482125ad015
Partial-Bug: 1949491
(cherry picked from commit 6f303256517588d9e1ac530150d419c7f8573fd8)

Author: Diko Parvanov
Author Date: 2021-11-22 10:24:53 UTC

Adding uplink_status_propagation option

Add charm option uplink-status-propagation, which for releases >= stein
will add the ml2 plugin uplink_status_propagation, that enabled ports to
have the propagate_uplink_status attribute to allow instance VF to see the PF
link state change for SR-IOV ports.

Change-Id: I4f1ace630c74363057b0bbdbc759c482125ad015
Partial-Bug: 1949491
(cherry picked from commit 3e387d591869b714be1c323f240fcaff289b3c10)

Author: Diko Parvanov
Author Date: 2021-11-22 10:24:53 UTC

Adding uplink_status_propagation option

Add charm option uplink-status-propagation, which for releases >= stein
will add the ml2 plugin uplink_status_propagation, that enabled ports to
have the propagate_uplink_status attribute to allow instance VF to see the PF
link state change for SR-IOV ports.

Change-Id: I4f1ace630c74363057b0bbdbc759c482125ad015
Partial-Bug: 1949491
(cherry picked from commit 3e387d591869b714be1c323f240fcaff289b3c10)

Author: Alex Kavanagh
Author Date: 2023-08-18 14:04:43 UTC

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

Change-Id: Ie679f22092dc317c7550a68e9ba493c291d65806

Author: Aurelien Lourot
Author Date: 2021-11-28 18:24:44 UTC

Fix removing fwaas when upgrading from Ussuri to Victoria

Without this fix, upgrading from Ussuri to Victoria won't
fully remove fwaas everywhere, leading to broken floating
IPs.

Fixes https://github.com/openstack-charmers/charmed-openstack-tester/issues/57

Change-Id: I959e8f8cafc6d4040895762c21f8ad8b6f190a3b
(cherry picked from commit e18b89a3f0f61e88adbc3e82c90e6f43a1215927)

Author: Aurelien Lourot
Author Date: 2021-11-28 18:24:44 UTC

Fix removing fwaas when upgrading from Ussuri to Victoria

Without this fix, upgrading from Ussuri to Victoria won't
fully remove fwaas everywhere, leading to broken floating
IPs.

Fixes https://github.com/openstack-charmers/charmed-openstack-tester/issues/57

Change-Id: I959e8f8cafc6d4040895762c21f8ad8b6f190a3b
(cherry picked from commit e18b89a3f0f61e88adbc3e82c90e6f43a1215927)

Author: Aurelien Lourot
Author Date: 2021-11-28 18:24:44 UTC

Fix removing fwaas when upgrading from Ussuri to Victoria

Without this fix, upgrading from Ussuri to Victoria won't
fully remove fwaas everywhere, leading to broken floating
IPs.

Fixes https://github.com/openstack-charmers/charmed-openstack-tester/issues/57

Change-Id: I959e8f8cafc6d4040895762c21f8ad8b6f190a3b
(cherry picked from commit e18b89a3f0f61e88adbc3e82c90e6f43a1215927)

Author: Aurelien Lourot
Author Date: 2021-11-28 18:24:44 UTC

Fix removing fwaas when upgrading from Ussuri to Victoria

Without this fix, upgrading from Ussuri to Victoria won't
fully remove fwaas everywhere, leading to broken floating
IPs.

Fixes https://github.com/openstack-charmers/charmed-openstack-tester/issues/57

Change-Id: I959e8f8cafc6d4040895762c21f8ad8b6f190a3b
(cherry picked from commit e18b89a3f0f61e88adbc3e82c90e6f43a1215927)

Author: Hemanth Nakkina
Author Date: 2021-09-14 11:09:46 UTC

Add enable-fwaas to relation data

Add enable-fwaas to neutron-plugin-api relation data so
that neutron-openvswitch updates neutron-l3-agent
configuration accordingly.

Synced charmhelpers to get related changes
https://github.com/juju/charm-helpers/pull/640

Partial-Bug: #1934129

(cherry picked from commit 69af89a6158679e87d9b6c2a437268b725fbcd80)
Change-Id: I5019c5ed3b8ab556d4900f1fe46dee69f5f09ee7

Author: Aurelien Lourot
Author Date: 2021-02-10 19:12:58 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: I300be50bd8952ac630b0b0a8056ab2469da43a8b

Author: Aurelien Lourot
Author Date: 2020-11-02 10:48:34 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: Ie552d2d3dfce5b83c0471eae5780013edc629ca1

Author: Edward Hope-Morley
Author Date: 2020-08-26 09:42:40 UTC

Fix db init notifications

Ensures that leader does not respond to db init
notifications to avoid infitinite looping after
leader switches to a different unit.

Also ensures that leader only restarts its neutron-server
once on db init.

Closes-Bug: #1893008

Change-Id: I59b9d5e0caab62b72380879bf16cb0fd8703bb32
(cherry picked from commit 104626a19f7edbdee04725ec502f74c54bbfedd2)

Author: David Ames
Author Date: 2020-05-21 16:57:35 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: I5d2b28e5e050ee8f2ab986f577e212711f7b9060

Author: Liam Young
Author Date: 2020-02-17 15:46:33 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch zaza bundles to stable charms.

Switch to using stable charm-helpers branch.

Change-Id: I8c341da317d2825a5a0d85873fd43559130123d1

Author: Stamatis Katsaounis
Author Date: 2019-11-22 21:08:20 UTC

Remove lbaas in OpenStack Train deployments

This patch removes completely any lbaas related service or
configuration for OS Train deployements.

Change-Id: Ib48adee32d649e5254265924175c3bf2d3437c0b
Closes-Bug: #1853868
Signed-off-by: Stamatis Katsaounis <skatsaounis@admin.grnet.gr>
(cherry picked from commit b36ac4b4ed228e5763034f5e8b75c761a96027a4)

Author: Sahid Orentino
Author Date: 2019-09-09 07:32:10 UTC

revert "Ensure that only cloud admins are neutron admins"

We can't add constraints to admin role without consider
regressions. It happens that two tempest scenarios are now failling:

 tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
 tempest.scenario.test_server_multinode.TestServerMultinode.test_schedule_to_all_nodes

If admin wants to give role (even Admin role) to an user for a tenant,
the right way is to use keystone trust API.

Change-Id: I161ea7d1aec5e5784455b5bce4605b2f9143daa2
Related-Bug: #1830536
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@canonical.com>
(cherry picked from commit 2ad425b1cdd8093b40f4cd57ba59b0c3b4eb8e6a)

Author: David Ames
Author Date: 2019-05-06 23:15:39 UTC

Update stable charms to use stable CH in test reqs

In our test-requirements.txt we often pull in charm-helpers. As stable and
master branches of charm-helpers diverge this can lead to testing failures
on the stable branch charms.

Update tests-requirements.txt to point to the stable branch of charm-helpers.

Change-Id: I7a6fa95563d7da7a18cc5b020166c35eb902bef3

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:53 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:53 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:53 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:53 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:53 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:52 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:52 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:52 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:52 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.

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:44:52 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.