public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v1 1/9] bringup: prevent the use of vagrant
Date: Tue, 14 Jan 2025 15:03:40 -0500	[thread overview]
Message-ID: <20250114200348.1706018-2-cel@kernel.org> (raw)
In-Reply-To: <20250114200348.1706018-1-cel@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

Vagrant virtualization has been deprecated for some time, but its
been left in kdevops to allow time for folks to move over to
guestfs, which has been the default for a while.

It's time to start removing Vagrant, so remove the menu choice to
select the use of Vagrant virtualization. This change will be quick
to revert if there are loud complaints.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 kconfigs/Kconfig.bringup | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/kconfigs/Kconfig.bringup b/kconfigs/Kconfig.bringup
index 8effdcb8e9cb..a9aefc56e3fa 100644
--- a/kconfigs/Kconfig.bringup
+++ b/kconfigs/Kconfig.bringup
@@ -9,22 +9,6 @@ choice
 	prompt "Node bring up method"
 	default GUESTFS
 
-config VAGRANT
-	bool "Vagrant for local virtualization (KVM / VirtualBox)"
-	select KDEVOPS_SSH_CONFIG_UPDATE_STRICT
-	select EXTRA_STORAGE_SUPPORTS_ZNS
-	select EXTRA_STORAGE_SUPPORTS_LARGEIO
-	select BRINGUP_SUPPORTS_CXL
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will enable use of Vagrant. Enable this if you want to
-	  use local virtualization technologies such as KVM with libvirt or
-	  VirtualBox. Enabling this feature will enable you to select which
-	  target guests to use, and configures things for you. It will also
-	  ensure dependencies are installed for Vagrant when running:
-
-	    make deps
-
 config GUESTFS
 	bool "Use guestfs-tools for local virtualization via KVM and libvirt"
 	select KDEVOPS_ENABLE_GUESTFS
-- 
2.47.1


  reply	other threads:[~2025-01-14 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 20:03 [PATCH v1 0/9] Random short subjects cel
2025-01-14 20:03 ` cel [this message]
2025-01-14 20:03 ` [PATCH v1 2/9] Remove defconfigs/nfsd cel
2025-01-14 20:03 ` [PATCH v1 3/9] terraform/aws: Clean up a few nits cel
2025-01-14 20:03 ` [PATCH v1 4/9] Clean up task messages cel
2025-01-14 20:03 ` [PATCH v1 5/9] devconfig: Replace import_tasks with include_tasks cel
2025-01-28 13:03   ` Daniel Gomez
2025-01-28 14:20     ` Chuck Lever
2025-01-28 14:40       ` Daniel Gomez
2025-01-28 14:43         ` Chuck Lever
2025-01-14 20:03 ` [PATCH v1 6/9] terraform/aws: Enable selection of a Fedora (40) AMI cel
2025-01-14 20:03 ` [PATCH v1 7/9] terraform/aws: Add a couple more instance types cel
2025-01-14 20:03 ` [PATCH v1 8/9] terraform/aws: Add support for m7a " cel
2025-01-14 20:03 ` [PATCH v1 9/9] terraform: Hoist aws_profile into the terraform Kconfig cel
2025-01-17 21:05 ` [PATCH v1 0/9] Random short subjects Luis Chamberlain

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=20250114200348.1706018-2-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