vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Notice message: <enrichment_name>: Document enrichment failed due to lack of memory

Suggested action: Increase the orchestrator container memory limit. Enter the following command to increase the memory limit from 4 Gi to 6 Gi:

oc patch wd wd --type=merge --patch='{"spec": {"orchestrator": {"resources": {"limits": {"memory": "6Gi"} } } } }'
* Notice messsage: Indexing request timed out

Suggested action: Increase the timeout for pushing documents to Elasticsearch. Enter the following command to increase the default timeout from 10 to 20 minutes:

oc patch wd wd --type=merge --patch='{"spec": {"shared": {"elastic": {"publishTimeoutSeconds": 1200 } } } }'
satellite.config-subscription.delete A Satellite subscription is removed. 
 satellite.config-subscription.setversion A Satellite subscription is set to a specific configuration version. 
 satellite.config-group.create A cluster group is created. 
 satellite.config-group.delete A cluster group is removed. 







 Events for Satellite storage 



Satellite storage actions that generate events.

 Action Description 

 satellite.storage-template.get A storage template is retrieved. 
 satellite.storage-template.list A list of storage templates is retrieved. 
 satellite.storage-template.get-changelog A storage template's change log is retrieved. 
 satellite.storage-configuration.get A storage configuration is retrieved. 
 satellite.storage-configuration.list A list of storage configurations is retrieved. 
 satellite.storage-configuration.get-desired A desired storage configuration is returned. 
 satellite.storage-configuration.set-desired A desired storage configuration request is created. 
 satellite.storage-configuration.delete-desired A storage request is deleted. 
 satellite.storage-configuration.expand-desired The desired capacity of a storage request is increased. 
 satellite.storage-configuration.ack-desired-capacity A storage capacity expansion request is acknowledged. 
 satellite.storage-configuration.get-assigned Assigned storage configuration details is returned. 
 satellite.storage-configuration.create A storage configuration is created. 
 satellite.storage-configuration.delete A storage configuration is deleted. 
 satellite.storage-configuration.update A storage configuration is updated. 
 satellite.storage-configuration.get-by-controller Lists storage configurations that are created for the given location. 
 satellite.storage-configuration.update-revision A storage configuration was updated to use the latest template revision. 







 Events for Satellite assignments 



Assignment actions that generate events.

 Action Description 

 satellite.subscription.get The details of assignment are retrieved. 
 satellite.subscription.list A list of assignments is retrieved. 
 satellite.subscription.get-by-name An assignment is retrieved. 
 satellite.subscription.get-by-config An assignment is retrieved by using the associated configuration. 
 satellite.subscription.get-by-controller A list of assignments is retrieved by using a location.
new-tier
: For endurance storage only. Enter the new number of IOPS per GB that you want. For valid IOPS, see [Deciding on the File Storage for Classic configuration](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass). If you don't specify the IOPS, the current IOPS is used. If the original IOPS/GB ratio for the volume is less than 0.25, the new IOPS/GB ratio must be less than 0.25. If the original IOPS/GB ratio for the volume is greater than or equal to 0.25, the new IOPS/GB ratio for the volume must be greater than or equal to 0.25.

Example output

Order 31020713 was placed successfully!.
> Storage as a Service

> 40 GBs

> 2 IOPS per GB

> 20 GB Storage Space (Snapshot Space)

You may run 'ibmcloud sl file volume-list --order 12345667' to find this file volume after it is ready.
4. If you changed the size of your volume and you use the volume in a pod, log in to your pod to verify the new size. List all the pods that use PVC. Pods are returned in the format: <pod_name>: <pvc_name>.

kubectl get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"
5. Log in to your pod.

kubectl exec -it <pod_name> bash
6. Show the disk usage statistics and find the server path for your volume that you retrieved earlier.

df -h

Example output

Filesystem Size Used Avail Use% Mounted on
overlay 99G 4.8G 89G 6% /
To limit the amount of secondary storage that is consumed by your pod, use resource requests and limits for [ephemeral storage](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/local-ephemeral-storage). 
 Data access pattern Read and write operations of any frequency Read and write operations of any frequency 
 Access Via the container's local file system Via [Kubernetes hostPath](https://kubernetes.io/docs/concepts/storage/volumes/hostpath) for access to worker node primary storage. Via [Kubernetes emptyDir volume](https://kubernetes.io/docs/concepts/storage/volumes/emptydir) for access to worker node secondary storage. 
 Performance High High with lower latency when you use SSD 
 Resiliency Low Low 
 Availability Specific to the container Specific to the worker node 
 Scalability Difficult to extend as limited to the worker node's secondary disk capacity Difficult to extend as limited to the worker node's primary and secondary disk capacity 
 Durability Data is lost when the container crashes or is removed. Data in hostPath or emptyDir volumes is lost when the worker node is deleted, the worker node is reloaded or updated, the cluster is deleted, the IBM Cloud account reaches a suspended state. In addition, data in an emptyDir volume is removed when the assigned pod is permanently deleted from the worker node, the assigned pod is scheduled on another worker node. 
 Common use cases Local image cache or container logs Setting up a high-performance local cache, accessing files from the worker node file system, or running unit tests. 
 Non-ideal use cases Persistent data storage or sharing data between containers Persistent data storage 







 Persistent storage for single zone clusters 

If you have a single zone cluster, you can choose between the following options in IBM Cloud Kubernetes Service that provide fast access to your data. For higher availability, use a storage option that is designed for geographically distributed data and, if possible for your requirements, create a multizone cluster.

The following image shows the options that you have in IBM Cloud Kubernetes Service to permanently store your data in a single cluster.

Zoom

!
This error occurs when the amount of memory that is remaining for your organization is less than the amount of memory that is required by the app that you want to deploy. The maximum memory quota for a Lite account is 256 MB.

 How to fix it 

You can either increase the memory quota of your account, or reduce the memory that your apps use.



* To increase the memory quota of your account, upgrade your Lite account to a billable account. For more information, see [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
* To reduce the memory that your apps use, use either the IBM Cloud console or the Cloud Foundry command line interface.



If you use the IBM Cloud console, complete the following steps:



1. Select your app from the resource list. The app details page opens.
2. In the runtime pane, you can reduce the maximum memory limit or the numbers of app instances, or both, for your app.



If you use the command line interface, complete the following steps:



1. Check how much memory is being used for your apps:

ibmcloud cf list

The ibmcloud cf list command lists all the apps that you deployed in your current space. The status of each app is also displayed.
2. To reduce the amount of memory that is used by your app, reduce the number of app instances or the maximum memory limit, or both:

ibmcloud cf push appname -p app_path -i instance_number -m memory_limit
3. Restart your app for the changes to take effect.







 Apps aren't automatically restarted 

An app isn't automatically restarted when a service that you bind to the app stops working.

 What’s happening 

When a service that you bind to an app crashes, problems such as outages, exceptions, and connection failures might occur on the app. IBM Cloud doesn't automatically restart the app to recover from these problems.

 Why it’s happening 

This behavior is by design of Cloud Foundry.

 How to fix it 

You can manually restart an app that is already deployed by typing the following command in the command-line interface:
Build fails when the ephemeral storage limit is exceeded 

 What’s happening 

After you create and run a build, your build does not complete successfully and you receive a message that the ephemeral storage usage exceeds limits.

 Why it’s happening 

If you receive a message that the ephemeral storage limit is exceeded, then your build size is too small.

When a build runs, it needs to load the source code. When you use a Docker build, the base image needs to be downloaded and the necessary steps to build the target image need to be performed. The build run needs disk space for these steps, which is released after the build run is finished. This disk space is called ephemeral local storage. Depending on whether you choose a small, medium, large, or xlarge size for your build, a maximum amount of ephemeral storage is available to a build run. When the maximum ephemeral storage is reached, the build run is stopped with an error message; for example,

Example error messages

Summary: Failed to run build due to exceeded ephemeral storage
Reason: Pod ephemeral local storage usage exceeds the total limit of containers <AMOUNT>.

Summary: Failed to run build due to exceeded ephemeral storage
Reason: Container <STEP_NAME> exceeded its local ephemeral storage limit <AMOUNT>.

 How to fix it 

Try using the following information to resolve your problem.

Whether you are running your build in the console or in the CLI, use the CLI for troubleshooting problems with your build.



1. Run the ibmcloud ce buildrun get --name BUILDRUN_NAME command to display the details of your build run.
2. Review the Reason in the command output.



To resolve this problem, use a larger size for the build.

A larger build size also means that more memory and CPU cores are assigned to the build runs. Increasing this size will probably speed up the build runs, but also increases their cost.

For more information about build sizes, see [Determining build sizes](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-size).



1.
For more information, see [Adjusting IOPS for block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops).

You can monitor the progress of your volume expansion from the UI or CLI. You can also use the [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events) to verify that the volume was expanded. After a volume is expanded, you can't reduce its capacity.

You can resize a data volume that is attached to an IBM Cloud Hyper Protect Virtual Servers for IBM Cloud® Virtual Private Cloud instance, however you must restart the instance to use the resized volume.

z/OS - Experimental When you expand block storage volume capacity on an existing z/OS virtual server instance, a new device address is broadcasted to the users with the additional storage size.





 Boot volumes 

By default, when you create an instance from a stock image, a 100 GB, 3,000 IOPS boot volume is created and attached to the instance. Instances that are created from a custom image can have a boot volume capacity 10 GB to 250 GB.

For either stock or custom images, you can increase boot volume capacity from its minimum provisioned size up to 250 GB, either when you provision an instance or when you update the boot volume from the list of block storage volumes. For more information, see [Increasing boot volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes).

The boot volume expansion takes effect without a reboot. However, to use the increased boot volume space, you must expand your operating system so the increased boot volume capacity is recognized. For more information, see [Modifying a Linux OS for expanding boot volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-modifying-the-linux-os-expanded-boot-volume).







 Requirements 



 Data volume requirements 

You must meet the following requirements to increase a data volume's capacity.



* The volume is expanded based on their predefined IOPS profile or custom IOPS range.
For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_reference). If you want to change any of the pre-set values, create your own customized storage class.
5. Decide on a name for your bucket. The name of a bucket must be unique in IBM Cloud Object Storage. You can also choose to automatically create a name for your bucket by the IBM Cloud Object Storage plug-in. To organize data in a bucket, you can create subdirectories.

The storage class that you chose earlier determines the pricing for the entire bucket. You can't define different storage classes for subdirectories. If you want to store data with different access requirements, consider creating multiple buckets by using multiple PVCs.
6. Choose if you want to keep your data and the bucket after the cluster or the persistent volume claim (PVC) is deleted. When you delete the PVC, the PV is always deleted. You can choose if you want to also automatically delete the data and the bucket when you delete the PVC. Your IBM Cloud Object Storage service instance is independent from the retention policy that you select for your data and is never removed when you delete a PVC.



Now that you decided on the configuration that you want, you are ready to [create a PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_apps) to provision IBM Cloud Object Storage.





 Verifying your installation 

Review the pod details to verify that the plug-in installation succeeded.



1. Verify the installation succeeded by listing the driver pods.

oc get pod --all-namespaces -o wide | grep object

Example output

ibmcloud-object-storage-driver-9n8g8 1/1 Running 0 2m
ibmcloud-object-storage-plugin-7c774d484b-pcnnx 1/1 Running 0 2m
Again right-click the Disk tile and select Initialize Disk from the menu, check to make sure that the correct disk is selected, select GPT as the default partition style - see footnote (+) below - and click Ok
1. Now right-click the related tile to the right that shows Unallocated and select New Simple Volume...
1. Click Next twice, which retains the default value for the disk size and then specify your preferred drive letter, or leave the default and click Next
1. Overwrite the Folder Name, for example, SAP and leave the other default values and click Next - note, that File System FAT32 is NOT SUPPORTED for SAP applications
1. Check the values and click Finish
1. After the volume has been prepared and formatted, you can find the new disk in the Windows Explorer

(+) [!About partition styles - GPT and MBR.](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/initialize-new-disksabout-partition-styles---gpt-and-mbr)

 Specifying the page file

1. Start the Windows Control Panel
1. Click System and Security then System
1. Click Advanced system settings
1. Click the tab Advanced then in Section Performance the button Settings...
1. Click the tab Advanced then in Section Virtual memory the button Change...
1. Deselect the check mark Automacally manage...
1. Select drive C: and click Custom size
1. Enter Initial size and Maximum size 32768, click Set and Ok

Your next step is to [download and install your SAP software and applications](install-sap-wins) if a single virtual server sample is sufficient for your needs.

 Installing two virtual server instances in a 3-tier setup {: 3-tier-wins step}

A more complex scenario involves installing two virtual servers. One server is the SAP NetWeaver Application Server (sap-wapp) and the other server (sap-wdb) is the database server for SAP NetWeaver.
* UI
* CLI
* API
* Terraform







 Adjusting IOPS 

With this feature, IBM Cloud® File Storage for Classic storage users can adjust the IOPS of their existing File Storage for Classic immediately. They don't need to create a duplicate or manually copy data to new storage. Users don't experience any kind of outage or lack of access to the storage while the adjustment is taking place.

Billing for the storage is updated to add the pro-rated difference of the new price to the current billing cycle. The full new amount is billed in the next billing cycle.



 Advantages of adjustable IOPS 



* Cost management – Some of our clients might need high IOPS just during peak usage times. For example, a large retail store has peak usage during the holidays and might need higher IOPS on their storage then than in the middle of the summer. This feature allows them to manage their costs and pay for higher IOPs only when they need it.







 Limitations 

Clients can’t switch between Endurance and Performance when they adjust their IOPS. Users can specify a new IOPS tier or IOPS level for their storage based on the following criteria and restrictions.



* If original volume is Endurance 0.25 tier, IOPS tier can’t be updated.
* If original volume is Performance with less than or equal to 0.30 IOPS/GB, options available include only the size and IOPS combinations that result in less than or equal to 0.30 IOPS/GB.
* If original volume is Performance with more than 0.30 IOPS/GB, options available include only the size and IOPS combinations that result in more than 0.30 IOPS/GB.





Table 1. Available IOPS based on volume size for Performance volumes

 Volume size (GB) IOPS range 

 10 - 39 100 - 1,000 
 40 - 79 100 - 2,000 
 80 - 99 100 - 4,000 
 100 - 499 100 - 6,000 
 500 - 999 100 - 10,000 
 1,000 - 1,999 100 - 20,000 
 2,000 - 2,999 200 - 40,000 
 3,000 - 3,999 200 - 48,000 
 4,000 - 7,999 300 - 48,000
For details, see [About IBM COS SDKs](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-about).





 Is there a 100-bucket limit to an account? What happens if I need more? 

Yes, 100 is the current bucket limit. Generally, prefixes are a better way to group objects in a bucket, unless the data needs to be in a different region or storage class. For example, to group patient records, you would use one prefix per patient. If this is not a workable solution and you require additional buckets, contact IBM customer support.





 If I want to store my data by using IBM Cloud Object Storage Vault or Cold Vault, do I need to create another account? 

No, storage classes (and regions as well) are defined at the bucket level. Simply create a new bucket that is set to the wanted storage class.





 When I create a bucket by using the API, how do I set the storage class? 

The storage class (for example, us-smart) is assigned to the LocationConstraint configuration variable for that bucket. This is because of a key difference between the way AWS S3 and IBM Cloud Object Storage handle storage classes. Object Storage sets storage classes at the bucket level, while AWS S3 assigns a storage class to an individual object. For a list of valid provisioning codes for LocationConstraint, see [the Storage Classes guide](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-classes).





 Can the storage class of a bucket be changed? For example, if you have production data in 'standard', can we easily switch it to 'vault' for billing purposes if we are not using it frequently? 

You can change the storage class by manually moving or copying the data from one bucket to another bucket with the wanted storage class.





 Can the location of a bucket be changed? 

To change a location, create a new bucket in the desired location and move existing data to the new bucket.





 Does data consistency in Object Storage come with a performance impact?
* Plan for high availability of instance management, including the possibility of multiple instances, multiple clusters, and vCenter HA.
* Use backup solutions such as Veeam to plan for business continuity for your workloads.







 Storage planning 

In addition to capacity planning, complete the following to ensure that your storage configuration meets your performance and availability requirements:



* Storage performance depends on various factors. This action includes RAID configuration and disk striping, network configuration, block size, IOPS configuration (input/output operations per second) for network-attached storage. Also, VM hardware configuration and method of storage attachment, clustering and replication methods, and use of storage policies such as encryption, deduplication, and compression. Plan time to test and adjust your configuration to meet your storage performance needs.
* Review your vSAN storage policy:



* RAID 1 provides better performance and smaller windows of susceptibility to sequential failure, such as shorter rebuild time, than RAID 5. However, RAID 5 has less storage overload.
* RAID 6 provides protection against dual failures, but requires a minimum of six hosts compared to four hosts for RAID 5.



* To add more storage to your vSAN cluster, you must add new hosts to the cluster or add IBM Cloud VPC file storage instead. Adding disks to the existing hosts is not currently supported.







 Related links 



* [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers)
* [IBM Cloud VPC RYO VMware reference architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-arch-overview)
* [IBM Cloud Direct Link overview](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
The RAM provisioned to your deployment remains for your future needs, or until you scale down your deployment manually. The disk provisioned to your deployment remains because disk cannot be scaled down.
* If you need to add resources to your deployment only occasionally or rarely, [manually scale](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling) your deployment.
* Read-only replicas do not auto-scale to match the leader. If the amount of data you store outgrows the disk that is allocated to your deployments, scale the disk on the read-only replicas and then the leader. Scaling the read-only replica first ensures that you do not run out of space on the read-only replicas. If you scaled the leader's disk for performance and not for space, it is not necessary to scale the read-only replicas.







 Configuring Autoscaling in the UI 

The Autoscaling panel is on the Resources tab of your deployment's Manage page. To enable scaling, enter your parameters. Then, check the boxes to enable the parameters you are using. Be sure to click Save Changes for your configuration to be saved and your changes to take effect.

To disable autoscaling, clear the boxes for the parameters that you no longer want to use. If you clear all the boxes, autoscaling is disabled. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

You can get the autoscaling parameters for your deployment through the CLI by using the [cdb deployment-autoscaling](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-) command.

ibmcloud cdb deployment-autoscaling <deployment name or CRN> member