Re: [PATCH v1 00/13] Block device provisioning for storage nodes

[Luis Chamberlain <mcgrof@kernel.org>]

On Mon, Mar 10, 2025 at 10:18:00AM -0400, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> Hi -
> 
> Sorry for the length of the series. I'm posting the series as a
> whole to provide context for each of the individual changes. Feel
> free to focus on whichever patch or patches in this series are most
> interesting to you. All review comments are welcome.
> 
> The high-level goal is to enable testing NFS / SMB / iSCSI with
> kdevops in the cloud. These workflows are already operational for
> guestfs. The basic challenge is each cloud provider has a distinct
> way of provisioning and attaching block devices.
> 
> This series can be considered in two sections:
> 
> - the first four patches wrangle the terraform for some of the
>   cloud providers to make them provision a set of extra block
>   volumes, each of the same size, just as guestfs and AWS
>   currently do.
> 
> - the second half of the series adds a new playbook that:
> 
>   - de-duplicates the scripting that creates an LVM volume group,
>     because three different roles each implement this the same way
> 
>   - replaces the "skip one device" method for determining which
>     extra block volume the /data partition should live on. AWS still
>     needs some work here because NVMe devices can get renamed after
>     every instance reboot
> 
>   - adds LVM support that handles the differences amongst the cloud
>     providers, tucked away in the new playbook
> 
> 
> GCE and OpenStack are not yet updated, but they are in plan.

Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>

  Luis