Console Installation Guide
Installing Red Hat Gluster Storage Console
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 Gluster Storage Console
- The Red Hat Gluster Storage Console is a centralized management system and is used to view and manage storage servers. Red Hat Gluster Storage Console features include search capabilities, resource management, and provisioning. The Red Hat Gluster Storage Console runs on Red Hat Enterprise Linux 6.x systems.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 Gluster 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 Gluster 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
Red Hat Gluster Storage Console Installation
- Install the Red Hat Gluster Storage Console. For details, see Part II, “Installing Red Hat Gluster Storage Console”.
Chapter 2. System Requirements
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 be used as clients to access the Administration Portal.
2.1.1. Management Server 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.
- 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 Gluster Storage Console node even when the server is down.
2.2. Storage Server Requirements
2.3. Software Requirements
rhsc-setup) supports the
en_US.utf-8locales. Installing on a system without one of the supported locale values fails.
2.3.1. Red Hat Gluster Storage Console Operating System Requirements
2.3.2. Red Hat Gluster 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
adminuser configured. Use the domain management tool (
rhsc-manage-domains) to authenticate additional users by attaching directory service domains.
2.3.4. Firewall Configuration
rhsc-setupscript to automatically set up the firewall rules required by Red Hat Gluster Storage Console. If a firewall is already configured, manually integrate the existing configuration with the Red Hat Gluster Storage requirements in this section.
iptablescommand to open a port:
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 5667 -j ACCEPT # service iptables save
# firewall-cmd --zone=zone_name --add-service=glusterfs # firewall-cmd --zone=zone_name --add-service=glusterfs --permanent
# firewall-cmd --zone=public --add-port=5667/tcp # firewall-cmd --zone=public --add-port=5667/tcp --permanent
Table 2.1. Red Hat Gluster Storage Console Firewall Requirements
|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
|88, 464||TCP, UDP||Red Hat Gluster Storage Console||Directory Server||Kerberos authentication|
|389, 636||TCP||Red Hat Gluster 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
|5432||TCP, UDP||Red Hat Gluster Storage Console||PostgreSQL database server||Default port for PostgreSQL database connections.|
2.3.7. Red Hat Gluster Storage Server Firewall Requirements
Table 2.4. Server Firewall Requirements
|22||TCP||Red Hat Gluster Storage Console||Red Hat Gluster Storage Servers||Secure Shell (SSH) access.|
|54321||TCP||Red Hat Gluster Storage Console||Red Hat Gluster Storage Servers||VDSM communications with the Red Hat Gluster Storage Console.|
2.3.8. Red Hat Gluster 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 Gluster Storage Console
- Online installation
- Install Red Hat Gluster Storage Console on a system that can access the internet to download installation packages.
- Offline installation
- Install Red Hat Gluster Storage Console on a system that cannot access the internet.
rhsc-setupscript. See Chapter 6, Automating configuration for details.
Chapter 3. 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 Gluster Storage Nodes.
- The password you use to secure the Red Hat Gluster 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-osspextension had been loaded by the remote database server.
- The organization name to use when creating the Console's security certificates. The default value is an automatically-detected domain-based name.
Chapter 4. Installing the console from packages
- Register your system so that it can download the packages required for installation.
- Install the Red Hat Gluster Storage Console packages.
- Run the setup script.
- Connect your storage servers to the console.
4.1. Registering to Red Hat Network
Procedure 4.1. Registering with Subscription Manager using Command Line
Register the System with Subscription ManagerRun 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 PoolsRun the following commands to find entitlement pools containing the repositories required to install the Red Hat Gluster Storage Console:
# subscription-manager list --available | grep -A8 "Red Hat Enterprise Linux Server" # subscription-manager list --available | grep -A8 "Red Hat Gluster Storage"
Attach Entitlement Pools to the SystemUse the pool identifiers located in the previous step to attach the
Red Hat Enterprise Linux Serverand
Red Hat Gluster Storage Consoleentitlements to the system. Run the following command to attach the entitlements:
# subscription-manager attach --pool=[POOLID]
Enable the Required RepositoriesRun the following commands to enable the repositories required to install Red Hat Gluster 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 enabledRun the following command to verify if the repositories are enabled:
# yum repolist
Procedure 4.2. Registering with Subscription Manager using GUI
Verify if the Repositories are enabledRun the following command to verify if the repositories are enabled:
# yum repolist
Procedure 4.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.
rhn_registercommand 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
- Run the following command to subscribe the system to the required Red Hat Gluster 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
4.2. Installing Red Hat Gluster Storage Console
- Installing Red Hat Gluster Storage Console 3.x on Red Hat Gluster Storage 3.x is not supported.
- Installing Red Hat Gluster Storage Console on Red Hat Enterprise Linux 7.x is not supported.
Procedure 4.4. Installing Red Hat Gluster Storage Console
- Use the
yumcommand to ensure that the most recent version of installed packages are in use.
yumto initiate the installation of the
rhscpackage and all the dependencies. You must run this command as the
yum install rhsc
4.3. Configuring Red Hat Gluster Storage Console
rhsc-setupscript 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 Gluster Storage Console services are started. The
rhsc-setupscript 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 4.5. Configuring the Console
Start console setup
rhsc-setupThe script then checks whether it is performing an upgrade or an installation before proceeding.
Checking for product updates... No product updates found
Check hostname configurationThe
rhsc-setupscript automatically detects the hostname. Correct the detected hostname if required. 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]:
rhsc-setupscript 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.
Configure databaseYou 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]: AutomaticFor information on how to prepare a PostgreSQL database, see Chapter 8, Use a PostgreSQL Database Server with Red Hat Gluster Storage Console
Configure administrator credentialsYou need to set an administrator password for the automatically created administrative user of the Red Hat Gluster 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.
Configure certificatesThe 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]:
Configure web serverThe 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]: AutomaticThe Red Hat Gluster Storage Console uses the Apache web server to present a landing page to users.
rhsc-setupscript 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]:
Configure console settingsThe
rhsc-setupscript by default uses the GlusterFS application mode and skips the NFS configuration.
[ INFO ] NFS configuration skipped with application mode GlusterThe
rhsc-setupscript 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-setupscript 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 Red Hat Gluster Storage Console to be brokered through a proxy server? (Yes, No) [No]: NoThe
rhsc-setupscript prompts to confirm whether to enable or disable monitoring by entering
NoFor information on how to configure Nagios, see Configuring Nagios for Red Hat Gluster Storage Console in Red Hat Gluster Storage Console 3.4 Administration Guide
Would you like external monitoring to be enabled? (Yes, No) [Yes]:
--== CONFIGURATION PREVIEW ==-- Application mode : gluster Firewall manager : iptables Update Firewall : True Host FQDN : rhsc.example.com 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 Engine installation : True PKI organization : redhat 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
OKand 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.
Confirm 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, and
Red Hat Gluster Storage Console URLfor later reference.
--== SUMMARY ==-- [ INFO ] To enable monitoring, ensure the managed nodes are migrated to Red Hat Gluster Storage 3.4. Also make sure the auto discovery tool is executed to start monitoring the Red Hat Gluster Storage Nodes, after the cluster nodes are added to Red Hat Gluster Storage Console. For detail, refer to Red Hat Gluster Storage Console 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. [ INFO ] To enable monitoring, ensure that the managed nodes are migrated to Red Hat Gluster Storage 3.0 or above. Also ensure that the auto-discovery command (configure-gluster-nagios) is executed to start monitoring the Red Hat Gluster Storage Nodes after the nodes are added to Red Hat Gluster Storage Console. For more details, refer Red Hat Gluster Storage Console Administration Guide. [WARNING] Less than 16384MB of memory is available Engine database resources: Database name: Database user name: 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 loginAt this stage, the engine service and httpd 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-20150722181911-5zsqnr.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20150722182856-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of setup completed successfully
The Red Hat Gluster Storage Console is installed and configured. You can connect to the Administration Portal using the instructions in Chapter 7, Connecting to the Administration Portal.
4.3.1. Enabling SELinux
- If Nagios server is installed on the Console node, set the following boolean:
# setsebool -P nagios_run_sudo on
- Set the following booleans on Red Hat Gluster Storage node for Nagois to function:
# setsebool -P nagios_run_sudo on # setsebool -P logging_syslogd_run_nagios_plugins on
Chapter 5. Installing the console from the virtual appliance
5.1. Installing the virtual appliance on a virtual machine
- Obtain the Red Hat Gluster Storage Console Appliance and upload it to Red Hat Virtualization Management.
- Create a virtual machine to act as a server for Red Hat Gluster Storage Console, using the Red Hat Gluster Storage Console Appliance OVA file as a template.
- Boot the new virtual machine and run the setup script.
5.1.1. Before you begin
5.1.2. Install Red Hat Gluster Storage Console on a RHV-M virtual machine
Procedure 5.1. Uploading the appliance into Red Hat Virtualization Manager
Download the appliance
- Log on to the Red Hat Customer Portal (http://access.redhat.com/).
- Click onto go to Software and Download Center.
- Clickto go to Download Red Hat Gluster Storage.
- Set the Product Variant to
Red Hat Gluster Storage Management Console (for RHEL Server).
- Set the Version to the appropriate version. The appliance is available in version 3.1 or later.
- Click on Download Now beside the appropriate version of Red Hat Gluster Gluster Storage Console Appliance to download the appliance OVA file.
Upload the appliance to RHV-MUpload the appliance OVA file from
/path/to/appliance.ovato a Red Hat Virtualization Manager storage domain.
# ovirt-image-uploader -n appliance_name -e rhvm_storage_domain upload /path/to/appliance.ovaEnter the REST API password for the Red Hat Virtualization Manager administrative user (
admin@internal) when prompted.
Procedure 5.2. Creating a virtual machine with the appliance template
Start creating a new virtual machineLog in to the Red Hat Virtualization Manager interface and navigate to the Virtual Machines tab in the navigation pane.Click New VM to start the creation process.
Use the appliance as a templateFollow the prompts, ensuring that you select appliance_name in the Based on Template drop-down menu.
Procedure 5.3. Configuring the console appliance virtual machine
Ensure spice-xpi is installedEnsure that spice-xpi is installed on your local system so that you can view the console of your new virtual machine.
Start the new virtual machineWhen your new virtual machine is finished installing, start the virtual machine.
Configure the new virtual machineOpen the console of your new virtual machine. Run the
rhsc-setupcommand and follow the prompts to complete setup of Red Hat Gluster Storage.By default,
rhsc-setupruns in the online mode. This requires registration to Red Hat Network channels or repositories. Follow the steps in Section 4.1, “Registering to Red Hat Network” to register with Red Hat Network and subscribe to the appropriate channels and repositories.If your system has limited connectivity, or you don't want to configure repositories now, you can run this command in the offline mode:
# rhsc-setup --offlineIf you are configuring a number of machines the same way, you can also use the
--config-appendparameter to use a pre-configured answers file.When setup is complete, you can follow the normal process of setting up bricks, volumes, and trusted storage pools. If you set up in offline mode, you can also optionally register Red Hat Gluster Storage Console for updates by following the instructions in Section 4.1, “Registering to Red Hat Network”.
Chapter 6. Automating configuration
rhsc-setupscript with an answer file. An answer file contains answers to the questions asked by the
- To create an answer file, use the
--generate-answerparameter 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-appendparameter to specify the path and file name of the answer file to be used. The
rhsc-setupcommand 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.
rhsc-setupfor a full list of parameters.
Chapter 7. Connecting to the Administration Portal
- In a browser, navigate to https://<IP Address>/ovirt-engine. Replace <IP Address> with the URL provided during installation.
- When initially connecting to the Administration Portal, a prompt appears asking if the
ca.cercertificate 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
adminas the User Name. Enter the password set during installation in the Password field. Select the
internaldomain from the Domain list.Clickto log in.
Chapter 8. Use a PostgreSQL Database Server with Red Hat Gluster Storage Console
postgresql-serverpackages are installed.
Procedure 8.1. Manually Preparing a PostgreSQL Database Server for use with Red Hat Gluster 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 Gluster 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.conffile, and add this line:
host all all X.X.X.X/24 trustReplace 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.conffile, and add this line:
listen_addresses='*' port = 5432This 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
postgresservice. This step is required on both local and remote manually configured database servers.
service postgresql restart
Procedure 8.2. Configuring the Manager to use a Manually Configured Local or Remote PostgreSQL Database
- During the Red Hat Gluster Storage Console installation using the
rhsc-setuputility, 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 Gluster 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-setuputility with the hostname of the database server and the port it is listening on.
Database host [localhost]: Database port :
- 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:
NoteUsing a secured connection to the database requires you to have also manually configured secured database connections.
rhsc-setuputility continues with the rest of the storage environment configuration.
Chapter 9. Upgrading Red Hat Gluster 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 Gluster Storage hosts continue to operate independently. When the upgrade is complete, you can then upgrade your hosts to the latest versions of Red Hat Gluster Storage.
9.1. Upgrades between Minor Releases
Procedure 9.1. Checking for Red Hat Gluster Storage Console Updates
- Run the following command on the machine on which the Red Hat Gluster Storage Console is installed:
- If there are no updates are available, the command will output the text
# 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.2.3-1.el6ev.noarch VERB: update - otopi-1.4.0-0.0.1.master.el6ev.noarch VERB: updated - otopi-java-1.2.3-1.el6ev.noarch VERB: update - otopi-java-1.4.0-0.0.1.master.el6ev.noarch VERB: updated - rhsc-lib-3.0.4-1.25.el6rhs.noarch VERB: update - rhsc-lib-3.1.0-0.62.el6.noarch VERB: updated - rhsc-setup-3.0.4-1.25.el6rhs.noarch VERB: update - rhsc-setup-3.1.0-0.62.el6.noarch VERB: updated - rhsc-setup-base-3.0.4-1.25.el6rhs.noarch VERB: update - rhsc-setup-base-3.1.0-0.62.el6.noarch VERB: updated - rhsc-setup-plugin-ovirt-engine-3.0.4-1.25.el6rhs.noarch VERB: update - rhsc-setup-plugin-ovirt-engine-3.1.0-0.62.el6.noarch VERB: updated - rhsc-setup-plugin-ovirt-engine-common-3.0.4-1.25.el6rhs.noarch VERB: update - rhsc-setup-plugin-ovirt-engine-common-3.1.0-0.62.el6.noarch VERB: updated - rhsc-setup-plugins-3.0.4-1.2.el6rhs.noarch VERB: update - rhsc-setup-plugins-3.1.0-3.el6rhs.noarch Upgrade available
Procedure 9.2. Updating Red Hat Gluster Storage Console
- Stopping the
- Downloading and installing the updated packages.
- Backing up and updating the database.
- Performing post-installation configuration.
- Starting the
- Run the following command to update the
# yum update rhsc-setup
- Run the following command to update the Red Hat Gluster Storage Console:
- Run the following command to ensure that all packages are up to date:
# yum updateIf this includes updates to the Nagios plugin (nagios-server-addons), re-run the Nagios configuration command to ensure it is correctly configured after upgrade.
9.2. Post-Upgrade Tasks
Procedure 9.3. Migrating Red Hat Gluster Storage Nodes
- Log in to the Administration Portal as the administrative user. By default this is the
- Click the Hosts tab and select the desired host to display the Details pane.
- Click Maintenance and to place the host in maintenance mode.
- Upgrade the Red Hat Gluster Storage nodes.For more information, refer section Upgrading from Red Hat Gluster Storage 2.1 Update 4 to Red Hat Gluster Storage 3.0 using yum in Red Hat Gluster Storage 3 Administration Guide.
- Click Edit and change the protocol to JSON by checking the Use JSON Protocol checkbox.
- On the Hosts tab, click Reinstall to reinstall the hosts.
- Enter the password for the Host in Install Host window and click OK.
Procedure 9.4. Changing the Cluster Compatibility Version
- Log in to the Administration Portal as the administrative user. By default this is the
- 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 thebutton.
- Change the Compatibility Version to the desired value.For more information on the Cluster compatibility version, refer Cluster Properties section in Red Hat Gluster Storage Console Administration Guide.
- Click Change Cluster Compatibility Version confirmation window.to open the
- Clickto confirm.
Chapter 10. Removing Red Hat Gluster Storage Console
rhsc-cleanupcommand removes all the existing Red Hat Gluster Storage Console data. This includes configuration settings, certificates, and database tables.
Procedure 10.1. Removing the Console
rhsc-cleanuputility to allow quick and easy removal of the data files associated with the installation. After
rhsc-cleanupis run, you can remove the Red Hat Gluster Storage Console packages using
rhsc-cleanupon the system that Red Hat Gluster Storage Console is installed on. You must be logged in as the root user to run
- Confirm that you want to remove all of the Red Hat Gluster 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
NoteA 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 Gluster Storage Console. If you choose to proceed, the
ovirt-engineservice 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]: OKThe configuration files of the environment are removed.
- You can safely uninstall the Red Hat Gluster Storage Console packages using
# yum remove rhsc*
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 Gluster 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-domainscommand's help output:
# rhsc-manage-domains --help
A.1.2. Adding Domains to a Configuration
rhsc-manage-domainscommand is used to add the ActiveDirectory domain
test.redhat.comto the Red Hat Gluster Storage Console configuration. The configuration is set to use the administrator 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-domainscommand is used to edit the
directory.test.redhat.comdomain in the Red Hat Gluster 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-domainscommand is used to remove the
directory.test.redhat.comdomain from the Red Hat Gluster Storage Console configuration. Users defined in the removed domain will no longer be able to authenticate with the Red Hat Gluster Storage Console. The entries for the affected users will remain defined in the Red Hat Gluster 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-domainscommand is used to validate the Red Hat Gluster 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-domainscommand is used to list the domains defined in the Red Hat Gluster 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 3.4-1||Tue Sep 04 2018|