Creating a CentOS template.
1) Miniumal install of Center OS 6
2) su - # Switch User to root
3) wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/
4) yum install rhev-agent-pam-rhev-cred rhev-agent
5) service rhev-agentd start
6) Yum -y upgrade # Install al updates.
7) Install any packages you want on the system.
oVirt 3.1 is currently in beta and compared to 3.0 it adds a several new features. One of the nice new features is glusterfs support. For it intended use it works well but I personally think it needs to be adjusted to for more generic use. The 2 main limits that effect me are. 1) Only oVirt nodes in the same cluster can be used as bricks to create clusters. So you can't add in storage only nodes in the same oVirt cluster as nodes. However you can create a cluster of just gluster only nodes.
So lets begin by installing the engine. The engine install is pretty standard the only major change is going to be turning on gluster support in the cluster tab. Lets walk though the steps for installing the engine.
So lets begin by installing the a node. The node install is pretty standard but there are a few very important steps that have to be done or it wont work correctly. All the issues I have found have been put into bugzilla. Before you begin your node install please make sure you have the engine setup correctly as outlined in Engine Install.
Now that all the nodes are setup and added to the cluster we need to tweak a few settings create our 1st volume and add it to the data center. Before completing these steps please make sure you have gone though and confirm you have both the Engine and the Node are setup before contining.
Something I want to keep track of as it looks usful for servers that do more then Apache on them.
From http://www.pool.ntp.org/join.html
It would be nice (but it's not necessary) if you could redirect web requests on port 80 of your time server to the official web page of the project at http://www.pool.ntp.org. If you run Apache, you could do this with:
Adjust as needed but noting the syntax as I can never seem to get it right at 3:00 AM.
To Reboot:
ipmitool -I lan -H 192.168.100.xxx -U root -P password power cycle
I am switching over to Zabbix it just works better then Zenoss for me. During the process I added in templates for postfix. Those are outlined here.
After having issues with network manager after my laptop shutdown I found a fix to the issue. To read the full blog post go here.
I found his info really useful but his page is unreadable I had to copy the text off in order to read.
Thanks
Robert
