Currently we've builtin:
pldrctl create deployment -a 172.16.1.15 -m 00:50:56:a5:29:2c -c booty
These have generally hardcoded configuration and can only be used once, this Issue is to track the capability to create a configuration based upon these as templates.
Something like:
Would configure a BOOTy configuration from the template with some settings and name it pullImage
pldrctl create config --template booty \
--sourceDevice /dev/sda
--destinationAddress http://192.168.0.12/images
--name pullImage
pldrctl create deployment -a 172.16.1.15 -m 00:50:56:a5:29:2c -c pullImage
pldrctl create config --template preseed \
--packages openssh cloud-utils
--noSwap
--name kubernetes
pldrctl create deployment -a 172.16.1.16 -m 00:50:56:a5:f9:24 -c kubernetes
Currently we've builtin:
preseedbootykickstartpldrctl create deployment -a 172.16.1.15 -m 00:50:56:a5:29:2c -c bootyThese have generally hardcoded configuration and can only be used once, this Issue is to track the capability to create a configuration based upon these as templates.
Something like:
Would configure a BOOTy configuration from the template with some settings and name it
pullImagepldrctl create deployment -a 172.16.1.15 -m 00:50:56:a5:29:2c -c pullImagepldrctl create deployment -a 172.16.1.16 -m 00:50:56:a5:f9:24 -c kubernetes