jcarr
/
virtbuf
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
45 Commits 3 Branches 13 Tags 3.3 MiB
Go 93.9%
Makefile 6.1%
Go to file
Jeff Carr 2882686caf anypb is probably overkill here 
Signed-off-by: Jeff Carr <jcarr@wit.com>
 		2024-10-25 03:34:03 -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 deprecate old experiment 2024-10-24 18:22:31 -05:00
droplet.proto rm old code 2024-10-24 18:56:38 -05:00
events.proto anypb is probably overkill here 2024-10-25 03:34:03 -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'