Allow custom variables to be defined as 6th parameter on PART

[cyberplant]

For example the SWRAIDLEVEL can be changed for different partitions:

SWRAIDLEVEL 1
PART /boot  ext3 512M
PART /      ext4 40G
PART swap   swap 4G
PART /mnt   xfs all "" SWRAIDLEVEL=0

Not tested yet, done quickly on the Github UI, can test it later.

[cyberplant]

I had to do many adjustments but now it's working!

With this config file:

DRIVE1 /dev/nvme0n1
DRIVE2 /dev/nvme1n1
SWRAID 1
SWRAIDLEVEL 1
PART /boot  ext3 512M
PART /      ext4 40G
PART swap   swap 4G
PART /mnt   xfs all no array_raidlevel=0

I was able to get the first 3 partitions with RAID1 and the last one with RAID0.

NOTE: I changed the logic for the "crypt" part.. before it was just checking if the 5th column had anything, now it must say "yes" to have crypt enabled (it can be changed to any other word, of course).

This is the result after running it on one real server:

[cyberplant]

hey @asciiprod , what do you think about this?

I have adapted my launch scripts to use my patched version, but it could be better if we can merge it and we just go back to use upstream version.

I'm open to comments!

[awsms]

Was able to create a RAID1+0 flawlessly with #85, thanks!

[cyberplant]

Cool, glad to hear that, @awsms ! 😊

[lraphael]

Would something like this also work?

SWRAID 1
SWRAIDLEVEL 1

PART /boot ext3 1024M
PART lvm vg0 20G
PART lvm vg1 all array_raidlevel=0

LV vg0 root / ext4 20G
LV vg1 swap swap swap 4G
LV vg1 clusterstorage /var/lib/longhorn ext4 all

[cyberplant]

@lraphael sorry for the delay. Yes, I think it should work, but keep in mind that you need to populate the "encrypt" field before our custom variables.