From: Chuck Lever <cel@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kruces.com>,
Swarna Prabhu <s.prabhu@samsung.com>,
swarnassp6@gmail.com, kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@gmail.com>
Subject: Re: [PATCH] guestfs: add scsi extra storage option
Date: Sun, 13 Jul 2025 12:30:10 -0400 [thread overview]
Message-ID: <5bf948e4-38b2-4c66-8ec8-1550e02d9be2@kernel.org> (raw)
In-Reply-To: <c3288eea-d57c-4419-b8bc-5ae53b8e3c1e@kernel.org>
On 7/12/25 3:47 AM, Daniel Gomez wrote:
> On 10/07/2025 19.35, Luis Chamberlain wrote:
>> From: Luis Chamberlain <mcgrof@gmail.com>
>> diff --git a/playbooks/roles/gen_nodes/templates/Vagrantfile.j2 b/playbooks/roles/gen_nodes/templates/Vagrantfile.j2
>> index 2298c3455251..a52f5566280e 100644
>> --- a/playbooks/roles/gen_nodes/templates/Vagrantfile.j2
>> +++ b/playbooks/roles/gen_nodes/templates/Vagrantfile.j2
>
> We need to nuke this Vagrant stuff...
>
Agreed. I would like to see it gone before I move forward with
integrating ssh config management between terraform and guestfs.
I've been looking at ways of chipping away at removing Vagrant
but the implementation is integrated into a number of subsystems
that kdevops still uses. It doesn't seem to be a matter of just
ripping it out.
--
Chuck Lever
next prev parent reply other threads:[~2025-07-13 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 17:35 [PATCH] guestfs: add scsi extra storage option Luis Chamberlain
2025-07-10 22:53 ` Chuck Lever
2025-07-11 0:45 ` Luis Chamberlain
2025-07-11 12:53 ` Chuck Lever
2025-07-18 4:48 ` Luis Chamberlain
2025-07-18 13:22 ` Chuck Lever
2025-07-12 7:47 ` Daniel Gomez
2025-07-13 16:30 ` Chuck Lever [this message]
2025-07-13 16:35 ` 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=5bf948e4-38b2-4c66-8ec8-1550e02d9be2@kernel.org \
--to=cel@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@gmail.com \
--cc=mcgrof@kernel.org \
--cc=s.prabhu@samsung.com \
--cc=swarnassp6@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.