Readme for IBM® Spectrum Conductor 2.4.1 Interim Fix 543319
Readme file for: IBM Spectrum Conductor
Product/Component Release: 2.4.1
Update Name: Interim Fix 543319
Fix ID: sc-2.4.1-build543319
Publication date: May 21, 2020
Interim fix
contains an updated Jupyter 5.4.0 notebook package with several
enhancements for Jupyter with
IBM Spectrum Conductor 2.4.1:
·
Support for Jupyter Enterprise Gateway
2.1.1. Requires notebook package version 6.0.0 or later.
·
Support only EGO authentication (not token
authentication).
·
Jupyter notebook now sets the following
headers: X-Content-Type-Options, X-Frame-Options, and X-XSS-Protection.
·
Support for passing environment variables
to the Python kernel from the notebook for CUDA_VISIBLE_DEVICES and
EGO_SERVICE_CREDENTIAL by default. These values are changeable by setting
JUPYTER_ENV_WHITELIST to be a list of environment variables that are available
to the Python kernel. Surround each environment variable in the list with
single quotation marks, and separate each with a comma, so that the list is
in this format: 'ENV','ENV'. These values
do not get passed to the Spark kernels as they pick up the environment
variables through Spark settings.
·
The PATH of the notebook now includes
the conda environment bin path.
· A new environment variable, JEG_STARTUP_TIMEOUT, which controls timeout of Jupyter Enterprise Gateway when your machine is slow to start up. The default setting is a timeout value of 5 seconds.
Contents
1.
Download location
2.
Installation and configuration
3.
List of files
4.
Product notifications
5.
Copyright and trademark information
1.
Download location
Download interim fix 543319 from the following location: http://www.ibm.com/eserver/support/fixes/
2.
Installation and configuration
Follow the instructions in this
section to download and install this interim fix to your cluster.
System requirements
Linux x86_64 or Linux
ppc64le
Before installation
If you are updating an
existing notebook, back up the notebook base data directory:
Note: For updated notebook packages, the notebook is
undeployed and the new version is deployed. Therefore, if you specified the
notebook base data directory under, or the same, as the notebook's deployment
directory, the base data directory is removed. To retain your data, manually
back up the contents of the base data directory before you update the instance
group.
a. Log in to the cluster management console as the cluster
administrator.
b. Click Workload
> Instance Groups, then click the
instance group that you want to check.
c. Click Manage, and
then Configure.
d. In the Basic Settings tab, click the Configuration
link in the Notebooks section, then check the Base data directory value.
Note: If the notebook base data
directory is under or is the same as the notebook’s deployment directory, back
up the base data directory by running the following commands from the command
line:
> mkdir -p
/tmp/backup
> cp -a base_data_directory/ig_name /tmp/backup
Ensure that you back up the notebook base data directory for each instance group
that you want to upgrade.
Installation
a.
Log
in to the cluster management console as the cluster administrator.
b.
Download
the sc-2.4.1.0_build543319.tgz package and extract its contents to get the Jupyter-5.4.0.tar.gz file for the Jupyter 5.4.0 notebook.
c.
Add
the Jupyter 5.4.0 package to your cluster:
To update an existing
notebook:
1) Click Resources > Frameworks > Notebook Management, select Jupyter, and click Configure.
2) In the Deployment Settings tab, click Choose File in the Package section.
3) Select the Jupyter 5.4.0 package.
4) Click Update Notebook.
To add a new notebook:
1) Click Resources
> Frameworks > Notebook Management, and click Add.
2) In the Deployment Settings tab, click Choose File in the Package section.
3) Select the Jupyter 5.4.0 package.
4)
Set the following parameters:
· Name: Jupyter
· Version: 5.4.0
· Start command: ./scripts/start_jupyter.sh
· Stop command: ./scripts/stop_jupyter.sh
· Job monitor command: ./scripts/jobMonitor.sh
· Longest update interval for job monitor: 280
5)
Check these options: Enable
collaboration for the notebook, Supports SSL, Supports
user impersonation, and Anaconda required
6)
Click Add.
Post installation
a.
From the cluster management console, click Workload > Instance
Groups.
1) Create a new instance
group that uses Jupyter 5.4.0. For
details, see Creating
instance groups.
2) If required, update your existing instance groups that use Jupyter 5.4.0. For details, see Modifying
instance groups.
b.
For
the backed-up instance groups, restore the
notebook base data directory files:
> cp -a /tmp/backup/ig_name base_data_dircectory
c. Verify that permissions and ownership of the replaced files are the same as they were before applying the fix. Update any file permissions or ownership as required.
3.
List of files
Jupyter-5.4.0.tar.gz
4.
Product notifications
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.
5.
Copyright and trademark information
© 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