From: Chuck Lever <cel@kernel.org>
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 0/7] Remove support for OpenStack-based clouds
Date: Fri, 31 Oct 2025 20:50:12 -0400 [thread overview]
Message-ID: <20251101005020.3492781-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
We're thinking that there are no users and that OpenStack support
has grown fallow. Considering the amount of churn that is coming for
the kdevops terraform providers, it will be an easier maintenance
burden to decommission OpenStack now.
Chuck Lever (7):
docs: Remove OpenStack documentation
CLAUDE.md: Remove OpenStack from infrastructure list
kconfigs: Remove remaining OpenStack references
scripts: Remove OpenStack from terraform.Makefile
playbooks: Remove OpenStack ansible support
terraform: Remove OpenStack from Kconfig.providers
terraform: Remove OpenStack provider directory
CLAUDE.md | 2 +-
docs/kdevops-terraform.md | 35 ------
kconfigs/Kconfig.bringup | 1 -
kconfigs/Kconfig.guestfs | 2 +-
kconfigs/Kconfig.libvirt | 4 -
playbooks/roles/gen_tfvars/defaults/main.yml | 6 -
.../templates/openstack/terraform.tfvars.j2 | 18 ---
.../tasks/terraform/openstack.yml | 4 -
scripts/terraform.Makefile | 13 ---
terraform/Kconfig | 2 +-
terraform/Kconfig.providers | 7 --
terraform/openstack/Kconfig | 66 -----------
terraform/openstack/ansible_provision_cmd.tpl | 1 -
terraform/openstack/clouds-public.yaml | 19 ----
terraform/openstack/main.tf | 107 ------------------
terraform/openstack/output.tf | 28 -----
terraform/openstack/output_minicloud.tf | 51 ---------
terraform/openstack/provider.tf | 23 ----
terraform/openstack/shared.tf | 1 -
.../openstack/update_ssh_config_minicloud.tf | 25 ----
terraform/openstack/vars.tf | 46 --------
21 files changed, 3 insertions(+), 458 deletions(-)
delete mode 100644 playbooks/roles/gen_tfvars/templates/openstack/terraform.tfvars.j2
delete mode 100644 playbooks/roles/volume_group/tasks/terraform/openstack.yml
delete mode 100644 terraform/openstack/Kconfig
delete mode 120000 terraform/openstack/ansible_provision_cmd.tpl
delete mode 100644 terraform/openstack/clouds-public.yaml
delete mode 100644 terraform/openstack/main.tf
delete mode 100644 terraform/openstack/output.tf
delete mode 100644 terraform/openstack/output_minicloud.tf
delete mode 100644 terraform/openstack/provider.tf
delete mode 120000 terraform/openstack/shared.tf
delete mode 100644 terraform/openstack/update_ssh_config_minicloud.tf
delete mode 100644 terraform/openstack/vars.tf
--
2.51.0
next 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 Chuck Lever [this message]
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 ` [PATCH 3/7] kconfigs: Remove remaining OpenStack references Chuck Lever
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-1-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