virtbuf

Go to file

Jeff Carr 9608bb680f rename and rm old code Signed-off-by: Jeff Carr <jcarr@wit.com>		2024-10-30 11:06:14 -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
LICENSE	start cleaning junk fields from config files	2024-10-26 12:33:13 -05:00
Makefile	events should not be plural	2024-10-26 06:01:19 -05:00
README.md	update thinking in the notes	2024-10-24 16:16:47 -05:00
add.go	rename	2024-10-30 11:04:55 -05:00
backup.go	try to actually make real files	2024-10-27 07:49:03 -05:00
backupDir.go	try to actually make real files	2024-10-27 07:49:03 -05:00
change.go	rename and rm old code	2024-10-30 11:06:14 -05:00
cluster.proto	events should not be plural	2024-10-26 06:01:19 -05:00
config.go	rename and rm old code	2024-10-30 11:06:14 -05:00
droplet.proto	droplet.ForceHypervisor for binding it there	2024-10-27 05:43:30 -05:00
event.proto	events should not be plural	2024-10-26 06:01:19 -05:00
experiments.proto	of course I spelled this wrong	2024-10-24 17:52:46 -05:00
helpers.go	rename and rm old code	2024-10-30 11:06:14 -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'