From: Chuck Lever <cel@kernel.org>
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 3/7] kconfigs: Remove remaining OpenStack references
Date: Fri, 31 Oct 2025 20:50:16 -0400 [thread overview]
Message-ID: <20251101005020.3492781-5-cel@kernel.org> (raw)
In-Reply-To: <20251101005020.3492781-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
Remove OpenStack references from various Kconfig files including:
- Remove OpenStack example from guestfs cloud-init documentation
- Remove OpenStack nova reference from libvirt aio mode documentation
- Remove OpenStack from bringup terraform cloud provider list
- Remove TERRAFORM_OPENSTACK dependency from TERRAFORM_PRIVATE_NET
Generated-by: Claude AI
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
kconfigs/Kconfig.bringup | 1 -
kconfigs/Kconfig.guestfs | 2 +-
kconfigs/Kconfig.libvirt | 4 ----
terraform/Kconfig | 2 +-
4 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/kconfigs/Kconfig.bringup b/kconfigs/Kconfig.bringup
index 0b1c8805d0b2..39bd93b8686d 100644
--- a/kconfigs/Kconfig.bringup
+++ b/kconfigs/Kconfig.bringup
@@ -45,7 +45,6 @@ config TERRAFORM
* Azure
* AWS
- * OpenStack
* GCE
Enabling this option will enable installing terraform dependencies
diff --git a/kconfigs/Kconfig.guestfs b/kconfigs/Kconfig.guestfs
index 3bc4b06032be..75996c5eba7e 100644
--- a/kconfigs/Kconfig.guestfs
+++ b/kconfigs/Kconfig.guestfs
@@ -147,7 +147,7 @@ choice
config GUESTFS_DEBIAN_TRIXIE_GENERIC_AMD64
bool "debian-13-generic-amd64-daily"
help
- Should run in any environment using cloud-init, for e.g. OpenStack,
+ Should run in any environment using cloud-init, for e.g.
DigitalOcean and also on bare metal. This is the image you should
try to use and stick to for kernel testing.
diff --git a/kconfigs/Kconfig.libvirt b/kconfigs/Kconfig.libvirt
index 4f29630912f2..cadec787ba1e 100644
--- a/kconfigs/Kconfig.libvirt
+++ b/kconfigs/Kconfig.libvirt
@@ -936,13 +936,9 @@ config LIBVIRT_AIO_MODE_NATIVE
aio=native on sparsefiles. The claim seems to be that a host
filesystems metadata write can block the AIO io_submit() call and
therefore block QEMU threads which expect AIO behaviour on the guest.
- This is documented when on Openstack nova an aio mode option was
- requested to be available for different backends:
If you want to use PCIe passthrough you cannot use aio=native.
- https://review.opendev.org/c/openstack/nova-specs/+/232514/7/specs/mitaka/approved/libvirt-aio-mode.rst
-
config LIBVIRT_AIO_MODE_THREADS
bool "aio=threads"
help
diff --git a/terraform/Kconfig b/terraform/Kconfig
index c0b2bfb0338c..62d138b621a4 100644
--- a/terraform/Kconfig
+++ b/terraform/Kconfig
@@ -10,7 +10,7 @@ endmenu
config TERRAFORM_PRIVATE_NET
bool "Add a private network for the guests"
- depends on TERRAFORM_OPENSTACK || TERRAFORM_AZURE
+ depends on TERRAFORM_AZURE
default y
help
This option adds a private network between the various guests
--
2.51.0
next prev parent reply other threads:[~2025-11-01 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 0:50 [PATCH 0/7] Remove support for OpenStack-based clouds Chuck Lever
2025-11-01 0:50 ` [PATCH] CLAUDE.md: Suggest method for checking generated Kconfig files Chuck Lever
2025-11-01 0:50 ` [PATCH 1/7] docs: Remove OpenStack documentation Chuck Lever
2025-11-01 0:50 ` [PATCH 2/7] CLAUDE.md: Remove OpenStack from infrastructure list Chuck Lever
2025-11-01 0:50 ` Chuck Lever [this message]
2025-11-01 0:50 ` [PATCH 4/7] scripts: Remove OpenStack from terraform.Makefile Chuck Lever
2025-11-01 0:50 ` [PATCH 5/7] playbooks: Remove OpenStack ansible support Chuck Lever
2025-11-01 0:50 ` [PATCH 6/7] terraform: Remove OpenStack from Kconfig.providers Chuck Lever
2025-11-01 0:50 ` [PATCH 7/7] terraform: Remove OpenStack provider directory Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251101005020.3492781-5-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox