vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Creates a storage pool called sqldatapool.
* Creates a virtual disk in this pool called sqldata for striping (-ResiliencySettingName simple).
* The virtual disk is initialized with a GPT partition and assigned a drive letter of D.
* The virtual disk is formatted with the NTFS filesystem with a block size of 64KB and assigned a label of SQLDATA.



$dataserial = "<SerialNumber>"
New-StoragePool -FriendlyName "sqldatapool" -StorageSubsystemFriendlyName "Windows Storage" -PhysicalDisks (Get-PhysicalDisk -SerialNumber $dataserial) | New-VirtualDisk -FriendlyName "sqldata" -Interleave 65536 -NumberOfColumns 1 -ResiliencySettingName simple –UseMaximumSize | Initialize-Disk -PartitionStyle GPT -PassThru | New-Partition -DriveLetter "D" -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "SQLDATA" -AllocationUnitSize 65536 -Confirm:$false -UseLargeFRS

If you are using multiple data volumes for increased performance, then this PowerShell command must be modified. An example for 2 disks:

New-StoragePool -FriendlyName "sqldatapool" -StorageSubsystemFriendlyName "Windows Storage" -PhysicalDisks (Get-PhysicalDisk | where {($_.SerialNumber -eq "<Disk1_SerialNumber>") -or ($_.SerialNumber -eq "<Disk2_SerialNumber>")}) | New-VirtualDisk -FriendlyName "sqldata" -Interleave 65536 -NumberOfColumns 2 -ResiliencySettingName simple –UseMaximumSize | Initialize-Disk -PartitionStyle GPT -PassThru | New-Partition -DriveLetter "D" -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "SQLDATA" -AllocationUnitSize 65536 -Confirm:$false -UseLargeFRS
type = "Endurance"
datacenter = "dal05"
capacity = 20
iops = 0.25
os_format_type = "Linux"

 Optional fields
allowed_virtual_guest_ids = [ 27699397 ]
allowed_ip_addresses = ["10.40.98.193", "10.40.98.200"]
snapshot_capacity = 10
hourly_billing = true
}

For more information about the arguments and attributes, see [ibm_storage_block](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_block).
For more information about the architecture, see [Overview of VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_overview).





 Technical specifications for vCenter Server instances 

The availability and pricing of standardized hardware configurations might vary based on the IBM Cloud data center that is selected for deployment.

The following components are included in your vCenter Server instance.



 Bare metal server 

You can order three or more bare metal servers on the consolidated or management cluster, and optionally two or more bare metal servers on the workload cluster.

If you plan to use vSAN storage, the configuration requires a minimum of four bare metal servers.

The following configurations are available:



* Cascade Lake - 4-CPU Intel® Cascade Lake generation servers (Quad Intel Xeon® 6200/8200 series) or 2-CPU Intel Cascade Lake generation servers (Dual Intel Xeon 4200/5200/6200/8200 series) with your selected RAM size.
* SAP-certified Cascade Lake - 2-CPU Intel Cascade Lake generation servers (Dual Intel Xeon 5200/6200/8200 series).







 Networking 

The following networking components are ordered:



* 10 Gbps dual public and private network uplinks.
* Three VLANs (Virtual LANs) - one public and two private.
* (NSX-T only) One overlay network with a T1 and T0 router for potential east-west communication between local workloads that are connected to layer 2 (L2) networks. This network is deployed as a sample routing topology, which you can modify, build on, or remove.
* (NSX-V only) One VXLAN (Virtual eXtensible LAN) with DLR (Distributed Logical Router) for potential east-west communication between local workloads that are connected to layer 2 (L2) networks. The VXLAN is deployed as a sample routing topology, which you can modify, build on it, or remove it. You can also add security zones by attaching extra VXLANs to new logical interfaces on the DLR.
* VMware NSX Edge Services Gateways (four for NSX-T and two for NSX-V):
Understanding high availability and disaster recovery for DNS Services 

All IBM Cloud® general availability (GA) offerings have a Service Level Agreement of 99.99% availability. IBM Cloud® DNS Services is a GA service that is offered globally. The public API endpoints for DNS configuration are available globally through a global load balancer in two MZRs (Multi Zone Regions) of IBM Cloud, providing high availability. The regions are Dallas and Washington, DC. If one region experiences an outage, the global load balancer ensures that the API traffic gets routed to another region. For instance, if the Dallas region experiences an outage, requests get routed to the geographically nearest region, in this case, Washington, DC.

The DNS resolvers are distributed around the world in multiple MZRs for optimizing latencies and providing high availability. If one region experiences an outage, the DNS resolvers route DNS requests to another region. The data is replicated to the following regions for latency optimization and high availability:



*  Dallas (us-south)
*  Washington, D.C. (us-east)
*  London (eu-gb)
*  Frankfurt (eu-de)
*  Osaka (jp-osa)
*  Tokyo (jp-tok)
*  Toronto (ca-tor)
*  Sydney (au-syd)
*  Sao Paulo (br-sao)



Custom resolvers are deployed to two locations by default, to ensure high availability.

See [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud. You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slasslas).
Each storage node has multiple paths to its own Solid-State Drives and its partner node's SSDs as well. This configuration protects against path failure, and also controller failure because the node can still access its partner's disks seamlessly. For more information, see [Availability and Durability of Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-storageavailability).





 How can I identify a Block Storage for Classic volume from my OS? 

Various reasons exist for why you would want to look up the LUN ID of the attached storage volumes on the Compute host. For example, you might have multiple storage devices that are mounted on the same host with the same volume sizes. You want to detach and decommission one of them. However, you are not sure how to correlate what you see on your Linux® host with what you see in the console. Another example might be that you have multiple Block Storage for Classic volumes that are attached to an esxi server. You want to expand the volume size of one of the LUNs, and you need to know the correct LUN ID of the storage to do that. For OS-specific instructions, click one of the following links.



* [Viewing LUN information in Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-identifyLUNidentifyLUNLin)
* [Viewing LUN information in Windows®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-identifyLUNidentifyLUNWin)
* [Viewing LUN information in VMWare®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-identifyLUNidentifyLUNVMware)







 Can I get storage performance metrics (IOPS or latency) from the Support teams? 

IBM Cloud® does not provide storage performance IOPS and latency metrics. Customers are expected to monitor their own Block Storage for Classic devices by using their choice of third-party monitoring tools.

The following examples are utilities that you might consider to use to check performance statistics.
)<br> * [ibm_is_backup_policy_plans](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_backup_policy_plans)<br> * [ibm_is_bare_metal_server](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server)<br> * [ibm_is_bare_metal_server_disk"](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_disk)<br> * [ibm_is_bare_metal_server_disks](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_disks)<br> * [ibm_is_bare_metal_server_initialization](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_bare_metal_server_initialization)<br> * [ibm_
: Buckets can now be created in an AP Cross Region configuration. Data stored in these buckets is distributed across the Seoul, Tokyo, and Hong Kong data centers. More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints).

New feature!
: Users can run SELECT SQL queries directly against structured data objects using IBM Cloud® Data Engine. More information can be found in the [Data Engine documentation](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overview).





 7 March 2018 

New feature!
: Users who upload or download files using the web-based console have the option to use Aspera high-speed transfer for these operations via a browser plug-in. This allows for transfers of objects larger than 200MB, and also allows for greater control and visibility of uploads and downloads. Additional information can be found in the [Uploading Data](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-aspera) documentation. Downloads using Aspera high-speed incur additional egress charges. For more information, see the [pricing page](https://www.ibm.com/cloud/object-storage).





 11 February 2018 

New location!
: Buckets can now be created in a Single Data Center configuration in Toronto, Canada and Melbourne, Australia. This allows for lower latency when accessing storage from compute resources co-located within the same data center, or for data requiring a specific geographic location. More information can be found in the [Select Regions and Endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints) documentation.





 8 August 2017 

Introducing IBM Cloud Object Storage
: Object Storage is a highly available, durable, and secure platform for storing unstructured data.
Table 3. Options for SAP-certified Cascade Lake - NetWeaver and HANA

 CPU model SAP certification Cores GHz RAM Storage type 

 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW192) NetWeaver 32 2.3 192 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW384) NetWeaver 32 2.3 384 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 6248 processor (Cascade Lake, BI.S4.NW768) NetWeaver 40 2.5 768 GB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8260 processor (Cascade Lake, BI.S4.NW768_v2) Netweaver 48 2.4 768 GB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.NW1500) Netweaver 56 2.7 1.5 TB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.NW3000) Netweaver 56 2.7 3 TB Up to 12 Drivers 
 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.H2.192) HANA and NetWeaver 32 2.3 192 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.H2.384) HANA and NetWeaver 32 2.3 384 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 6248 processor (Cascade Lake, BI.S4.H2.768) HANA and NetWeaver 40 2.5 768 GB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H2.1500) HANA and NetWeaver 56 2.7 1.5 TB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H2.3000) HANA and NetWeaver 56 2.7 3 TB Up to 12 Drivers 
 Quad Intel Xeon Platinum 8280M processor (Cascade Lake, BI.S4.H4.3000) HANA and NetWeaver 112 2.7 3 TB Up to 24 Drivers
* --logging-datapath-active: Enable or disable datapath logging for this load balancer. Datapath logging is applicable only for application load balancer. One of: false, true.
* --subnets: Comma-separated ID or name of the subnets to provision this load balancer. Load balancer availability depends on the availability of the zones that the specified subnets reside in. Currently, only the load balancer in the application family supports this option.
* --dns-instance-crn: The CRN of the DNS instance that is associated with the DNS zone.
* --dns-zone-id: ID of the DNS Zone.
* --reset-dns: Specify this flag to remove any existing DNS records.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is load-balancers 

List all load balancers.

ibmcloud is load-balancers [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command options 



* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --all-resource-groups: Query all resource groups.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------









 Network ACLs 



 ibmcloud is network-acls 

List all network ACLs.
BI.S4.H4.3000 IBM Cloud Bare Metal (Local SSD) 112 224 3,072 285,970 Intel Cascade Lake SP 13.71 Appliance OLAP/OLTP Classic 
 BI.S4.H4.6000 IBM Cloud Bare Metal (Local SSD) 112 224 6,144 285,970 Intel Cascade Lake SP 27.43 Appliance OLAP/OLTP, Scale-Out Classic 
 BI.S4.H8.6000 IBM Cloud Bare Metal (Local SSD) 224 448 6,144 550,670 Intel Cascade Lake SP 13.71 Appliance OLAP/OLTP, Scale-Out Classic 
 BI.S4.H8.12000 IBM Cloud Bare Metal (Local SSD) 224 448 12,288 550,670 Intel Cascade Lake SP 27.43 Appliance/TDI OLAP/OLTP, Scale-Out Classic 
 bx2d-metal-96x384 IBM Cloud Bare Metal (Local SSD) 48 96 384 124,130 Intel Cascade Lake SP 4.00 Appliance OLAP/OLTP VPC 
 bx2d-metal-192x768 IBM Cloud Bare Metal (Local SSD) 96 192 768 255,800 Intel Cascade Lake SP 4.00 Appliance OLAP/OLTP VPC 
 mx2d-metal-96x768 IBM Cloud Bare Metal (Local SSD) 48 96 768 127,620 Intel Cascade Lake SP 8.00 Appliance OLAP/OLTP VPC 
 mx2-8x64 IBM Cloud Virtual Server -- 8 64 10,283 Intel Cascade Lake SP 8.00 TDI SAP Business One for HANA VPC 
 mx2-16x128 IBM Cloud Virtual Server -- 16 128 20,565 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC 
 mx2-32x256 IBM Cloud Virtual Server -- 32 256 41,130 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC 
 mx2-48x384 IBM Cloud Virtual Server -- 48 384 56,970 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC
The intermediate dataset is displayed below the query on the Results tab associated with the Job







 Step 4: Combine Jupyter Notebooks with Data Engine 

In this section, you will use the Data Engine client within a Jupyter Notebook. This re-uses the data stored on Object Storage in a data analysis tool. The combination also creates datasets that are automatically stored in Object Storage that can then be accessed by applications and tools serving line of business users.

First, create a new Jupyter Notebook and service connections in Watson Studio.



1. Access the data-lake-studio Watson Studio service instance from the [Resource List](https://cloud.ibm.com/resources) under the AI / Machine Learning section.



* Click Launch in IBM Cloud Pak for Data.
* Click Create a Project followed by Create an empty project.
* Use Data lake project as Name.
* Under Define storage select data-lake-cos.
* Click Create.



2. In the resulting project, add an access token to the project.



* Click the Manage tab.
* Click Access control on the left.
* Click the Access tokens tab.
* Click New access token.
* Enter a name and select Editor for access role and click Create.



3. Click the Assets tab and then click New asset and Connection.



* From the list of services select IBM Cloud Data Engine.
* In the dialog enter SQLQuery as Name.
* As CRN copy in the Data Engine instance CRN. You can obtain it by clicking in the [Resource List](https://cloud.ibm.com/resources) right to the service name. data-lake-sql. The pop-up has the CRN and a copy button.
* Fill in cos://us-south/<your-bucket-name> as Target. Replace us-south and <your-bucket-name> similar to how you did it earlier.
* As Password under Credentials use the API key which you created earlier. The value is from the field apikey.
* Finally, click Create.



4. Now create the notebook. Click New asset and Jupyter notebook editor.
Storage types 

The Spectrum Scale solution offers three different storage types: scratch, persistent, and evaluation.



 Scratch storage 

A scratch configuration uses virtual server instances with instance storage. If a virtual server instance with instance storage is powered off, all data stored on the instance storage volumes is rendered inaccessible after a subsequent power up of the virtual server instance. Therefore, use of scratch storage is not recommended for long running or mission-critical workloads.





 Persistent storage 

A persistent configuration uses bare metal servers with locally attached NVMe storage. In addition to higher resilience, persistent storage provides higher performance and capacity than scratch storage.





 Evaluation storage 

Evaluation storage is based on Spectrum Scale Developer Edition. This option supports all advanced features of Spectrum Scale Data Management Edition but is limited to 12TB of storage.

With evaluation storage, you can try out the Spectrum Scale solution on IBM Cloud® without a license. The automated deployment is done on virtual server instances with instance storage, with Spectrum Scale Developer Edition packages, and is available only for prototyping and testing purposes.





 Storage type comparison 



Table 1. Spectrum Scale storage types comparison
The first row of the table describes a Spectrum Scale feature, and the first column describes the specifics of that feature as it pertains to scratch storage. The second column describes the specifics of persistent storage, and the third column describes the specifics of evaluation storage, which map to the Spectrum Scale feature in each row.

 Scratch (default) Persistent Evaluation 

 Storage cluster nodes Virtual server instances Bare metal servers Virtual server instances 
 Compute cluster nodes Virtual server instances Virtual server instances Virtual server instances 
 Storage cluster node count Min 3 <br>Max 18 Min 3 <br>Max 10 Min 3 <br>Max 18 
 Compute cluster node count Min 3 <br>Max 64 Min 3 <br>Max 64 Min 3 <br>Max 64 
 Storage cluster OS support RHEL 8.4 <br>(custom or stock images) RHEL 8.4 <br>(stock image) RHEL 8.4 <br>(custom image)
If you deploy the cluster to a different IBM Cloud data center or IBM Cloud infrastructure pod, three extra VLANs are ordered for use with the ordered IBM Cloud bare metal servers.





 Cascade Lake 

For Cascade Lake servers, you can choose the following CPU models and a supported RAM size, which depends on the NSX networking solution.

NSX-T instances



Table 1. Options for Cascade Lake bare metal servers - NSX-T instances

 CPU model Cores GHz RAM 

 Dual Intel Xeon Silver 4210 processor 20 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6248 processor 40 2.5 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6250 processor 16 3.9 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Platinum 8260 processor 48 2.4 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Quad Intel Xeon Gold 6248 processor 80 2.5 384 GB, 768 GB, 1.5 TB, 3 TB 
 Quad Intel Xeon Platinum 8260 processor 96 2.4 384 GB, 768 GB, 1.5 TB, 3 TB 







 SAP-certified Cascade Lake 

For SAP-certified Cascade Lake servers, you can select from the following configurations:



Table 2. Options for SAP-certified Cascade Lake - NetWeaver and HANA

 CPU model SAP certification Cores GHz RAM Storage type 

 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW192) NetWeaver 32 2.3 192 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW384) NetWeaver 32 2.3 384 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 6248 processor (Cascade Lake, BI.S4.NW768) NetWeaver 40 2.5 768 GB Up to 12 Drivers
About 

[Understanding IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-overviewoverview)



* [What is IBM Cloud Kubernetes Service and how does it work?](https://cloud.ibm.com/docs/containers?topic=containers-overviewwhat-is-overview)
* [What is Kubernetes?](https://cloud.ibm.com/docs/containers?topic=containers-overviewwhat-is-kube-overview)
* [What are containers?](https://cloud.ibm.com/docs/containers?topic=containers-overviewwhat-are-containers-overview)
* [What compute host infrastructure does the service offer?](https://cloud.ibm.com/docs/containers?topic=containers-overviewwhat-compute-infra-is-offered)
* [Related resources](https://cloud.ibm.com/docs/containers?topic=containers-overviewkubernetes-resources)



[Benefits and service offerings](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovcs_ov)



* [Benefits of using the service](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovbenefits)
* [Comparison of offerings and their combinations](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovdifferentiation)
* [Comparison of free and standard clusters](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovcluster_types)
* [Comparison between Red Hat OpenShift and community Kubernetes clusters](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovopenshift_kubernetes)



[Supported infrastructure providers](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providersinfrastructure_providers)
"tcp://1.2.3.4:23",
"tcp://1.2.3.4:24"
] ! ! ,
"proxy_protocol": false,
"ip_firewall": false,
"edge_ips": {
"type": "dynamic",
"connectivity": "all"
},
"tls": "full",
"traffic_type": "direct"
}

{
"protocol": "tcp/22",
"dns": {
"type": "CNAME",
"name": "glb.example.com"
},
"origin_dns": {
"name": "name-to-glb.example.com"
},
"origin_port": 22,
"proxy_protocol": false,
"ip_firewall": false,
"edge_ips": {
"type": "dynamic",
"connectivity": "all"
},
"tls": "full",
"traffic_type": "direct"
}
Show more
-s, --json-str: Deprecated. The JSON data describing a range application.-j, --json-file: Deprecated. A file contains input JSON data.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-range-app-options" "> --><-- <section "id="section-update-range-app-examples" "> --> Examples Update range app ea95132c15732412d22c1476fa83f27a.