Go to file
Jeff Carr 87b7bc17b3 seperate config files for droplets, hypervisors & events
Signed-off-by: Jeff Carr <jcarr@wit.com>
2024-10-24 16:57:50 -05:00
example seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
.gitignore seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
Makefile seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
README.md update thinking in the notes 2024-10-24 16:16:47 -05:00
cluster.proto add hypervisor struct 2024-10-22 03:26:02 -05:00
config.go seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
droplet.proto seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
events.proto add timestamp and any types 2024-10-24 16:04:26 -05:00
helpers.go seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
hypervisor.proto seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
sampleData.go another total violation of protobuf by renumbering 2024-10-23 17:39:50 -05:00
storageinfo.go notsure 2024-10-23 00:20:22 -05:00

README.md

They are what to use for starting droplets with virsh, but for making a cluster or "home cloud" with virtigo

When possible & sensible, use the same variable names as libvirt

virtigo needs to coordinate all the virtual machine information centrally. The information in the libvirt xml files are imported into these protobuf definitions and passed around as protobufs

virtigo recreates the libvirt xml files and calls 'virsh create'