3.6 - curtin preseed, or cloud-init for SED operations?

Users
,
1

I have a scenario where some of the systems controlled by MAAS may end up with locked, self-encrypting nvme drives.

I’ll need to install a .deb package with a utility - and run a script to unlock / revert these drives before deployment.

I’m running 3.6.0 as a snap - and have been looking over the documentation for a variety of techniques, like preseeds, curtin user scripts, deploy scripts…but it seems some (most) of these have been removed for 3.6. It isn’t clear to me what they have been replaced with (if anything)

What would be the recommended technique to run something to revert these drives at deploy time?

Thanks for any guidance

Ben

2

Any reference about this? None of them have been removed

3

I can’t find any of them in the UI?
References to them in the cli don’t seem to be there either.

I’ve tried looking for preseed in https://maas.io/docs/api - and can find how to read it, but not set it.

Asking ChatGPT has been an exercise in futility - and I can’t seem to find how to properly inject a curtin user script…ideally for all machines - but if I have to do it on a per-machine basis, that’s OK too.

Maybe this is just be being new to MAAS, and not being able to find the right doc.

Could you point me in the right direction?

4

https://maas.io/docs/about-machine-customization - preseeding section