vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The bx2d-metal-192x768 profile provides mirrored 960 GB SATA M.2 drives as boot storage and 16 3.2 TB U.2 NVMe SSDs as secondary local storage to support vSAN, or user-managed RAID.



VPC Block Storage is not supported. VPC File Storage is compatible when it becomes generally available.

Currently, IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access. For more information about file storage, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).

Encryption in transit is not supported on Bare Metal Servers for VPC.





 What is required to set up my Bare Metal Servers for VPC? 

When you are planning to create the bare metal servers, you can go through the configuration checklist on [Planning for bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers).





 What regions are Bare Metal Servers for VPC available? 

Bare metal servers are available in eu-de, us-east, and us-south regions.





 Do I need to configure multiple network interfaces on a bare metal server to support the full 100 Gbps bandwidth? 

No. You can add as many or as few vNICs as you need. Every interface can take advantage of the 100 Gbps bandwidth, but the total aggregate is 100 Gbps for each server. Meaning that the bandwidth is shared by all the vNICs. For more information about networking on bare metal, see [Networking overview for bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-network).





 How many NVMe drives does a bare metal server support? 

The number NVMe drives that are supported depends on the profile that you select.
* The bx2-metal-192x768 profile provides mirrored 960 GB SATA M.2 drives as boot storage only.
* The bx2d-metal-192x768 profile provides mirrored 960 GB SATA M.2 drives as boot storage and 16 3.2 TB U.2 NVMe SSDs as secondary local storage to support vSAN, or user-managed RAID.



VPC Block Storage is not supported. VPC File Storage is compatible when it becomes generally available.

Currently, IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access. For more information about file storage, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).

Encryption in transit is not supported on Bare Metal Servers for VPC.
* What is required to set up my Bare Metal Servers for VPC?

When you are planning to create the bare metal servers, you can go through the configuration checklist on [Planning for bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers).
* What regions are Bare Metal Servers for VPC available?

Bare metal servers are available in eu-de, us-east, and us-south regions.
* Do I need to configure multiple network interfaces on a bare metal server to support the full 100 Gbps bandwidth?

No. You can add as many or as few vNICs as you need. Every interface can take advantage of the 100 Gbps bandwidth, but the total aggregate is 100 Gbps for each server. Meaning that the bandwidth is shared by all the vNICs. For more information about networking on bare metal, see [Networking overview for bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-network).
Storage overview for Bare Metal Servers for VPC 

All profiles of Bare Metal Servers for VPC provide one 0.96 TB SATA M.2 mirrored SSD as the boot disk. Profile bx2d-metal-192x768 provides an extra set of NVMe (Non-Volatile Memory Express) U.2 solid-state drives (SSD) as secondary local storage. NVMe SSDs provides fast and affordable storage to support options such as VMware vSAN, or customer-managed RAID.

Storage for Bare Metal Servers for VPC is unmanaged. You are responsible for encryption and backing up your data.

The following network-attached storages are not supported:



*  Block Storage for VPC
*  File Storage for VPC
VPC Storage - <br>5 IOPS per GB tier It is designed for high I/O intensity workloads that are characterized by a large percentage of active data, such as transactional and other performance-sensitive databases. 99.999999999% <br>(11 9's) 99.999% <br>(5 9's) Provider-managed AES-256 encryption + Customer-managed encryption 
 VPC Storage - <br>10 IOPS per GB tier It is designed for demanding storage workloads such as data-intensive workloads created by NoSQL databases, data processing for video, machine learning, and analytics. 99.999999999% <br>(11 9's) 99.999% <br>(5 9's) Provider-managed AES-256 encryption + Customer-managed encryption 





 Durability 

Think of durability as a measurement of how healthy and resilient your data is. Durability in File Storage for Classic means that your data is stored consistent and intact without any signs of data decay, influence of drive failures, or any other form of corruption. 99.999999999% (11 nines) durability means that if you store 10 million files, then you expect to lose one file every 10000 years.

When people hear the word durability, most of them think of hardware failures of storage, compute, and network components that might cause data loss. In File Storage for Classic, your data is protected against drive failures and numerous type of disk errors that otherwise might negatively impact data durability and data integrity. The data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.

Other than physical failure, a common source of data loss is accidental deletion or modifications of files by users. File Storage for Classic is only accessible to authorized hosts within your network. You control who can access it. Another measure to protect against accidental deletion and modification of files by users is a snapshot. If a user accidentally modifies or deletes crucial data from a volume, the data can be easily and quickly restored from a snapshot copy.
VPC Storage - <br>5 IOPS per GB tier It is designed for high I/O intensity workloads that are characterized by a large percentage of active data, such as transactional and other performance-sensitive databases. 99.999999999% <br>(11 9's) 99.999% <br>(5 9's) Provider-managed AES-256 encryption + Customer-managed encryption 
 VPC Storage - <br>10 IOPS per GB tier It is designed for demanding storage workloads such as data-intensive workloads created by NoSQL databases, data processing for video, machine learning, and analytics. 99.999999999% <br>(11 9's) 99.999% <br>(5 9's) Provider-managed AES-256 encryption + Customer-managed encryption 





 Durability 

Think of durability as a measurement of how healthy and resilient your data is. Durability in Block Storage for Classic means that your data is stored consistent and intact without any signs of data decay, influence of drive failures, or any other form of corruption. 99.999999999% (11 nines) durability means that if you store 10 million files, then you expect to lose one file every 10000 years.

When people hear the word durability, most of them think of hardware failures of storage, compute, and network components that might cause data loss. In Block Storage for Classic, your data is protected against drive failures and numerous type of disk errors that otherwise might negatively impact data durability and data integrity. The data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.

Other than physical failure, a common source of data loss is accidental deletion or modifications of files by users. Block Storage for Classic is only accessible to authorized hosts within your network. You control who can access it. Another measure to protect against accidental deletion and modification of files by users is a snapshot. If a user accidentally modifies or deletes crucial data from a volume, the data can be easily and quickly restored from a snapshot copy.
VMware Shared Reserved <br><br> * The vCPU and RAM virtual data center reservations are pre-allocated and their availability is guaranteed.<br> <br> <br> <br> <br> * vCPU and RAM resources can be increased and decreased later as required.<br> * The amount of storage that can be allocated and used in the virtual data center is unlimited. Charges are hourly based on GB of allocated storage.<br> * The amount of inbound and outbound public networking is unlimited. Public outbound bandwidth is charged per GB.<br> <br> <br> <br> <br><br><br> 





 Price breakdown 



 Usage 

Metering is for the full potential size of the resource for the time period that the resource is used.

For example, a single-zone on-demand virtual data center is created with a resource limit of 100 vCPU and 800 GB RAM. The data center has no VMs running on it, so you do not receive a charge for the vCPU and RAM. If an 8 vCPU with 8 GB virtual machine (VM) is started, metering is calculated for the size of that VM. If the VM uses fewer resources than the ones assigned to it, metering is applicable to the full size of the VM.





 Allocation 

Metering is applicable to the full potential size of the resource for the life of the resource.

For example, a single zone reserved virtual data center is created with a resource allocation of 100 vCPU and 800 GB RAM and no VMs are created or running on it. Metering is applicable to 100 vCPU and 800 GB RAM.





 Monthly peak metric usage 

The maximum value of the metric used over a full month.

For example, a single zone reserved virtual data center is created with 100 vCPU and 800 GB RAM. Later in the month, the data center is reduced to 50 vCPU and 400 GB RAM. The monthly peak usage is 100 vCPU and 800 GB RAM.





 Hourly peak metric usage 

The maximum value of the metric used over an hour. For example, if 100 vCPU is used for a minute of the hour with 0 vCPU used for the other 59 mins, the hourly peak metric usage is 100 vCPU.
Ordering virtual data centers 

IBM Cloud® for VMware Solutions Shared offers either a standardized or customizable deployment option of VMware® virtual data center environments. Choose the On-demand or Reserved option.



 Requirements for virtual data centers 

If you are ordering a virtual data center for the first time, ensure that you completed the tasks in the Before you begin section on the ordering page. For more information, see [Setting up your environment for your first order](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklist).





 System settings 

You must specify the following system settings when you order a VMware Shared virtual data center.



 Pricing plans 

The pricing plan is based on your selection of On-demand or Reserved.



 On-demand 

For the On-demand offering, virtual data center virtual CPU (vCPU) and RAM are allocated as needed. The amount of time that the allocation takes depends on global usage of the virtual data center vCPU and RAM.



* The limits that are established for the amount of vCPU and RAM are maximum values that can be used at any time.
* You can increase and decrease the vCPU and RAM resources on a virtual data center later as required.
* The price is calculated hourly and it is based on the resource usage in the virtual data center.
* The amount of storage that can be allocated and used in the virtual data center is limited to 200 TB for each storage policy. Charges are calculated per hour and are based on GB of allocated storage.
* The amount of inbound and outbound public networking is unlimited. Public outbound bandwidth is charged per GB.







 Reserved 

For the Reserved offering, the vCPU and RAM virtual data center reservations are pre-allocated and their availability is guaranteed.



* The price is calculated monthly for the full reservation and it is based on the allocation size of the virtual data center.
* vCPU and RAM resources can be increased and decreased later as required.
* The amount of storage that can be allocated and used in the virtual data center is unlimited. Charges are calculated per hour and are based on GB of allocated storage.
* The amount of inbound and outbound public networking is unlimited.
With Sustained Usage Discount, the more a server is used, the less the cost per hour.





 Storage specifications 

When the virtual server profiles for SAP HANA are initially provisioned, the servers all have one pre-configured volume (vda) attached with the following basic layout:



Table 4. Storage configuration of the default virtual server deployment (boot volume)

 File system Partition Storage type Size (GB) Nr. of <br>IOPS 

 / vda1 Pre-configured boot volume 100 3,000 
 /boot vda2 Pre-configured boot volume 0.25 3,000 





 IBM® Cloud Block Storage for Virtual Private Cloud 

[IBM® Cloud Block Storage for Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about) volumes for Virtual Servers can be created based on different volume profiles that provide different levels of IOPS per gigabyte (IOPS/GB). For more information, see [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers).

You must consider the total IOPS required for your installation and the performance characteristics of your database. One option is to collocate multiple directories into a single large volume with high IOPS, versus isolating directories into individual small volumes with an insufficient number of IOPS for the workload characteristics.

For an overview of all available storage profiles, see [VPC Block Storage Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles).





 Storage for SAP HANA - single-node 

To fulfill the KPIs defined by SAP HANA, each profile needs different storage volumes that are listed in details in the following sections. These configurations are mandatory storage configurations, not sample storage configurations, because they are the tested and certified storage layouts that comply with SAP HANA Tailored Data Center Integration (TDI) Phase 5. It is highly recommended to stick to these specific specifications.
For more information, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). Data volumes can be detached and attached to virtual servers as required. Data volumes are encrypted by default with IBM-managed encryption. You can also encrypt data volumes using your own root keys. Refer to [Block storage capacity and performance](https://cloud.ibm.com/docs/vpc?topic=vpc-capacity-performance) advice on choosing the optimal block storage volume size and performance level.
* Instance Storage - Optionally, the virtual server can include [Instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) which provides solid state drives directly attached to the virtual server instance when the instance is provisioned. Instance storage disk provides fast, temporary storage to improve performance of many workloads including transactional processing. The data stored on instance storage is ephemeral, meaning it is tied directly to the lifecycle of the instance. The instance storage disk is automatically created and destroyed with the instance. Instance storage data is not lost, however, when an instance is rebooted. If performance is a concern then MS SQL Server tempdb can be placed on instance storage



For more information, see [About Block Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about).

Under rare maintenance operations, a live migration of the virtual server to a new host may necessary. The virtual server will experience a brief pause of around 10 seconds, and in some cases up to 30 seconds. The virtual server instance is not rebooted as part of this process. However, for virtual servers with Instance Storage, then the server will be restarted. Refer to [Understanding Cloud Maintenance Operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance) for further information.







 Connecting to the server
Adding File Storage for VPC to apps 

IBM Cloud® Kubernetes Service provides pre-defined storage classes for File Storage for VPC that you can use to provision File Storage for VPC with a specific configuration.

Every storage class specifies the type of File Storage for VPC that you provision, including available size, IOPS, file system, and the retention policy.

After you provision a specific type of storage by using a storage class, you can't change the type, or retention policy for the storage device. However, you can [change the size and the IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) if you want to increase your storage capacity and performance. To change the type and retention policy for your storage, you must create a new storage instance and copy the data from the old storage instance to your new one.

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. Decide on a storage configuration by reviewing the storage class reference.

For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-managing). If you don't find what you are looking for, consider creating your own customized storage class. To get started, check out the [customized storage class samples](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-managingstorage-file-vpc-custom-sc).
2. List available storage classes in Red Hat OpenShift on IBM Cloud.

oc get storageclasses | grep file

Example output

NAME TYPE
ibmc-vpc-file-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-3iops-tier vpc.file.csi.ibm.io
accessModes:
- ReadWriteMany
resources:
requests:
storage: 24Gi
storageClassName: ibmc-file-silver

Example for using the custom storage class.

The following .yaml file creates a claim that is named mypvc of the storage class ibmc-file-retain-custom, billed "hourly", with a gigabyte size of 45Gi and IOPS of "300".

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mypvc
labels:
billingType: "hourly"
region: us-south
zone: dal13
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 45Gi
iops: "300"
storageClassName: ibmc-file-retain-custom
Show more

name
: Enter the name of the PVC.

billingType
: Specify the frequency for which your storage bill is calculated, "monthly" or "hourly". If you don't specify a billing type, the storage is provisioned with an hourly billing type.

region
: Optional: Specify the region where you want to provision your File Storage for Classic. To connect to your storage, create the storage in the same region that your cluster is in. If you specify the region, you must also specify a zone. If you don't specify a region, or the specified region is not found, the storage is created in the same region as your cluster. To get the region for your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID> and look for the region prefix in the Master URL, such as eu-de in https://c2.eu-de.containers.cloud.ibm.com:11111. Instead of specifying the region and zone in the PVC, you can also specify these values in a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_multizone_yaml).
Adding File Storage for VPC to apps 

IBM Cloud® Kubernetes Service provides pre-defined storage classes for File Storage for VPC that you can use to provision File Storage for VPC with a specific configuration.

Every storage class specifies the type of File Storage for VPC that you provision, including available size, IOPS, file system, and the retention policy.

After you provision a specific type of storage by using a storage class, you can't change the type, or retention policy for the storage device. However, you can [change the size and the IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) if you want to increase your storage capacity and performance. To change the type and retention policy for your storage, you must create a new storage instance and copy the data from the old storage instance to your new one.

Before you begin: [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. Decide on a storage configuration by reviewing the storage class reference.

For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managing). If you don't find what you are looking for, consider creating your own customized storage class. To get started, check out the [customized storage class samples](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingstorage-file-vpc-custom-sc).
2. List available storage classes in IBM Cloud Kubernetes Service.

kubectl get storageclasses | grep file

Example output

NAME TYPE
ibmc-vpc-file-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-3iops-tier vpc.file.csi.ibm.io
* If you create a job to process information from IBM Cloud Object Storage with one job instance and that runs for an hour and uses 4 GB of memory, you are billed for 1 CPU hour and 4 GB hours.
* If you scale the same job to 4 instances and then it completes in 15 minutes, you are charged for 4 vCPU and 16 GB for .25 hours.



For valid CPU and memory combinations, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).

Note that the time that it takes to pull your image or to build it from source code is included in the billable time.





 Build pricing 

When you build an image from source code to deploy as an app or run as a job, you are billed for the memory and vCPU usage time that the build consumes. However, this charge is separate from the charges that you might incur when you use the resulting image in an application or job run. You are not charged for your build configuration.

Builds are classified as small, medium, large, and xlarge size. The size of the build defines how CPU cores, memory, and disk space are assigned to the build when it runs. A smaller build is less expensive, but typically also slower due to the lower number of CPU cores. In addition, the memory and disk requirements of your build might cause the build to fail if you choose too small a size. For more information about build size, see [Determine the size of the build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-size).

Note that the time that it takes to pull source code and push your built image is included in the billable time.