vania-janet/multiturn-rag-retrieval-data huggingface dataset:
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Show more





 Version 2.3 

To view the contents of version 2.3, from the running image, type default_versions.sh. This image includes the following tools:

 node --version
v10.16.0

 npm --version
6.9.0

 jq --version
jq-1.6

 yq --version
yq version 2.4.0

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

 helm version --client
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}

 ibmcloud -version
ibmcloud version 0.16.3+68cb57c-2019-06-20T08:59:16+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status
cloud-functions/wsk/functions/fn 1.0.32
container-registry 0.1.395
container-service/kubernetes-service 0.3.58
doi 0.1.3

 java -version
openjdk version "1.8.0_212"
mb4c.32x384.6x3.8tb.ssd 384GB 10000Mbps 32 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 1920GB SSD 
 mb4c.32x768.3.8tb.ssd 768GB 10000Mbps 32 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 960GB SSD 
 mb4c.48x1536 1536GB 10000Mbps 48 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 960GB SSD 
 me4c.4x32 32GB 10000Mbps 4 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 2000GB HDD 
 me4c.4x32.1.9tb.ssd 32GB 10000Mbps 4 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 960GB SSD 
 mg4c.32x384.2xp100 384GB 10000Mbps 32 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 960GB SSD 
 mg4c.48x384.2xv100 384GB 10000Mbps 48 Physical UBUNTU_18_64, UBUNTU_20_64 (default) 2000GB HDD 960GB SSD 
 u3c.2x4 4GB 1000Mbps 2 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD 







 osa 



Table 8. Worker node flavors for Osaka.

 Name Memory Network speed Cores Type OS Primary storage Secondary storage 

 b3c.16x64 64GB 1000Mbps 16 Virtual UBUNTU_18_64, UBUNTU_20_64 (default) 25GB SSD 100GB SSD
[etcd3](https://www.npmjs.com/package/etcd3) A high-quality, production-ready client for the Protocol Buffer-based etcdv3 API. 
 [express](https://www.npmjs.com/package/express) A fast, minimalist web framework for node. 
 [express-session](https://www.npmjs.com/package/express-session) A server-side session data storing module. 
 [formidable](https://www.npmjs.com/package/formidable) A Node.js module for parsing form data, especially file uploads. 
 [glob](https://www.npmjs.com/package/glob) Match files by using the patterns that the shell uses, like stars and stuff. 
 [gm](https://www.npmjs.com/package/gm) GraphicsMagick and ImageMagick for Node. 
 [got](https://www.npmjs.com/package/got) Human-friendly and powerful HTTP request library for Node.js. 
 [ibm-cos-sdk](https://www.npmjs.com/package/ibm-cos-sdk) IBM Cloud® Object Storage SDK for Node.js. 
 [ibm_db](https://www.npmjs.com/package/ibm_db) An asynchronous/synchronous interface for Node.js to IBM DB2 and IBM Informix. 
 [ibm-watson](https://www.npmjs.com/package/ibm-watson) A Node.js client library to use the Watson APIs. 
 [iconv-lite](https://www.npmjs.com/package/iconv-lite) Pure JS character encoding conversion. 
 [jest](https://www.npmjs.com/package/jest) Delightful JavaScript Testing.
: This release of the buildpack adds IBM SDK for Node.js runtime versions 0.10.45, 0.12.14, 4.4.4, 6.0.0, and 6.1.0. The default is now 4.4.4.

Included are fixes for the following security vulnerabilities:



* [CVE-2015-8855](https://www.ibm.com/support/pages/node/278621)
* [CVE-2016-2108 CVE-2016-2107 CVE-2016-2105 CVE-2016-2106 CVE-2016-2109 CVE-2016-2176](https://www.openssl.org/news/secadv/20160503.txt)



Note that there is a known issue with NPM v3 and the App Management inspector utility. NPM 3.8.6 is the default with the 6.0.0 and 6.1.0 runtimes. If you want to use either of the 6.x runtimes and the inspector utility, you should specify a 2.x NPM version in your package.json as a temporary workaround.





 5 May 2016 

Updated Liberty buildpack v2.8-20160430-1011
: The buildpack contains an updated version of WebSphere Liberty based on the [April beta](https://developer.ibm.com/wasdev/blog/2016/04/08/beta-websphere-liberty-and-tools-april-2016/). The updated version of Liberty makes the logstashCollector-1.0 GA feature and the logmetCollector-1.0 beta feature available in IBM Cloud.



* The buildpack also contains updated versions of IBM JRE: 8 SR3 and 7.1 SR3 FP40.
* The buildpack adds initial support for the [AppDynamics](https://www.appdynamics.com/) app monitoring agent.
OS: Linux 4.9.184-linuxkit amd64

 oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Show more





 Version 2.4 

To view the contents of version 2.4, from the running image, type default_versions.sh. This image includes the following tools:

 node --version
v10.16.3

 npm --version
6.9.0

 jq --version
jq-1.6

 yq --version
yq version 2.4.0

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

 helm version --client
Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}

 ibmcloud -version
ibmcloud version 0.18.1+09d36ed-2019-08-19T08:23:11+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status
doi 0.1.5
cloud-functions/wsk/functions/fn 1.0.32
container-registry 0.1.404
container-service/kubernetes-service 0.4.3
(stonith:fence_ibm_powervs):	 Started cl-sap-2
* Resource Group: s01_ascs01_group:
* s01_vip_ascs01	(ocf::heartbeat:IPaddr2):	 Started cl-sap-1
* s01_fs_ascs01_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-1
* s01_fs_ascs01	(ocf::heartbeat:Filesystem):	 Started cl-sap-1
* s01_ascs01	(ocf::heartbeat:SAPInstance):	 Started cl-sap-1
* Resource Group: s01_ers02_group:
* s01_vip_ers02	(ocf::heartbeat:IPaddr2):	 Started cl-sap-2
* s01_fs_ers02_lvm	(ocf::heartbeat:LVM-activate):	 Started cl-sap-2
* s01_fs_ers02	(ocf::heartbeat:Filesystem):	 Started cl-sap-2
* s01_ers02	(ocf::heartbeat:SAPInstance):	 Started cl-sap-2
* Clone Set: fs_sapmnt-clone [fs_sapmnt]:
* Started: [ cl-sap-1 cl-sap-2 ]

Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled





 Test1 - Test Procedure 

Crash SAP ASCS instance by sending a SIGKILL signal as user ${sid}adm to the enque server.

On NODE1, identify the PID of the enque server.

pgrep -af "(en|enq).sap"

Send a SIGKILL signal to the identified process.

Sample output:
v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1listsynonyms)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodelistsynonyms)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javalistsynonyms)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythonlistsynonyms) 
 Add entity value synonym Add a new synonym to an entity value. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1createsynonym)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodecreatesynonym)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javacreatesynonym)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythoncreatesynonym) 
 Get entity value synonym Get information about a synonym of an entity value. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1getsynonym)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodegetsynonym)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javagetsynonym)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythongetsynonym) 
 Update entity value synonym Update an existing entity value synonym with new text.
Windows (unsupported):

With Virtuozzo Containers 4 Windows, you have downtime during the transition (between 20 seconds up to 5 minutes) because of not having an online option to pass.

If you use Virtuozzo 3.0 for Windows, then you need to upgrade the hardware node to at least Virtuozzo 3.5.1 for Windows.

Virtuozzo Containers 4 for Windows, by default, runs in compatibility mode.

Restoring backups from 3.5.1 on a Virtuozzo Containers 4 hardware node can also be performed by copying the full backup to the destination node, running vzbackupsync.exe and restoring the backup as normal.

Make sure that the same templates are installed on the new hardware node.
* Are containers isolated from each other and the host?

Your containers are restricted from loading LKMs, performing a chroot(“../../../”) out of their own environment and don't share IPC Resources (semaphore sets and shared memory segments).

You have no security concerns with how Virtuozzo manages resources and isolates the processes. With a bridged network configuration, all containers in the same VLAN (on the same hardware node) can see each other's traffic. Using routed mode is highly suggested.
* Why can't I cache RedHat and SUSE OS templates in Virtuozzo?

You can experience issues when you cache to RedHat and SUSE OS templates if you use Vitruozzo. These OS templates require extra licensing, which IBM Cloud doesn't provide. If you receive any of the following errors, you need to have your own accounts with the respective vendors and configure the corresponding variables within /etc/vztt/url.map (/etc/vztt/vztt.conf in Virtuozzo 3.)





 TIMESTAMP Click here to open/close the operation details.Update OS Template Cache Failed 
 TIMESTAMP Operation update with the Env(s) "virtuozzo00.softlayer.local" and package(s) .redhat-as4-x86_64 is started
[HPC Cluster solution page](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/hpc_catalog.png)

HPC cluster solution page
2. In the Set the deployment values section, supply the required values: api_key, ibm_customer_number, remote_allowed_ips, ssh_key_name, and zone.
3. After you confirm with the license agreement, you can use the default values for other parameters and click Install. The HPC cluster is created and completed within 5 minutes with the default configuration.





 Parameters for cluster deployment 

See the following table for a list of parameters that you can configure for your HPC cluster:



Table 1. Parameter values

 Parameter Description 

 cluster_prefix The prefix used to name the VPC resources that are provisioned to build the HPC cluster. There are resources where their names must be unique in the same cloud account given a single region. Make sure that the name is unique (for example, add your initials to the name: po-hpc-cluster). 
 hyperthreading_enabled You can enable hyper-threading in the worker nodes of the cluster by setting this value to true (default). Otherwise, hyper-threading is disabled. 
 image_name Edit and add the custom image with LSF. You can use the default LSF custom image that is provided by the solution. If you created your own custom image, edit the value to the name of your custom image. 
 management_node_count You can have up to three management nodes in the cluster. If you want failover support that is provided by LSF, you need to specify the value to be larger than one. In this case, when the primary management node is down, one of the candidate management nodes become the primary and your cluster remains functional without interruption. 
 region Edit the region where you want your cluster to be created.
Worker node flavors for Chennai.

 Name Memory Network speed Cores Type OS Primary storage Secondary storage 

 b3c.16x64 64GB 1000Mbps 16 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 b3c.16x64.300gb 64GB 1000Mbps 16 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 300GB SSD 
 b3c.32x128 128GB 1000Mbps 32 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 b3c.4x16 16GB 1000Mbps 4 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 b3c.56x242 242GB 1000Mbps 56 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 b3c.8x32 32GB 1000Mbps 8 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 c3c.16x16 16GB 1000Mbps 16 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 c3c.16x32 32GB 1000Mbps 16 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 c3c.32x32 32GB 1000Mbps 32 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 c3c.32x64 64GB 1000Mbps 32 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 m3c.4x32 32GB 1000Mbps 4 Virtual REDHAT_7_64 (default), REDHAT_8_64 25GB SSD 100GB SSD 
 mb4c.20x192 192GB 10000Mbps 20 Physical REDHAT_7_64 (default), REDHAT_8_64 2000GB HDD 960GB SSD
Adding a node adds another member with a size of 5120 MB of disk and 1028 MB of RAM, bringing your total resource usage for your deployment to 20480 MB of disk and 4096 MB of RAM.

Billing is based on the total amount of resources that are allocated to the service.



 Adding Nodes through the API 

The Foundation Endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API.

To view the current and scalable resources on a deployment, use the [/deployments/{id}/groups](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-available-scaling-groups-from-a-depl)

curl -X GET -H "Authorization: Bearer $APIKEY" https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups'

To add nodes, use the [/deployments/{id}/groups/{group_id}](https://cloud.ibm.com/apidocs/cloud-databases-apiset-scaling-values-on-a-specified-group) API endpoint, sending a PATCH request with the number of nodes you want in your deployment. The example request increases the number of nodes from the default of 3 to 5.

curl -X PATCH 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups/member' -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{"members": {"allocation_count": 5}}'

When you use the CRN, remember to URL encode the CRN value as it might include the forward-slash (/) %2F character.

When properly encoded, a CRN that uses a forward-slash (/) character substitutes with a %2F character string. For example, the following CRN
The amount of time it takes to resync a read replica varies, but the process can be very long running.

To start a resync through the CLI, use the [cdb read-replica-resync](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referenceread-replica-resync) command.

ibmcloud cdb read-replica-resync <deployment name>

To start a resync through the API, send a POST to the [/deployments/{id}/remotes/resync](https://cloud.ibm.com/apidocs/cloud-databases-apiresync-read-replica) endpoint.

curl -X POST https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/remotes/resync -H 'Authorization: Bearer <>'





 Promoting a Read Replica 

A read replica is able to be promoted to an independent cluster that can accept write operations as well as read operations. If something happens to the source database instance, the read replica can be promoted to a stand-alone cluster and start accepting writes from your application.

To promote a read replica from the UI, click the Promote Read Replica button.

Upon promotion, the read replica terminates its connection to the source database instance and becomes a stand-alone Databases for MySQL deployment. The deployment can start accepting and running read and write operations, backups are enabled, and it is issued its own admin user. A new data member is added so the deployment becomes a cluster with three data members. This increases the cost as it is billed at the same per member consumption rate, but the deployment has three members instead of one.

When you promote a read replica, you can skip the initial backup that would normally be taken upon promotion. Skipping the initial backup means that your replica becomes available more quickly, but there is no immediate backup available. You can start an on-demand backup once the promotion process is complete.
To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

At least one worker node in the cluster is not available, but other worker nodes are available and can take over the workload. Try to [reload](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_reload) the unavailable worker nodes. - Your cluster has zero worker nodes, such as if you created a cluster without any worker nodes or manually removed all the worker nodes from the cluster. [Resize your worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool) to add worker nodes to recover from a Warning state, and then [update the Calico node entries for your worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-zero_nodes_calico_failure). - A control plane operation for your cluster failed. View the cluster in the console or run ibmcloud oc cluster get --cluster <cluster_name_or_ID> to [check](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_master) the Master Status for further debugging.
etcd configuration N/A N/A Improved etcd probe configurations. 
 IBM Cloud Controller Manager v1.26.4-7 v1.27.1-8 Updated to support the Kubernetes 1.27.1 release. Updated Go dependencies and to Go version 1.20.3. Base image updated. Increased default number of concurrent node and service sync workers. VPC load balancer updates can now be complete asynchronously. 
 Kubernetes v1.26.5 v1.27.2 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.27.2). 
 Kubernetes add-on resizer 1.8.16 1.8.18 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.18). 
 Kubernetes CSI snapshot controller and CRDs v6.0.1 v6.2.1 See the [Kubernetes container storage interface (CSI) snapshotter release notes](https://github.com/kubernetes-csi/external-snapshotter/releases/tag/v6.2.1). 
 Kubernetes DNS autoscaler configuration N/A N/A Increased Kubernetes DNS autoscaler memory resource request to 10Mi. 
 Kubernetes Metrics Server v0.6.2 v0.6.3 See the [Kubernetes Metrics Server release notes](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.3). 
 Kubernetes NodeLocal DNS cache configuration N/A N/A Increased Kubernetes NodeLocal DNS cache memory resource request to 20Mi.
Adding Elasticsearch Nodes 

It is possible to scale your IBM Cloud® Databases for Elasticsearch deployment horizontally by adding more Elasticsearch nodes (also referred to as members). If your deployment starts to strain or slow down, adding nodes increases capacity and reliability. When a node is added, Elasticsearch automatically balances the workload across all the nodes in your deployment.

Nodes that you add to your deployment are added with the amount of disk, memory, and CPU as the other nodes currently in your deployment. A visual representation of your data members and their resource allocation is available on the Resources tab of your deployment's Manage page. However, horizontal scaling is only available by using the API.

Zoom

![The Scale Resources Pane in Resources](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/images/settings-scaling.png)

Figure 1. The Scale Resources Pane

A default IBM Cloud® Databases for Elasticsearch deployment runs with three data members in a cluster, and resources are allocated to all three members equally. For example, the minimum storage of an Elasticsearch deployment is 15360 MB, which equates to an initial size of 5120 MB per member. The minimum RAM for an Elasticsearch deployment is 3072 MB, which equates to an initial allocation of 1028 MB per member. Adding a node adds another member with a size of 5120 MB of disk and 1028 MB of RAM, bringing your total resource usage for your deployment to 20480 MB of disk and 4096 MB of RAM.

Billing is based on the total amount of resources that are allocated to the service.



 Adding Nodes through the API 

The Foundation Endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API.
skopeo --version
skopeo version 1.8.0
Show more





 Version 3.9 

To view the contents of version 3.9, from the running image, type default_versions.sh. The 3.x branch provides images with the current tool versions. The current Java™ version is Java™ 17. Node.js no longer uses nvm to manage different node.js versions. It provides the current LTS version of Node.js at the time that it was built.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image includes the following tools:

 node --version
v16.16.0

 npm --version
8.11.0

 jq --version
jq-1.6

 yq --version
yq (https://github.com/mikefarah/yq/) version 4.26.1

 kubectl version --client
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T14:08:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey).





 Step 2: Create SSH key 

Create an SSH key in your IBM Cloud account. This is your SSH key that you will use to access the LSF cluster. Ensure that the SSH key is present in the same resource group and region where the cluster is being provisioned. You can use multiple comma-separated SSH keys, if the cluster needs multiple SSH keys. For more information, see [Managing SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ssh-keys).





 Step 3: Create custom image(s) 

The offering provides a default set of images that you can use for the nodes within your HPC cluster. However, if you would prefer to use your own custom images, documentation and scripts are provided to help you create them.

Worker Image: The default image that is specified in image_name acts as the worker image. This image is used to create the LSF cluster nodes: management, management-candidates, and workers. In addition to the base operating system, the image includes some commonly used software packages:



* GNU compilers for C, C++, Fortran (gcc, gcc-c++, gcc-gfortran)
* Open MPI (openMPI)
* [Intel® MPI Library for Intel® oneAPI](https://www.intel.com/content/www/us/en/develop/documentation/get-started-with-mpi-for-linux/top.html)



If you prefer to create the worker custom image with your own settings and configurations, follow the instructions that are provided [here](https://github.com/IBM-Cloud/hpc-cluster-lsf/tree/main/custom_image/workerreadme).

Storage Image: If you intend to use Spectrum Scale as shared storage for the cluster, the default image specified in scale_storage_image_name acts as the storage image. This image is used to create the Spectrum Scale storage cluster nodes.