vania-janet/multiturn-rag-retrieval-data huggingface dataset:
How volume bandwidth is allocated 

Bandwidth that is available to the VSI is split between attached block storage volumes and networking. The initial volume and network bandwidth allocation depends on the [instance profile](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles) and the bandwidth ratio that you selected for your instance.

The allocation of the instance's total bandwidth can be adjusted, balancing between network bandwidth and volume bandwidth. If you do not specify the initial volume and network bandwidth allocation, then 25% of total instance bandwidth is allocated to volume bandwidth and 75% is allocated to network bandwidth.

The maximum volume bandwidth is the highest potential bandwidth that can be allocated to the volume when it is attached to an instance. In cases where the total maximum bandwidth of attached volumes exceeds the amount that is available on the instance, the bandwidth for each volume attachment is set proportionally. The bandwidth is allocated based on the corresponding volume's maximum bandwidth.

The volume bandwidth available to the instance is apportioned on a per-volume basis. The bandwidth is assigned per volume, not shared between volumes.

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles).





 How block size affects performance 

IOPS value is based on a 16 KB block size (for all the tiers) with a 50-50 read/write random workload. Each 16 KB of data read/written counts as one read/write operation; a single write of less than 16 KB counts as a single write operation.

Baseline throughput is determined by the number of IOPS multiplied by the throughput multiplier. The throughput multiplier is 16 KB for 3 IOPS/GB or 5 IOPS/GB tiers, or 256 KB for 10 IOPS/GB or custom IOPS tiers. The higher the IOPS that you specify, the higher the throughput. Maximum throughput is 1024 MBps.

The application I/O size directly impacts storage performance. If the application I/O size is smaller than the throughput multiplier that is used by the profile to calculate the volume’s bandwidth limit, the IOPS limit is reached before the throughput limit.
Each device has a unique SSH key, so the key for the newly provisioned or reloaded device is different from the image. However, SSH keys that are associated with either a Flex Image or a standard image templates are associated with the device when it is provisioned or reloaded. You can also add keys during the setup process.
* Which virtual server instance types can be reserved?

Only SAN-backed balanced, memory, and compute family sizes can be reserved.
* Can I combine different CPUxRAM sizes or change the sizes later?

You cannot combine different CPUxRAM sizes or change the sizes later. The set of virtual server instances that you provision to your reserved capacity must be the same size as your reservation.
* Is my payment upfront or monthly?

Reserved capacity and instances are purchased for a 1 or 3-year term. After that point, you're committed to a monthly payment.
* What happens at the end of my contract?

Depending on whether you choose hourly or monthly billing, the billing price for the CPU and RAM converts to the current list price, with any account discounts applied. Contact your sales representative, who in turn works with your global sales manager to determine end-of-contract options such as renewal or restructuring of your contract provisions. For more information about pricing, see [Build your virtual server](https://www.ibm.com/cloud/virtual-servers).
* What happens if I don't need my reserved virtual server instances anymore?

You can reclaim reserved virtual server instances, but you cannot cancel reserved capacity.
* Does the reservation include everything that I configured into my virtual server instance?

Only CPU and RAM are included in your reservation. Primary disk and no-additional charge network or storage products are not included in your reservation. More network bandwidth, storage capacity, OS, and third-party software are charged on an hourly or monthly basis, which depends on the instance type.
* Why do I need to choose hourly or monthly billing on the virtual server instance?

Your additional software, storage, and network selections need to be billed either hourly or monthly.
* What types of virtual servers are available for use?

IBM Cloud® offers a couple types of virtual servers within its Classic Infrastructure.
Target latency for a 16-KB block size volume is under 1 millisecond for random reads and under 2 milliseconds for writes.
* What mechanisms are used to avoid data storage contention?

 What mechanisms are used to avoid data storage contention? 

Data storage contention is a common issue when multiple instances compete for access to the same Block Storage for VPC volume. Block Storage for VPC uses Rate Limiting at the hypervisor for optimal bandwidth between the hypervisor and Block Storage for VPC service. As a result, latency is guaranteed to be less than 1 millisecond for random reads and under 2 milliseconds for writes for a typical 16-KB block size. Latency outside these metrics might indicate a problem on the client side.
* What happens when a volume is in a degraded health state?

 What happens when a volume is in a degraded health state? 

Volume health state defines whether a volume is performing as expected, given its status. Volume health can be OK, degraded, inapplicable, or faulted, depending on what is happening. For example, a degraded status is displayed when a volume is being restored from a snapshot and the volume is not yet fully restored. For more information about volume health states, see [Block Storage for VPC volume health states](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-monitoringblock-storage-vpc-health-states).
* How secure is data in a Block Storage for VPC volume?

 How secure is data in a Block Storage for VPC volume? 

All Block Storage for VPC volumes are encrypted at rest with IBM-managed encryption. IBM-managed keys are generated and securely stored in a Block Storage for VPC vault that is backed by Consul and maintained by IBM Cloud® operations.

For more security, you can protect your data by using your own customer root keys (CRKs). You import your root keys to, or create them in, a supported key management service (KMS). Your root keys are safely managed by the supported KMS, either Key Protect (FIPS 140-2 Level 3 compliance) or Hyper Protect Crypto Services.
[GPU](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesgpu) GPU enabled profiles provide on-demand access to NVIDIA V100 and A100 GPUs to accelerate AI, high-performance computing, data science, and graphics workloads. 
 [Storage Optimized](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesstorageopt) Storage Optimized profiles offer temporary SSD instance storagedisks at a ratio of 1 vCPU to 300 GB instance storage with a lower price point per GB. These profiles are designed for storage-dense workloads and offer virtio interface type for attached disks. 



Profiles with instance storage and profiles with 64 or more vCPUs are deployed exclusively on the Intel®'s second-generation quad processor Xeon® Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or Intel®'s quad processor Xeon® Gold 6248 Cascade Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.

Profiles with AMD manufactured processors are available in the Toronto region.



 Balanced 

Balanced profiles provide a mix of performance and scalability for more common workloads with a ratio of 4 GiB of memory for every 1 vCPU of compute. The Balanced profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage). The following table shows all Balanced profiles available for Intel® x86-64, and AMD x86-64 processors.

Balanced profiles with the bx2d prefix are available in the US South (Dallas), US East (Washington DC), Canada (Toronto), United Kingdom (London), EU Germany (Frankfurt), Japan (Tokyo), Japan (Osaka), and Australia (Sydney) regions.

Intel x86-64

AMD x86-64



Table 3. Balance profiles options for Intel x86-64 instances
Balanced profiles options for Intel x86-64 virtual server instances.
For more information about available images, see [Virtual server images](https://cloud.ibm.com/docs/docs/vpc?topic=vpc-about-images). Default value: ibm-redhat-8-4-minimal-amd64-1. 
 SSH_KEYS List of SSH Keys IDs that are allowed to SSH as root to the VSI. Can contain one or more IDs. View the list of available SSH Keys on the IBM Cloud Console [SSH keys for VPC](https://cloud.ibm.com/vpc-ext/compute/sshKeys) page. Sample input (use your own SSH IDs from IIBM Cloud): [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a", "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ] 
 VOL1 [ number ] The size for the disk in GB to be attached to the BASTION VSI as storage for the SAP deployment kits. The mount point for the new volume is: "/storage". Default value: 100 GB. 



Sensitive* - The variable value is not displayed in your workspace details after it is stored. Make sure to select Sensitive on the Settings page for all fields marked "Sensitive".

VOL1 [ number ] variable represents the defined customer size of the storage that is needed to store downloaded SAP kits before you run the automated SAP deployment. The storage size can be customized when you deploy the bastion SAP VPC and VSI. Default storage that is allocated is 100 Gb.





 Before you begin 



1. To complete this procedure, you need a general understanding of IBM Cloud VPC and VSIs. To run the example in IBM Cloud Schematics, you need an IBM Cloud account. The deployed resources are chargeable.
2. [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key).
Pricing 

A Databases for Redis Standard plan deploys as one highly available Redis cluster with two data members. Your data is replicated on both members. The Standard plan is priced based on the total amount of disk storage, RAM, dedicated cores, and backup storage that is allocated to deployments, prorated hourly. Databases for Redis deployments have a minimum of 1 GB of disk and 1 GB of RAM per data member.



 Using the Pricing Calculator 

Templates are provided for ease of use and provide balanced resource allocations appropriate for general purpose workloads. The Custom tab can be used to configure Disk, RAM, and vCPU, as desired.

For pricing estimation, use the Add to Estimate button on the [Databases for Redis catalog page](https://cloud.ibm.com/catalog/databases-for-redis). Input your total consumption across two data members into the calculator. This is roughly double the size of your data because your data is replicated to both members. For example, 1 GB of disk and 1 GB of RAM across two data members would be priced at 2 GB of disk and 2 GB of RAM respectively.





 Backups Pricing 

You receive your total disk space purchased, per database, in free backup storage. For example, in a given month, if you have a Databases for Redis deployment that has 20 GB of disk per member, and has three data members, you receive 60 GB of backup storage free for that month. If your backup storage utilization is greater than 60 GB for the month (in this scenario), you are charged an overage of $0.03/month per gigabyte.

By default, Cloud Databases provides a daily backup that is stored for 30 days. These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB.
* [VPC Gen 2 flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavors)*



* VPC: For more information about network performance caps for virtual machines, see [VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). The network speeds refer to the speeds of the worker node network interfaces. The maximum speed available to your worker nodes is 25Gbps. Because IP in IP encapsulation is required for traffic between pods that are on different subnets, data transfer speeds between pods on different subnets might be slower, about half the compute profile network speed. Overall network speeds for apps that you deploy to your cluster depend on the worker node size and application's architecture.







 Physical machines (bare metal) 

You can provision your worker node as a single-tenant physical server, also referred to as bare metal.

Physical machines are available for classic clusters only and are not supported in VPC clusters.



 Planning considerations for bare metal 

How is bare metal different than VMs?
: Bare metal gives you direct access to the physical resources on the machine, such as the memory or CPU. This setup eliminates the virtual machine hypervisor that allocates physical resources to virtual machines that run on the host. Instead, all a bare metal machine's resources are dedicated exclusively to the worker, so you don't need to worry about "noisy neighbors" sharing resources or slowing down performance. Physical flavors have more local storage than virtual, and some have RAID to increase data availability. Local storage on the worker node is for short-term processing only, and the primary and auxiliary disks are wiped when you update or reload the worker node. For persistent storage solutions, see [Planning highly available persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).

Because you have full control over the isolation and resource consumption for your workloads, you can use bare metal machines to achieve HIPAA and PCI compliance for your environment.

Bare metal seems awesome! What's stopping me from ordering one immediately?
LinuxONE (s390x processor architecture)
: You can now create virtual server instances on LinuxONE (s390x processor architecture) in IBM Cloud in the Japan (Tokyo), United Kingdom (London), and São Paulo regions. For more information about available LinuxONE (s390x processor architecture) profiles, see [s390x instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-vs-profiles). To create instances on LinuxONE (s390x processor architecture), see [Creating virtual server instances by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).

Resizable boot volumes
: You can now increase the capacity of a boot volume, up to 250 gigabytes (GB), when you create an instance from an image or instance template. You can also directly update an existing boot volume to increase its capacity. For more information, see [Increasing boot volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes).

Backup for VPC (closed beta)
: For accounts authorized to preview this service, you can create backup policies that automatically backup your block storage volumes. Backups are triggered when a user tag is applied to a volume matches a backup policy tag. Each backup policy has a backup plan, which defines how often backups are taken and how long they're retained. For more information, see [About Backup for VPC (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).

File Storage for VPC
: The file service is now integrated with the Security and Compliance Center to help you manage security and compliance for your organization. For more information about this feature, see [Managing security and compliance](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-vpc-manage-security).





 14 February 2022 

Snapshots for VPC
* UI
* CLI
* API







 File Storage for VPC profiles 

When you provision File Storage for VPC file shares by using the IBM Cloud console, CLI, or API, you specify a file share profile. The profile defines the performance level that you require based on the file share size.

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.



 File storage profiles overview 

When you [create a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create) in your availability zone, you select share size and IOPS performance based on a file storage profile. New file shares are created based on the high performance, [dp2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile) profile.

Earlier file shares that were created by using either the [IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers) profiles or [custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-custom) profile can continue to operate based on these profiles. You can also update these file shares to use the dp2 profile or switch back to a previous profile. However, you cannot use the previous profiles when you create a new file share.

Table 1 shows the dp2 profile performance levels compared to the earlier profiles. [Table 2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile) presents the IOPS and capacity ranges for the dp2 profile.
In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date. Your storage instances remain active until the next anniversary date and you can continue to use them until this date, such as to give your team time to make backups of your data.



* When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete and you choose to remove the PVC, the PV and the storage instance are immediately removed. For hourly billed storage, billing stops immediately. For monthly billed storage, you are still charged for the remainder of the month. After your storage is removed and billing stops, you might still see your storage instance in the console or the CLI for up to 72 hours.



What do I need to be aware of before I delete persistent storage?
: When you clean up persistent storage, you delete all the data that is stored in it. If you need a copy of the data, make a backup for [file storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_backup_restore) or [block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_backup_restore).

I deleted my storage instance. Why can I still see my instance?
: After you remove persistent storage, it can take up to 72 hours for the removal to be fully processed and for the storage to disappear from your IBM Cloud console or CLI.

I deleted my cluster. How do I remove the remaining storage volumes?
: See the steps in [Why am I still seeing charges for block storage devices after deleting my cluster](https://cloud.ibm.com/docs/containers?topic=containers-ts_storage_clean_volume).



 Cleaning up Block Storage for VPC
This is migrated as-is to VPC.
2. Classic virtual server instance has network file storage:



* An equivalent Linux file system (ext4) is created in VPC and then the contents are copied over.
* VPC does not yet support NAS storage. Your storage will be on the Linux file system on your VPC instance, and it cannot be shared.



3. Classic virtual server has network block storage (iSCSI devices):



* The content migration agent will discover the existence of a Linux file system on top of dev mapper devices and will migrate the contents to VPC.
* Partition information between source and destination will be retained.
* File systems on top of the iSCSI luns are copied to the destination instance. Neither multi-pathing nor user-friendly names configured on your source will be available. in your destination.



4. Classic virtual instance has portable storage, network file storage, and network block storage.









 Considerations for SSH keys 

The VPC+ tool can detect the SSH public keys that were added during the initial ordering process of your classic virtual server instances. If the SSH public keys aren't RSA or were added after you ordered your instances, then the VPC+ tool will require you to add a new SSH key.





 Considerations for secondary volumes 

If you want to migrate a virtual server instance with a primary volume and there is a secondary volume that is attached to it, make sure that when you mount your disks in your classic machine it is mounted permanently. Accomplish this by adding the nofail in the secondary volume mount entry of the /etc/fstab file.

A typical entry looks like the following:

"/dev/disk /mnt/disk ext4 defaults,nofail 0 2”

You need to add nofail next to defaults if it isn’t there already.

VPC+ Cloud Migration only supports a maximum of three secondary volumes for migration.

If a server cannot be migrated because it's not configured as cloud-init, you can still migrate the secondary volume of that server. First, create a compatible server in VPC, then migrate the secondary volume by using the previous procedure.





 Considerations for load balancers
Pricing 

A IBM Cloud® Messages for RabbitMQ Standard plan deploys as one highly available RabbitMQ cluster with three data members. Your data is replicated across members. The Standard plan is priced based on the total amount of disk storage, RAM, dedicated cores, and backup storage that is allocated to deployments, prorated hourly. Messages for RabbitMQ deployments have a minimum of 1 GB of disk and 1 GB of RAM per data member.



 Using the Pricing Calculator 

Templates are provided for ease of use and provide balanced resource allocations appropriate for general-purpose workloads. The Custom tab can be used to configure Disk, RAM, and vCPU, as wanted.

For pricing estimation, use the Add to Estimate button at the bottom of the [Messages for RabbitMQ catalog page](https://cloud.ibm.com/catalog/messages-for-rabbitmq). Input your total consumption across three data members into the calculator. For example, 1 GB of disk and 1 GB of RAM across three data members would be priced at 3 GB of disk and 3 GB of RAM respectively.





 Backups Pricing 

Users also receive their total disk space purchased, per database, in free backup storage. For example, in a month, if you have a Messages for RabbitMQ deployment that has provisioned 1 GB of disk per member, which has three data members, you receive 3 GB of backup storage free for that month. If your backup storage utilization is greater than 3 GB for the month in this scenario, each gigabyte is charged at an overage $0.03/month. Most deployments will not ever go over the allotted credit.





 Dedicated Cores Pricing 

You have the option of selecting the CPU allocation for your deployment. With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $30 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with 3 dedicated cores per member, that is a total of 9 cores, and billed at $270 per month.

Dedicated cores are an optional feature.