Chown `targets`, Add run and kill scripts
Lol Joe figured it out
* Dude it works holy shit
We need to fix some logistical bugs, probably, and also like remove dead
code lol
* Open VNC session on the node that the VM belongs
Figured out why I couldn't open a session on anything but 01. It was
because I was making the API call on proxmox01-nrh. So that's where the
session opened. I hope that by doing this, it will balance the load
(what little there is) from VNC sessions.
* Update websockify-related tasks
* Remove SSH key from build
* Add option to specify VNC port.
Should be 443 for OKD, probably 8081 for development.
This hosts a smattering of fixes, acutally uses gunicorn properly(?),
launches websockify correctly, and introduces MORE DEAD CODE!
TODO: Fix the scheduling system
* Make things not crash as much :)
* Remove obviously dead code
There's still some code in here that may require more careful
extraction, testing, and review, so I'm saving that for another PR.
* Fix Joe's complaints
* Replace hardcoded URL
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.
