These instructions take in account that your control panel (with ip 10.40.1.1 in this example) is where templates and backups are stored, if this is not the case adjust them accordingly.
Before starting with the hypervisor installation, make sure you can reach your SAN/Volumes and Onapp management network.
- echo >> /etc/fstab ‘10.40.1.1:/onapp/backups /onapp/backups nfs soft,noatime,intr,tcp,rsize=32768,wsize=32768 0 0’
- echo >> /etc/fstab ‘10.40.1.1:/onapp/templates /onapp/templates nfs soft,noatime,intr,tcp,rsize=32768,wsize=32768 0 0’
- Go to 10.40.1.1 and edit the file /etc/exports in order to allow nfs access from the hypervisor ip you are installing. Restart nfs by doing /etc/init.d/nfs restart
- mkdir -p /onapp/backups
- mkdir -p /onapp/templates
- wget http://rpm.repo.onapp.com/repo/centos/5/x86_64/OnApp-x86_64.repo -O /etc/yum.repos.d/OnApp-x86_64.repo
- yum install onapp-hv-install
- /onapp/onapp-hv-install/onapp-hv-xen-install.sh or /onapp/onapp-hv-install/onapp-hv-kvm-install.sh
- /onapp/onapp-hv-install/onapp-hv-config.sh -h 10.40.1.1
- nohup ruby /onapp/tools/vmon.rb > /dev/null &
- nohup ruby /onapp/tools/stats.rb > /dev/null &
- mount -a (in order to make sure everything is alright with your fstab)
- Go to your cloud control painel and add the hypervisor to the desired hypervisor zone.
These instructions worked at the time i wrote this, in the future they may not work.