From 76acde9919033797d1b858111bbf2fb0da10d53d Mon Sep 17 00:00:00 2001 From: Ivan Anfimov Date: Mon, 19 May 2025 21:22:43 +0000 Subject: [PATCH] Remove code for suse from post-devstack installation Change-Id: I02595e69b84cdd9c25049d6a28da841e2c52514e --- doc/source/contributor/internals/objects_usage.rst | 2 -- doc/source/contributor/internals/ovn/metadata_api.rst | 4 ++-- tools/configure_for_func_testing.sh | 7 ------- 3 files changed, 2 insertions(+), 11 deletions(-) diff --git a/doc/source/contributor/internals/objects_usage.rst b/doc/source/contributor/internals/objects_usage.rst index 97baede807a..ff9a3f743ea 100644 --- a/doc/source/contributor/internals/objects_usage.rst +++ b/doc/source/contributor/internals/objects_usage.rst @@ -644,7 +644,6 @@ four releases newer than what is running on the computes. Known fast forward upgrade windows are: * Red Hat OpenStack Platform (RHOSP): X -> X+3 [#]_ -* SuSE OpenStack Cloud (SOC): X -> X+2 [#]_ * Ubuntu Cloud Archive: X -> X+4 [#]_ Therefore removal of OVO version downgrade code should be removed in the fifth @@ -690,6 +689,5 @@ References .. [#] https://docs.openstack.org/neutron/latest/contributor/internals/db_layer.html#the-standard-attribute-table .. [#] https://opendev.org/openstack/neutron/src/tag/ocata-eol/neutron/objects/rbac_db.py#L291 .. [#] https://access.redhat.com/support/policy/updates/openstack/platform/ -.. [#] https://www.suse.com/releasenotes/x86_64/SUSE-OPENSTACK-CLOUD/8/#Upgrade .. [#] https://www.ubuntu.com/about/release-cycle .. [#] https://opendev.org/openstack/neutron-lib/src/neutron_lib/objects/utils.py diff --git a/doc/source/contributor/internals/ovn/metadata_api.rst b/doc/source/contributor/internals/ovn/metadata_api.rst index 1c34fdd3c2d..31b82496659 100644 --- a/doc/source/contributor/internals/ovn/metadata_api.rst +++ b/doc/source/contributor/internals/ovn/metadata_api.rst @@ -24,7 +24,7 @@ Neutron and Metadata Today The following blog post describes how VMs access the metadata API through Neutron today. -https://www.suse.com/communities/blog/vms-get-access-metadata-neutron/ +https://www.suse.com/c/vms-get-access-metadata-neutron/ In summary, we run a metadata proxy in either the router namespace or DHCP namespace. The DHCP namespace can be used when there's no router connected to @@ -341,7 +341,7 @@ L3 HA, we will want to evolve to it. Other References ---------------- -* Haproxy config -- +* HAProxy config -- https://review.openstack.org/#/c/431691/34/neutron/agent/metadata/driver.py * https://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-reloads.html diff --git a/tools/configure_for_func_testing.sh b/tools/configure_for_func_testing.sh index 1a43d018177..1c368b100a4 100755 --- a/tools/configure_for_func_testing.sh +++ b/tools/configure_for_func_testing.sh @@ -257,13 +257,6 @@ function _install_post_devstack { elif is_fedora; then install_package dhclient install_package nmap-ncat - elif is_suse; then - install_package dhcp-client - # NOTE(armax): no harm in allowing 'other' to read and - # execute the script. This is required in fullstack - # testing and avoids quite a bit of rootwrap pain - sudo chmod o+rx /sbin/dhclient-script - install_package ncat else exit_distro_not_supported "installing dhclient and ncat packages" fi