vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* CLI
* API
* Terraform







 Managing file shares 

Manage file shares that you created. You can rename a file. You can increase its capacity and modify its IOPS. You can add mount targets to a file share, mount, and unmount a file share from virtual server instances. You can rename or delete a mount target, and you can delete a file share.

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 for VPC service requires IAM permissions for role-based access control. For example, to create a file share, you need to at least editor permissions. For more information, see the [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls) for file shares.



 Manage file shares and mount points in the UI 

In the console, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uirename-file-share-ui).
* [Add mount target to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uiadd-mount-target-ui).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uirename-mount-target-ui).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-update-profile-ui)
Adjust the slider to increase or decrease the resources that are allocated to your service. The slider controls how much memory or disk is allocated per member. The UI currently uses a coarser-grained resolution of 8 GB increments for disk and 1 GB increments for memory. The UI shows the total allocated memory or disk for the position of the slider. Click Scale to trigger the scaling operations and return to the dashboard overview.





 Resources and Scaling in the CLI 

[IBM Cloud CLI cloud databases plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference) supports viewing and scaling the resources on your deployment. Use the command cdb deployment-groups to see current resource information for your service, including which resource groups are adjustable. To scale any of the available resource groups, use cdb deployment-groups-set command.

For example, the command to view the resource groups for a deployment named "example-deployment":
ibmcloud cdb deployment-groups example-deployment

This produces the output:

Group member
Count 3

+ Memory
| Allocation 3072mb
| Allocation per member 1024mb
| Minimum 3072mb
| Step Size 384mb
| Adjustable true

+ CPU
| Allocation 0
| Allocation per member 0
| Minimum 9
| Step Size 3
| Adjustable true

+ Disk
| Allocation 3072mb
| Allocation per member 1024mb
| Minimum 3072mb
| Step Size 3072mb
| Adjustable true

The deployment has three members, with 3072 MB of RAM disk allocated in total. The "per member" allocation is 1024 MB of RAM and 1024 MB of disk. The minimum value is the lowest the total allocation can be set. The step size is the smallest amount by which the total allocation can be adjusted.

The cdb deployment-groups-set command allows either the total RAM or total disk allocation to be set, in MB.
Removing the local block storage configuration from the console 

Use the console to remove a storage configuration.



1. From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.







 Removing the local block storage configuration from the command line 



1. List the resources in the local-storage namespace. When you delete your storage assignment, these resources are removed.

oc get all -n local-storage

Example output

NAME READY STATUS RESTARTS AGE
pod/local-disk-local-diskmaker-clvg6 1/1 Running 0 29h
pod/local-disk-local-diskmaker-kqddq 1/1 Running 0 29h
pod/local-disk-local-diskmaker-p6z9q 1/1 Running 0 29h
pod/local-disk-local-provisioner-dw5g7 1/1 Running 0 29h
pod/local-disk-local-provisioner-hxd9n 1/1 Running 0 29h
pod/local-disk-local-provisioner-tfg95 1/1 Running 0 29h
pod/local-storage-operator-df4994656-7826l 1/1 Running 0 29h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/local-storage-operator ClusterIP 172.21.147.17 <none> 60000/TCP 29h

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/local-disk-local-diskmaker 3 3 3 3 3 <none> 29h
daemonset.apps/local-disk-local-provisioner 3 3 3 3 3 <none> 29h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/local-storage-operator 1/1 1 1 29h

NAME DESIRED CURRENT READY AGE
replicaset.apps/local-storage-operator-df4994656 1 1 1 29h
2. List your storage assignments and find the one that you used for your cluster.
Storage capacity cannot be scaled down. To move to a lower storage capacity requires creating a new Event Streams service instance at the lower capacity unit.





 How to scale capacity 

The following steps show you how to scale up throughput and storage capacity for an Event Streams Enterprise plan service instance. If you do not have an Enterprise instance, these steps help you to create one.

Currently, scaling up an Event Streams service instance capacity requires the use of the IBM Cloud CLI.

To install this tool, see [install devtools](https://cloud.ibm.com/docs/cli?topic=cli-install-devtools-manuallyinstall-devtools-manually).

The IBM Cloud CLI command uses the service-instance-update command to update your Event Streams service instance resource. The user ID in the account used to issue the service-instance- command must be assigned the same access policies that are needed when you create resources. For information about access requirements, see [creating resources](https://cloud.ibm.com/docs/account?topic=account-manage_resourcecreating-resources).



 During the scale-up process 

The time required to scale up the Event Streams service instance is variable, but under normal circumstances it does not exceed 3 hours. Both throughput and storage require provisioning extra infrastructure.

During this time, the flow of Kafka data is not affected (the scaling operation is nondisruptive). Kafka topic and partition add, update, and delete operations are suspended. This ensures that the integrity of data is maintained during storage volume infrastructure scale-up operations. This suspension of topic and partition operations occurs only during a brief portion of the scale-up process, not the entire process.

Valid combinations and values for the "throughput" and "storage_size" are listed in the following table.



Table 2. Valid combinations and values for 'throughput' and 'storage_size'

 Throughput capacity (maximum) "throughput" value to specify Storage capacity "storage_size" value to specify 

 1 (150 MB/s) 150 2 TB 2048 
 4 TB 4096 
 6 TB 6144 
 8 TB 8192 
 10 TB 10240
* UI
* CLI
* API
* Terraform







 Ordering Block Storage for Classic 

You can provision Block Storage for Classic and fine-tune to meet your capacity and operations-speed needs. Get the most out of your storage with two options for specifying performance.



* You can provision with Endurance tiers that feature pre-defined performance levels to fit workloads that don't have well-defined performance requirements.
* You can fine-tune your storage to meet specific performance requirements and build a high-powered Performance environment by specifying the total number of input/output operations per second (IOPS)



By default, you can provision a combined total of 700 Block Storage for Classic and File Storage for Classic volumes. To increase the number of your volumes, contact your sales representative. For more information about increasing limits, see [Managing Storage limits](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-managingstoragelimits).



 Ordering Block Storage for Classic in the UI 



1. Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog), and click Storage. Then, select Block Storage for Classic, and click Create.
2. Select your deployment location (region, location, zone).



* Ensure that the new Storage is added in the same location as the compute host or hosts that you have.



3. Billing. You can choose between Monthly or Hourly Billing.



* With hourly billing, the number of hours the block LUN existed on the account is calculated at the time the LUN is deleted or at the end of the billing cycle. Which ever comes first. Hourly billing is a good choice for storage that is used for a few days or less than a full month.
* With monthly billing, the calculation for the price is pro-rated from the date of creation to the end of the billing cycle and billed immediately. If a block LUN is deleted before the end of the billing cycle, the difference is not refunded. Monthly billing is a good choice for storage that is used in production workloads that use data that needs to be stored and accessed for long periods of time (month or longer).



4.
Before you can start to mount your existing storage to an app, you must retrieve all necessary information for your PV and prepare the storage to be accessible in your cluster.

For storage that was provisioned with a retain storage class.
: If you provisioned storage with a retain storage class and you remove the PVC, the PV and the physical storage device are not automatically removed. To reuse the storage in your cluster, you must remove the remaining PV first.

To use existing storage in a different cluster than the one where you provisioned it, follow the steps for [storage that was created outside of the cluster](https://cloud.ibm.com/docs/containers?topic=containers-file_storageexternal_storage) to add the storage to the subnet of your worker node.



1. List existing PVs.

kubectl get pv

Look for the PV that belongs to your persistent storage. The PV is in a released state.
2. Get the details of the PV.

kubectl describe pv <pv_name>
3. Note the CapacityGb, storageClass, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, server, and path.
4. Remove the PV.

kubectl delete pv <pv_name>
5. Verify that the PV is removed.

kubectl get pv



For persistent storage that was provisioned outside the cluster
: If you want to use existing storage that you provisioned earlier, but never used in your cluster before, you must make the storage available in the same subnet as your worker nodes.



1. From the [IBM Cloud infrastructure portal](https://cloud.ibm.com/classic), click Storage.
2. Click File Storage for Classic and from the Actions menu, select Authorize Host.
3. Select Subnets.
4. From the drop-down list, select the private VLAN subnet that your worker node is connected to.
The modification to the capacity does not affect the integrity of the data that is stored in the vault. For more information, see [expanding vault capacity](https://cloud.ibm.com/docs/Backup?topic=Backup-expandcapacityexpandcapacity).
* What happens when the IBM Cloud Backup for Classic capacity is exceeded?

You can still save and retrieve your backups even if you reached the limit of the capacity that you purchased previously. However, you are going to receive an extra charge for every additional GB that was used in the next billing statement.
* How can I set up notifications in the Cloud Backup Portal that can alert me if a backup fails?

Notifications can be set up on the Advanced tab. Follow the instructions that you can find in Quick Links in the Portal.
* When we use the BMR plug-in, can we move from a single disk to a raid array?

Yes, that works. However, you need to select a large capacity device due to the size decrease that the raid array causes.
* When we use the BMR plug-in, what happens when the image is restored to a larger disk than the original volume?

If you restore the image to a larger disk than the original volume, the leftover space is deallocated. So for example - when you have a 500-GB drive and restore its data to a 1-TB disk, you end up with 500 GB of deallocated disk space. With windows 2008, you can use the built-in disk utility to grow the primary partition. However, Windows 2003 does not have a similar built-in capability, so you must allocate the space another way.
* Can BMR be used for regular backup?

BMR backup isn't a disk image, but a system volume image backup system. The system isn't intended to be used for regular backups, but along with them.
* Can BMR be used for database backups?

Database backups must be made separately with the normal IBM Cloud Backup for Classic methods. BMR doesn't replace the need for SQL or Oracle plug-ins.
(https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/cs_storage_dynamic-01-01.svg)

Figure 1. Sample flow to dynamically provision file storage in a cluster



1. The user creates a persistent volume claim (PVC) that specifies the storage type, storage class, size in gigabytes, number of IOPS, and billing type. The storage class determines the type of storage that is provisioned and the allowed ranges for size and IOPS. Creating a PVC in a cluster automatically triggers the storage plug-in for the requested type of storage to provision storage with the given specification.
2. The storage device is automatically ordered and provisioned into your IBM Cloud infrastructure account. The billing cycle for your storage device starts.
3. The storage plug-in automatically creates a persistent volume (PV) in the cluster, a virtual storage device that points to the actual storage device in your IBM Cloud infrastructure account.
4. The PVC and PV are automatically connected to each other. The status of the PVC and the PV changes to Bound. You can now use the PVC to mount persistent storage to your app. If you delete the PVC, the PV and related storage instance are also deleted.



Review the following common use cases for dynamic provisioning:



1. Provision storage when needed: Instead of pre-providing persistent storage for developers and paying for storage that is not used, you can give developers the freedom to provision storage when they need it. To determine the type of storage that the developer can provision, you can define storage classes.
2. Automate the creation of PVC, PV, and storage device: You want to automatically provision and deprovision storage without manual intervention from a cluster admin.
3. Create and delete storage often: You have an app or set up a continuous delivery pipeline that creates and removes persistent storage regularly. Persistent storage that is dynamically provisioned with a non-retaining storage class can be removed by deleting the PVC.







 Static provisioning
For more information about the limit on simultaneous authorizations, see the [FAQs](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsauthlimit).





 Ordering File Storage for Classic from the SLCLI 

You can use the SLCLI to place orders for products that are normally ordered through the [IBM Cloud console](https://cloud.ibm.com/login).

Each order must have an associated location (data center). When you order File Storage for Classic, make sure that it is provisioned in the same location as your compute instances.

For more information about how to install and use the SLCLI, see [Python CLI Client](https://softlayer-python.readthedocs.io/en/latest/cli/).

Use the slcli file volume-order command to provision the file share volume.

 slcli file volume-order --help
Usage: slcli file volume-order [OPTIONS]

Order a file storage volume.

Options:
--storage-type [performance|endurance]
Type of file storage volume [required]
--size INTEGER Size of file storage volume in GB
[required]
--iops INTEGER Performance Storage IOPs, between 100 and
6000 in multiples of 100 [required for
storage-type performance]
--tier [0.25|2|4|10] Endurance Storage Tier (IOP per GB)
[required for storage-type endurance]
--location TEXT Datacenter short name (e.g.: dal09)
[required]
--snapshot-size INTEGER Optional parameter for ordering snapshot
space along with endurance file storage;
specifies the size (in GB) of snapshot space
to order
--service-offering [storage_as_a_service|enterprise|performance]
The service offering package to use for
placing the order [optional, default is
'storage_as_a_service']
--billing [hourly|monthly] Optional parameter for Billing rate (default
to monthly)
Before you can start to mount your existing storage to an app, you must retrieve all necessary information for your PV and prepare the storage to be accessible in your cluster.

For storage that was provisioned with a retain storage class.
: If you provisioned storage with a retain storage class and you remove the PVC, the PV and the physical storage device are not automatically removed. To reuse the storage in your cluster, you must remove the remaining PV first.

To use existing storage in a different cluster than the one where you provisioned it, follow the steps for [storage that was created outside of the cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageexternal_storage) to add the storage to the subnet of your worker node.



1. List existing PVs.

oc get pv

Look for the PV that belongs to your persistent storage. The PV is in a released state.
2. Get the details of the PV.

oc describe pv <pv_name>
3. Note the CapacityGb, storageClass, failure-domain.beta.kubernetes.io/region, failure-domain.beta.kubernetes.io/zone, server, and path.
4. Remove the PV.

oc delete pv <pv_name>
5. Verify that the PV is removed.

oc get pv



For persistent storage that was provisioned outside the cluster
: If you want to use existing storage that you provisioned earlier, but never used in your cluster before, you must make the storage available in the same subnet as your worker nodes.



1. From the [IBM Cloud infrastructure portal](https://cloud.ibm.com/classic), click Storage.
2. Click File Storage for Classic and from the Actions menu, select Authorize Host.
3. Select Subnets.
4. From the drop-down list, select the private VLAN subnet that your worker node is connected to.
Click on Edit to select the desired storage volume size in the Modify storage volume window. You can increase only the size of the storage volume.
4. Read the service agreement and agree to the terms. Click Order to complete the volume modification process and accept the price.
5. To verify your new storage size, go back to Storage volumes.
6. In an AIX VM instance, if you resize your boot storage volume, run the chvg -g rootvg command.



To apply or verify an IBM i software key, the VM must be active and in running state. If you already ran a resize operation, you must wait until the resize operation complete and VM returns to OK status.







 Adding or removing a public network 

You can remove or add a public network by clicking the Public networks toggle in Virtual server instances. When you toggle a public network off and then on, the Power Systems Virtual Server user interface regenerates new internal and external IP addresses. You need to check the Power Systems Virtual Server user interface for the new internal IP address (that maps to the external IP address). You must add a network interface controller (NIC) and point it to the new internal IP address. For information on how to add or remove an interface, see [How to add or remove a network interface from an AIX virtual machine (VM)](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-network-interface) or [How to add or remove a network interface from an IBM i virtual machine (VM)](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-network-interface-ibmi).

You cannot toggle a public network off if there are no other defined networks.





 Detecting problems by using the System Reference Code (SRC) 

A system reference code (SRC) is a set of eight alphanumeric characters that identifies the name of the system component that detects, the error codes, and the reference code that describes the error condition. When the Power Systems Virtual Server instance detects a problem, an SRC number is displayed along with a timestamp in the Server details page.
Resizing an existing virtual server 

Complete the following steps to resize an existing virtual server that uses pre-set profiles.



1. From the Devices menu, select Device List.
2. From the Device List, click the name of the virtual server that you want to resize.
3. Select Resize.
4. In the Resize window section, specify the window of time your system is down to perform the update. You can select Immediately for an immediate update, or schedule a time for the update to become active by choosing a date and time for the update. You can also specify any applicable notes for your device.
5. In the Profiles section, select a new profile configuration for your device.

When you modify a profile that uses local storage, you cannot switch to a profile that uses nonlocal storage. Likewise, when you modify a profile that uses nonlocal storage, you cannot switch to a profile that uses local storage.
6. If you need extra storage, you can attach storage disks to your device.
7. Click Resize to confirm your order and apply the changes to your device.







 Resizing an existing virtual server (before pre-set profiles) or dedicated virtual server 

Complete the following steps to resize an existing virtual server (before pre-set profiles) or a dedicated virtual server.



1. From the Device menu, select Device List.
2. From the Device List, click the name of the virtual server that you want to resize.
3. Select Resize.
4. In the Resize window section, specify the window of time your system is down to perform the update. You can select Immediately for an immediate update, or schedule a time for the update to become active by choosing a date and time for the update. You can also specify any applicable notes for your device.
5. In the Computing instance section, you can select new vCPU and RAM for your device.
6. If you need extra storage, you can attach storage disks to your device. The type of storage disks that are available to you depend on the profile that you select.
So when you determine how much Snapshot space you need, consider the rate of change carefully. It's a huge influence on how much snapshot space you need. A bigger volume is more likely to change more often. However, a 500-GB volume with 5 GB of change and a 10-TB volume with 5 GB of change use the same amount of snapshot space.

Additionally, for most workloads, the larger a volume is the less space needs to be set aside initially. It's primarily due to the underlying data efficiencies, and the nature of how snapshots work in the environment.





 Ordering Snapshot space in the UI 



1. Log in to the [IBM Cloud® console](https://cloud.ibm.com/login) and click the menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/icon_hamburger.svg).
2. Select Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/classic.svg).
3. Access your Storage through Storage > File Storage for Classic.
4. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg), then click Add Snapshot Space.
5. Select the amount of space that you need and the payment method.
6. Click Continue.
7. Enter any Promo Codes that you have and click Recalculate. The Charges for this order and Order Review have default values.

Discounts are applied when the order is processed.
8.