thatch45 / butter Goto Github PK

If a hypervisor is detected and it does not have libvirt ssl keys, we want butter kvm to make and distribute them for us, so that we can control them from butter. Also allow libvirt certs to be overwritten.

Also, add a config option so that if a hyper is detected and it does not have certs, push em' out automatically!

look into it!

kvmd and statd

Very simple, but has a config and gathers status info from minions and loads a db that "something" can look at, the "something" will most likely be a web interface.

The clean_old function needs to do something, this is blocked by changing the format of the redis data

butter needs to do some serious magic with vms:
allow seamless shared and non-shared storage support
operate on live state data
Autodetect if vm is on shared or non-shared storage
Execute migration - full path
apply a fully customizable set of overlay data
overlay data is applied on the hypervisor
CLI interface needs to work like this:
butter kvm -C foo
butter kvm --daemon
Need to be able to recreate the root from a stored overlay
butter will require that salt is running and that all of the hypervisors in the cloud have access to shared storage along the same path. If these are the only reqs then the master can follow the salt master and we can use salt clustering when it becomes available.
keep all configs on the master, no minion configs.
allow for configs to be placed on shared storage for salt cluster support.

Allow for the stats of a vm to be edited on the fly, primarily cpus and ram

Need to make it so that the purge function detects drive images, we have the data!

the vdb is the wrong name and in the wrong path

Create a configuration file format via yaml that allows for all of the vms in a deployment to be mapped, then call butter vm and butter will ensure that the state of all virtual machines is consistent.

The output file is bad

need to make sure the vm was made before exiting, and print out data about it

What they type is what they get

The next plugin for butter, the stat gathering interface!

as it says

Basically verbosity settings, allow for the queries to list less data

I need to lose some sleep thinking about the best way to do this

I need to make adding overlay components to a virtual machine a pluggable thing, so that somebody can say "I want to generate overlay info for system X" or "We should add a module for BIND support"
So they they can just add it in.

dosent seem to apply

When purging a vm, the vm needs to be, um, PURGED

We need a butter interface that does all of the puppet work for you, so that we don't need a puppet daemon running on the puppets, I want to make puppet a push system via butter.

query the info for a single hyper

But, the remnants need to be cleaned up, and the migration needs to be verified