The Gluster Blog

Gluster blog stories provide high-level spotlights on our users all over the world

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

Gluster
2012-07-04

Node Install

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.

  1. Do a base (Minimal) install of your chosen OS.
  2. Upgrade to the lastest packages.
    yum -y upgrade
  3. Setup a glusterfs repo this repo was created by the same person who does the 3.2.5 packages in Fedora/EL6.
    • For RHEL/CentOs/Scientific Linux 6.2

      wget http://repos.fedorapeople.org/repos/kkeithle/glusterfs/epel-glusterfs.repo -P /etc/yum.repos.d/
    • For Fedora 17

      wget http://repos.fedorapeople.org/repos/kkeithle/glusterfs/fedora-glusterfs.repo -P /etc/yum.repos.d/
  4. Setup the oVirt repo you intentend to use.
    • For RHEL/CentOs/Scientific Linux 6.2

      wget http://www.dreyou.org/ovirt/ovirt-dre.repo -P /etc/yum.repos.d/
    • For Fedora 17

      wget http://ovirt.org/releases/beta/ovirt-engine.repo -P /etc/yum.repos.d/
  5. Now lets install some packages
    yum clean all
    yum install vdsm vdsm-cli vdsm-gluster

Now lets get the install ready to join the cluster.

  1. Force NFS to use ver. 3 edit /etc/nfsmount.conf and add.
    [ NFSMount_Global_Options ]
    Defaultproto=tcp
    Defaultvers=3
    Nfsvers=3
  2. Based on my install the management bridge fails to create most of the time. Here is how I manually create them. The example config files all reside in /etc/sysconfig/network-scripts.
    First we edit /etc/sysconfig/network-scripts/ifcfg-eth0. On your system it might be em0 instead of eth0. Adjust the device line to match what is already there.

    DEVICE=eth0
    BOOTPROTO=none
    NM_CONTROLLED=no
    ONBOOT=yes
    BRIDGE=ovirtmgmt
  3. Now we create /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt with the following
    DEVICE=ovirtmgmt
    BOOTPROTO=static
    GATEWAY=192.168.100.254
    IPADDR=192.168.100.201
    NETMASK=255.255.255.0
    NM_CONTROLLED=no
    ONBOOT=yes
    TYPE=Bridge

Now lets return to the engine and add the host into the cluster.

  1. Select the Host tab.
  2. Click New to add a new host.
  3. Name: Enter a Name you want the host to be known as.
  4. Address: Either enter the IP address or URL for the host.
  5. Root Password: Enter the root password for the host
  6. Automatically configure host firewall: Leave it checked
  7. You need to setup your power management settings. Below is a screen shot of my Drac5 settings. Note your 1st node will fail since there isn’t a 2nd node as you can see from the screen shot
  8. This step will take about 5 min a node and will reboot the node. Only add one node at a time I have had weird issue

Repeat for each host. Note you still need to make some changes on each host but because each node needs to talk to each other I suggest setting up all nodes first.

Next Step Volume Setup

topic: 

Groups: 

BLOG

  • 06 Dec 2020
    Looking back at 2020 – with g...

    2020 has not been a year we would have been able to predict. With a worldwide pandemic and lives thrown out of gear, as we head into 2021, we are thankful that our community and project continued to receive new developers, users and make small gains. For that and a...

    Read more
  • 27 Apr 2020
    Update from the team

    It has been a while since we provided an update to the Gluster community. Across the world various nations, states and localities have put together sets of guidelines around shelter-in-place and quarantine. We request our community members to stay safe, to care for their loved ones, to continue to be...

    Read more
  • 03 Feb 2020
    Building a longer term focus for Gl...

    The initial rounds of conversation around the planning of content for release 8 has helped the project identify one key thing – the need to stagger out features and enhancements over multiple releases. Thus, while release 8 is unlikely to be feature heavy as previous releases, it will be the...

    Read more