virtbuf

Go to file

Jeff Carr 9ad173a845 expose cluster.Hypervisors Signed-off-by: Jeff Carr <jcarr@wit.com>		2024-10-31 13:21:10 -05:00
example	example runs	2024-10-31 13:12:11 -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	expose cluster.Hypervisors	2024-10-31 13:21:10 -05:00
backupDir.go	try to actually make real files	2024-10-27 07:49:03 -05:00
change.go	seems to compile	2024-10-31 13:07:24 -05:00
cluster.proto	seems to compile	2024-10-31 13:07:24 -05:00
config.go	expose cluster.Hypervisors	2024-10-31 13:21:10 -05:00
configBackup.go	code cleanups	2024-10-31 09:19:15 -05:00
droplet.proto	seems to compile	2024-10-31 13:07:24 -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	expose cluster.Hypervisors	2024-10-31 13:21:10 -05:00
hypervisor.proto	attempt at hypervisor arch	2024-10-31 09:28:45 -05:00
newCluster.go	expose cluster.Hypervisors	2024-10-31 13:21:10 -05:00
sampleData.go	expose cluster.Hypervisors	2024-10-31 13:21:10 -05:00
scanIterator.go	example runs	2024-10-31 13:12:11 -05:00
storageinfo.go	just make a .proto file for experiments	2024-10-24 17:50:50 -05:00
time.go	add time duration to cluster	2024-10-31 04:52:14 -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'