Go to file
Jeff Carr 7a0925041e of course I spelled this wrong
Signed-off-by: Jeff Carr <jcarr@wit.com>
2024-10-24 17:52:46 -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 of course I spelled this wrong 2024-10-24 17:52:46 -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 keep and deprecate 2024-10-24 17:21:40 -05:00
events.proto just make a .proto file for experiments 2024-10-24 17:50:50 -05:00
experiments.proto of course I spelled this wrong 2024-10-24 17:52:46 -05:00
helpers.go don't do experiements anymore in droplets.proto 2024-10-24 17:12:05 -05:00
hypervisor.proto seperate config files for droplets, hypervisors & events 2024-10-24 16:57:50 -05:00
sampleData.go just make a .proto file for experiments 2024-10-24 17:50:50 -05:00
storageinfo.go just make a .proto file for experiments 2024-10-24 17:50:50 -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'