jcarr
/
virtbuf
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
37 Commits 3 Branches 13 Tags 3.3 MiB
Go 93.9%
Makefile 6.1%
Go to file
Jeff Carr dac27e31b5 update thinking in the notes 
Signed-off-by: Jeff Carr <jcarr@wit.com>
 		2024-10-24 16:16:47 -05:00
configfile notsure 2024-10-23 00:20:22 -05:00
.gitignore first go at it 2024-10-18 20:58:15 -05:00
Makefile stub out some kinda events something or other 2024-10-22 23:35:52 -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
droplet.proto minor formating 2024-10-24 16:09:39 -05:00
events.proto add timestamp and any types 2024-10-24 16:04:26 -05:00
helpers.go virtigo can now replace libvirt xml files 2024-10-23 16:06:02 -05:00
hypervisor.proto minor formating 2024-10-24 16:09:39 -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'