Support VM provisioning #22
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Support provisioning VMs via image support.
Also, support arbitrary scripts to generate VMs as an alternative to images.
changed title from Support VM provisioning{- via images-} to Support VM provisioning
changed the description
Step 1: Allow removing VMs including all disk devices.
Step 1 was completed.
Step 2: Implement templating system for VM sizes/base configurations (RAM, CPU, network, disks etc.).
Step 3: Implement scripting template system for VM deployment
Image support
Template support
system
vcpu
,memory
.network
vni
, multiple.disk
template
,volume
,size
, multiple.Script support
prep
,chroot
,cleanup
. Usevm define
for inspiration as same exact idea (import, modify by replace or$EDITOR
).VM add sequence
pvc-common
instead ofpvc-client-common
?).prep
scripts.chroot
and launchingchroot
scripts.cleanup
scripts and unmapping RBDs.Replanning this as a separate daemon, not an integrated node feature.
mentioned in commit
5995353597
Initial implementation of script-based provisioning done. Working on tweaks to make more configurable VMs.
Working on integrating cloud-init metadata into the system. Deploying as a second daemon that will listen on the well-known link-local IP address and provide DigitalOcean-style Metadata to the VMs, especially user-data which will be added to the provisioner DB and tied to profiles.
mentioned in merge request !1
closed via merge request !1
mentioned in commit
45dbc0eef8