Chapter 3. Red Hat Storage Console Installation

Procedure 3.1. Registering with Subscription Manager using Command Line

1. Register the System with Subscription Manager

   Run the following command and enter your Red Hat Network user name and password to register the system with the Red Hat Network:

   # subscription-manager register

2. Identify Available Entitlement Pools

   Run the following commands to find entitlement pools containing the repositories required to install the Red Hat Storage Console:

   # subscription-manager list --available | grep -A8 "Red Hat Enterprise Linux Server"
   # subscription-manager list --available | grep -A8 "Red Hat Storage"

3. Attach Entitlement Pools to the System

   Use the pool identifiers located in the previous step to attach the Red Hat Enterprise Linux Server and Red Hat Storage Console entitlements to the system. Run the following command to attach the entitlements:

   # subscription-manager attach --pool=[POOLID]

4. Enable the Required Repositories

   Run the following commands to enable the repositories required to install Red Hat Storage Console:

   # subscription-manager repos --enable=rhel-6-server-rpms 
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms
   # subscription-manager repos --enable=rhsc-3-for-rhel-6-server-rpms
   # subscription-manager repos --enable=rhs-nagios-3-for-rhel-6-server-rpms
   

5. Verify if the Repositories are enabled

   Run the following command to verify if the repositories are enabled:

   # yum repolist

Procedure 3.2. Registering with Subscription Manager using GUI

1. To register and to attach suitable subscription, see Registering from the GUI section in Red Hat Subscription Management Guide.

   Important

   To attach Red Hat Storage Console subscription, select Manually assign subscriptions after registration option.
2. Run the following commands as root user to enable the repositories required to install Red Hat Storage Console:

   # subscription-manager repos --enable=rhel-6-server-rpms 
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms
   # subscription-manager repos --enable=rhsc-3-for-rhel-6-server-rpms
   # subscription-manager repos --enable=rhs-nagios-3-for-rhel-6-server-rpms
   

3. Verify if the Repositories are enabled

   Run the following command to verify if the repositories are enabled:

   # yum repolist

Procedure 3.3. Registering with Red Hat Satellite Server

1. Configure the client system to access Red Hat Satellite. Refer section Registering Clients with Red Hat Satellite Server in Red Hat Satellite 5.6 Client Configuration Guide.
2. Run rhn_register command to register the system with the Red Hat Satellite.
3. In the select operating system release page, select All available updates and follow the prompts to register the system to the standard base channel for Red Hat Enterprise Linux 6 rhel-x86_64-server-6.
4. Run the following command to subscribe the system to the required Red Hat Storage Console server channels.

   # rhn-channel --add --channel rhel-x86_64-server-6-rhs-rhsc-3 --channel  jbappplatform-6-x86_64-server-6-rpm --channel rhel-x86_64-server-6-rhs-nagios-3

5. Run the following command to verify that the system is registered successfully.

   # rhn-channel --list
   rhel-x86_64-server-6
   rhel-x86_64-server-6-rhs-rhsc-3
   jbappplatform-6-x86_64-server-6-rpm
   rhel-x86_64-server-6-rhs-nagios-3

Procedure 3.4. Installing the Red Hat Storage Console

1. Use the yum command to enure that the most recent version of installed packages are in use.

   # yum update

2. Use yum to initiate the installation of the rhsc package and all the dependencies. You must run this command as the root user.

   # yum install rhsc

Procedure 3.9. Migrating Red Hat Storage Nodes

1. Log in to the Administration Portal as the administrative user. By default this is the admin user.
2. Click the Hosts tab and select the desired host to display the Details pane.
3. Click Maintenance and click OK to place the host in maintenance mode.
4. Upgrade the Red Hat Storage nodes.
   For more information, refer section Upgrading from Red Hat Storage 2.1 Update 4 to Red Hat Storage 3.0 using yum in Red Hat Storage 3 Administration Guide.
5. Click the Hosts tab and select the host to display General tab with the host details.
6. Click here link in Action Items to reinstall the hosts.
7. Enter the password for the Host in Install Host window and click OK.

Procedure 3.10. Changing the Cluster Compatibility Version

1. Log in to the Administration Portal as the administrative user. By default this is the admin user.
2. Click the Clusters tab.
3. Select the cluster to change from the list displayed. If the list of clusters is too long to filter visually then perform a search to locate the desired cluster.
4. Click the Edit button.
5. Change the Compatibility Version to the desired value.
   For more information on the Cluster compatibility version, refer Cluster Properties section in Red Hat Storage Console Administration Guide.
6. Click OK to open the Change Cluster Compatibility Version confirmation window.
7. Click OK to confirm.

Procedure 3.11. Configuring the Console

1. Execute rhsc-setup command

   #rhsc-setup

2. Packages Check
   The rhsc-setup script checks if it is performing an upgrade, or an installation. No user input is required at this stage.

   Checking for product updates...
   No product updates found

3. Network Configuration
   A reverse look-up is also performed on the hostname, which is automatically detected. You can correct the auto-detected hostname if it is incorrect. The fully qualified domain name should have both forward and reverse lookup records in DNS.

   Host fully qualified DNS name of this server [autodetected domain-based name]:

   The rhsc-setup script looks for firewall managers which are both active and enabled in the environment and you can choose to configure the firewall.

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]: yes
   [INFO] iptables will be configured as firewall manager.
   

4. Database Configuration
   You can use either a local or remote PostgreSQL database. The script can automatically configure the database, including adding a user and a database, or use the values that you provide.

   Where is the database located? (Local, Remote) [Local]: Local
   Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
   Would you like Setup to automatically configure postgresql, or prefer to perform that manually? (Automatic, Manual) [Automatic]: Automatic

   For information on how to prepare a postgrSQL database, see Section 3.1.9, “Preparing a PostgreSQL Database Server for use with Red Hat Storage Console”
5. Set the administrator credentials
   You need to set an administrator password for the automatically created administrative user of the Red Hat Storage Console: admin@internal.

   Engine admin password: 
   Confirm engine admin password:

   A message appears on the terminal if the password you have set is weak.
6. PKI Configuration
   The Console uses certificates to communicate securely with its hosts. You need to provide the organization name for the certificate. This certificate can also optionally be used to secure HTTPS communications with the Console.

   Organization name for certificate [autodetected domain-based name]:

7. Apache Configuration
   The external SSL (HTTPS) communications with the Console are secured with the self-signed certificate created in the PKI configuration stage by default, to securely communicate with hosts. You may choose to use another certificate for external HTTPS connections, without affecting how the Console communicates with hosts.

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
   Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]: Automatic
   

   The Red Hat Storage Console uses the Apache web server to present a landing page to users. rhsc-setup script can make the Console's landing page the default page presented by Apache.

    Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
   Do you wish to set the application as the default page of the web server? (Yes, No) [Yes]:
   

8. System Configuration
   The rhsc-setup script by default uses the GlusterFS application mode and skips the NFS configuration.

   [ INFO ] NFS configuration skipped with application mode Gluster

   The rhsc-setup script validates all the inputs, and warns you of any possible problem. Further input is only required if any of the inputs you provided would adversely impact the environment.
   The rhsc-setup script prompts to confirm whether to connect to the Red Hat Access Plug-in.
   On agreeing to configure the proxy server, you are prompted to enter the IP address and the port number of the proxy server. You also have the option to set a user name for the proxy server with a password.

   Would you like transactions from the Red Hat Access Plug-in sent from the RHSC to be brokered through a proxy server? (Yes, No) [No]: No
   

   The rhsc-setup script prompts to confirm whether to enable or disable monitoring by entering Yes or No
   For information on how to configure Nagios, see Configuring Nagios for Red Hat Storage Console in Red Hat Storage Console Administration Guide

   Would you like external monitoring to be enabled? (Yes, No) [Yes]:

   --=CONFIGURATION PREVIEW=--
   Engine database name                    : engine
   Engine database secured connection      : False
   Engine database host                    : localhost
   Engine database user name               : engine
   Engine database host name validation    : False
   Engine database port                    : 5432
   PKI organization                        : example.com
   Application mode                        : gluster
   Firewall manager                        : iptables
   Update Firewall                         : True
   Configure WebSocket Proxy               : False
   Host FQDN                               : rhsc.example.com
   Configure local Engine database         : True
   Set application as default page         : True
   Configure Apache SSL                    : True
   Nagios monitoring enabled for gluster hosts: True
            
             Please confirm installation settings (OK, Cancel) [OK]: OK
   [ INFO  ] Stage: Transaction setup
   [ INFO  ] Stopping engine service
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Stage: Package installation
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Initializing PostgreSQL
   [ INFO  ] Creating PostgreSQL 'engine' database
   [ INFO  ] Configuring PostgreSQL
   [ INFO  ] Creating Engine database schema
   [ INFO  ] Creating CA
   [ INFO  ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'
   [ INFO  ] Stage: Transaction commit
   [ INFO  ] Stage: Closing up
   
   

   • To confirm the displayed configuration values, type OK and press Enter.
   • To correct one or more configuration values, type cancel, this causes the set-up to fail. Run the setup again to provide the correct values.
9. Summary
   When all the required values are provided, the script lists the values for a final confirmation.
   When the script completes, note the additional information provided. Copy the SSH Certificate fingerprint, SSH Public key fingerprint, and Red Hat Storage Console URL for later reference.

    --== SUMMARY ==--
            
   [ INFO  ]  To enable monitoring, ensure the managed nodes are migrated to Red Hat Storage-3.0.Also make sure the auto discovery tool is executed to start monitoring the RHS Nodes, after the cluster nodes are added to Red Hat Storage Console. For detail, refer to RHSC Administration Guide.
   [WARNING] Less than 16384MB of memory is available
             SSH fingerprint: 
             Internal CA 
             Web access is enabled at:
                 http://HostURL:portnumber/ovirt-engine
                 https://HostURL:portnumber/ovirt-engine
             Please use the user "admin" and password specified in order to login.

10. End of Summary
    At this stage, the engine service and http daemon are started.

              --== END OF SUMMARY ==--
             
    [ INFO  ] Starting engine service
    [ INFO  ] Restarting httpd
    [ INFO  ] Stage: Clean up
              Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20141120141807-f4igl5.log
    [ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20141120142427-setup.conf'
    [ INFO  ] Stage: Pre-termination
    [ INFO  ] Stage: Termination
    [ INFO  ] Execution of setup completed successfully
    

    Note

    Automated installations are created by providing the rhsc-setup with an answer file. An answer file contains answers to the questions asked by the setup command.

    • To create an answer file, use the --generate-answer parameter to specify a path and file name with which to create the answer file. When this option is specified, the answers for the questions in the setup process are recorded in the answer file.

      # rhsc-setup --generate-answer=[ANSWER_FILE]

    • To use an answer file for a new installation, use the --config-append parameter to specify the path and file name of the answer file to be used. The rhsc-setup command will use the answers stored in the file to complete the installation.

      # rhsc-setup --config-append=[ANSWER_FILE]

      --config - replaces default system configuration
      --config-append - appends configuration to existing system configuration

    Run rhsc-setup --help for a full list of parameters.

Procedure 3.12. Removing the Console

1. Execute rhsc-cleanup on the system that Red Hat Storage Console is installed on. You must be logged in as the root user to run rhsc-cleanup.

   # rhsc-cleanup

2. Confirm that you want to remove all of the Red Hat Storage Console components. These include PKI Keys, the locally hosted ISO domain file system layout, PKI Configuration, the local NFS exports configuration, and the engine database content.

   Do you want to remove all components? (Yes, No) [Yes]: yes

   Note

   A backup of the Engine database and a compressed archive of the PKI keys and configuration are always automatically created. These are saved under /var/lib/ovirt-engine/backups/, and their filenames include the date and engine- and engine-pki-, respectively.
3. You will be prompted to confirm the action to remove Red Hat Storage Console. If you choose to proceed, the ovirt-engine service is stopped, and the configuration is removed according to the options you select.

   During execution engine service will be stopped (OK, Cancel) [OK]: OK
   ovirt-engine is about to be removed, data will be lost (OK, Cancel) [Cancel]: OK
   

   The configuration files of the environment are removed.
4. You can safely uninstall the Red Hat Storage Console packages using yum.

   # yum remove rhsc*

1. In a browser, navigate to https://<IP Address>/webadmin. Replace <IP Address> with the URL provided during installation.
2. When initially connecting to the Administration Portal, a prompt appears asking if the ca.cer certificate is trusted. Follow the prompts and then click the new link that appears on the page to reload the Administration Portal.
3. The portal log in screen displays. Enter admin as the User Name. Enter the password set during installation in the Password field. Select the internal domain from the Domain list.
   Click Login to log in.

Procedure 3.13. Preparing a PostgreSQL Database Server for use with Red Hat Storage Console

1. Initialize the database and start the postgreSQL service by running the commands:

       # service postgresql initdb
       # service postgresql start

2. Create a postgreSQL user for the Red Hat Storage Console to use when it reads from and writes to the database, and a database to store information about the environment in. This step is required on both local and remote manually configured database servers.

   # su - postgres
   $ psql              
   postgres=# create user USER password 'PASSWORD';
   postgres=# create database DATABASE owner USER;

3. Make sure that database can be accessed remotely by enabling client authentication. This step is required on manually configured remote database servers. Edit the /var/lib/pgsql/data/pg_hba.conf file, and add this line:

   host all all X.X.X.X/24 trust

   Replace X.X.X.X with the IP address of the Console server.
4. Allow TCP/IP connections to the database. This step is required on manually configured remote database servers. Edit the /var/lib/pgsql/data/postgresql.conf file, and add this line:

   listen_addresses='*'
   port = 5432

   This example makes postgreSQL listen for connections on all interfaces. You can specify an interface by giving its IP address.This requires a restart of the postgreSQL server.
5. Restart the postgres service. This step is required on both local and remote manually configured database servers.

   service postgresql restart

Procedure 3.14. Configuring the Manager to use a Manually Configured Local or Remote PostgreSQL Database

1. During the Red Hat Storage Console installation using the rhsc-setup utility, you are prompted to decide where the database is located.

   Where is the database located? (Local, Remote) [Local]:

   The steps involved in manually configuring the Red Hat Storage Console to use remote and local databases are the same, except that to use a remotely hosted database, you need to provide the hostname of the remote database server, and the port it is listening on.
2. If you are using a remote manually configured database, supply the rhsc-setup utility with the hostname of the database server and the port it is listening on.

   Database host [localhost]:
   Database port [5432]:

3. In either case, you are prompted to confirm whether the database uses a secured connection. Provide a username and password for the newly configured database.

   Database secured connection (Yes, No) [No]: 
   Database name [engine]: 
   Database user [engine]: 
   Database password:

   Note

   Using a secured connection to the database requires you to have also manually configured secured database connections.