23.2. Verifying that Red Hat Gluster Storage Instance is Running

You can verify that Red Hat Gluster Storage instance is running by performing a remote login to the Red Hat Gluster Storage instance and issuing a command.
To verify that Red Hat Gluster Storage instance is running
  1. On the Amazon Web Services home page, click the Amazon EC2 tab. The Amazon EC2 Console Dashboard is displayed.
  2. Click the Instances link from the Instances section on the left. The screen displays your current instances.
  3. Check the Status column and verify that the instance is running. A yellow circle indicates a status of pending while a green circle indicates that the instance is running.
    Click the instance and verify the details displayed in the Description tab.
  4. Note the domain name in the Public DNS field. You can use this domain to perform a remote login to the instance.
  5. Using SSH and the domain from the previous step, login to the Red Hat Amazon Machine Image instance. You must use the key pair that was selected or created when launching the instance.
    Example:
    Enter the following in command line:
    # ssh -i rhs-aws.pem ec2-user@ec2-23-20-52-123.compute-1.amazonaws.com
    # sudo su
  6. At the command line, enter the following command:
    # service glusterd status
    Verify that the command indicates that the glusterd daemon is running on the instance.

    Note

    Samba and NFS-Ganesha channels are disabled by default. To use standalone Samba and NFS-Ganesha, perform the following steps to enable the repos and install the relevant packages.
    • For enabling the Red Hat Gluster Storage Samba repo, run the following command:
      yum-config-manager --enable rhui-REGION-rh-gluster-3-samba-for-rhel-6-server-rpms
    • For enabling the Red Hat Gluster Storage NFS-Ganesha repo, run the following command:
      yum-config-manager --enable rhui-REGION-rh-gluster-3-nfs-for-rhel-6-server-rpms

Important

Before using yum update to update the Amazon EC2 Red Hat Gluster Storage AMI, follow the steps listed in https://access.redhat.com/solutions/1556793 Knowledgebase article.