Installing oVirt 3.1 and glusterfs using either NFS or Posix (Native) File System Engine Install

Submitted by rmiddle on Wed, 07/04/2012 - 18:09

Engine Install

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.
  1. Do a base (Minimal) install of your choosen OS.
  2. Upgrade to the lastest packages. yum -y upgrade
  3. Setup the oVirt repo you intentend to use.
    • For RHEL/CentOs/Scientific Linux 6.2 wget -P /etc/yum.repos.d/
    • For Fedora 17 wget -P /etc/yum.repos.d/
  4. Installing Prerequisite Packages: yum install -y postgresql-server postgresql-contrib
  5. Now install the engine yum install ovirt-engine
  6. Lets confirm the version of Java installed since someone reported only having 1.6 installed instead of the required 1.7 alternatives --config java There are 2 programs which provide 'java'.Selection Command ----------------------------------------------- + 1 /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java * 2 /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/javaEnter to keep the current selection[+], or type selection number: In this case you need to select #2 If jre-1.7.0-openjdk.x86_64 isn't listed you need to manually install Java 1.7 yum install java-1.7.0-openjdk.x86_64 java-1.7.0-openjdk-devel.x86_64 Now re-run alternatives to confirm 1.7 is the default.
  7. Now we setup oVirt Engine. Most of the setting we will use the defauls. Note there are NFS shares needed for exports and ISO you can do them under gluster but there really isn't a need since the are only used when setting up or backing up a VM and not during VM usage. Because my oVirt engine systems has a few hundred gigs free I create the NFS share on the same server as the oVirt Engine server. If you want to use a diff NFS server for the ISO and export folders simple say No when asked about creating the nfs share.

Run the engine setup

    1. engine-setup
    2. Welcome to oVirt Engine setup utility ovirt uses httpd to proxy requests to the application server. It looks like the httpd installed locally is being actively used. The installer can override current configuration . Alternately you can use JBoss directly (on ports higher than 1024) Do you wish to override current httpd configuration and restart the service? ['yes'| 'no'] [yes] : *yes *Then it will ask if you want to overwrite your current httpd configuiration. Say Yes
    3. HTTP Port [80] : 80
    4. HTTPS Port [443] : 443
    5. Host fully qualified domain name, note that this name should be fully resolvable [] : Enter * Note the Domain name must exist if it doesn't you need to add it to /etc/host on the engine and all the nodes.
    6. Password for Administrator (admin@internal) : *Password * Make sure you pick a password you can remember you will need this to log into the web interface.
    7. Organization Name for the Certificate: *Example Inc *This will be visible to anyone who uses the web interface.
    8. Since we are installing gluster I assume you wont be using FC or iSCSI and posix fs isn't an option but we can change it later. The default storage type you will be using ['NFS'| 'FC'| 'ISCSI'] [NFS] : NFS
    9. You can do a remote server but it is up to you to get that setup and working. Enter DB type for installation ['remote'| 'local'] [local] : Enter
    10. Local database password :password *This the database password you only need to use this if you are planing on tweaking database fileds. Make it strong.
    11. Should the installer configure NFS share on this server to be used as an ISO Domain? ['yes'| 'no'] [yes] : *yes * Unless you are planning to use a different system for NFS I recommend you answer yes.
    12. Local ISO domain path: */nfs/iso * Note no trailing / and make sure the target location already exists.
    13. Display name for the ISO Domain:*iso * Will be used later just make sure you remember what you called you iso share
    14. Firewall ports need to be opened. You can let the installer configure iptables automatically overriding the current configuration. The old configuration will be backed up. Alternately you can configure the firewall later using an example iptables file found under /usr/share/ovirt-engine/conf/iptables.example Configure iptables ? ['yes'| 'no']: yes
    15. oVirt Engine will be installed using the following configuration: ======================================================== override-httpd-config: yes http-port: 80 https-port: 443 host-fqdn: auth-pass: ******** org-name: Example Inc. default-dc-type: NFS db-remote-install: local db-local-pass: ******** nfs-mp: /nfs/iso iso-domain-name: iso config-nfs: yes override-iptables: yes Proceed with the configuration listed above? (yes|no): yes
    16. Installing: Configuring oVirt-engine... [ DONE ] Creating CA... [ DONE ] Editing JBoss Configuration... [ DONE ] Setting Database Configuration... [ DONE ] Setting Database Security... [ DONE ] Creating Database... [ DONE ] Updating the Default Data Center Storage Type... [ DONE ] Editing oVirt Engine Configuration... [ DONE ] Editing Postgresql Configuration... [ DONE ] Configuring the Default ISO Domain... [ DONE ] Configuring Firewall (iptables)... [ DONE ] Starting JBoss Service... [ DONE ] Handling HTTPD... [ DONE ]**** Installation completed successfully ******(Please allow oVirt Engine a few moments to start up.....) Additional information: * SSL Certificate fingerprint: B1:92:11:35:A7:38:2E:8E:D2:D2:48:00:AF:68:61:0E:27:BE:1D:97 * SSH Public key fingerprint: 2c:32:83:33:b2:db:e4:31:a3:39:e2:57:32:ad:e8:de * A default ISO share has been created on this host. If IP based access restrictions are required, please edit /nfs/iso entry in /etc/exports * The firewall has been updated, the old iptables configuration file was saved to /usr/share/ovirt-engine/conf/iptables.backup.024634-07022012_23666 * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2012_07_02_02_22_46.log * Please use the user "admin" and password specified in order to login into oVirt Engine * To configure additional users, first configure authentication domains using the 'engine-manage-domains' utility * To access oVirt Engine please go to the following URL:

NFS share Setup Non Gluster

  1. Now lets cleanup the NFS share some. The default install works fine but something there are issue. I found the instructions at to be useful and helps to fix a lot of issues. Let add an export share and tweak the ISO share as well to make sure it just works.
  2. First lets create /nfs/export and make sure the ownership is correct. cd /nfs mkdir -p export chown -R 36.36 iso export
  3. Now lets update /etc/export vi /etc/export change it to the following
    /nfs/iso *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36)
    /nfs/export *(rw,sync,no_subtree_check,all_squash,anonuid=36,anongid=36)
    vi /etc/sysconfig/nfs Add the following to the end of the file file.
    Now lets restart NFS
    • For RHEL/CentOs/Scientific Linux 6.2 service nfs restart
    • For Fedora 17 systemctl restart nfs-server.service

Log into the website

  1. Go to you URL for the website. In my example it is
  2. Selected Administrator Portal * You will likely get an error about the certification not be valid. That is expected. You can manually replace the cert with one that is signed if you intend to allow non techincal users to log into the site.
  3. User name is Admin the password is what you set during install.
  4. You should now see the Main Menu Welcome to your oVirt Manager

Change from NFS to Posix FS (Native Gluser FS)

  1. Skip this section if you plan to access Gluster using NFS!
  2. Select the Tab Marked Data Center
  3. Selete the Item Default from the list.
  4. You should be able to click on Edit.
  5. Select Type and change from NFS to Posix compliant FS

Enabling Gluster support. Both NFS and Native Posix FS

  1. Select tab marked cluster.
  2. Select Edit then add a check box next to *"Enable Gluster Service" * You can create a storage only cluster by selecting new -> Then removeing Enable Ovirt Service and then add one in Enable Gluster Service

Concoraulation You Engine is now setup to run gluster next step setup and configure your nodes.

Node Install