This is the commit message #4:
Basic functionality works, VNC is still trash fire
Don't use config_local
Add a workdir
RUN touch proxmox_ssh_key, update permissions
Update development instructions
Add some comments to the template file, Make it easier-ish for the kiddos.
A comprehensive™ instruction booklet for setting up your own instance of
Proxstar to mess around with. This is _roughly_ what I had to do to get
this all working.
Update the UI boot order selection element. It has been modified to
support the new 'order=' format for the Proxmox boot order option
in a more intuitive way for the user. The new element allows users
to enable any bootable device and choose the order for these
devices to boot in.
The new UI element is a table with four columns. The first column
indicates the order of the corresponding device. The second column
indicates whether the device is enabled as bootable. The third
column contains the device name. The fourth column contains the
device description. The order of the columns is changed by
dragging, enabled by SortableJS.
In cases of legacy nodes, the older dropdown boxes are used.
Change format of the VM boot order JSON. This new format allows
the UI to mimic the Proxmox boot order selection system.
The new format is as follows
{
'legacy': False,
'order': [
{
'device': 'virtio0',
'description': 'local-lvm:vm-102-disk-0,size=8G',
'enabled': True
},
...
]
}
Propose new boot order to owners of VMs that exist on nodes
running Proxmox version 6.3 or greater.
Instead of returning the legacy boot order to the UI, a new boot
order is created and sent instead. The new order mimics the old
order, but is compliant with the new format. The new order will
take effect only if the user explicitly updates.
Update boot order parsing so as to be compatible with the new
Proxmox syntax for virtual machine boot device ordering.
Maintain support for the deprecated boot device order syntax. Virtual
machines using the deprecated syntax are not updated to use the new
syntax.
