On Sat, 26 Jun 2021 at 02:50, Ryan Harper <email address hidden>
wrote:
> I'm missing the storage config you're trying to process.
Yes, fair. The reason I'm running into this is to handle machines with
VROC, which often ship with containers and volumes pre-congfigured (or
configured with the UEFI application for this, i.e. pre-OS boot). So I can
show you a config but you probably don't have access to a machine that can
run it...
IIUC, our
> existing preserve: true raid scenario looks like this (see
> curtin/examples/tests/preserve-raid.yaml) but let's extend it and create
> a partition on the raid
>
I pushed a new vmtest to the branch in review (not using the new flag added
by the review). I haven't run it yet, I will do so soon.
> The disk handler never runs against a raid device, just like it doesn't
> run against lvm or any other composed device.
>
On Sat, 26 Jun 2021 at 02:50, Ryan Harper <email address hidden>
wrote:
> I'm missing the storage config you're trying to process.
Yes, fair. The reason I'm running into this is to handle machines with
VROC, which often ship with containers and volumes pre-congfigured (or
configured with the UEFI application for this, i.e. pre-OS boot). So I can
show you a config but you probably don't have access to a machine that can
run it...
IIUC, our examples/ tests/preserve- raid.yaml) but let's extend it and create
> existing preserve: true raid scenario looks like this (see
> curtin/
> a partition on the raid
>
I pushed a new vmtest to the branch in review (not using the new flag added
by the review). I haven't run it yet, I will do so soon.
> The disk handler never runs against a raid device, just like it doesn't
> run against lvm or any other composed device.
>
Sure it does: /git.launchpad. net/curtin/ tree/curtin/ commands/ block_meta. py#n1612
https:/