Readme File for IBM® Spectrum Symphony 7.3.0 RFE 144449
Readme file for: IBM Spectrum Symphony
Product release: 7.3.0
Fix ID: sym-7.3-build566339-jpmc
Publication date: December 16, 2020
This enhancement provides two configuration attributes:
· RUN_SIM_AS_CLUSTER_ADMIN in the application profile to run SIM and the Docker client using the cluster administrator OS user.
· SIM_DOCKER_CONTAINER_USER_FROM_CONSUMER in the sd.xml configuration file to use the application’s consumer’s execution user to run a Docker container.
Before you install this enhancement to your cluster, note the following requirements:
|
Operating system |
RHEL 6.4 or higher 64-bit |
|
Product version |
IBM Spectrum Symphony 7.3.0 |
Follow these instructions to download and install this enhancement on hosts in your cluster.
IBM Spectrum Symphony 7.3.0 Advanced Edition must be installed on Linux hosts in your cluster, with interim fix 550947 also installed.
a. Log on to the primary host as the cluster administrator, disable all applications, stop all services and shutdown your cluster:
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all -f
> egosh service stop all
> egosh ego shutdown
b. On each management and compute host, create a directory (for example, /symfixes) and download the egocore-3.8.0.1_x86_64_build566339.tar.gz and soamcore-7.3.0.0_x86_64_build566339.tar.gz files to the directory.
c. Run the egoinstallfixes command to install the egocore-3.8.0.1_x86_64_build566339.tar.gz and soamcore-7.3.0.0_x86_64_build566339.tar.gz files:
> egoinstallfixes /symfixes/egocore-3.8.0.1_x86_64_build566339.tar.gz
> egoinstallfixes /symfixes/soamcore-7.3.0.0_x86_64_build566339.tar.gz
This enhancement provides a new attribute in the application profile, called RUN_SIM_AS_CLUSTER_ADMIN, which allows you to run SIM and the Docker client using the cluster administrator OS user.
Required or optional: Optional
Valid values: TRUE or FALSE
Default value: FALSE
This enhancement also provides a new attribute in the sd.xml file, called SIM_DOCKER_CONTAINER_USER_FROM_CONSUMER, which allows you to use the application’s consumer’s execution user to run a Docker container.
Required or optional: Optional
Valid values: Y or N
Default value: N
Configuration
a. For the application profile enabled for Docker (using the enableDockerForServiceInstance="true" setting in the Consumer section), edit the SOAM > SIM > OsTypes > OsType > env section to add the RUN_SIM_AS_CLUSTER_ADMIN configuration:
<env name="RUN_SIM_AS_CLUSTER_ADMIN">TRUE</env>
b. For each application that using the RUN_SIM_AS_CLUSTER_ADMIN=TRUE setting, clean up the application’s Docker client’s log files and log lock files which are identified with a dockercontroller.log prefix. The log location is defined by the logDirectory attribute in the Service section of the application profile (logDirectory="${SOAM_HOME}/work", by default).
c. On each management host, edit the $EGO_ESRVDIR/esc/conf/services/sd.xml file to add the SIM_DOCKER_CONTAINER_USER_FROM_CONSUMER configuration:
<ego:EnvironmentVariable name="SIM_DOCKER_CONTAINER_USER_FROM_CONSUMER">value</ego:EnvironmentVariable>
d. From the primary host, start the cluster and enable your applications:
> egosh ego start
> soamcontrol app enable appName
If required, uninstall this enhancement from Linux management and compute hosts in your cluster:
a. Log on to the primary host as the cluster administrator, disable all applications, stop all services and shut down your cluster:
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all -f
> egosh service stop all
> egosh ego shutdown
b. On each management and compute host , roll back this enhancement:
> egoinstallfixes -r 566339
c. Edit the modified application profile and remove the RUN_SIM_AS_CLUSTER_ADMIN configuration.
d. For each application where you removed the RUN_SIM_AS_CLUSTER_ADMIN configuration, clean up the application’s Docker client’s log files and log lock files which are identified with a dockercontroller.log prefix. The log location is defined by the logDirectory attribute in the Service section of the application profile (logDirectory="${SOAM_HOME}/work", by default).
e. Edit the $EGO_ESRVDIR/esc/conf/services/sd.xml file and remove the SIM_DOCKER_CONTAINER_USER_FROM_CONSUMER configuration.
f. From the primary host, start the cluster and enable your applications:
> egosh ego start
> soamcontrol app enable appName
egocore-3.8.0.1_x86_64_build566339.tar.gz;a472bf24dc486f4abacb915958ce540e
3.8/linux-x86_64/etc/egodocker/libs/pod/dockerclient.py;ed5961926498d70e6eec0155081ba97a
3.8/linux-x86_64/etc/vemkd;2b7dc79ed41d6a418683dd5588a01d79
soamcore-7.3.0.0_x86_64_build566339.tar.gz;70ad19d98def97949bf323de145025ae
soam/7.3/linux-x86_64/etc/sd;e2ca074d76c589d4ef813f6a141f0d7d
soam/7.3/linux-x86_64/etc/sim;fcd11d4cf9dfd50ab94a4500eaa9887e
soam/7.3/linux-x86_64/etc/ssm;bccdc73167f7d87806f2e18deaa20be7
soam/7.3/linux-x86_64/lib64/libsoam_resources_7.3.so;ca6caa9f15e4113bacc9bc2501a4721e
soam/7.3/linux-x86_64/lib/libsoam_resources_7.3.so;bedb9cf26225babffb166b2b23378db5
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 2020
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.