If you have every created a linux virtual machine template you’ve probably experienced the issue where a new ethernet device would be created on each VM instance created from that template. For those that have not found the resolution to this problem are in for a treat if your working with CentOS or RHEL. All thats needed is to delete the “/etc/udev/rules.d/70-persistent-net.rules” file right before you shutdown the vm and make it a template.
The tip I have for you this time is to use CloudStacks interface for accessing meta-data about you instance from within the instance. It’s very simple to use and can be very useful. In this tip I’ll show how you can use the meta-data to rename a CentOS 6.4 linux instance automatically after it is created. But first lets introduce the meta-data interface for CloudStack.
CloudStack 4.2 is ready for release but the site has not updated so that you can just update your repo and install or upgrade so in this post I’ll go thru the process I use to compile from source. You can use this process for other versions but some things may change. You could also follow the process on the Apache Cloudstack documentation website but this is a slim down version to get you quickly moving with 4.2.
oVirt 3.3 is now release. If you have no idea what oVirt is or what it’s used for put simply it’s pretty similar to VMware vCenter except open source and doesn’t manage ESX. oVirt is a centralized management solution used to manage KVM hosts and GlusterFS as well as other aspects of your virtualization environment. If your just looking to create and manage virtual machines, oVirt has you convered and includes many of those got to have features like HA and live migration.
If you’ve wanted to access one of the cloudstack system vm’s but couldn’t find out how well this is your lucky day.
Before adding your hosts in the cloudstack manager you need to pressed the system vm template. This does not go over the process for setting up the storage backend (NFS).
Finally there’s an easy way to deploy Openstack on Redhat and CentOS. RDO is a community of people using and deploying OpenStack on Red Hat and Red Hat-based platforms. I have always thought that it’s been much too complicated to install and setup Openstack and all it’s components. With RDO I was able to get an Openstack two node environment setup in my lab in roughly 30 minutes. There’s more to Openstack than just the installation and now that my time can be better spent on that other stuff.
If you have installed the cloudstack agent and it will not start you may be seeing these errors.
CloudStack is now at 4.1 and there have been many changes. This means that the installation process has also changed so I wanted to update the process I outlined from a previous post (http://thehyperadvisor.com/?p=2093) for CloudStack 4.1. I will outline some of those changes, which is really only one for the kvm host server, to help you easily install CloudStack on CentOS. This post will focus on the kvm host server.
So, this is my second day working with totally converting from having and Vmware hypervisor. You can read the Day One blog here. Today I was task to install a few vm guests, totally wipe my main Vista x64 desktop and install Fedora 12 with KVM. Again I choose the base install during the Fedora 12 installation.