vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Quotas:
Category Used Limit
App revisions 1 60
Apps 1 20
Build runs 1 100
Builds 2 100
Configmaps 2 100
CPU 0 64
Ephemeral storage 0 256G
Instances (active) 0 250
Instances (total) 0 2500
Job runs 0 100
Jobs 0 100
Memory 0 256G
Secrets 6 100
Subscriptions (cron) 0 100
Subscriptions (IBM Cloud Object Storage) 0 100
Subscriptions (Kafka) 0 100
9. Create an application that is only visible to the private endpoint. Use the [ibmcloud ce application create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command with the --visibility=private option. Alternatively, you can use the console to create an app or update an existing app and set the [visibility of your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsoptionsvisibility).

ibmcloud ce application create -n myapp --visibility=private



You have now configured and set up your virtual private endpoint to manage project resources. If you want to control which app to expose to the private endpoint, you can [set up a VPE to access your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-vpeusing-vpes-app).





 Using your VPE to access an app securely 

Before you begin, you must have an [IBM Cloud account](https://cloud.ibm.com/registration).

You can only use your VPE to access your app with a private endpoint if your selected project supports [application private visibility](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsapp-endpoint-private).
Wait for your PVC to bind, then [create a deployment that uses your PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block).
6. [Verify the encryption of your Block Storage for Classic volumes](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_encrypt).







 Verifying the encryption of your Block Storage for Classic volumes 

You can verify the encryption of your volumes by checking the volume mount path.



1. Log in to your app pod. Replace <pod_name> with the name of the pod that mounts your encrypted Block Storage for Classic volume.

kubectl exec <pod_name> -it bash
2. List the file system of your pod.

df -h
3. Review the file system path for your encrypted Block Storage for Classic volume.



* Encrypted volumes have a path structure of /dev/mapper/<pvc-ID_encrypted>. In this example, the encrypted volume is mounted to the /test file path in the pod.

Filesystem Size Used Avail Use% Mounted on
overlay 98G 8.2G 85G 9% /
tmpfs 64M 0 64M 0% /dev
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/mapper/pvc-a011a111-1111-1111-111a-aaa1a1111a11_encrypted 20G 45M 20G 1% /test
* Unencrypted volumes have a path structure of dev/mapper/<random_string>.

Filesystem Size Used Avail Use% Mounted on
overlay 98G 16G 78G 17% /
tmpfs 64M 0 64M 0% /dev
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
If you determine that disabling Hyper-Threading Technology is right for your configuration, you can use one of the following methods to disable it on your guest virtual machines (VMs) in IBM Cloud.





 Checking Hyper-Threading Technology status and changing it in my guest VM: Basics 

When a virtual machine is up and running, you can check the Hyper-Threading Technology status by using the lscpu command on Linux operating systems. You see output similar to the following:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
...

In this example, notice that the Thread(s) per core displays 2, indicating that Hyper-Threading Technology is enabled. The VM has 4 physical cores and 8 virtual CPUs. Modern versions of the Linux kernel allow users to disable Hyper-Threading Technology on a per core basis. You can run some cores with Hyper-Threading Technology enabled and other cores with Hyper-Threading Technology disabled. To see this on a per core basis, you can use the command lscpu --extended. You see output similar to the following:

CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE
0 0 0 0 0:0:0:0 yes
1 0 0 0 1:1:0:0 yes
2 0 0 1 2:2:1:0 yes
3 0 0 1 3:3:1:0 yes
4 0 0 2 4:4:2:0 yes
5 0 0 2 5:5:2:0 yes
6 0 0 3 6:6:3:0 yes
7 0 0 3 7:7:3:0 yes

The preceding example output shows that each core has 2 CPUs and both CPUs are online. Core 0 has siblings: CPU 0 and CPU 1. To get the sibling list, you can find the data in thread_sibling_list in the devices file system as shown in the following example:
Connecting to DTS Device in Linux®for CentOS/RHEL 7 

To interact with an iSCSI LUN in Linux-based operating systems, you must connect to the LUN by entering a series of commands in the terminal. The tool that is used to interact with an iSCSI LUN in a Linux®-based OS is dependent upon the type and version of the OS that is installed on the device.

Before you begin, retrieve the iSCSI username, password, and storage address for the storage volume that you want to connect from the [IBM Cloud console](https://cloud.ibm.com/login).



 Configuring connection in CentOS 7 and RHEL 7 



1. Install iSCSI initiator and multipath mapper utilities for Linux®.

yum -y install iscsi-initiator-utils device-mapper device-mapper-multipath
2. Create the iscsid.conf configuration file.
3. Back up the original configuration.

cp /etc/iscsi/iscsid.conf{,.save}
4. Open /etc/iscsi/iscsid.conf with your favorite text editor and replace the contents with the following code:

node.startup = automatic
node.session.auth.username = ISCSI_USER
node.session.auth.password = ISCSI_PASS
discovery.sendtargets.auth.username = ISCSI_USER
discovery.sendtargets.auth.password = ISCSI_PASS
node.session.timeo.replacement_timeout = 120
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 10
node.conn[0].timeo.noop_out_timeout = 15
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
* Updates the UBI to version 8.8-860.







 Revision 21, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 20, released 4 April 2023 



* Resolves the following CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)[CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)[CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)[CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)
* Updates the UBI to version 8.7-1085.1679482090.







 Revision 19, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 18, released 6 March 2023
* Updates the UBI to version 8.8-860.







 Revision 20, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 19, released 4 April 2023 



* Resolves the following CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)[CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)[CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)[CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)
* Updates the UBI to version 8.7-1085.1679482090.







 Revision 18, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 17, released 6 March 2023
* Updates the UBI to version 8.8-860.







 Revision 5, released 21 April 2023 



* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361)
* Updates the UBI to version 8.7-1107.
* Ignore aggregate usage limit if set to 0%







 Revision 4, released 4 April 2023 



* Resolves the following CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)[CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)[CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)[CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)
* Updates the UBI to version 8.7-1085.1679482090.







 Revision 3, released 21 March 2023 



* Resolves the following CVEs: [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 2, released 6 March 2023
BI.S4.H8.12000 IBM Cloud Bare Metal (Local SDD) 184,320 Up to 16 nodes:  15 active nodes (1 parent, 14 worker nodes) and 1 standby node TDI OLAP 3,360 6,720 [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2302) [OLAP Scale-Out Record](https://www.sap.com/dmc/exp/2018-benchmark-directory//bwh?id=bm:f050d27b-f541-4807-9df1-78aae4095661) <br><br>[Certification #2021065](https://www.sap.com/dmc/benchmark/2021/Cert21065.pdf) 
 BI.S4.H8.12000 IBM Cloud Bare Metal (Local SDD) 36,864 Up to 4 nodes:   3 active nodes (1 parent, 2 worker nodes) and 1 standby node TDI OLTP 672 1,344 [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2304) n/a n/a 
 vx2d-176x2464 IBM Cloud Virtual Server 17,248 Up to 8 nodes:  7 active nodes (1 parent, 6 worker nodes) and 1 standby node TDI OLAP -- 1,232 [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=v:deCertified;iaas;ve:28;v:105&id=s:2606) n/a [ n/a 
 bh1-30x3000 IBM Power Virtual Server 21,000 Up to 8 nodes:   7 active nodes (1 parent, 6 worker nodes) and 1 standby node TDI OLAP 210 1,680 n/a n/a
: Added the required ports and subnets that must be allowed for [inbound](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-networkreqs-host-network-firewall-inbound) and [outbound connectivity](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound) on hosts' public networks.





 6 October 2020 

Review the release notes for 6 October 2020.

CLI change log
: Added a CLI plug-in change log page for the [release of version 1.0.178](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).

Location subdomain troubleshooting
: Added steps for further troubleshooting when [the location subdomain does not route traffic to control plane hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-location-subdomain).







 September 2020 

Review the release notes for September 2020.



 14 September 2020 

Review the release notes for 14 September 2020.

Host requirements
: Clarified that the localhost value must resolve to a valid local IP address, typically 127.0.0.1, on a [host](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network).

IAM
: Updated [assigning access to Satellite Config in IBM Cloud IAM](https://cloud.ibm.com/docs/satellite?topic=satellite-iam) to note that you cannot scope access policies to specific configurations, subscriptions, or IBM Cloud resource group.

Provider documentation
: Updated the provider requirements, such as examples for installing RHEL packages on GCP hosts before you attach the host to your Satellite location.

Service requirements
: Added that you can provision up to [40 IBM Cloud service instances per Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-requirementsreqs-services).







 August 2020 

Review the release notes for August 2020.



 21 August 2020
"nameField": "six",
"_id": "14746fe384c7e2f06f7295403df89187",
"_rev": "1-b2c48b89f48f1dc172d4db3f17ff6b9a"
}
},
...{
"value": {
"rev": "1-7130413a8c7c5f1de5528fe4d373045c"
},
"id": "49baa66cc66b4dda86ffb2852ae78eb8",
"key": "49baa66cc66b4dda86ffb2852ae78eb8",
"doc": {
"temperatureField": 40,
"descriptionField": "hot",
"numberField": 2,
"nameField": "two",
"_id": "49baa66cc66b4dda86ffb2852ae78eb8",
"_rev": "1-7130413a8c7c5f1de5528fe4d373045c"
}
}
],
"total_rows": 5,
"offset": 0
}
Show more







 Step 6: Deleting the database 



1. Delete the database.

try :
client.delete_database(databaseName)
except CloudantException:
print("There was a problem deleting '{0}'.n".format(databaseName))
else:
print("'{0}' successfully deleted.n".format(databaseName))
2. Review the basic error handling that was included to illustrate how problems can be caught and addressed.







 Step 7: Closing the connection to the service instance 



1. Disconnect the Python client application from the service instance.
2. Run the disconnect command.

client.disconnect()
Run the SHOW TEMPORAL HISTOGRAM command or by use the web console to view the space that is used by deleted rows per day or per range of days into the past to estimate the space that might be reclaimed.



 Viewing space usage with the SHOW TEMPORAL HISTOGRAM command 

SHOW TEMPORAL HISTOGRAM <TEMPORAL TABLE> [DAYSPERROW <number of days>]

Example:

show temporal histogram flight;
BASE_TIMESTAMP | STARTDAYSAGO | ENDDAYSAGO | DELETEDROWS | MBYTESUSED | USAGEPERCENT
----------------------------+--------------+------------+-------------+------------+--------------
2022-11-08 15:35:59.442782 | 1 | 0 | 503 | 144.230 | 19.23
2022-11-08 15:35:59.442782 | 2 | 1 | 0 | 0 | 0
2022-11-08 15:35:59.442782 | 3 | 2 | 451 | 110.294 | 14.71
2022-11-08 15:35:59.442782 | 4 | 3 | 913 | 218.529 | 29.14
2022-11-08 15:35:59.442782 | 5 | 4 | 0 | 0 | 0
2022-11-08 15:35:59.442782 | 6 | 5 | 389 | 88.235 | 11.76

The virtual [_SYS_START and _SYS_END columns](https://cloud.ibm.com/docs/netezza?topic=netezza-runningqueries_ttrowvalidity_tt) do not take up additional space in the (current or historical) rows of table. They are derived from other hidden fields that are already present in the on-disk rows.
mount -t nfs -o nfsvers=3 nfshou0201d-fz.service.softlayer.com:/IBM01SEV1414935_2 /mnt

The mount point information can be obtained from the File Storage for Classic Details page in the UI, with an API call - SoftLayer_Network_Storage::getNetworkMountAddress(), or by looking at the ibm_storage_file resource in Terraform.
3. Verify that the mount was successful by using the disk file system command.

 df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 25G 1.4G 22G 6% /
/tmpfs 1.9G 0 1.9G 0% /dev/shm
/dev/xvda1 97M 51M 42M 55%
4. Go to the mount point, and read/write files.

 touch /mnt/test
 ls -la /mnt
total 12
drwxr-xr-x 2 nobody nobody 4096 Sep 8 15:52 .
dr-xr-xr-x. 22 root root 4096 Sep 8 14:30 ..
-rw-r--r-- 1 nobody nobody 0 Sep 8 15:52 test
5. Make the configuration persistent by editing the file systems table (/etc/fstab). Add the remote share to the list of entries that are automatically mounted on startup:

sudo nano /etc/fstab

Add a line with the following syntax to the end of file.

(hostname):/(mount_point) /mnt nfs_version defaults 0 0

Example

nfsdal0501a.service.softlayer.com:/IBM01SV278685_7 /mnt nfsvers=3 defaults 0 0
6. Verify that the configuration file has no errors.

 mount -fav

If the command completes with no errors, your setup is complete.

If you're using NFS 4.1, add sec=sys to the mount command to prevent file ownership issues.
UNLIMITED_SSL_VPN_USERS_1_PPTP_VPN_USER_PER_ACCOUNT Unlimited SSL VPN Users ibmcloud sl order item-list 2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES 



The order command requires the following additional information:



* <lhbr_hostname> - For example, lhbr01.
* <root_domain> - For example, test.ibmcloud.local.
* <private_vlan_id> - For example, 3127648.



Then, the information is incorporated into the order command as shown in the following example:

"hardware":[{"hostname":"lhbr01","domain":"test.ibmcloud.local","primaryBackendNetworkComponent": {"networkVlan": {"id": 3127648}}}]

The order command also requires the definition of the disks and RAID for use in storageGroups. To get all the Raid Type options, use the following command:

ibmcloud sl call-api SoftLayer_Configuration_Storage_Group_Array_Type getAllObjects. A summary of the response of this command is shown in the following table:



Table 2. RAID IDs

 ID Description 

 1 RAID 0 
 2 RAID 1 
 3 RAID 5 
 4 RAID 6 
 5 RAID 10 
 9 JBOD 
 10 HOT_SPARE 
 11 GLOBAL_HOT_SPARE 
 21 Straight through connection to the onboard drive controller 



The specification requires two disks in RAID 1 (disks 0 and 1) and 8 x disks in RAID 6 (disks 2, 3, 4, 5, 6, 7, 8 and 9). The following command is used:

"storageGroups":[{"arrayTypeId": 2,"arraySize": 1000,"hardDrives": 0,1],"partitionTemplateId": 1},{"arrayTypeId": 4,"arraySize": 12000,"hardDrives": 2,3,4,5,6,7,8,9]}]
3 0 0 1 3:3:1:0 yes
4 0 0 2 4:4:2:0 yes
5 - - - ::: no
6 0 0 3 6:6:3:0 yes
7 0 0 3 7:7:3:0 yes

You can repeat the previous process for each core to disable Hyper-Threading Technology for the VM. When the VM has a lot of CPUs, this can be difficult. The following script is a very simple bash script to disable Hyper-Threading Technology on each core:

!/bin/bash
for vcpu in cat /sys/devices/system/cpu/cpu/topology/thread_siblings_list | cut -s -d- -f2 | cut -d- -f2 | uniq; do
echo 0 > /sys/devices/system/cpu/cpu$vcpu/online
done



 Enabling Hyper-Threading Technology for a specific core and associated CPU 

If you want to enable Hyper-Threading Technology again, you can do so by writing a 1 into the online field for each of the CPUs.

echo 1 > /sys/devices/system/cpu/cpu5/online





 Enabling Hyper-Threading Technology for all cores in the VM 

Alternatively, you can use the following simple bash script to enable Hyper-Threading Technology for the VM.

!/bin/bash
for vcpu in lscpu --extended | grep "no" | awk '{print $1}'; do
echo 1 > /sys/devices/system/cpu/cpu$vcpu/online
done







 Enabling and disabling Hyper-Threading Technology in my guest VM: Script 

You can also try this [script](https://github.com/seelam/Manage_Hyperthreading.sh), created by Wyatt Gorman, for enabling and disabling Hyper-Threading Technology. When you download and run the script, you get these options:

OPTIONS
-d | --disable Disable Hyper-Threaded vCPUs
-e | --enable Enable Hyper-Threaded vCPUs
-s | --show Show Hyper-Threading status
If the IBM Cloud CLI is connected to private.cloud.ibm.com, the Code Engine project behaves as if --endpoint is private. If the IBM Cloud CLI is connected to cloud.ibm.com, the Code Engine project behaves as if --endpoint is public.
8. If you did not create a new project and you selected an existing project, and you want your app to only be visible to the private endpoint, confirm the existing project supports applications with private visibility. Use the [ibmcloud ce project get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-get) command to verify the output for Application Private Visibility Supported is set to true. If the value is false, [contact IBM support](https://cloud.ibm.com/docs/codeengine?topic=codeengine-get-support) to enable this capability within your existing project.

ibmcloud ce project get -n myproject

Example output

Getting project 'myproject'...
OK

Name: myproject
ID: abcdabcd-abcd-abcd-abcd-f1de4aab5d5d
Status: active
Enabled: true
Application Private Visibility Supported: false
Selected: true
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Tue, 28 Sep 2021 05:12:16 -0500
Updated: Tue, 28 Sep 2021 05:12:19 -0500

Quotas:
Category Used Limit
App revisions 1 60
Apps 1 20
Build runs 1 100
Builds 2 100
Configmaps 2 100
CPU 0 64
Ephemeral storage 0 256G
Instances (active) 0 250
Instances (total) 0 2500
Job runs 0 100
Jobs 0 100
Memory 0 256G
Secrets 6 100
Subscriptions (cron) 0 100
* [Revision 2, released 6 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.10-rev-2-change-log)
* [Revision 1, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.10-rev-1-change-log)



* [Version 22.04](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nas22.04-change-log)



* [Revision 19, released 19 June 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-19-change-log)
* [Revision 18, released 21 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-18-change-log)
* [Revision 17, released 4 April 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-17-change-log)
* [Revision 16, released 21 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-16-change-log)
* [Revision 15, released 6 March 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-netapp-ontap-nasnetapp-ontap-nas-22.04-rev-15-change-log)
(*): RHEL 7.6 for SAP Solutions, RHEL 7.9 for SAP Solutions, RHEL 8.2 for SAP Solutions -- SLES 12 SP4, SLES 12 SP5, SLES 15, SLES 15 SP1, SLES 15 SP2, SLES 15 SP3

Please regard the supported operated systems mentioned in the footnotes.





 Bare Metal profile names 

The Bare Metal profile names are contextual and sequential. For more information, see [Understanding Bare Metal profile names](https://test.cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-bmhana-iaas-intel-bm-names)





 Storage specifications 



 Name HANA DB Size (TB) Storage Needed (1TB shared plus DB size data) Boot (Log) Storage Array (Data + Shared) 

 BI.S4.H2.1.5TB RAM + 1.5TB Persistent Memory 3 7 2x 960GB SSD (RAID 1) 8 x 1.9TB SSD (RAID 10) 
 BI.S4.H4.3TB RAM + 3TB Persistent Memory 6 13 2x 960GB SSD (RAID 1) 8 x 3.8TB SSD (RAID 10) 
 BI.S4.H8.6TB RAM + 6TB Persistent Memory 12 25 2x 960GB SSD (RAID 1) 8 x 7.68TB SSD (RAID 10) 
 1:2 DRAM:PMem 
 BI.S4.H2.768GB RAM + 1.5TB Persistent Memory 2.25 5.5 2x 960GB SSD (RAID 1) 6 x 1.9TB SSD (RAID 10) 
 BI.S4.H2.1.5TB RAM + 3TB Persistent Memory 4.5 10 2x 960GB SSD (RAID 1) 6 x 3.8TB SSD (RAID 10) 
 BI.S4.H2.768GB RAM + 3TB Persistent Memory 3.75 8.5 2x 960GB SSD (RAID 1) 10 x 1.9TB SSD (RAID 10)
The specification requires two disks in RAID 1 (disks 0 and 1) and 8 x disks in RAID 6 (disks 2, 3, 4, 5, 6, 7, 8 and 9). The following command is used:

"storageGroups":[{"arrayTypeId": 2,"arraySize": 1000,"hardDrives": 0,1],"partitionTemplateId": 1},{"arrayTypeId": 4,"arraySize": 12000,"hardDrives": 2,3,4,5,6,7,8,9]}]



* The arrayTypeId": 2,"arraySize": 1000 represents the total capacity of 2 x 1 TB drives in RAID 1 in GB.
* The "arrayTypeId": 4,"arraySize": 12000 represents the total capacity of 8 x 2 TB drives in RAID 6 in GB.



Now, all the required information is in place for the sample order. To verify this example, use the following command:

ibmcloud sl order place 
2U_DUAL_INTEL_XEON_PROCESSOR_SCALABLE_FAMILY_12_DRIVES 
DALLAS10 
INTEL_INTEL_XEON_5120_2_20,
OS_RHEL_8_X_64_BIT_PER_PROCESSOR_LICENSING,
RAM_64_GB_DDR4_2133_ECC_NON_REG,
DISK_CONTROLLER_RAID,
HARD_DRIVE_1_00_TB_SATA_2,HARD_DRIVE_1_00_TB_SATA_2,
HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,HARD_DRIVE_2_00_TB_SATA_2,
BANDWIDTH_0_GB,