pvc/node-daemon
Joshua Boniface 5995353597 Implement VM metadata and use it
Implements the storing of three VM metadata attributes:
1. Node limits - allows specifying a list of hosts on which the VM must
run. This limit influences the migration behaviour of VMs.
2. Per-VM node selectors - allows each VM to have its migration
autoselection method specified, to automatically allow different methods
per VM based on the administrator's preferences.
3. VM autorestart - allows a VM to be automatically restarted from a
stopped state, presumably due to a failure to find a target node (either
due to limits or otherwise) during a flush/fence recovery, on the next
node unflush/ready state of its home hypervisor. Useful mostly in
conjunction with limits to ensure that VMs which were shut down due to
there being no valid migration targets are started back up when their
node becomes ready again.

Includes the full client interaction with these metadata options,
including printing, as well as defining a new function to modify this
metadata. For the CLI it is set/modified either on `vm define` or via the
`vm meta` command. For the API it is set/modified either on a POST to
the `/vm` endpoint (during VM definition) or on POST to the `/vm/<vm>`
endpoint. For the API this replaces the previous reserved word for VM
creation from scratch as this will no longer be implemented in-daemon
(see #22).

Closes #52
2019-10-12 01:17:39 -04:00
..
pvcd Implement VM metadata and use it 2019-10-12 01:17:39 -04:00
pvc-flush.service Wait on both sides for 30s 2019-05-24 01:23:18 -04:00
pvcd.py Massive rejigger into single daemon 2018-10-14 02:40:54 -04:00
pvcd.sample.yaml Properly support debug logging via config 2019-08-01 11:22:27 -04:00
pvcd.service Perform additional tweaks to units 2019-05-23 23:18:28 -04:00
pvcd.target Add node autoflush service and target 2019-05-23 22:42:51 -04:00