virtigo

control your cluster of virtual machines

Go to file

Jeff Carr 3ce3a0d7f6 check if spice port has changed Signed-off-by: Jeff Carr <jcarr@wit.com>		2024-10-23 18:53:02 -05:00
resources	keep processing my libvirt xml files	2024-10-23 18:06:46 -05:00
.gitignore	initial something. doesn't do anything yet.	2024-10-11 13:55:13 -05:00
LICENSE	initial something. doesn't do anything yet.	2024-10-11 13:55:13 -05:00
Makefile	compiles and runs. logic wrong	2024-10-23 02:56:55 -05:00
README	clean up logging of initial scan of droplets	2024-10-17 15:29:47 -05:00
addDroplet.go	check if spice port has changed	2024-10-23 18:53:02 -05:00
argv.go	work on adding droplets from libvirt xml files	2024-10-23 04:25:24 -05:00
configfiles.go	compiles and runs. logic wrong	2024-10-23 02:56:55 -05:00
event.go	compiles and runs	2024-10-22 18:19:21 -05:00
http.go	keep processing my libvirt xml files	2024-10-23 18:06:46 -05:00
main.go	cleanup STDOUT logging	2024-10-23 06:27:56 -05:00
poll.go	deprecate hypervisor file. yay!	2024-10-22 19:34:50 -05:00
structs.go	compiles and runs. logic wrong	2024-10-23 02:56:55 -05:00
watchdog.go	global hypervisor poll delay	2024-10-22 19:57:49 -05:00
xml.go	check if spice port has changed	2024-10-23 18:53:02 -05:00

README

virtigo: a control panel for your virtual machine cluster

This is an attempt to make something that should:

* Maintain the master list of virtual machines that should be running at all times
* Work with a cluster of dom0 hypervisiors via libvirt and/or qemu
* Understand the cluster and autostart droplets that have failed
* Initiate and Handle all droplet events: start, stop, clone, migrate, etc
* Verify consistancy on the hypervisors
* Initiate and handle live migrations between hypervisors
* Talk to the hypervisors using only the virtigo daemon via protobuf
* Work in GUI mode (GTK/QT/etc) but ALSO the console (ncurses)
* GPL'd with the intent for use with homelab and personal hobbyists

Notes & Goals:

* Be super easy to use.
* Automatically map access to serial and graphical consoles
* Only temporarily generate libvirt XML files for virsh create
* This is intended for managing Virtual Machines, not for containers
* This often uses the DO nomenclature 'droplets' instead of 'virtual machines' or 'domU'
* Every droplet is considered hostile
* When possible, use protobuf
* Let security be handled externally at the socket layer with other tools
* Put network, cpu, etc stats in external tools
* Automatic live migration to decommission nodes
* Implement iptable rules via the virtigo daemon

Inspired by:

* kvm
* virt-manager
* golang
* the simplicity of the DO droplet control panel