-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat Gluster Storage
Console Installation Guide
Installing Red Hat Storage Console
Red Hat Documentation Team
Abstract
Part I. Before you Begin
Chapter 1. Overview
- Support to quickly create and manage storage clusters and volumes.
- Multilevel administration to enable administration of physical infrastructure as well as administration of virtual objects.
1.1. System Components
- Red Hat Storage Console
- The Red Hat Storage Console is a centralized management system and is used to view and manage storage servers. Red Hat Storage Console features include search capabilities, resource management, and provisioning. The Red Hat Storage Console runs on Red Hat Enterprise Linux 6.5 and Red Hat Enterprise Linux 6.6.The console provides a graphical user interface (GUI) to administer the storage environment's physical and logical resources. The console manages provisioning, user sessions, and high availability / clustering.The Red Hat Storage Console exposes an Administration Portal and an Application Programming Interface (API).
- The Administration Portal is used for set up, configuration, and management tasks for the Red Hat Storage environment.
- The REST API is an interface used to automate manual user tasks. Scripts for the REST API can be written in any language that supports accessing HTTP and HTTPS resources.
1.2. Installation Workflow
Check System Requirements
- Install and configure the hardware requirements listed in Section 2.1, “Hardware Requirements”.
- Install and configure the software requirements listed in Section 2.3, “Software Requirements”.
Red Hat Storage Console Installation
- Install the Red Hat Storage Console. For details, see Chapter 3, Red Hat Storage Console Installation.
Chapter 2. System Requirements
Important
2.1. Hardware Requirements
- One machine to act as the management server
- One or more machines to act as storage servers. At least two machines are required to support replicated volumes.
- One or more machines to use as clients to access the Administration Portal.
2.1.1. Management Server Requirements
Minimum Requirements
- A dual core CPU.
- 4 GB of available system RAM that is not being consumed by existing processes.
- One Network Interface Card (NIC) with bandwidth of at least 1 Gbps.
Recommended Requirements
- A quad core CPU or multiple dual core CPUs.
- 16 GB of available system RAM that is not being consumed by existing processes.
- One Network Interface Card (NIC) with bandwidth of at least 1 Gbps.
- An out of band management card to manage and monitor the Red Hat Storage Console node even when the server is down.
2.2. Storage Server Requirements
Note
2.3. Software Requirements
Important
rhsc-setup
) supports the en_US.UTF-8
, en_US.utf8
, and en_US.utf-8
locales. Installing on a system without one of the supported locale values fails.
2.3.1. Red Hat Storage Console Operating System Requirements
Important
2.3.2. Red Hat Storage Console Client Requirements
- Mozilla Firefox 24 or later, on Red Hat Enterprise Linux is required to access the Administration Portal.
- Internet Explorer 9 or 10 on Microsoft Windows is required to access the Administration Portal. Use the desktop version, not the touchscreen version for Internet Explorer version 10.
2.3.3. Directory Services
admin
user configured. Use the domain management tool (rhsc-manage-domains
) to authenticate additional users by attaching directory service domains.
Note
2.3.4. Firewall Configuration
rhsc-setup
script to automatically set up the firewall rules required by Red Hat Storage Console. If a firewall configuration is previously implemented, skip this step and manually integrate the new and existing configurations.
Table 2.1. Red Hat Storage Console Firewall Requirements
Port(s) | Protocol | Source | Destination | Purpose |
---|---|---|---|---|
22 | TCP |
|
| SSH (optional) |
80, 443 | TCP |
|
| Provides HTTP and HTTPS access to the console. |
2.3.5. Directory Server Firewall Requirements
Table 2.2. Directory Firewall Requirements
Port(s) | Protocol | Source | Destination | Purpose |
---|---|---|---|---|
88, 464 | TCP, UDP | Red Hat Storage Console | Directory Server | Kerberos authentication |
389, 636 | TCP | Red Hat Storage Console | Directory Server | Lightweight Directory Access Protocol (LDAP) and LDAP over SSL |
2.3.6. Database Server Firewall Requirements
Table 2.3. Database Server Firewall Requirements
Port | Protocol | Source | Destination | Purpose |
---|---|---|---|---|
5432 | TCP, UDP | Red Hat Storage Console | PostgreSQL database server | Default port for PostgreSQL database connections. |
2.3.7. Red Hat Storage Server Firewall Requirements
Table 2.4. Server Firewall Requirements
Port | Protocol | Source | Destination | Purpose |
---|---|---|---|---|
22 | TCP | Red Hat Storage Console | Red Hat Storage Servers | Secure Shell (SSH) access. |
54321 | TCP | Red Hat Storage Console | Red Hat Storage Servers | VDSM communications with the Red Hat Storage Console. |
2.3.8. Red Hat Storage Console User Accounts and Groups
- The kvm group (GID 36) includes the vdsm user (UID 36)
- The ovirt group (GID 108) includes the ovirt user (UID108)
Part II. Installing Red Hat Storage Console
Chapter 3. Red Hat Storage Console Installation
3.1. Console Installation Overview
3.1.1. Prerequisites
- The firewall rules, if any, present on the system. The default option is to allow the Console's setup script to configure the firewall automatically; this overwrites any existing settings. To integrate the existing settings with the firewall rules required by the Console, you must configure the firewall manually. If you choose to manually configure the firewall, the setup script provides a custom list of ports that need to be opened, based on the options selected during setup.
- The fully qualified domain name (FQDN) of the system on which the Console is to be installed. The default value is the system's current host name. The FQDN must be reachable from all the Red Hat Storage Nodes.
- The password you use to secure the Red Hat Storage Console administration account.
- The location of the database server to be used as the Console database. You can use the setup script to install and configure a local database server; this is the default setting. Alternatively, use an existing remote database server. This database must be created before the Console is configured. To use a remote database server you must know:You must also know the name of the database, and the user name and password of a user that has permissions on the remote database server. The default name for both the database and the user is
- The host name of the system on which the remote database server exists.
- The port on which the remote database server is listening. The default port is 5432.
- That the
uuid-ossp
extension had been loaded by the remote database server.
redhat
. - The organization name to use when creating the Console's security certificates. The default value is an automatically-detected domain-based name.
3.1.2. Registering to Red Hat Network
Procedure 3.1. Registering with Subscription Manager using Command Line
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
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"
Attach Entitlement Pools to the System
Use the pool identifiers located in the previous step to attach theRed Hat Enterprise Linux Server
andRed Hat Storage Console
entitlements to the system. Run the following command to attach the entitlements:# subscription-manager attach --pool=[POOLID]
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
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
- 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. - 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
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
- 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.
- Run
rhn_register
command to register the system with the Red Hat Satellite. - 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
. - 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
- 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
3.1.3. Installing Red Hat Storage Console
Important
- Installing Red Hat Storage Console 3.0 on Red Hat Storage 3.0 is not supported.
- Set SELinux to permissive on the Nagios server.
- If you have existing installations of the technology preview version of the Red Hat Storage Console, you need to remove those installations and perform a fresh installation of the product. An upgrade from technical preview version is not supported.
Procedure 3.4. Installing the Red Hat Storage Console
- Use the
yum
command to enure that the most recent version of installed packages are in use.#
yum update
- Use
yum
to initiate the installation of the rhsc package and all the dependencies. You must run this command as theroot
user.#
yum install rhsc
3.1.4. Upgrading Red Hat Storage Console
- Configuring channels and entitlements.
- Updating the required packages.
- Performing the upgrade.
rhsc-setup
, which provides an interactive interface. While the upgrade is in process, Red Hat Storage hosts continue to operate independently. When the upgrade is complete, you can then upgrade your hosts to the latest versions of Red Hat Storage.
Important
3.1.4.1. Upgrades between Minor Releases
Procedure 3.5. Checking for Red Hat Storage Console Updates
- Run the following command on the machine on which the Red Hat Storage Console is installed:
# rhsc-upgrade-check
- If there are no updates are available, the command will output the text
No upgrade
:# rhsc-upgrade-check VERB: queue package rhsc-setup for update VERB: Building transaction VERB: Empty transaction VERB: Transaction Summary: No upgrade
- If updates are available, the command will list the packages to be updated:
# rhsc-upgrade-check VERB: queue package rhsc-setup for update VERB: Downloading: repomdoInTMztmp.xml (0%) VERB: Downloading: repomdoInTMztmp.xml 4.4 k(100%) VERB: Downloading: repomdhPVwA7tmp.xml (0%) VERB: Downloading: repomdhPVwA7tmp.xml 4.4 k(100%) VERB: Downloading: repomdvWktrFtmp.xml (0%) VERB: Downloading: repomdvWktrFtmp.xml 3.3 k(100%) VERB: Downloading: rhs-nagios-3-for-rhel-6-server-rpms/primary_db (0%) VERB: Downloading: rhs-nagios-3-for-rhel-6-server-rpms/primary_db 13 k(74%) VERB: Downloading: rhs-nagios-3-for-rhel-6-server-rpms/primary_db 18 k(100%) VERB: Downloading: repomds0eFt9tmp.xml (0%) VERB: Downloading: repomds0eFt9tmp.xml 2.8 k(100%) VERB: Downloading: repomdrL4fCttmp.xml (0%) VERB: Downloading: repomdrL4fCttmp.xml 3.3 k(100%) VERB: Downloading: rhsc-3-for-rhel-6-server-rpms/primary_db (0%) VERB: Downloading: rhsc-3-for-rhel-6-server-rpms/primary_db 9.1 k(55%) VERB: Downloading: rhsc-3-for-rhel-6-server-rpms/primary_db 16 k(100%) VERB: package rhsc-setup queued VERB: Building transaction VERB: Transaction built VERB: Transaction Summary: VERB: updated - otopi-1.1.2-1.el6ev.noarch VERB: update - otopi-1.2.0-1.el6ev.noarch VERB: updated - otopi-java-1.1.2-1.el6ev.noarch VERB: update - otopi-java-1.2.0-1.el6ev.noarch VERB: obsoleted - rhevm-setup-plugins-3.3.0-4.el6ev.noarch VERB: updated - rhsc-lib-2.1.2-0.40.el6rhs.noarch VERB: update - rhsc-lib-3.0.0-0.14.el6rhs.noarch VERB: updated - rhsc-setup-2.1.2-0.40.el6rhs.noarch VERB: update - rhsc-setup-3.0.0-0.14.el6rhs.noarch VERB: install - rhsc-setup-base-3.0.0-0.14.el6rhs.noarch VERB: install - rhsc-setup-plugin-ovirt-engine-3.0.0-0.14.el6rhs.noarch VERB: install - rhsc-setup-plugin-ovirt-engine-common-3.0.0-0.14.el6rhs.noarch VERB: obsoleting - rhsc-setup-plugins-3.0.0-0.2.el6rhs.noarch Upgrade available
Procedure 3.6. Updating Red Hat Storage Console
- Stopping the
ovirt-engine
service. - Downloading and installing the updated packages.
- Backing up and updating the database.
- Performing post-installation configuration.
- Starting the
ovirt-engine
service.
- Run the following command to update the rhsc-setup package:
# yum update rhsc-setup
- Run the following command to update the Red Hat Storage Console:
# rhsc-setup
- Run the following command to ensure that all packages are up to date:
# yum update
3.1.4.2. Upgrading Red Hat Storage Console 2.1 Update 4 to Red Hat Storage Console 3.0
Important
Procedure 3.7. Upgrading Red Hat Storage Console 2.1 Update 4 to Red Hat Storage Console 3.0 using Subscription Manager
- Verify the subscription status by running the following command:
# migrate-rhs-classic-to-rhsm --status
- Install the required packages using the following command:
# yum install subscription-manager-migration
- Execute the following command to migrate from Red Hat Network Classic to Red Hat Subscription Manager:
# migrate-rhs-classic-to-rhsm --rhn-to-rhsm
- To enable the Red Hat Storage Console 3.0 repositories, execute the following command:
# migrate-rhs-classic-to-rhsm --upgrade --version 3
- To verify if the migration from Red Hat Network Classic to Red Hat Subscription Manager is successful, execute the following command:
# migrate-rhs-classic-to-rhsm --status
- Run the following command to ensure that you have the most recent version of
rhsc-setup
by updating therhsc-setup
package:# yum update rhsc-setup
- Run the following command and follow the prompts to upgrade the Red Hat Storage Console:
# rhsc-setup
EnterYes
orNo
when prompted to select whether to enable or disable monitoring. - Remove or disable the Red Hat Storage Console 2.1 repositories to ensure that the system does not use any Red Hat Storage Console 2.1 packages using the following command:
# subscription-manager repos --disable=rhsc-2.1-for-rhel-6-server-rpms
- Run the following command to ensure all packages are up to date:
# yum update
Procedure 3.8. Upgrading Red Hat Storage Console 2.1 Update 4 to Red Hat Storage Console 3.0 using Red Hat Satellite Server
- Subscribe the system on which the Red Hat Storage Console is installed to the required channels for receiving Red Hat Storage Console 3.0 packages using the following command:
# rhn-channel --add --channel rhel-x86_64-server-6-rhs-rhsc-3 --channel rhel-x86_64-server-6-rhs-nagios-3
- Run the following command to ensure that you have the most recent version of
rhsc-setup
by updating therhsc-setup
package:# yum update rhsc-setup
- Run the following command and follow the prompts to upgrade the Red Hat Storage Console:
# rhsc-setup
EnterYes
orNo
when prompted to select whether to enable or disable monitoring. - Remove or disable the Red Hat Storage Console 2.1 channels to ensure that the system does not use any Red Hat Storage Console 2.1 packages using the following command:
# rhn-channel --remove --channel rhel-x86_64-server-6-rhs-rhsc-2.1
- Run the following command to ensure all packages are up to date:
# yum update
3.1.5. Post-Upgrade Tasks
Note
Procedure 3.9. Migrating Red Hat Storage Nodes
- Log in to the Administration Portal as the administrative user. By default this is the
admin
user. - Click the Hosts tab and select the desired host to display the Details pane.
- Click Maintenance and click OK to place the host in maintenance mode.
- 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.
- Click the Hosts tab and select the host to display General tab with the host details.
- Click here link in Action Items to reinstall the hosts.
- Enter the password for the Host in Install Host window and click OK.
Procedure 3.10. Changing the Cluster Compatibility Version
- Log in to the Administration Portal as the administrative user. By default this is the
admin
user. - Click the Clusters tab.
- 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.
- Click the Edit button.
- 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.
- Click OK to open the Change Cluster Compatibility Version confirmation window.
- Click OK to confirm.
3.1.6. Configuring Red Hat Storage Console
rhsc-setup
script is provided to assist with this task. The script asks you a series of questions, and configures the environment based on the answers. When required values are provided, the updated configuration is applied and the Red Hat Storage Console services are started. The rhsc-setup
script guides you through several distinct configuration stages. The script suggests possible configuration defaults in square brackets. No additional input is required wherever the default values are acceptable.
Procedure 3.11. Configuring the Console
- Execute
rhsc-setup
command#
rhsc-setup
- Packages CheckThe
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
- Network ConfigurationA 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
]:Therhsc-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.
- Database ConfigurationYou 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” - Set the administrator credentialsYou 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. - PKI ConfigurationThe 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
]: - Apache ConfigurationThe 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]:
- System ConfigurationThe
rhsc-setup
script by default uses the GlusterFS application mode and skips the NFS configuration.[ INFO ] NFS configuration skipped with application mode Gluster
Therhsc-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.Therhsc-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
Therhsc-setup
script prompts to confirm whether to enable or disable monitoring by enteringYes
orNo
For information on how to configure Nagios, see Configuring Nagios for Red Hat Storage Console in Red Hat Storage Console Administration GuideWould 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.
- SummaryWhen 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
, andRed 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.
- End of SummaryAt 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 therhsc-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. Therhsc-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
Runrhsc-setup
for a full list of parameters.--help
The Red Hat Storage Console is installed and configured. You can connect to the Administration Portal using the instructions in Section 3.1.8, “Connecting to the Administration Portal”.
Note
3.1.7. Removing Red Hat Storage Console
Warning
rhsc-cleanup
command removes all the existing Red Hat Storage Console data. This includes configuration settings, certificates, and database tables.
Procedure 3.12. Removing the Console
rhsc-cleanup
utility to allow quick and easy removal of the data files associated with the installation. After rhsc-cleanup
is run, you can remove the Red Hat Storage Console packages using yum
.
- Execute
rhsc-cleanup
on the system that Red Hat Storage Console is installed on. You must be logged in as the root user to runrhsc-cleanup
.# rhsc-cleanup
- 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. - 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. - You can safely uninstall the Red Hat Storage Console packages using
yum
.# yum remove rhsc*
Note
3.1.8. Connecting to the Administration Portal
- In a browser, navigate to https://<IP Address>/webadmin. Replace <IP Address> with the URL provided during installation.
- 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. - The portal log in screen displays. Enter
admin
as the User Name. Enter the password set during installation in the Password field. Select theinternal
domain from the Domain list.Click Login to log in.
3.1.9. Preparing a PostgreSQL Database Server for use with Red Hat Storage Console
posgresql
and postgresql-server
packages are installed.
rhsc-setup
utility.
Procedure 3.13. Preparing a PostgreSQL Database Server for use with Red Hat Storage Console
- Initialize the database and start the postgreSQL service by running the commands:
# service postgresql initdb # service postgresql start
- 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;
- 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. - 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. - Restart the
postgres
service. This step is required on both local and remote manually configured database servers.service postgresql restart
3.1.10. Configuring the Manager to use a Manually Configured Local or Remote PostgreSQL Database
# service postgresql initdb # service postgresql start
rhsc-setup
utility, you can opt to use a manually configured database. You can select to use a locally or remotely installed postgreSQL database.
Procedure 3.14. Configuring the Manager to use a Manually Configured Local or Remote PostgreSQL Database
- 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. - 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]:
- 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.
rhsc-setup
utility continues with the rest of the storage environment configuration.
Part III. Appendices
Appendix A. Additional Utilities
A.1. The Domain Management Tool
rhsc-manage-domains
. This command is only accessible from the machine on which Red Hat Storage Console is installed, and must be run as the root user.
A.1.1. Syntax of the Domain Management Tool
rhsc-manage-domains -action=ACTION [options]
rhsc-manage-domains
command's help output:
# rhsc-manage-domains --help
A.1.2. Adding Domains to a Configuration
rhsc-manage-domains
command is used to add the ActiveDirectory domain test.redhat.com
to the Red Hat Storage Console configuration. The configuration is set to use the administator user when querying the domain; the password is provided interactively.
Example A.1. rhsc-manage-domains Add Action
# rhsc-manage-domains -action=add -domain='test.redhat.com' -provider=ActiveDirectory -user='admin' -interactive Enter password: The domain test.redhat.com has been added to the engine as an authentication source but no users from that domain have been granted permissions within the oVirt Manager. Users from this domain can be granted permissions from the Web administration interface or by editing the domain using -action=edit and specifying -addPermissions. oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart). Manage Domains completed successfully
A.1.3. Editing a Domain in the Configuration
rhsc-manage-domains
command is used to edit the directory.test.redhat.com
domain in the Red Hat Storage Console configuration. The configuration is updated to use the administrator user when querying this domain; the password is provided interactively.
Example A.2. rhsc-manage-domains Edit Action
# rhsc-manage-domains -action=edit -domain='test.redhat.com' -provider=ActiveDirectory -interactive Enter password: oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart). Manage Domains completed successfully
A.1.4. Deleting a Domain from the Configuration
rhsc-manage-domains
command is used to remove the directory.test.redhat.com
domain from the Red Hat Storage Console configuration. Users defined in the removed domain will no longer be able to authenticate with the Red Hat Storage Console. The entries for the affected users will remain defined in the Red Hat Storage Console until they are explicitly removed.
Example A.3. rhsc-manage-domains Delete Action
# rhsc-manage-domains -action=delete -domain='test.redhat.com' WARNING: Domain test.redhat.com is the last domain in the configuration. After deleting it you will have to either add another domain, or to use the internal administrator user in order to login. Are you sure you like to delete domain test.redhat.com (yes/no) : yes Successfully deleted domain test.redhat.com. Please remove all users and groups of this domain using the Administration portal or the API. oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart). Manage Domains completed successfully
A.1.5. Validating a Domain Configuration
rhsc-manage-domains
command is used to validate the Red Hat Storage Console configuration. The command attempts to log into each listed domain with the credentials provided in the configuration. The domain is reported as valid if the attempt is successful.
Example A.4. rhsc-manage-domains Validate Action
# rhsc-manage-domains -action=validate Domain test.redhat.com is valid. The configured user for domain test.redhat.com is admin@TEST.REDHAT.COM Manage Domains completed successfully
A.1.6. Listing the Domains in a Configuration
rhsc-manage-domains
command is used to list the domains defined in the Red Hat Storage Console configuration. For each configuration entry, the command displays the domain, the user name - in User Principle Name (UPN) format - and whether the domain is local or remote.
Example A.5. rhsc-manage-domains List Action
# rhsc-manage-domains -action=list Domain: test.redhat.com User name: admin@TEST.REDHAT.COM Manage Domains completed successfully
Appendix B. Revision History
Revision History | |||
---|---|---|---|
Revision 3-34 | Thu Mar 26 2015 | Divya Muntimadugu | |
| |||
Revision 3-33 | Wed Feb 18 2015 | Shalaka Harne | |
| |||
Revision 3-32 | Wed Jan 07 2015 | Shalaka Harne | |
| |||
Revision 3-28 | Mon Nov 03 2014 | Shalaka Harne | |
|