vania-janet/multiturn-rag-retrieval-data huggingface dataset:
__ Decide whether you want to [restrict access](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboutfs-mount-access-mode) to the file share from one specific virtual server instance or allow mounting on all virtual server instances within a VPC. <br><br>New 
 __ Evaluate the capacity and performance that you need. The dp2 profile provides ample flexibility in this regard. The range of total IOPS that you can specify is based on the size of the file share. You can provision shares with IOPS performance from 100 IOPS (default minimum) to 96,000 IOPS. For more information, see [File Storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles). 
 __ Estimate the size of the file share that you require for your current needs. File share sizes can range between 10 - 32,000 GB. You can later [increase the size of the file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacity), depending on what the file share profile allows. 
 __ Decide whether to [set up replication](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-replication). The replica file share is in a different zone from the primary file share. Replication is a good way to recover from events and protect against prolonged outages because it provides a read-only copy of the share in a different zone of your region. You can fail over to the replica site if the primary site becomes unavailable or compromised. 
 __ Make sure that you have a unique name for your file share that easily identifies the file share as your list of shares grows. Associate it with a resource group in your IBM Cloud customer account. 
 __ Think about which encryption type suits your needs the best. By default, your file shares are encrypted with IBM-managed encryption. For greater control, consider the use of customer-managed encryption. Your data can be protected at rest with your own root keys.
When you push a stand-alone app and bind to container-managed services, the Liberty buildpack generates the necessary server.xml stanzas for the bound services.

When you provide a server.xml file and bind to container-managed services, the Liberty buildpack will either generate or update the configuration stanzas.



* If the provided server.xml file does not contain configuration stanzas for the bound services, Liberty generates the configuration for the bound services.
* If the provided server.xml file contains configuration stanzas for the bound services, Liberty updates the configuration for the bound services.



See the documentation for the bound service type for more details.





 Opting out of service auto-configuration 

In some cases, you might not want the Liberty buildpack to automatically configure the services that have been bound. Consider the following scenarios.



* My app uses dashDB, but I want the app to directly manage the connection to the database. The app contains the necessary client driver JAR file. I do not want the Liberty buildpack to automatically configure the dashDB service.
* I am providing a server.xml file and I provided the configuration stanzas for the cloudant instance because I require a non-standard datasource configuration. I do not want the Liberty buildpack to update my server.xml file, but I still require the Liberty buildpack to ensure that the appropriate supporting software is installed.



To opt out of automatic service configuration, use the services_autoconfig_excludes environment variable. You can include this environment variable in a manifest.yml or set it using the IBM Cloud client.

You can opt out of automatic configuration of services on a per-service-type basis. You can choose to completely opt out (as in the dashDB scenario) or opt out of only the server.xml file configuration updates (as in the cloudant scenario). The value that you specify for the services_autoconfig_excludes environment variable is a string as shown below.



* The string can contain opt-out specifications for one or more services.
* The opt-out specification for a specific service is service_type=option, where:



* The service_type is the label for the service as displayed in VCAP_SERVICES.
* To adjust IOPS, the volume must be attached to a virtual server instance that is powered on and running.
* To adjust IOPS, the volume must be in an available state.







 Volume and IOPS limitations 



* For a volume that was created by using an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers), select a different profile for the volume size to increase or decrease IOPS. If the volume size exceeds that of the new IOPS tier profile, you can't change the profile.
* A [custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) can expand to the highest value that is allowed by the custom band. You can't switch custom bands unless you increase volume size and move to a higher band.
* Custom IOPS can be adjusted multiple times until the maximum or minimum limit is reached.
* Maximum IOPS for a volume for all profiles is [48,000 IOPs](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers).







 Other limitations 



* When a volume is in transition, the volume remains in an updating state until you reattach it to a running instance. For example, if the volume is detached while IOPS adjustment is in progress, the IOPS expansion resumes and completes only after the volume is reattached.
* When you delete an instance, volumes that are marked for auto-deletion are not deleted while the IOPS adjustment is underway.









 Adjust IOPS in the UI 

Follow these steps to adjust IOPS by selecting a new IOPS tier or custom IOPS band:



1. Go to the list of Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block Storage volumes.
Mount the partition and run df -vh to verify that the new size is correct.

 mount /dev/mapper/3600a098038304338415d4b4159487669p1 /SL02SEL1160157-73

 df -vh
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 99G 3.7G 90G 4% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 1.7M 3.9G 1% /dev/shm
tmpfs 3.9G 25M 3.8G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/xvda1 240M 148M 80M 65% /boot
fsf-sjc0401b-fz.adn.networklayer.com:/SL02SV1160157_8/data01 40G 1.1G 39G 3% /SL02SV1160157_8
tmpfs 782M 0 782M 0% /run/user/0 /dev/mapper/3600a098038304338415d4b4159487669p1 99G 1.1G 93G 2% /SL02SEL1160157-73





* Non-LVM - xfs



1. Mount the xfs file system back to its mount point. See /etc/fstab if you're not sure what the old mount point is for the xfs partition.

 mount /dev/sdb1 /mnt
2. Extend the file system. Substitute the mount point of the file system.

 xfs_growfs -d </mnt>









* Why do I see two disks in Disk Management when I add a single storage device?

Seeing two disks in Disk Management can occur if MPIO is not installed or is disabled for ISCSI.
After you provision an IBM Cloudant instance, the connection URL and IAM authorization details can be found when you generate new credentials in the Service Credentials tab of the IBM Cloud Dashboard. For more information, see [Locating your service credentials](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-locating-your-service-credentials). If you chose this option during provisioning, the IBM Cloudant legacy username and password is also included.

The IBM Cloudant team recommends you use IAM access controls for authentication whenever possible. If you're using IBM Cloudant legacy authentication, the IBM Cloudant team recommends that you use [API keys](https://cloud.ibm.com/apidocs/cloudantintroduction) rather than account-level credentials for programmatic access and replication jobs.





 High availability, disaster recovery, and backup in a data center 

To provide high availability (HA) and disaster recovery (DR) within a data center, all data is stored in triplicate across three separate physical servers in a cluster. You can provision accounts in multiple data centers, then use continuous data replication to provide HA/DR across data centers. IBM Cloudant data isn't automatically backed up, but supported tools are provided to handle backups. Review the [Disaster recovery and backup guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backup) to explore all HA, DR, and backup considerations to meet your application requirements.





 IBM Cloud Support 

Support for Standard and Dedicated plan service instances is optional. Support is provided when you purchase IBM Cloud Standard Support. Support isn't available for the Lite plan.

For more information, see the [IBM Cloud Standard Support plans](https://www.ibm.com/cloud/support944376) and the [IBM support guide](https://www.ibm.com/support/pages/node/733923).

The support systems that are used for IBM Cloudant don't offer features for the protection of personal data or sensitive personal data. This content includes Healthcare Information, health data, Protected Health Information, or data that is subject to more regulatory requirements.
To configure the Cloudant instance feature such as cloudantnosqldb.sapi.usercors action you need the cloudant service manager role. For more information, about IBM Cloud cloudant, see [ibm_cloudant](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cloudant) resource.





 Can I increase or decrease timeouts while deleting Terraform resource? 

Yes, you can increase or decrease timeouts by using timeouts blocks within your resource block as shown in the example. For more information, about a resource having timeouts block, see [ibm_container_vpc_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_clustertimeouts) timeouts.

timeouts {
create = "3h"
update = "2h"
delete = "1h"
}

resource "ibm_container_cluster" "mycluster" {
...
timeouts {
delete = "60m" something higher than the default of 45m
}
}





 Can I update the changes into the current existing Terraform file? 

Yes, Terraform saves the configuration in the form of the state file and identifies the drift that is made outside Terraform. When you run Terraform apply on the drift, Terraform reverts to the configuration that is present in your Terraform file. Hence, you can modify or update Terraform files to be in line with changes that are made outside Terraform and run Terraform refresh.





 How can I run Terraform files sequentially based on the results in IBM Cloud Schematics? 

You can use [module blocks](https://developer.hashicorp.com/terraform/language/modules/syntax) which is a container for multiple resources that are used together. The Terraform configuration has at least one module known as its root module, which consists of the resources defined in the .tf files of the main working directory.
* Apps that have memory limits greater than or equal to 512M have a heap size ratio of 75%



When you specify the heap memory using environment variables, you override the default heap size ratios.





 Specifying Heap Memory 

You can set the heap memory size by using environment variables or by changing the jvm.options file. When you use either the JVM_ARGS or JBP_CONFIG_IBMJDK environment variables, any changes will take effect when pushing your app to IBM Cloud. By changing the jvm.options file, the effect to the heap size configuration can also be tested locally.



* Use the JVM_ARGS environment variable and the -Xmx argument. For example to set the maximum heap size to 512 M use the following command, then restage your app.

ibmcloud cf set-env myapp JVM_ARGS -Xmx512m
* Specify the heap size ratio using the JBP_CONFIG_IBMJDK environment variable. The heap_size_ratio is a floating point value which specifies how much of memory limit to allocate to the heap. For example, to allocate half of the available memory to the heap (50% or 0.50), issue the following command and restage your app.

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "heap_size_ratio: 0.50"
* Specify the -Xmx argument in the jvm.options file if your app is a [server directory](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingserver_directory) or a [packaged server](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingpackaged_server). For more information about using the jvm.options file with the Liberty runtime, see [Setting generic JVM](https://www.ibm.com/support/pages/node/476495).
To configure the Cloudant instance feature such as cloudantnosqldb.sapi.usercors action you need the cloudant service manager role. For more information, about IBM Cloud cloudant, see [ibm_cloudant](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cloudant) resource.
* Can I increase or decrease timeouts while deleting Terraform resource?

Yes, you can increase or decrease timeouts by using timeouts blocks within your resource block as shown in the example. For more information, about a resource having timeouts block, see [ibm_container_vpc_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_clustertimeouts) timeouts.

timeouts {
create = "3h"
update = "2h"
delete = "1h"
}

resource "ibm_container_cluster" "mycluster" {
...
timeouts {
delete = "60m" something higher than the default of 45m
}
}
* Can I update the changes into the current existing Terraform file?

Yes, Terraform saves the configuration in the form of the state file and identifies the drift that is made outside Terraform. When you run Terraform apply on the drift, Terraform reverts to the configuration that is present in your Terraform file. Hence, you can modify or update Terraform files to be in line with changes that are made outside Terraform and run Terraform refresh.
* How can I run Terraform files sequentially based on the results in IBM Cloud Schematics?

You can use [module blocks](https://developer.hashicorp.com/terraform/language/modules/syntax) which is a container for multiple resources that are used together. The Terraform configuration has at least one module known as its root module, which consists of the resources defined in the .tf files of the main working directory.
If no snapshot space size is specified, the snapshot space size of the original volume is used.

-d, --dependent-duplicate
: Whether this duplicate is a dependent duplicate of the origin volume.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-duplicate 12345678

This command shows order a new volume by duplicating the volume with ID 12345678.





 ibmcloud sl file volume-order 

Order a file storage volume:

ibmcloud sl file volume-order [OPTIONS]

Command options:

-t, --storage-type
: Required. Type of storage volume, options are: performance, endurance.

-s, --size
: Required. Size of storage volume in GB.

-i, --iops
: Performance Storage IOPs. Range 100-6000, and in multiples of 100 [required for storage-type performance].

-e, --tier
: Endurance Storage Tier (IOP per GB) [required for storage-type endurance]. Options are: 0.25,2,4,10.

-d, --datacenter
: Required. Data center short name.

-n, --snapshot-size
: Optional parameter for ordering snapshot space along with the volume.

-b, --billing
: Optional parameter for Billing rate (default to monthly), options are: hourly, monthly.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-order --storage-type performance --size 1000 --iops 4000 -d dal09

This command orders a performance volume with size is 1000 GB, IOPS is 4000, and in data center dal09.





 ibmcloud sl file volume-modify 

Modify an existing file storage volume:

ibmcloud sl file volume-modify VOLUME_ID [OPTIONS]

Command options:

-c, --new-size
: New Size of file volume in GB. If no size is given, the original size of volume is used.
This command lists all endurance volumes on the current account that are located in data center dal09, and sorts them by capacity.





 ibmcloud sl file volume-convert 

Convert a dependent duplicate volume to an independent volume:

ibmcloud sl file volume-convert VOLUME_ID

Examples:

ibmcloud sl file volume-convert 12345678

Convert a dependent duplicate 12345678 to an independent volume.





 ibmcloud sl file volume-detail 

Display details for a specified volume:

ibmcloud sl file volume-detail VOLUME_ID

Examples:

ibmcloud sl file volume-detail 12345678

This command shows details of volume with ID 12345678.





 ibmcloud sl file volume-duplicate 

Order a file volume by duplicating an existing volume:

ibmcloud sl file volume-duplicate VOLUME_ID [OPTIONS]

Command options:

-o, --origin-snapshot-id
: ID of an original volume snapshot to use for duplication.

-s, --duplicate-size
: Size of duplicate file volume in GB. If no size is specified, the size of the original volume is used.

-i, --duplicate-iops
: Performance Storage IOPS. Range 100-6000, and in multiples of 100. If no IOPS is specified, the IOPS of the original volume is used.

-t, --duplicate-tier
: Endurance Storage Tier. If no tier is specified, the tier of the original volume is used.

-n, --duplicate-snapshot-size
: The size of snapshot space to order for the duplicate. If no snapshot space size is specified, the snapshot space size of the original volume is used.

-d, --dependent-duplicate
: Whether this duplicate is a dependent duplicate of the origin volume.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl file volume-duplicate 12345678

This command shows order a new volume by duplicating the volume with ID 12345678.





 ibmcloud sl file volume-order
See this topic on [Kubernetes cluster expiration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-manage-console-cluster-expiration) for information on what is happening and what you can do.





 After I deploy a node in the console, I'm seeing a message in my Kubernetes cluster on IBM Cloud reporting that the pod has unbound immediate persistent volume claims. Is this an error? 

 What’s happening 

I see what looks like an error in my Kubernetes cluster on IBM Cloud reporting that a pod has unbound immediate persistent volume claims and am worried that my node has failed to deploy.

 Why it’s happening 

More time is needed for the node to come up or you've possibly exceeded the maximum number of storage instances for your IBM Cloud account.

 How to fix it 

Unbound immediate persistent volume claims are a normal part of the deployment process for any node, reflecting that the persistent volume claim has been made but that the node itself has not yet deployed. Wait a few minutes for the node to deploy. If it is still not resolved, run the following kubectl command to describe the persistent volume claim for your namespace:

kubectl describe pvc <pvc_name> -n <namespace>

If you see the following error, it is likely that you have reached your limit of storage volumes:

Backend Error:Your order will exceed the maximum number of storage volumes allowed. Please contact Sales. Type:StorageOrderFailed, RC:500, Recommended Action(s):Wait a few minutes, then try re-creating your PVC. If the problem persists, open an IBM Cloud support case.

See the troubleshooting topic on [File storage and block storage: PVC remains in a pending state](https://cloud.ibm.com/docs/containers?topic=containers-file_pvc_pending) for more details.





 After I deploy a node, I'm seeing a message in my Kubernetes cluster on IBM Cloud reporting that the pod has hit a crash loop backoff. Is this an error?
Managing captures 

A capture is a trace file that you can generate to analyze what happens in a host during a time frame. For example, you can use it to analyze bottlenecks, or component interactions. In the IBM Cloud Monitoring service, you can create, explore, download, and delete captures for individual nodes.

The capture file size limit is 100 MB.

Captures contain system calls, and other OS events such as system-level latencies, batch jobs duration, deployments interruption times, autoscaling latencies, container startup times, or application transaction time. Captures include detailed information from every container on a node.

You can create, explore, download, and delete captures for individual nodes. A node can be a host, a container, a virtual machine, a bare metal, or any metrics source where you install a monitoring agent.



* In the web UI, you create captures in the Explore section and manage capture files through the Captures section.
* You can visualize data from a capture by using Csysdig (the curses-based command-line UI).
* You can search data in a capture by using filters.
* You can manipulate data in a capture by using chisels (scripts).



When you enable the capture feature for a team, capture files are only visible to members of that team.

The following list outlines the main tasks when you work with captures:



* [Creating a capture](https://cloud.ibm.com/docs/monitoring?topic=monitoring-capturescaptures_create)
* [Deleting a capture](https://cloud.ibm.com/docs/monitoring?topic=monitoring-capturescaptures_delete)
* [Explore a capture](https://cloud.ibm.com/docs/monitoring?topic=monitoring-capturescaptures_explore)
* [Download a capture](https://cloud.ibm.com/docs/monitoring?topic=monitoring-capturescaptures_download)





 Creating a capture 

You create a capture in the Explore view.

Complete the following steps to create a capture file:



1. Navigate to the Explore section in the web UI.
If you have worker nodes with 11 CPU cores or more, you can support 10 pods per core, up to a limit of 250 pods per worker node. The number of pods includes kube-system and ibm-system pods that run on the worker node. For improved performance, consider limiting the number of pods that you run per compute core so that you don't overuse the worker node. For example, on a worker node with a b3c.4x16 flavor, you might run 10 pods per core that use no more than 75% of the worker node total capacity. 
 Time-based one-time passcode (TOTP) To use [TOTP](https://cloud.ibm.com/docs/account?topic=account-totp), make sure that you [enable multifactor authentication (MFA)](https://cloud.ibm.com/docs/account?topic=account-enablemfa) for your entire IBM Cloud account. If MFA is enabled only for some users but not at the account level, authentication errors might occur. 
 Worker node quota You can't exceed 500 worker nodes across all clusters in a region, per [infrastructure provider](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers). If you need more of the resource, [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the support case, include the new quota limit for the region and infrastructure provider that you want. 
 Worker pool size You must always have a minimum of 2 worker nodes in your cluster . Additionally, you can't scale down a worker pool to fewer than 2 worker nodes per zone. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqssmallest_cluster). You can't scale worker pools down to zero. Because of the worker node quota, you are limited in the number of worker pools per cluster and number of worker nodes per worker pool.