vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Block storage capacity and performance 

Choosing the optimal block storage volume size and performance level for your workloads is important. When you provision Block Storage for VPC, you can specify the size of your volume and the performance level that you require.



 Capacity 

Block Storage for VPC offers a range of storage capacities to meet your requirements.

Based on the [storage profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) that you chose for your data volume, you can specify 10-16,000 GB of capacity per block storage data volume in 1 GB increments.

Boot volumes are 100 GB by default. If you provision an instance from a custom image, you can specify boot volume capacity up to 250 GB.





 Block storage IOPS profiles 

When you provision Block Storage for VPC volumes, you specify an [IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles) that best meets your storage requirements. Three predefined tiered profiles are available, or you can choose a custom profile. [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) provide guaranteed IOPS/GB performance for volumes up to 16,000 GB capacity. A [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) profile defines ranges of volume capacity and IOPS that you can select. These profiles are backed by solid-state drives (SSDs).





 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.
It can be based on the number of days that you want to keep the backups. Or it can be based on the total number of backups that you want to retain before the oldest ones are deleted. Planning for the retention and deletion of your backups can keep the costs down.

Backups require that the volume that you're backing up is attached to a running virtual server instance. Put another way, you can't back up an unattached volume.

A volume is backed up when a [user-provided tag](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-about-tags) that is associated with a Block Storage for VPC volume match the tags for target resources in a backup policy. The volume must have at least one of the backup policy’s tags for the target resources. When the scheduled backup is triggered by a backup plan, all volumes with matching tags are backed up. You can [view the status of the backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs) in the UI, from the CLI, or the API.

If a volume has multiple tags, only one tag needs to match for a backup to trigger. You can add user tags to boot and data volumes at any time, when you [create a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=uicreate-from-vsi) or in an instance template.

When the backup is triggered at the scheduled interval, a backup copy is created of your volume contents. Behind the scenes, the [Snapshot for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about) service is used to create a point-in-time copy of your data. When the first backup snapshot is taken, the entire contents of the volume are copied and retained in IBM Cloud® Object Storage. Subsequent backups of the same volume capture the changes that occurred since the previous backup.
IBM Cloud File Storage for VPC add-on change log 

File Storage for VPC is available for allowlisted accounts in the Washington D.C., Dallas, Frankfurt, London, Sydney, Sao Paulo, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.

File Storage for VPC is available in Beta. Do not use this add-on for production workloads.

View information for patch updates to the IBM Cloud File Storage for VPC add-on in your IBM Cloud Kubernetes Service clusters.

Patch updates
: Patch updates are delivered automatically by IBM and don't contain any feature updates or changes in the supported add-on and cluster versions.

Release updates
: Release updates contain new features for the IBM Cloud File Storage for VPC or changes in the supported add-on or cluster versions. You must manually apply release updates to your IBM Cloud File Storage for VPC add-on. To update your IBM Cloud File Storage for VPC add-on, see [Updating the IBM Cloud File Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managing).

To view a list of add-ons and the supported cluster versions in the CLI, run the following command.

ibmcloud ks cluster addon versions --addon vpc-file-csi-driver

To view a list of add-ons and the supported cluster versions, see the [Supported cluster add-ons table](https://cloud.ibm.com/docs/containers?topic=containers-supported-cluster-addon-versions).



 Version 1.1 



 Change log for version 1.1, released 3 July 2023 



* Updates the following sidecar images:



* storage-secret-sidecar to v1.2.24.
* csi-node-driver-registrar to v2.7.0.
* livenessprobe to v2.9.0.
* csi-provisioner to v3.4.1.
* csi-resizer to v1.7.0.



* Updates the UBI image 8.8-860.
* Single Sites: mon01, sjc04



Europe:



* Regional: eu-gb, eu-de
* Single Sites: ams03, mil01, par01



South America:



* Regional: br-sao



Asia Pacific:



* Regional: au-syd, jp-osa, jp-tok
* Single Sites: che01, sng01







 Is the pricing different for the four One-Rate pricing regions? 

The pricing rates are same for North America and Europe, similarly for South America and Asia Pacific. See [One Rate pricing plan details](https://cloud.ibm.com/objectstorage/createpricing).





 Are all Cloud Object Storage features available in the One-Rate Plan? 

All Cloud Object Storage features (Versioning, Archive, Replication, WORM, Expiration, etc.) are available in the One-Rate Plan.





 Is the One-Rate plan available in all Cloud Object Storage regions? 

The One-Rate plan is available in all Cloud Object Storage Regional and Single sites.





 Can I configure a lifecycle policy to archive or expire my objects in the One Rate Active buckets? 

Yes, you can set a lifecycle policy to archive objects from the One Rate Active buckets to either Archive (restore ≤ 12 hours) or Accelerated Archive (restore ≤ 2 hours). Similarly, you can set expiration rules to expire objects based on the date of creation of the object, or a specific date.





 What pricing rates will apply to objects archived from the One Rate Active buckets? 

For Archive and Accelerated Archive, standard pricing applies based on the bucket location. For example, a bucket created in us-south will incur archive pricing for us-south. Similarly, a bucket in ca-tor will incur archive pricing for ca-tor.





 Can I move my existing buckets from Standard plan to One-Rate plan? 

Existing buckets in the Standard plan cannot be moved to the One-rate plan. Clients must first enroll in the One-Rate plan, create a new service instance and new buckets before data can be populated.





 Can I upgrade my Cloud Object Storage Lite plan instance to One-Rate plan?
<br> <br>This network would typically include 2-3 organizations. Configurations include: <br> <br> <br> <br>CouchDB <br> <br>File Storage (Bronze) <br> <br>Not included: HA, Backup,<br><br>HSM<br><br>, Log Analysis, Monitoring, Dedicated hardware/HW Total estimated cost per month: $606 USD <br> <br>Includes: <br> <br>Single node Raft ordering service <br> <br>0.35 vCPU/0.7GB RAM/100GB Storage <br> <br>2 CAs <br> <br>2 x (0.1 vCPU/0.2GB RAM/20 GB Storage) <br> <br>1 Peer <br>1.1 vCPU/2.8 GB RAM/100 GB Storage<br><br><br><br> * Peer container: 0.2 vCPU/1GB RAM/50GB Storage<br> * Couch container: 0.2 vCPU/0.4GB RAM/50GB Storage<br> * Smart contract container: 0.5 vCPU/1GB RAM/0GB Storage<br> * Logging/gRPC Web container: 0.2 vCPU/0.4GB RAM/0GB Storage<br><br><br> Total estimated cost per month: $368 USD <br> <br>Includes: <br> <br>1 CA <br> <br>0.1 vCPU/0.2GB RAM/20 GB Storage <br> <br>1 Peer <br>1.1 vCPU/2.8 GB RAM/100 GB Storage<br><br><br><br> * Peer container: 0.2 vCPU/1GB RAM/50GB Storage<br> * CouchDB container: 0.2 vCPU/0.4GB RAM/50GB Storage<br> * Smart contract container: 0.5 vCPU/1GB RAM/0GB Storage<br> * Logging/gRPC Web container: 0.2 vCPU/0.4GB RAM/0GB Storage<br><br><br>
If the physical storage is reprovisioned to another account, a new set of pointers is assigned. A new account can't access any data that was on the physical storage. The new set of pointers shows all 0's. When new data is written to the volume or LUN, any inaccessible data that still exists is overwritten.
* Can I use a Red Hat Cloud Access subscription to create a virtual server?

Yes. When you import an image, you can specify that you provide the operating system license. For more information, see [Use Red Hat Cloud Access](https://cloud.ibm.com/docs/image-templates?topic=image-templates-using-your-own-os-license-or-subscription). Then, you can order a virtual server from that image template and use your existing [Red Hat Cloud Access](https://www.redhat.com/en/technologies/cloud-computing/cloud-access) subscription.
* What is the difference between a virtual server and a virtual private server (VPS)?

A virtual server is similar to the virtual private server (VPS) or virtual dedicated server (VDS) platforms that you might already be familiar with. These "virtual server" environments allow for distinct environments to be provisioned privately and securely on a single hardware node, but VDS and VPS are more limited in their capabilities. VPS and VDS options are generally confined to a single-server architecture. The only resources that can be added or divided up between each virtual server on a VDS or VPS are the resources that are physically installed on that single server.

Virtual servers are provisioned on a multi-server cloud architecture that pools all available hardware resources for individual instances to use. Virtual servers can use a shared high-capacity SAN-based primary storage platform or high-performance local disk storage. Because each instance is part of the larger cloud environment, communication between all virtual servers is instantaneous.
* Why do I receive a capacity error when I provision a virtual server?

When you provision a virtual server, you might receive an insufficient capacity to complete the request error. When provisioning fails, all the virtual server instances within that particular request fail.
The following components are included in your virtual data center:



 Compute 

Compute processing is allocated to virtual data centers in vCPU increments. Each vCPU increment represents a single 2.0 GHz core. Compute memory is allocated in GB increments.





 Networking 

By default, every virtual data center comes configured with one advanced edge gateway with five public IP addresses and one private service IP address. The advanced edge gateway is customer configurable and can be customized.

The public IP addresses can be used for public facing vApps for inbound or outbound public internet traffic.

The service address can be used for access to IBM Cloud infrastructure services on the IBM Cloud internal private network, including the following services:



* NTP
* Windows® operating system licensing and updates
* Red Hat Enterprise Linux® operating system licensing and updates
* Cloud Object Storage







 Storage 

When you create or deploy vApps or VMs, you can select either an unencrypted or encrypted storage policy. Each option has six different tiers of storage available, depending on the storage performance required.

Storage policy availability can vary by region and deployment topology. On the VMware Shared order page, click the About tab to view available storage policy offerings.



 Unencrypted storage policy options 



* Standard - The storage tier with no maximum throughput. The number of IOPS/GB is not guaranteed.
* 10 IOPS/GB - The storage tier with a maximum throughput of 10 IOPS/GB, the highest guaranteed performance.
* 4 IOPS/GB - Storage tier with a maximum throughput of 4 IOPS/GB.
* 2 IOPS/GB - Storage tier with a maximum throughput of 2 IOPS/GB.
* 0.25 IOPS/GB - Storage tier with a maximum throughput of 0.25 IOPS/GB.
* vSAN™ - No IOPS limitation.



Standard is the default policy for virtual data centers.





 Encrypted storage policy options 

Encryption-enabled storage policies are available to all Organization virtual data centers. Encryption protects not only the VMs but also VM disks and other files.
You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-sc-ref) or [create your own storage class](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockcustom-sc-vpc-block). If you don't specify a storage class, the PV is created with the default storage class ibmc-vpc-file-3iops-tier.
2. Create the PVC.

kubectl apply -f mypvc.yaml
3. Verify that your PVC is created and bound to the PV. This process can take a few minutes.

kubectl describe pvc mypvc

Example output

Name: mypvc
Namespace: default
StorageClass: ""
Status: Bound
Volume: pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
Labels: <none>
Capacity: 20Gi
Access Modes: RWX
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibmc-vpc-file-retain-5iops-tier ", expecting that a volume for the claim is provisioned either manually or via external software
VMware Systems storage options 

You have several options when it comes to storage and VMware®. You can choose private, shared, or bring your own storage solutions. Use the following information to help you decide which storage solution works best with your workload.

See the following table for storage tiers and where your workload might fall.



Table 1. Storage tiers

 Tier 1 Tier 2 Tier 3 

 Business use High performance and or high availability production applications, databases, and data Nonmission critical test and development application, databases, and data Nonmission critical data storage, backup, and archive 
 Performance High (SSDs, SAS) Medium (SAS, SATA) Low (SATA) 
 Guaranteed IOPS Yes No No 
 High availability (HA) Yes No No 
 Replication Yes Yes No 
 Snapshots Yes No No 





 Private and shared storage 

For private storage, you can select local disk options, VSAN, or QuantaStor. For shared storage, you can select Endurance or Performance storage. If you decide to bring your storage, several “private” options are available, including NetApp OnTap Select, NetApp Private Storage (NPS), IBM® Spectrum Accelerate, and software defined storage. Table 2 and Table 3 offer a side-by-side comparison of the options for your convenience.





 Private storage options 

You have several options for storage for connecting to VMware in a single-tenant environment:



* Local
* vSAN
* QuantaStor
* NetApp Data OnTap Edge
* NPS
* IBM Spectrum Accelerate





 Local storage 

Order Bare Metal Servers from the IBM Cloud catalog with ESX and select the wanted disks [SATA, serial attached SCSI (SA SCSI), or SSD].

You can bring your own ESX license, but you need to open a ticket with Support to inform them of the change.



* Recommended workloads - Tier 3
* Performance - Limited dependent on RAID and disk type. SSDs present a cost increase for better performance.
* Scalability - Limited to the number of drive slots in the chassis
* Protocols - Not applicable
* Cost: Low capital expenditure (CapEx) and operating expenditure (OpEx)
FAQs for File Storage for VPC 

The following questions often arise about File Storage for VPC. If you have other questions you'd like to see addressed here, provide feedback by using the Open doc issue or Edit topic links.

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.



 Offering questions 



 Do I need to create a VPC before I can create a file share? 

No. You can create a file share independent of a VPC. However, to create a mount target, you must have a VPC available. To mount a file share, you must provision a virtual server instance within that VPC.





 I have existing VPCs. Can I create a file share within that VPC? 

Yes.





 What interfaces are supported for this release to create file shares? 

You can use the UI, CLI, API or Terraform to create and manage your file shares.





 Can I mount file shares on a Windows operating system? 

No, file shares can be mounted only on supported on Linux operating systems or a z/OS-based IBM Cloud® Compute Instance that support NFS file shares. For more information, see the mounting information for [Red Hat](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-RHE), [CentOS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-mount-centos), and [Ubuntu](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-ubuntu) Linux distributions, or [z/OS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-zos) systems.





 What is the minimum NFS version supported? 

File Storage for VPC requires NFS versions v4.1 or higher.
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.







 April 2021 



 30 April 2021 

File Storage for VPC
: File Storage for VPC is available to customers with special approval to preview this service in the Washington, Dallas, and Frankfurt regions. With this feature, you can create NFS-based file shares in a single zone in a region. You can share file storage over multiple virtual service instances within the same zone across multiple VPCs. For more information about this service, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about). Contact your IBM Sales representative if you are interested in getting access.





 07 April 2021 

File Storage for VPC (beta)
: NFS-based file shares for a zone within a region are available in a limited, allow-listed beta. You can share file storage over multiple virtual service instances within the same zone across multiple VPCs. For more information about this service, see [About File Storage for VPC (beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).

UI enhancement
: When provisioning a new VPN gateway in a default VPC, the UI now populates the subnet table with the default subnet information.





 06 April 2021 

New Toronto region
: The Toronto region endpoint is now in service at https://ca-tor.iaas.cloud.ibm.com.
The Block Storage for VPC add-on automatically retries mounting the storage to your apps. Wait a few more minutes for the storage to mount to your app.

oc describe deployment <deployment_name>

Example output

...
Volumes:
myvol:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: mypvc
ReadOnly: false







 Using an existing Block Storage for VPC instance 

If you have an existing physical Block Storage for VPC device that you want to use in your cluster, you can manually create the PV and PVC to statically provision the storage.

You can attach a volume to one worker node only. Make sure that the volume is in the same zone as the worker node for the attachment to succeed.



1. Determine the volume that you want to attach to a worker node in your VPC cluster. Note the volume ID.

ibmcloud is volumes
2. List the details of your volume. Note the Size, Zone, and IOPS. These values are used to create your PV.

ibmcloud is volume <volume_id>
3. Retrieve a list of worker nodes in your VPC cluster. Note the Zone of the worker node that is in the same zone as your storage volume.

ibmcloud oc worker ls -c <cluster_name>
4. Optional: If you provisioned your physical Block Storage for VPC instance by using a retain storage class, the PV and the physical storage is not removed when you remove the PVC. To use your physical Block Storage for VPC device in your cluster, you must remove the existing PV first.



1. List the PVs in your cluster and look for the PV that belongs to your Block Storage for VPC device. The PV is in a released state.

oc get pv
2. Remove the PV.

oc delete pv <pv_name>



5. Create a configuration file for your PV. Include the ID, Size, Zone, and IOPS that you retrieved earlier.

apiVersion: v1
[Memory](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilesmemory) Best for memory caching and real-time analytics workloads. 
 [GPU](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilesgpu) Best for high-performance workloads. 



Some of these families are also available for IBM Cloud® Virtual Servers for Virtual Private Cloud. For more information, see [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc-on-classic-vsi?topic=vpc-on-classic-vsi-getting-started).





 Balanced 

The balanced profiles (with network-attached storage) are ideal for common cloud workloads that require a balance of performance and scale. Network performance ranges from standard to premium.

The offering is available in the following profiles:



Table 2. Balanced profiles with network-attached storage

 Profile vCPU RAM Storage type 

 B1.1x2 1 2 GB SAN 
 B1.1x4 1 4 GB SAN 
 B1.2x4 2 4 GB SAN 
 B1.2x8 2 8 GB SAN 
 B1.4x8 4 8 GB SAN 
 B1.4x16 4 16 GB SAN 
 B1.8x16 8 16 GB SAN 
 B1.8x32 8 32 GB SAN 
 B1.16x32 16 32 GB SAN 
 B1.16x64 16 64 GB SAN 
 B1.32x64 32 64 GB SAN 
 B1.32x128 32 128 GB SAN 
 B1.48x192 48 192 GB SAN 





 Storage notes 



* SAN primary boot disk (25 or 100 GB) with more disks available, up to 2 TB each (five total disks allowed).
* Pricing for public virtual servers that use SAN storage includes virtual CPU, memory, and minimum primary boot disk. Extra disk prices depend on the disk size and quantity that you select.