MesosCon and moving to virt-manager

I was able to attend MesosCon in September in LA - it was awesome.  Really starting to see how the two level scheduling in Mesos is the key to unifying Kubernetes and the Smack stack under one umbrella.  I spoke with Brandon from openstack-helm about possibly deploying the helm charts on a k8's install inside DCOS.  This is probably a ways out - but considering how deploying k8's as a DCOS service could streamline that part of the equation - I think it may be worth a go.

Here are some links i used in setting up virt-manager on my 3 NUCS.  It seems like it should be lighter weight than Nutanix - which had overhead of 8G per NUC.   Even with Gnome running now, this looks more like 2G and that 6G savings is important.

http://www.itzgeek.com/how-tos/linux/centos-how-tos/install-gnome-gui-on-centos-7-rhel-7.html

http://laptops.eng.uci.edu/software-installation/using-linux/how-to-configure-xming-putty

---this did not allow X to run i ended up installing gnome also from link above.

https://www.linuxtechi.com/install-kvm-hypervisor-on-centos-7-and-rhel-7/

https://www.youtube.com/watch?v=rSxK_08LSZw

http://www.itzgeek.com/how-tos/mini-howtos/create-a-network-bridge-on-centos-7-rhel-7.html

I have not tried this one (moving the vm)

http://ostolc.org/kvm-move-guest-to-another-host.html

Word of caution:

If you plan to use virt-manager to host DCOS nodes : you CANNOT run docker on same host as the br0 bridge that links the VM's to the physical network.  It will fry the bridge connection.  At least the default install will.  You will not be able to ssh into the VM's etc