2 ms·
It does containers too; we're especially proud of how it uses common configuration when possible. For instance: # configure the disk image used to boot KVM V
by floren 9y ago
It does containers too; we're especially proud of how it uses common configuration when possible. For instance:
# configure the disk image used to boot KVM VMs
mm$ vm config disk /home/floren/debian.qcow2
# give it 4 gigs of RAM instead of the default 2
mm$ vm config mem 4096
# configure the virtual network, in this case we call it "foo"
mm$ vm config net foo
# launch three KVM VMs
mm$ vm launch kvm my-vm[1-3]
# now configure the container filesystem
mm$ vm config filesystem /home/floren/containerfs/
# launch 10 containers; they will also get 4GB of RAM and be connected to the "foo" network
mm$ vm launch container my-container[1-10]
# start all the VMs that we've launched so far
mm$ vm start all
- tyingq 9y agoAhh, that's great, and helps explain what makes it different. With containers in addition to VM, it now looks more like a stripped down proxmox that's much more scriptable. Looks like it would be a good underpinning to implement your own VPS service with "resource pools", where end users get some amount of cores, memory, disk, but can slice them however they want.
- floren 9y agoYeah, there's a lot of fun things to do with it. Namespaces are especially cool. First you set up your minimega cluster (the nodes can auto-discover each other), then you run e.g. `namespace foo`. This creates a namespace containing all other nodes in the cluster (your machine is considered the defacto 'head' node but you could also add it to the namespace if desired). Now if you launch VMs, they'll actually get distributed among the nodes of the cluster based on available memory & current load. This makes it super easy to go from prototyping on your desktop to running the whole thing across a cluster--add a 'namespace' call at the top of your script and it'll Just Work.