From: Chuck Lever <chuck.lever@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>, cel@kernel.org
Cc: kdevops@lists.linux.dev, Anna Schumaker <anna@kernel.org>
Subject: Re: [PATCH 4/6] NFSD: Implement NVMe storage for NFSD exports
Date: Wed, 11 Dec 2024 08:50:03 -0500 [thread overview]
Message-ID: <188cb2c1-5fc5-4b82-a3d2-16fa59a4e285@oracle.com> (raw)
In-Reply-To: <Z1kKQw7AWqopcloD@bombadil.infradead.org>
On 12/10/24 10:42 PM, Luis Chamberlain wrote:
> On Tue, Dec 10, 2024 at 02:29:17PM -0500, cel@kernel.org wrote:
>> diff --git a/playbooks/roles/nfsd/tasks/main.yml b/playbooks/roles/nfsd/tasks/main.yml
>> index 63388f857627..c7c41e79714b 100644
>> --- a/playbooks/roles/nfsd/tasks/main.yml
>> +++ b/playbooks/roles/nfsd/tasks/main.yml
>> @@ -38,15 +38,34 @@
>> when:
>> - nfsd_export_storage_local|bool
>>
>> -- name: Create a new LVM VG
>> - become: yes
>> - become_flags: 'su - -c'
>> - become_method: sudo
>> +- name: Enumerate NVMe devices to provision as PVs
>> + become: true
>> + become_flags: "su - -c"
>> + become_method: ansible.builtin.sudo
>> + ansible.builtin.command:
>> + cmd: "lsblk -np -o PATH,SERIAL"
>> + register: lsblk_output
>> + changed_when: false
>> + when:
>> + - nfsd_export_storage_nvme|bool
>> +
>> +- name: Build a list of NVMe devices to provision as PVs
>> + ansible.builtin.set_fact:
>> + nfsd_lvm_pvs: "{{ nfsd_lvm_pvs + [item | split() | first] }}"
>> + loop: "{{ lsblk_output.stdout_lines }}"
>> + when:
>> + - nfsd_export_storage_nvme|bool
>> + - '"AWS" in item'
>
> I think you may want to add a new output yaml for when the provider is
> AWS so you get devops_terraform_provider_is_aws so you can just check
> for that here as an extra bool. That will ensure with more determinism
> that the bringup is on AWS.
Apologies for asking, but do you have a particular commit ID or file I
could use as an example?
--
Chuck Lever
next prev parent reply other threads:[~2024-12-11 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:29 [PATCH 0/6] Recent fixes cel
2024-12-10 19:29 ` [PATCH 1/6] fstests: Fix NFS mount options for fstests cel
2024-12-10 19:29 ` [PATCH 2/6] gen_nodes: Fix generation of the list of test nodes cel
2024-12-10 19:29 ` [PATCH 3/6] fstests: Fix selection of NFSD export type for the pNFS test section cel
2024-12-10 19:29 ` [PATCH 4/6] NFSD: Implement NVMe storage for NFSD exports cel
2024-12-11 3:42 ` Luis Chamberlain
2024-12-11 13:50 ` Chuck Lever [this message]
2024-12-12 2:28 ` Luis Chamberlain
2024-12-10 19:29 ` [PATCH 5/6] playbooks: Add a Code Ready Builder role cel
2024-12-10 19:29 ` [PATCH 6/6] codereadyrepo: Enable codeready-builder in AWS cel
2024-12-11 3:44 ` [PATCH 0/6] Recent 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=188cb2c1-5fc5-4b82-a3d2-16fa59a4e285@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
/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