From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 1/4] steady-state: use extra sparse drives when on libvirt
Date: Thu, 17 Jul 2025 21:05:53 -0700 [thread overview]
Message-ID: <20250718040557.2774976-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20250718040557.2774976-1-mcgrof@kernel.org>
preconditioning and steady-state support is now merged. But the
ChatGPT codex implementation decided to use the same drives we'd
use for /data/ today when using libvirt. Since steady state doesn't
matter much for libvirt other than sanity tests to ensure it works,
let's use the extra spare 3rd drive on libvirt instead.
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
workflows/steady_state/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/workflows/steady_state/Kconfig b/workflows/steady_state/Kconfig
index f7064d07..5ead7562 100644
--- a/workflows/steady_state/Kconfig
+++ b/workflows/steady_state/Kconfig
@@ -3,9 +3,9 @@ menu "Configure SSD steady state workflow"
config SSD_STEADY_STATE_DEVICE
string "Device to pre-condition"
output yaml
- default "/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_kdevops1" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_NVME
- default "/dev/disk/by-id/virtio-kdevops1" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_VIRTIO
- default "/dev/disk/by-id/ata-QEMU_HARDDISK_kdevops1" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_IDE
+ default "/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_kdevops2" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_NVME
+ default "/dev/disk/by-id/virtio-kdevops2" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_VIRTIO
+ default "/dev/disk/by-id/ata-QEMU_HARDDISK_kdevops2" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_IDE
default "/dev/sdc" if LIBVIRT && LIBVIRT_EXTRA_STORAGE_DRIVE_SCSI
default "/dev/nvme2n1" if TERRAFORM_AWS_INSTANCE_M5AD_4XLARGE
default "/dev/nvme1n1" if TERRAFORM_GCE
--
2.47.2
next prev parent reply other threads:[~2025-07-18 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 4:05 [PATCH 0/4] steady-state: few fixes for steady state support Luis Chamberlain
2025-07-18 4:05 ` Luis Chamberlain [this message]
2025-07-18 4:05 ` [PATCH 2/4] steady-state: fix identation on Makefile Luis Chamberlain
2025-07-18 4:05 ` [PATCH 3/4] steady-state: remove extra menu Luis Chamberlain
2025-07-18 4:05 ` [PATCH 4/4] steady-state: quite a bit of fixes 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=20250718040557.2774976-2-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
--cc=slava@dubeyko.com \
/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