Readme File for IBM® Spectrum Symphony 7.2.0.2 Fix sym-7.2.0.2-build600159
Readme File for: IBM Spectrum Symphony
Product Release: 7.2.0.2
Fix ID: sym-7.2.0.2-build600159
Publication Date: February 6, 2021
Virtual Processor Core (VPC) is a unit by which IBM Spectrum
Symphony can be licensed. VPC is also referred to as Variable Use
Licensing (VUL). Usage of each VPC is measured in Virtual Processor
Core-Instance-Hours.
This fix configures cloud hosts that join your cluster to track
the core-hours used by each host's cores. You can query the total core-hours
that are used in your cluster between two dates.
Contents
1. Scope
2. Installation
3. Configuration and usage
4. Uninstallation
5. List of files
6. Product notification
7.
Copyright and trademark information
Before you install this enhancement to your cluster, note the following requirements:
|
Operating system |
Linux RHEL 6.x or 7.x |
|
Product version |
IBM Spectrum Symphony 7.2.0.2 |
a.
Log on to the primary host as the
cluster administrator:
> egosh user logon -u Admin -x password
b. Disable all applications:
> soamcontrol app disable all -f
c. Stop all services:
> egosh service stop all
d. Shut down the cluster:
> egosh ego shutdown all
e. On each management
and compute host, backup the following binaries:
3.6/linux-x86_64/etc/vemkd
3.6/linux-x86_64/etc/lim
3.6/linux-x86_64/bin/egosh
3.6/linux-x86_64/lib/libvem.so.3.6.0
f. On each management and compute host, copy the sym-7.2.0.2_x86_64_build600159.tar.gz package and extract its contents to the $EGO_TOP installation directory:
> tar zxfo sym-7.2.0.2_x86_64_build600159.tar.gz
-C $EGO_TOP
g. Use the command egosh -V
to verify the installation:
> egosh -V
Configuring your cloud hosts for core-hour usage involves tagging your cloud hosts with the corehoursaudit resource attribute. The corehoursaudit attribute marks cloud hosts as temporary and tracks the time that each host's cores are used. The corresponding metrics are then logged to the ego.cluster_name.entitlement.acct file.
If the cluster has spare perpetual
license capacity, it is possible to allow hosts to use a mix of perpetual and
variable use licenses. The EGO_LICENSE_CORE_ENTITLEMENT causes
hosts that are tagged with the corehoursaudit resource attribute to count against the
perpetual core entitlement until the entitlement limit defined by EGO_LICENSE_CORE_ENTITLEMENT is
reached. If the EGO_LICENSE_CORE_ENTITLEMENT value is not
configured, hosts configured with the corehoursaudit attribute do not add cores to the
perpetual core entitlement. These hosts log core-hours only.
a.
From the EGO primary host, open a command line and change to the
following directory:
> cd $EGO_CONFDIR
b.
In a text editor, open the ego.shared configuration file:
> vi ego.shared
c. Add the corehoursaudit resource attribute to the second last line of the ego.shared file that is before the line with End Resource:
corehoursaudit Boolean () ()
([VUL]Enables auditing of core-hour usage for this host)
d. From the EGO primary host, start the cluster:
>egosh ego
start all
e.
Add
the corehoursaudit resource attribute with the egoconfig addresourceattr command on the compute host:
> egoconfig
addresourceattr "[resource corehoursaudit]"
Ensure that you use the egoconfig addresourceattr command to tag cloud hosts before the cloud
host joins the cluster for the first time, either during image creation or
during post-provisioning (recommended).
Note: If a cloud host joined the cluster before without this attribute that
is assigned or to update this attribute, you must remove it from the cluster
and then start ego on this host to allow it to rejoin
the cluster:
> egosh resource close -reclaim host_name
> egosh
resource remove host_name
> egosh ego start
Tip: After you enable the corehoursaudit resource attribute, you can run the following
commands:
i.
To find all hosts currently
enabled to log core hours, you can run the following example command:
> egosh resource
list -l -R corehoursaudit
Sample output:
NAME
status mem swp tmp ut
it pg r1m
r15s r15m ls
host1
ok
45G 0M 889G 4%
258 0.0 0.9 1.2 0.9
2
ii.
To query the core usage
information between two dates, you can run the following example command:
> egosh
entitlement corehours -s "1/1/20" -e
"1/5/20"
Sample output:
Core hours: 20
To view more usage data, use the ego.cluster_ID.entitlement.acct file to view a summary of core-hour usage. Use the cluster.hostusage file to view detailed core-hour usage.
In addition, if you removed the tagged hosts from the cluster,
you can see the core usage information for these hosts in the lim.log<hostname> file. This lim log file by default is available in the $EGO_LOCAL_CONFDIR/../log directory.
Sample output:
removeVULHost: Removed the variable use
licensing host: host1. This host was active for 3.36 hours and logged 64 core
hours.
f. Optional: Change the defaults for core-hour usage parameters.
i.
Log in to
the primary host.
ii.
Backup
and edit the ego.conf file
at $EGO_CONFDIR and update the following parameters:
EGO_LICENSE_COREHOURS_MONITOR_INTERVAL_MINUTES
Interval at which core-hour usage is
monitored and logged to the cluster.hostusage file at $EGO_CONFDIR/../work/data/; default is 5 minutes. The cluster.hostusage file logs detailed core-hour metrics at a more
frequent interval than that logged to the ego.cluster_name.entitlement.acct file and is also used for recovery purposes.
EGO_LICENSE_CORE_ENTITLEMENT
Maximum number of cores that can be
entitled in your cluster. Default is 0, which indicates that all cloud hosts
with the corehoursaudit resource
attribute are counted only for core-hour usage. Define this parameter if you
want to use a combination of perpetual licenses and variable use licenses for
your cloud hosts. When defined, cloud hosts that join the cluster are licensed
by cores, up to the specified entitlement. After all perpetual licenses are
used, cloud hosts that join the cluster are licensed by core hours.
EGO_LICENSE_GPUCORE_ENTITLEMENT
Maximum number of GPU cores that can
be entitled when your cluster is licensed for IBM Spectrum Symphony GPU
Harvesting. Default is 0, which indicates that all cloud hosts with the corehoursaudit resource attribute are counted only for GPU
core-hour usage. Define this parameter if you want to use a combination of GPU
perpetual licenses and GPU variable use licenses for your cloud hosts. When
defined, cloud hosts that join the cluster are licensed by GPU cores, up to the
specified entitlement. After all GPU perpetual licenses are used, cloud hosts
that join the cluster are licensed by GPU core hours.
EGO_LICENSE_WORK_FILE_PURGE_DAYS
Maximum number of days to retain
core-hour usage records in the cluster.hostusage file; default is 2 days. Update this parameter
when you want to retain the records for more than 2 days.
iii.
Save your
changes.
iv.
Restart EGO:
>egosh
ego restart
a. Log on to the primary host as the cluster
administrator:
> egosh user logon -u Admin
b. Disable all applications:
> soamcontrol app disable all -f
c. Stop all services:
> egosh service stop all
d. Shut down the cluster:
> egosh ego shutdown all
e. Log on to each management and compute host and
restore the following files from your backup:
3.6/linux-x86_64/etc/vemkd
3.6/linux-x86_64/etc/lim
3.6/linux-x86_64/bin/egosh
3.6/linux-x86_64/lib/libvem.so.3.6.0
f.
From the primary host, start the
cluster:
> egosh ego start all
g. Enable your applications:
> soamcontrol app enable appName
|
sym-7.2.0.2_x86_64_build600159.tar.gz |
a6b695fc4053bfb05937a9fb072c61f0 |
|
3.6/linux-x86_64/etc/vemkd |
c20620c423626d51ebe12f80d0d3f584 |
|
3.6/linux-x86_64/etc/lim |
4ac8563fc5875422592ba84f7acb4723 |
|
3.6/linux-x86_64/bin/egosh |
2984659896134f808b30d03d5ee41395 |
|
3.6/linux-x86_64/lib/libvem.so.3.6.0 |
93acef401547398e6f08d5cddca5fe24 |
To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes.
© Copyright IBM Corporation 2021
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.