Fedora 27 Final hasn’t dropped yet (as of today, Nov 3, 2017) but it won’t stop those technologists among us who insist on showing some poor, defenseless code who’s boss.
After successfully surviving an upgrade from Fedora 25 to 27 Beta I knew it was time to keep moving forward. Being a long time VMware and XenServer fan I have always been a bit spoiled when it comes to managing virtual machines. Each hypervisor provides a fairly intuitive management interface with very little hassle in setting it up.
KVM has an abundance of available management tools here: http://www.linux-kvm.org/page/Management_Tools
My requirements for a hypervisor manager were pretty short:
- “Easy” install
- Simple configuration
I would have likely found success MUCH FASTER had I not insisted on using the latest Beta release of Fedora. For example, oVirt 4.2 is a beautiful solution that is the foundation of RHV. However it only has repo’s for CentOS/RHEL/SUSE.
I REALLY wanted to use the on-prem, opensource version of mist.io which uses best of breed modern tech stack (MongoDB, ElasticSearch, RabbitMQ, Docker) but I couldn’t get it through the “create a user” stage and chose to pick our headline technology. I’m going to chalk this up to some minor changes to the way that Docker-Compose works on FC27 and will DEFINITELY be trying this again in a few months when FC27 has been GA for a while.
sudo systemctl disable firewalld sudo systemctl stop firewalld
Minor semantic change from
sudo dnf install -y git python-pip libvirt-python libxml2-python python-websockify supervisor nginx
If you receive an error you will need to fix the permissions:
usermod -a -G libvirt nginx usermod -a -G kvm nginx