Escolar Documentos
Profissional Documentos
Cultura Documentos
This guide provides detailed instructions for the IBM Spectrum Scale GUI installation process.
Contact:
gpfs@de.ibm.com
1 Product Introduction.................................................................................................................................. 4
2 Functional Scope of the Beta.................................................................................................................... 5
3 Known GA Product Limitations................................................................................................................. 7
4 Known Issues & Work Arounds with the Beta delivery..............................................................................8
5 Installation Overview............................................................................................................................... 10
6 Installation Prerequisites......................................................................................................................... 10
Operating System requirements.............................................................................................................10
IBM Spectrum Scale Installation and configuration................................................................................10
YUM Repository Setup............................................................................................................................11
NTP Setup...............................................................................................................................................11
7 Packaging Overview and Extraction....................................................................................................... 12
8 GUI Login................................................................................................................................................ 20
9 Using the GUI......................................................................................................................................... 21
IBM Spectrum Scale GUI -Overview Mode ........................................................................................21
10 Using the Performance monitoring and the GUI...................................................................................23
11 Additional Notes.................................................................................................................................... 24
12 Active Directory setup for the GUI......................................................................................................... 25
Modifying the GUI servers server.xml.................................................................................................25
Disabling the internal user repository.................................................................................................25
Adding the LDAP/AD feature to WebSphere Liberty..........................................................................25
Configuring the LDAP/AD repository using the <ldapRegistry> element...........................................25
Specifying the LDAP group to GUI role mapping...............................................................................27
Viewing and modifying existing group to role mappings....................................................................27
Creating a group to role mapping for initial access............................................................................27
13 Configuring further group to role mappings using the Spectrum Scale GUI.........................................28
Troubleshooting................................................................................................................................ .31
Configure tracing.............................................................................................................................. .31
14 Generating a trusted SSL certificate for secure browsing .................................................................32
15 Appendix: Protocol (CES) node installation .........................................................................................34
16 Browser Support Statement.................................................................................................................. 35
17 Glossary................................................................................................................................................ 36
1 Product Introduction
IBM Spectrum Scale GUI Beta and Open Beta version 4.2.1-beta* ( * the actual version number starting with 2)
delivery includes the Beta version of the IBM General Parallel File System (IBM Spectrum Scale) GUI version
which is an alternative management tool instead of using IBM Spectrum Scale CLI commands of the Advanced
edition of the IBM Spectrum Scale product.
The purpose for this beta is to get early feedback from you:
-
Whether the GUI helps you to achieve management and monitoring tasks.
Whether the features and functions of the GUI are easy and intuitive to use.
If you are interested in testing the beta version of the GUI, the GUI node has to run RHEL7.x or SLES12 as the
operating system on Power ppc64 (Big or Little Endian) or Intel X86_64. Although the other nodes in the IBM
Spectrum Scale cluster could be on other platforms and operating systems.
Note that like IBM Spectrum Scale, the GUI serving functionality is also delivered (only) as software. The intent of
the functionality is to provide access to data managed by IBM Spectrum Scale via additional access methods.
The management of IBM Spectrum Scale serving functions in the Beta release is using the CLI installed with a base
IBM Spectrum Scale installation. The use of most of these CLI commands will require root/administrative access
but in the GUI we have role based access for use of the GUI. To some extend the CLI support
Delivery model
Customer provides a Spectrum Scale cluster with minimum release level>=4.1.0
This cluster might be a production or an evaluation cluster
Customer provides a dedicated node to install and run the GUI
This node needs to run Spectrum Scale 4.1.0-8 or 4.1.1-1 or 4.2.-beta or 4.2.0.0 on RHEL 7.x or
SLES12. Best is the latest GA version 4.2.0-1
Customer is responsible to obtain licenses for all Spectrum Scale nodes
No additional license is required for the GUI itself
Performance Tool as monitoring tool is part of the GUI rpm and will be installed by the this rpm with the rpm install
commands but the Performance Tool Sensors and Collectors are separated rpm files which needs to be installed.
Earlier Beta program customers just need to update the GUI rpm and the Performance Tool Collector rpm files, the
sensors collecting the performance data do not need to be updated.
Customers who have a Base IBM Spectrum Scale 4.2.0.0 installed may stay on this version but will face some issues
not fixed with this release.
We seek feedback from Beta customers on the functions described in the following section and also would like to
learn which aspects of your workload work as expected in this delivery and what enhancements you would like to
see in the future.
Performance Tool Sensor and Collector rpm files (separate rpm files)
Management of object accounts, containers, users and roles ( with a later code patch )
Monitoring
Monitor capacity of file systems, file sets, user and group quotas
Display the protocol states for NFS and CIFS and Object
Other
Integrated contextual help for all menu items and link to the IBM Spectrum Scale Knowledge Center for
advanced help
Description
Comments
The current testing was done only on for 1024 (1K) node
systems within IBM and so the test statement is we can
only support a cluster with 1024 nodes and provide no
warranty if you use the GUI with more nodes.
Snapshot deletion period is Actually the snapshot deletion happens once a day at 02:30 Under discussion if more
1 in 24 hours only.
in the night to prevent the bad impact on the performance often snapshots should be
of the cluster. Due to this limitation it is possible that there deleted.
is discrepancy between number of snapshots present on the
system and the number that should remain according to
the snapshot retention rules.
The Cancel button is only displayed once you have at least one dashboard defined. On initial
display you are required to define a new dashboard.
A summary of the changes:
- multiple dashboards can be created, all of them will be visible to all users
5 Installation Overview
The steps of the installation are listed here to provide an overview how to setup the GUI and some related
components so the system works well.
Make sure the cluster is healthy and all prerequisites are installed. You can use a platform specific installer or direct
rpm installation.
The GUI uses the IBM Java version 8 and IBM Websphere Liberty 8.5.5.7 but both are included in the GUI rpm.
6 Installation Prerequisites
This section describes the installation prerequisites that must be met to use the installation toolkit.
We depend on the postgre server pre-installed. We use the postgresql-server-9.4.1201 version we access with a
jdbc driver. If you use the YUM installation commands the dependency is automatically resolved by YUM. If you
use the rpm based installation you must take care by yourself if it is installed.
The Performance Collector must be installed on the GUI node as the GUI accesses it using the localhost
configuration by default.
IBM Spectrum Scale 4.2 must be installed to use the full range of capabilities.
The IBM Spectrum Scale Installation takes care for the Spectrum Scale and Performance Tool installation but maybe
not for the Postgres database installation.
functions does not work. To use the GUI with all features use the cli to create a FS if not done before and mount it or
mount it later after logged in to the GUI on the FS view.
This is the preferred way of installation as YUM checks the dependencies and automatically installs missing
platform dependencies like the postgres module we do not ship but require.
How to setup the GUI with YUM you see in chapter 7.
NTP Setup
It is recommended that Network Time Protocol (NTP) be configured on all nodes in your system to ensure that all of
the nodes clocks are synchronized. Clocks that are not synchronized will cause debugging issues and authentication
problems with the protocols. Here is an example of enabling NTP on a node. We suggest to setup a Linux NTP
server as described here. Another OS was not tested if that works.
10
1)
2)
3)
Update the ntp.conf on any server before the NTP daemon is enabled.Refer to the man
page for details about the configuration. You find it usually at /etc/ntp.conf.
4)
5)
6)
# timedatectl list-timezones
7)
# timedatectl set-timezone
8)
IIBM Spectrum Scale GUI rpm including IBM Websphere Liberty Profile and IBM Java 8 JRE.
The Performance Tool Collector rpm ( only on collector nodes / gui nodes)
SLES12 x86
gpfs.gui-4.2.0_beta-2.sles12.x86_64.rpm (X is the
counter for the latest version starting with 1)
gpfs.gui-4.2.0_beta-2.sles12.ppc64le.rpm (X is the
counter for the latest version starting with 1)
gpfs.gss.pmcollector-4.2.0-1.el7.x86_64.rpm
gpfs.gss.pmsensors-4.2.0-1 .el7.x86_64.rpm
gpfs.gss.pmcollector-4.2.0-1 .el7.ppc64.rpm
gpfs.gss.pmsensors-4.2.0-1 .el7.ppc64.rpm
11
gpfs.gss.pmcollector-4.2.0-1 .el7.ppc64le.rpm
gpfs.gss.pmsensors-4.2.0-1 .el7.ppc64le.rpm
SLES12 X86
gpfs.gss.pmcollector-4.2.0-1 .SLES12.x86_64.rpm
gpfs.gss.pmsensors-4.2.0-1 .SLES12.X86_64.rpm
SLES12 ppc64
gpfs.gss.pmcollector-4.2.0-1 .SLES12.ppc64.rpm
gpfs.gss.pmsensors-4.2.0-1 .SLES12.ppc64.rpm
SLES12 ppc64 LE
gpfs.gss.pmcollector-4.2.0-1 .SLES12.ppc64le.rpm
gpfs.gss.pmsensors-4.2.0-1 .SLES12.ppc64le.rpm
gpfs.gss.pmsensors-4.2.0-1 .SLES11.ppc64.rpm
gpfs.gss.pmsensors_4.2.0-1 .U14.04_amd64.deb
gpfs.gss.pmsensors_4.2.0-1 .U12.04_amd64.deb
gpfs.gss.pmsensors_4.2.0-1 .D7.6_amd64.deb
gpfs.gss.pmsensors_4.2.0-1 .D6.0.10_amd64.deb
The rpm files should be placed on the node that will run the installation. Only the ones for the specific
platform are needed.
12
1. Ensure that the prerequisites defined in Installation Prerequisites section are satisfied.
2. Obtain the rpm files and place it in a node that will be used for the installation. The node can be part
of your IBM Spectrum Scale cluster or IBM Spectrum Scale client node of the cluster.
3. Make sure the Performance Tool Collector runs on the same node as the GUI.
4. Installation
The preferred way to install the performance tool changed with the GA version of Spectrum Scale 4.2.0. The big
advantage is especially on larger systems that the installer takes care about the distribution to all nodes on RHEL7.
On RHEL 6 and SLES you can use the mmperfmon command to install and configure the the performance tool as
well. But there is a packaging issue on the GA version of Spectrum Scale 4.2.0 so you need to manually install the
RHEL 6 libraries for the pmsensors file.
You can also manually install the rpm files but must run the commands on all nodes you want to monitor or to be a
collector node. The GUI can run on up to 3 nodes must have a performance collector installed locally. The following
commands will install the pmsensors on each node in your cluster. The sensor configuration file will get stored in
the Spectrum Scale back-end.
13
RHEL
rpm -ivh gpfs.gss.pmsensors-4.2.0-1.el7.<arch>.rpm
rpm -ivh gpfs.gss.pmcollector-4.21.1-2.el7.<arch>.rpm
rpm -ivh gpfs.gui-4.2-0.el7.<arch>.rpm
SLES
zypper -ivh gpfs.gss.pmsensors-4.2.0-1.SLES12.<arch>.rpm
zypper -ivh gpfs.gss.pmcollector-4.2.0-1.SLES12.<arch>.rpm
zypper -ivh gpfs.gui-4.2.1_beta-2.el7.<arch>.rpm
The sensor rpm must be installed on any additional node you want to monitor. All senors must point to the
Collector node.
5. Installation adjustments
The Performance Tool is installed into /opt/IBM/zimon.
If you upgrade-only but you want to clean up the old collector data you must stop the collector service
and remove the /data directory under opt/IBM/zimon and start the pmcollector service again.
If you upgrade-only but you want to clean up the old collector data you must stop the collector service and run
following commands.
The Zimon configuration can be removed from the system. You have to remove the rpm files and cleanup the
configuration.
call
call
14
6. Initialization
The following command starts the Performance Tool if it is already correctly configured (must be done first):
systemctl start pmcollector ( only on the collector node or nodes)
systemctl start pmsensors ( on all sensor nodes)
f you have not configured the performance tool on your cluster so far you might encounter the message that the
service was not found.
To resolve this problem, first configure the GPFS cluster for the performance tool using the mmperfmon GPFS
command is described before. This step requires that the set of collector nodes is provided (insert their hostname or
IP address instead of [COLLECTOR_NODE_NAMES]):
mmperfmon config generate --collectors [COLLECTOR_NODE_NAMES]
Then enable the sensors on the cluster using the "mmchmode command. This will configure and start the
Performance Tool sensors on the given nodes (make sure pmsensors is already installed on all sensor nodes!):
15
[SENSOR_NODE_LIST] is a comma separated list of the sensor nodes hostnames or IP addresses without any
spaces between them.
In case this does not work, you can manually configure the performance tools sensor nodes by editing the file :
/opt/IBM/zimon/ZIMonSensors.cfg on all sensor nodes. Add the host name or IP address of the node running the
collector in this section:
collectors = {
host = "[HOSTNAME or IP ADDRESS]"
port = "4739"
}
This specifies the collector to which the sensor is reporting. Then try starting the sensor on every sensor node again
with:
To make sure the GUI and Performance Tool gets started on boot, run this command to enable it:
systemctl enable gpfsgui.service
systemctl enable pmsensor.service
systemctl enable pmcollector.service
16
You can also check if the Performance Tool backend can receive data by using the GUI or alternative by
using a Performance Tool command line tool called zc located in /opt/IBM/zimon
Usage:
echo "get metrics mem_active, cpu_idle, gpfs_ns_read_ops last 10 bucket_size 1" | ./zc 127.0.0.1
Result example:
1:
server-21.localnet.com|Memory|mem_active
2:
server-22.localnet.com|Memory|mem_active
3:
server-23.localnet.com|Memory|mem_active
4:
server-21.localnet.com|CPU|cpu_idle
5:
server-22.localnet.com|CPU|cpu_idle
6:
server-23.localnet.com|CPU|cpu_idle
7:
server-21.localnet.com|GPFSNode|gpfs_ns_read_ops
8:
server-22.localnet.com|GPFSNode|gpfs_ns_read_ops
9:
server-23.localnet.com|GPFSNode|gpfs_ns_read_ops
Row Timestamp
mem_active
mem_active mem_active
cpu_idle
cpu_idle
cpu_idle
gpfs_ns_read_ops
gpfs_ns_read_ops gpfs_ns_read_ops
1
2015-05-20 18:16:33 756424 686420 382672 99.000000
100.000000 95.980000
0
0
2
2015-05-20 18:16:34 756424 686420 382672 100.000000 100.000000 99.500000
0
0
3
2015-05-20 18:16:35 756424 686420 382672 100.000000 99.500000
100.000000
0
6
4
2015-05-20 18:16:36 756424 686420 382672 99.500000
100.000000 100.000000
0
0
17
0
0
0
0
5
0
6
0
7
0
8
0
9
0
10
0
18
2015-05-20 18:16:37
0
2015-05-20 18:16:38
0
2015-05-20 18:16:39
0
2015-05-20 18:16:40
0
2015-05-20 18:16:41
0
2015-05-20 18:16:42
0
98.510000
100.000000
100.000000
96.520000
100.000000
52.760000
52.760000
100.000000
69.000000
100.000000
100.000000
100.000000
8 GUI Login
To access the GUI, open your web-browser and enter "https://<server-url>". You should get the login page below.
The default account is "admin/admin001". You should change it after you logged in when you run in production or
more users share the access. Before you log-in we will show a message that the GUI is initialized. At the first time
this takes some time.
19
From here you can move to the menu and select an alternate sub menu ore menu item.
20
Each menu item typically contains a link to the contextual help which provides you some additional help
information for the selected operation. This can be a link in some of the widgets or the round button in the upper
right corner of the menu bar (see the next screen-shot).
Picture which shows the mentioned button:
21
A help menu for the performance monitoring you can find in the contextual help of the GUI or in the IBM
Knowledge Center.
https://www01.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.ins.doc/bl1ins_introtogui.htm?
lang=en
The GUI integrates different metrics to monitor the performance of file systems and block storage.
The performance tool charting area allows panning (click and drag the chart or the time-line control at the bottom)
and zooming (mouse wheel or resizing the time-line control). Two charts can be displayed side by side, in order to
compare different objects/metrics or different time periods of the same chart. More details you find in the contextual
help for this topic.
A list of available sensors you find only in the IBM Knowledge Center:
https://www01.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.adv.doc/bl1adv_listofmetricsP
MT.htm?lang=en .
More information about the monitoring tool you find in the IBM Knowledge Center:
https://www01.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.adv.doc/bl1adv_PMToverview.
htm?lang=en
22
11 Additional Notes
To enforce discovery of cluster components manually:
Call: '/usr/lpp/mmfs/gui/cli/lscluster'
Cluster id
Name
Primary server Secondary server Profile Mode
8393575977173099624 GSS.cluster.com gss01.cluster.com gss02.cluster.com unknown normal
EFSSG1000I The command completed successfully.
To clean up the database after an incompatible update:
The GUI must be stopped for the cleanup and restarted afterward.
Call: 'psql postgres postgres -c "drop schema fscc cascade"'
Whenever the cluster was recreated on a IBM Spectrum Scale level (and thus the clusterid changed) the database
MUST be cleaned up otherwise the GUI will display outdated data from the internal database of the old cluster id
and ignore the new data with the new cluster id ! You also must not change the Zimon configuration files directly as
they get overwritten when the node is synchronized with the central data store. Use the mm-commands instead.
To cleanly remove the GUI :
Call following sequence of commands:
1. systemctl stop gpfsgui
2. psql postgres postgres -c "drop schema fscc cascade"
3. systemctl stop pmcollector
4. yum remove gpfs.gss.gui gpfs.pmsensors*
5 .yum remove gpfs.gss.gui gpfs.collector*
After the cleanup you run the installation process again as described above in the install chapter.
23
24
Active Directory:
<ldapRegistry id="ldap"
host="ldapserver.mycity.mycompany.com" port="389" ignoreCase="true"
baseDN="cn=users,dc=adtest,dc=mycity,dc=mycompany,dc=com"
bindDN="cn=testuser,cn=users,dc=adtest,dc=mycity,dc=mycompany,dc=com"
bindPassword="testuserpwd"
ldapType="Microsoft Active Directory"
sslEnabled="false">
<activedFilters
userFilter="(&(sAMAccountName=%v)(objectcategory=person))"
groupFilter="(&(cn=%v)(objectcategory=group))"
userIdMap="user:sAMAccountName"
groupIdMap="*:cn"
groupMemberIdMap="memberOf:member">
</activedFilters>
</ldapRegistry>
For advanced configuration options or for enabling SSL refer to the IBM WebSphere Liberty knowledge center at
https://www01.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_sec_
ldap.html
After saving the changes, the management GUI service needs to be restarted:
Call: service gpfsgui start
25
26
13 Configuring further group to role mappings using the Spectrum Scale GUI
After the initial setup you can manage the group to role mappings directly from the Spectrum Scale GUI using the
Access -> GUI Access section (1/3):
27
Adding a new mapping is accomplished by clicking the Create Group Mapping button (2/3):
28
If the group you are trying to map does not exist (i.e. has not yet been created) in the external repository
you will get a warning; you will still be able to save the role assignment (3/3):
29
Troubleshooting
The Spectrum Scale GUI relies on WebSphere to connect to the specified LDAP repository and to execute the
necessary authentication steps. Therefore any LDAP connection, authentication or configuration failure should
appear in the WebSphere log wlp-messages.log found under : /var/log/cnlog/mgtsrv
Configure tracing
In most cases it helps to enable tracing on detail or finer level to troubleshoot a specific issue. This can be done
by modifying the property com.ibm.ws.logging.trace.specification in the bootstrap.properties found under
/opt/ibm/wlp/usr/servers/gpfsgui. The following setting would enable tracing for all classes (*) on the level
finer: com.ibm.ws.logging.trace.specification="*=finer"
By default the trace messages are written to the wlp-trace-log file under /var/log/cnlog/mgtsrv.
More information on trace logging options can be found here:
https://www01.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_logg
ing.html
To further debug LDAP/AD authentication issues you can enable tracing on level "finer" for the
"com.ibm.ws.security.wim.*" classes:
1.) Open /opt/ibm/wlp/usr/servers/gpfsgui/bootstrap.properties
2.) Replace the line:
com.ibm.ws.logging.trace.specification="*=audit"
with:
com.ibm.ws.logging.trace.specification="*=audit:com.ibm.ws.security.wim.*=finer"
3.) Restart the GUI: systemctl restart gpfsgui
You will now get some more detailed messages in the WebSphere Liberty trace log found here:
/var/log/cnlog/mgtsrv/wlp-trace-log. For example the groups retrieved from the LDAP/AD server are shown:
> cat wlp-trace-log | grep -A5 getGroupsForUser
...
[1/26/16 15:50:08:872 CET] 00000034 id=16de9e23 com.ibm.ws.security.wim.registry.util.MembershipBridge
< getGroupsForUser Exit
[CN=test_group,cn=users,DC=W2K8DOM02,DC=local]
30
You will be prompted to fill it out with information about your company:
Country Name (2 letter code) [XX]:
State or Province Name (full name) []:
Locality Name (eg, city) [Default City]:
Organization Name (eg, company) [Default Company Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:
Email Address []:
Please enter the following 'extra' attributes to be sent with your certificate request
A challenge password []:
An optional company name []:
3) Send the certificate request file to a trusted Certificate Authority in order to get a certificate file.
4) Generate PKCS12 file.
openssl pkcs12 -export -in <YourCertificateFile> -inkey <NameOfYourKey>.key >
<NameOfYourPKCS12File>.p12
5) Generate Java Keystore file .jks with keytool. It is typically stored in the directory
/opt/ibm/wlp/java/jre/bin/ - make sure you locate it correctly on your system.
<PathToKeytool>keytool -importkeystore -srckeystore <NameOfYourPKCS12File>.p12 -destkeystore
<NameOfYourJKSFile>.jks -srcstoretype pkcs12
You will be prompted to set the destination keystore password use here the same password as in
the step 4. The source keystore password is the export password from the step 4.
Enter destination keystore password: <YourPassword>
Re-enter new password: <YourPassword>
Enter source keystore password: <YourPassword>
6) Copy your new Java Keystore file to the directory 'security' of the gpfsgui server. It can be
typically found under /opt/ibm/wlp/usr/servers/gpfsgui/resources/security. It is a default place
where keystore files are stored.
cp <NameOfYourJKSFile>.jks <PathToSecurityDir>
7) An entry to your new Java Keystore file and its password must be defined in the server.xml file
of the gpfsgui server. You may want to encode your password if you don't want to have it there in
31
plain text. For that, use the security utility - it is typically stored in the directory /opt/ibm/wlp/bin.
The supported encodings are XOR and AES.
<PathToSecurityUtility>securityUtility encode --encoding=<xor or aes> <YourPassword>
32
Just in case no protocol node was configured make sure to setup one before the GUI is installed if you
want to use protocols.
The installer does only support RHEL 7 so a manual installation of a protocol (CES) node must be made.
Refer to the manual installation procedure described Knowledge Center: https://www01.ibm.com/support/knowledgecenter/STXKQY_4.2.0/com.ibm.spectrum.scale.v4r2.ins.doc/bl1in_InstallingIBMSp
ectrumScale.htm
If you also have a Spectrum Scale Raid System integrated into your cluster make sure you do not install the CES
node on an ESS node as this does not work without problems.
33
34
17 Glossary
IBM Spectrum Scale node
management GUI
back-end
database
IMM
SNMP
IPMI
mm-commands
Performance Monitor
HMC
GUI node
35