control your cluster of virtual machines
Go to file
Jeff Carr 8724a07b0d function to dump all droplets
Signed-off-by: Jeff Carr <jcarr@wit.com>
2024-10-29 09:00:40 -05:00
resources network is maybe correct as virtio. pci needed? 2024-10-26 02:31:52 -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 validate stuff should be here 2024-10-27 02:29:45 -05:00
README clean up logging of initial scan of droplets 2024-10-17 15:29:47 -05:00
argv.go validate stuff should be here 2024-10-27 02:29:45 -05:00
dump.go function to dump all droplets 2024-10-29 09:00:40 -05:00
event.go sets unique spice port and saves config files 2024-10-27 04:53:39 -05:00
http.go function to dump all droplets 2024-10-29 09:00:40 -05:00
main.go track droplets reported from each hypervisor 2024-10-27 11:02:50 -05:00
poll.go ready to release a debian package? 2024-10-28 11:44:53 -05:00
post.go start worked by sending protobuf 2024-10-26 20:09:59 -05:00
start.go sets unique spice port and saves config files 2024-10-27 04:53:39 -05:00
structs.go track droplets reported from each hypervisor 2024-10-27 11:02:50 -05:00
validate.go maybe fix duplicates? this isn't really safe probably 2024-10-27 08:10:19 -05:00
watchdog.go track droplets reported from each hypervisor 2024-10-27 11:02:50 -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