vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Bandwidth allocation for block storage volumes 

You can allocate bandwidth for volumes that are attached to a virtual server instance out of total instance bandwidth.



 Bandwidth allocation for volumes that are attached to an instance 

When you provision an instance, bandwidth is allocated between block storage volumes (boot volume and attached block storage volumes) and networking. The maximum bandwidth capacity is determined by the instance profile that you select during instance provisioning. For example, a bx2-2x8 balanced server profile allows a total instance bandwidth of 4,000 Mbps (4 Gbps). The initial storage and network bandwidth allocation depends on what you set by using the API or by the instance profile you selected.

The maximum bandwidth of a volume 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.

For example, for the bx2-2x8 profile you might have:



* Volumes: 1,000 Mbps,
* Network: 3,000 Mbps.



To ensure reasonable boot times, a minimum of 393 Mbps is allocated to the primary boot volume. In the example, the instance's total volume bandwidth is 1,000 Mbps and the remaining 607 Mbps is allocated to any secondary volumes that you attach, up to the maximum bandwidth of the volume. For example, if you have one data volume with 500 Mbps, you can expect to get that level of performance.

Each volume has an IOPS and bandwidth limit set. The IOPS limit is always set to the maximum IOPS of the volume. The bandwidth for each attached volume is set proportionally based on the [volume size and profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles).

For optimal bandwidth to be realized, detach and reattach the volume after volume bandwidth allocation in the UI, CLI, or API.



 Adjusting volume bandwidth 

You can change the volume/networking bandwidth ratio to meet your needs, but both volume and network bandwidth must be at least 500 Mbps each.
For data volumes attached to a virtual server instance, you can [increase volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes) in GB increments up to 16,000 GB capacity, depending on your volume profile. You can also [increase or decrease IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops) for a volume that is attached to an instance.

You can also apply user tags and access management tags to your boot and data volumes anytime. Add tags when you create a volume or update an existing volume with the UI, CLI, API and Terraform. For more information, see [Tags for Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutvpc-storage-about-tags).

When you create, view, or update a Block Storage for VPC volume, or [restore a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore), the volume health state is reported in the UI, CLI, or API. For more information, see [Block Storage for VPC volume health states](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-monitoringblock-storage-vpc-health-states).





 Block Storage for VPC volume types 

Block Storage for VPC offers block-level volumes that are attached to an instance as a boot volume when the instance is created or attached as secondary data volumes. You can configure up to 300 Block Storage for VPC volumes per account in a region. You can request to increase this quota by [opening support case](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-storage-limit) and specifying in which zone you need more volumes.

You can attach only one boot volume to a virtual server instance at a time, but you can attach up to 12 Block Storage for VPC data volumes to a single instance.
* Windows Server VM with iSCSI storage. This option is not supported by VMware® Regulated Workloads instances.
* Single Windows VSI with iSCSI storage. This option is not supported by Security and Compliance Readiness Bundle instances or VMware Regulated Workloads instances.
* Bare metal server with local storage. This option requires VMware vSphere 7.







 Storage size 

The capacity that meets your storage needs. This option is not applicable to the Bare metal server with local storage deployment type.

For an example that shows what the capacity might be like, see [Capacity planning for backup repositories](https://helpcenter.veeam.com/docs/one/reporter/capacity_planning_for_repositories.html?ver=100).





 Storage performance 

The IOPS (input/output operations per second) per GB based on your workload requirements. This option is not applicable to the Bare metal server with local storage deployment type.





 Backup disk 

The backup disks are used as storage repositories for backups. This option is applicable only to the Bare metal server with local storage deployment type.





 Linux hardened repository 

You can order a Linux® hardened repository (LHR) to use for immutable storage. If you select a Linux hardened repository, a list of backup disk size options is displayed. Select the disk size that you want to order.

The Linux hardened repository is only supported for vSphere 7 NSX-T instances.

For more information, see [Hardened Repository](https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository.html?ver=120) in the Veeam documentation.





 Number of VMs to license 

Enter the number of VMs (virtual machines) to license (minimum 1).

You can order a maximum of 3,000 licenses. If you need to have multiple licenses under a single license key, you must first purchase them.
Supported persistent storage solutions, such as IBM Cloud File Storage for Classic, IBM Cloud Block Storage, or IBM Cloud® Object Storage are integrated as Kubernetes flex drivers and can be set up by using [Helm charts](https://cloud.ibm.com/docs/openshift?topic=openshift-helm). The Helm chart automatically sets up Kubernetes storage classes, the storage provider, and the storage driver in your cluster. You can use the storage classes to provision persistent storage by using persistent volume claims (PVCs). For more information, see [Planning highly available persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).

To secure your cluster network or connect to an on-prem data center, you can configure one of the following options:



* [strongSwan IPSec VPN Service](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn-setup)
* [IBM Cloud® Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
* [Virtual Router Appliance (VRA)](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvyatta)
* [Fortigate Security Appliance (FSA)](https://cloud.ibm.com/docs/vmwaresolutions/services?topic=vmwaresolutions-fsa_considerations)







 IBM Cloud VPC infrastructure services 

With Red Hat OpenShift on IBM Cloud, you can create a standard cluster in a [Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). A VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.

Before you can create a VPC cluster, you must have a VPC and at least one VPC subnet that you provision by using the IBM Cloud console, CLI, or API.
For more information, see [About creating an image from a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc).



 13 May 2021 

Scheduled Scaling for VPC (GA)
: Scheduled Scaling for VPC lets you set scheduled actions to automatically scale instance group capacity up or down based on daily, intermittent, or seasonal demand. You can set multiple, recurring scheduled action frequencies that can scale monthly, weekly, daily, hourly, or even every set number of minutes. For more information, see [Scheduled scaling](https://cloud.ibm.com/docs/vpc?topic=vpc-scheduled-scaling-vpc).





 15 May 2021 

Virtual Private Cloud (VPC) Gen 1 end of service
: Virtual Private Cloud (VPC) Gen 1 reached end of service on 26 February 2021. The VPC on Classic API reference has been removed from the library page on 15 May, 2021. VPC on Classic users are being redirected to the [Virtual Private Cloud API](https://cloud.ibm.com/apidocs/vpc).





 06 May 2021 

New Ultra High Memory instance profile family (LA)
: Ultra High Memory profiles are hosted exclusively on the latest generation Intel® Xeon® Platinum Cascade Lake server hosts and are optimized for running memory intensive applications and in-memory database such as SAP HANA, Memcached, or Redis. This profile family offers our highest vCPU to memory ratio with 28 GiB of memory for every 1 vCPU of compute and up to 5.7 TiB of available RAM. For more information, see [x86 Instance Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).
: The Ultra High Memory family of profiles is currently available in the Dallas and Frankfurt multizone regions(MZRs). For more information, see the Multizone regions section in [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table). Contact your IBM Sales representative if you need Ultra High Memory profiles in a MZR other than Dallas or Frankfurt.
Pricing 

An IBM Cloud® Databases for etcd Standard plan deploys as one highly available etcd 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. Databases for etcd deployments have a minimum of 20 GB of disk (200 IOPS) and 1 GB of RAM per data member. Review the [documentation on performance](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-performance) to see the importance of accounting for IOPS in your capacity planning.



 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 [Databases for etcd catalog page](https://cloud.ibm.com/catalog/databases-for-etcd). Input your total consumption across two data members into the calculator. For example, 20 GB of disk and 1 GB of RAM across three data members would be priced at 60 GB of disk and 3 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 etcd 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.
For more information about the relationship of volume profiles to compute profiles, see [How virtual server profiles relate to storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles&interface=uivsi-profiles-relate-to-storage). For more information about how block size affects performance, see [Block storage capacity and performance](https://cloud.ibm.com/docs/vpc?topic=vpc-capacity-performance&interface=uihow-block-size-affects-performance).





 Next steps 

Allocate total volume bandwidth by using the API or CLI. For more information, see [Adjusting bandwidth allocation in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instancesadjusting-bandwidth-allocation-ui) and [Adjusting total volume bandwidth with the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=apiadjusting-bandwidth-allocation-api).

You can also [view volume bandwidth for an unattached volume](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage).
Container Registry determines the size of all new layers and adds the amount of storage to your monthly usage.



 Billing for storage and pull traffic 

Depending on the service plan that you choose, you are charged for the storage and pull traffic that you use per month in each region.



 Storage charges 

Every IBM Cloud Container Registry service plan comes with a certain amount of storage that you can use to store your Docker images in the namespaces of your IBM Cloud account. If you're on the standard plan, you are charged by GB-Months of usage. The first 0.5 GB-Months are free. If you're on the free plan, you can store your images in Container Registry for free until you reach the quota limits for the free plan. A GB-Month is an average of 1 GB of storage for a month (730 hours).

The following example is for the standard plan:
: You use 5 GB for exactly half the month and then you push several images to your namespace and use 10 GB for the rest of the month. Your monthly usage is calculated as shown in the following example:

(5 GB x 0.5 (months)) + (10 GB x 0.5 (months)) = 2.5 + 5 = 7.5 GB-Months

In the standard plan, the first 0.5 GB-Months are free, so you get charged for 7 GB-Months (7.5 GB-Months - 0.5 GB-Months).





 Pull traffic charges 

Every IBM Cloud Container Registry service plan includes a certain amount of free pull traffic to your private images that are stored in your namespace. Pull traffic is the bandwidth that you use when you pull a layer of an image from your namespace to your local computer. If you're on the standard plan, you're charged by GB of usage per month. The first 5 GB each month is free. If you're on the free plan, you can pull images from your namespace until you reach the quota limit for the free plan.

Pull traffic across public connections counts toward usage and quota. Pull traffic across private connections doesn't count.

The following example is for the standard plan:
: In the month, you pulled images that contain layers with a total size of 14 GB.
Estimating your cost for an IBM Cloud server to support your workload begins in the [IBM Cloud catalog](https://cloud.ibm.com/catalog). From the catalog, select Compute and choose the server type - Bare Metal Server, Virtual Server, or Virtual Server for VPC (Virtual Private Cloud). For more information, see the [Virtual servers provisioning calculator](https://www.ibm.com/cloud/virtual-servers/calculator/).
* Can I change the configuration of a virtual server?

After you provision a virtual server, you can upgrade or downgrade your server configuration at any time. For more information, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-servers). If the item that you want to change is not available from the Device List, you can cancel and reorder or contact [IBM Cloud Sales](https://cloud.ibm.com/catalog?contactmodule) for assistance.
* How do I cancel a virtual server?

You can cancel a virtual server at any time. Go to the [Device List](https://cloud.ibm.com/classic/devices). Click Actions for the server that you want to cancel, and select the cancel option from the menu. For more information, see [Canceling virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-serverscancel).
* Can I add disk storage to my hourly or monthly virtual server?

You can upgrade or downgrade disk storage for any virtual server by updating your storage options in the First Disk through Fifth Disk fields in the Configuration screen of the device you want to update. For more information, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-servers).
* How many hourly virtual servers can I start?

The number of instances that you can run depends on the maturity level of your account.
* 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-profiles&interface=apidp2-profile) profile.

Earlier file shares that were created by using either the [IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=apifs-tiers) profiles or [custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=apifs-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-profiles&interface=apidp2-profile) presents the IOPS and capacity ranges for the dp2 profile.
The bandwidth allocation can be changed on the instance details page after provisioning an instance.

For example, for the bx2-2x8 profile you might have:



* Storage: 1 Gbps
* Network: 3 Gbps



For a cx2-8x16 profile:



* Storage: 4 Gbps
* Network: 12 Gbps



The amount of overall bandwidth provided to volume bandwidth can be adjusted within the overall instance limits. A default amount of volume bandwidth is set on each instance profile.

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles) and [Adjusting bandwidth allocation using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=uiadjusting-bandwidth-allocation-ui).

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles) and [Adjusting bandwidth allocation using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=cliadjusting-bandwidth-allocation-cli).

For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles) and [Adjusting total storage bandwidth allocation from the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=apiadjusting-bandwidth-allocation-api).





 Bandwidth allocation with multiple network interfaces 

You can add up to 15 network interfaces for your virtual server instance, depending on the vCPU count that is included in the instance profile.



* 2-16 vCPUs: Up to 5 network interfaces
* 17-48 vCPUs: Up to 10 network interfaces
* 49 or more vCPUs: Up to 15 network interfaces



With multiple network interfaces, bandwidth is distributed evenly across the network interfaces that are attached to the virtual server instance.
Billing for Object Storage for Satellite 

Object Storage for Satellite has a different pricing model than the typical pay-as-you-go scheme used in the public cloud.

Instead, storage is allocated at a fixed capacity using a "T-shirt size" model. The available sizes are:



Table 1. Available sizes

 Object Storage capacity  Raw storage required  Monthly price 

 Small (12 TB)            18 TB                 $502          
 Medium (24 TB)           36 TB                 $878          
 Large (48 TB)            72 TB                 $1254         
 Extra Large (96 TB)      144 TB                $2006         



The total cost for using Object Storage for Satellite is a combination of:



1.  Cost of infrastructure
2.  Base Satellite charge
3.  Object Storage fixed capacity pricing





  Choosing capacity 

The storage instance capacity is set during the provisioning process. You will need to work with your Satellite administrator to ensure that enough raw capacity exists in the underlying Satellite infrastructure.

As each application has unique storage needs, it is not possible to provide much in the way of generic guidance for choosing a capacity. Take into account the nature of the application (for example, processing high-resolution satellite imagery or 4K video will require a greater capacity than a simple document repository) and the expected scaling of storage needs, and [consult IBM Cloud support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar) as needed.





  Adding capacity 

At this point, it is not possible to extend capacity once an instance is provisioned. Instead, you will need to provision an additional instance and create a new bucket for the overflow.
[Compute](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=uicompute-dh-pr) Best for workloads with intensive CPU demands, such as medium to high web traffic workloads, production batch processing, and front-end web servers. Compute profiles offer vCPU to memory ratios with 1 vCPU to 2 GiB of RAM. Compute profiles are offered with and without instance storage. 
 [Memory](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=uimemory-dh-pr) Best for memory intensive processes, such as memory caching, intensive database applications, or in-memory analytics workloads. Memory profiles offer vCPU to memory ratios with 1 vCPU to 8 GiB of RAM. Memory profiles are offered with and without instance storage. 
 [Very High Memory with instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=uivhm-is-dh-pr) Best for OLAP workloads and SAP-related services, such as SAP NetWeaver. The Very High Memory profile offers 1 vCPU to 14 GiB of RAM memory ratio, is hosted exclusively on the Intel® Xeon® Platinum Cascade Lake server, and includes instance storage for temporary swap space or cache. 
 [Ultra High Memory with instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=uiuhm-is-dh-pr) Best for in-memory OLTP databases, such as SAP. The Ultra High Memory profile offers the highest vCPU to memory ratios with 1 vCPU to 28 GiB of RAM, is hosted exclusively on the Intel® Xeon® Platinum Cascade Lake server, and includes instance storage for temporary swap space or cache 



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



 Balanced 

The Balanced profile provides a good mix of performance and scalability for more common workloads.

The Balanced with instance storage profile provides a good mix of performance and scalability for more common workloads.