vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The master volume is charged 2x size based on its Tier under the existing part numbers for Tier 1 and Tier 3.
* Replication capability cost is charged $Y/GB under a new part number "GLOBAL_REPLICATION_STORAGE_GIGABYTE_HOURS" that is independent of volume tier.



Upon a site failure due to a catastrophe, metering is not available from the failed site. The auxiliary volumes are charged from remote site for its 2x size based on its tier. There is no replication capability cost for any replication-enabled volume.





 Setting up the Global replication service 

The GRS involves two sites where storage replication is enabled. These two sites are fixed and mapped into one-to-one relationship mode in both directions. These two sites are fixed and are in replication partnership in both directions.

You can create a replication-enabled volume from any site, the site from where the request is initiated contains the master volume and play the role of master. The remote site is auxiliary and contain an auxiliary volume.

The following table explains how to determine the primary and secondary site based on replication-enabled volume creation:



Table 2. Primary and secondary site reference based on volume creation

 Replication-enabled volume creation site Primary site (master volume) Secondary site (auxiliary volume) 

 Site 1 Site 1 Site 2 
 Site 2 Site 2 Site 1 







 Preparation for disaster recovery 

When you have the virtual server instances with data volume running workloads, you can ensure that your data volumes are replicated and can be recovered from the remote site, in case of failure by performing [actions on primary site](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started-GRSconfigure-primary-site) and [secondary site](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started-GRSconfigure-secondary-site).



 Actions on the primary site 

To enable DR on the primary site, complete the following steps:



1.
When you deploy WAR or EAR files, the buildpack provides a configuration for the app with a default set of Liberty features. Although rare, that default set of Liberty features might change between the buildpack releases. The change in the default feature set might adversely affect the app. There are options to ensure that the app is not affected by the change in the feature defaults.



* Set the JBP_CONFIG_LIBERTY environment variable to explicitly specify a list of enabled features for the app. For more information, see [Stand-alone Apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingstand_alone_apps).
* Deploy your app as 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). Provide a custom server.xml file that specifies the exact set of features that are needed by your app.



Apps that are deployed as a server directory or a packaged server are unaffected by the change in the Liberty features default.





 Java version 

The buildpack provides a default JRE for the app. The major or minor version of the JRE might change between the buildpack releases. The minor version of the JRE might be updated frequently while the major version is rarely updated. The change in the major version of the JRE might adversely affect the app.

To ensure that the app is not affected by the major version change, set the environment variable with the appropriate JRE version as described in [Customizing the JRE](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-customizing_jre). For best results, adopt Java 8 for your apps.
Location Availability zone in your region, inherited from the VPC (for example, US South 1). 
 Size Size of the volume you specified, in GBs. 
 Attachment type Data, for a secondary volume attached to an instance, boot when attached as a boot volume, or blank for an unattached volume. 
 Health Health monitors the overall health of the volume, such as I/O performance and data consistency. Volume health statuses are OK or degraded. Volumes in a degraded state have degraded performance, capacity, or experience connection problems. Volumes being restored from a snapshot also show a degraded state. The service displays a possible reason for the degraded state so that you can resolve any issues. For more information, see [Block Storage for VPC volume health states](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storageblock-storage-vpc-health-states). 
 Encryption Encryption with IBM-managed keys is enabled by default on all volumes. You can also use your own root keys in a Key Protect or Hyper Protect Crypto Services instance to protect your data. For more information, see [Creating Block Storage for VPC volumes with customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption). 
 Tags Number of user tags that are applied to the volume. Click the number in this column to view or edit the tags in the new window. If no tags were applied to the volume, click Add tags and add them in the new window. User tags can associate the volume with a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-about) for creating backups of the volume. For more information, see [Add tags to Block Storage for VPC volumes for backup policies](https://test.cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uiblock-storage-add-tags). 
 Actions (...) Click the icon (...) to display a menu of context-specific actions you can take.
* Action: Print out information about an in progress multipart upload instance.
* Usage:ibmcloud cos parts --bucket BUCKET_NAME --key KEY --upload-id ID --part-number-marker VALUE [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* The KEY of the object.



* Flag: --key KEY



* Upload ID identifying the multipart upload.



* Flag: --upload-id ID



* Part number VALUE after which listing begins (default: 1)



* Flag: --part-number-marker VALUE



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out. (default: 1000)



* Flag: --page-size SIZE



* Optional: The total NUMBER of items to return in the command's output. If the total number of items available is more than the value specified, a NextToken is provided in the command's output. To resume pagination, provide the NextToken value in the starting-token argument of a subsequent command. (default: 0)



* Flag: --max-items NUMBER



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 Set bucket CORS 



* Action: Sets the CORS configuration for a bucket in the user's IBM Cloud Object Storage account.
* Usage:ibmcloud cos bucket-cors-put --bucket BUCKET_NAME [--cors-configuration STRUCTURE] [--region REGION] [--output FORMAT]
* Parameters to provide:
The API health status shows degraded, with the health reason initializing_from_snapshot and a message indicates that initializing from the snapshot failed.

 Why it’s happening 

Some or all of the data was not downloaded from Object Storage to the volume that's being created. Data blocks were not written.

 How to fix it 

Contact IBM support to determine the root cause of the failure and resolve the problem.





 A snapshot of a volume is in an unusable state during volume restoration 

 What’s happening 

The snapshot is in an unusable state and the data can't be restored from the snapshot. In this case, the health state is faulted. You can see the API health reason initializing_from_snapshot and a message that the snapshot is in an unusable state.

 Why it’s happening 

The data was not downloaded from Object Storage when you tried to restore a volume because the snapshot is not available. A possible cause is that the customer root key for the snapshot was disabled or deleted.

 How to fix it 

You can [enable a root key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-disable-keys&interface=uienable-ui) or [restore a root key](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managing&interface=uibyok-restore-root-key) within 30 days of deletion. Restoring the root key makes the snapshot available. For other issues, contact IBM support to determine the root cause of the failure and fix the problem.
* For more information about audio compression, see [Data compression (Audio)](https://wikipedia.org/wiki/Data_compressionAudio).
* For more information about the compression that is available with the audio formats that the service supports, see [Audio formats](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audio-formatsaudio-formats-list).
* For more information about using data compression to increase the amount of audio that you can send with a request, see [Data limits and compression](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audio-formatsaudio-formats-limits).









 Channels 

Channels indicate the number of streams of the recorded audio:



* Monaural (or mono) audio has only a single channel.
* Stereophonic (or stereo) audio typically has two channels.



The Speech to Text service accepts audio with a maximum of 16 channels. Because it uses only a single channel for speech recognition, the service downmixes audio with multiple channels to one-channel mono during transcoding.



 Notes about audio formats 



* For the audio/l16 format, you must specify the number of channels if your audio has more than one channel.
* For the audio/wav format, the service accepts audio with a maximum of nine channels.







 More information 



* For more information about audio channels, see [Audio signal](https://wikipedia.org/wiki/Audio_signal).









 Endianness 

Endianness indicates how bytes of data are organized by the underlying computer architecture:



* Big-endian orders data by most-significant bit.
* Little-endian orders data by least-significant bit.



The Speech to Text service automatically detects the endianness of the incoming audio.



 Notes about audio formats 



* For the audio/l16 format, you can specify the endianness to disable auto-detection if needed.







 More information 



* For more information about endianness, see [Endianness](https://wikipedia.org/wiki/Endianness).









 Audio frequency
The peer also includes a gRPC web proxy container, you cannot adjust the compute for this container.

As we noted in our section on [Considerations before you deploy a node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-before), it is recommended to use the defaults for these peer containers and adjust them later when it becomes apparent how they are being utilized by your use case.



 Resources Condition to increase 

 Peer container CPU and memory When you anticipate a high transaction throughput right away. 
 Peer storage When you anticipate installing many smart contracts on this peer and to join it to many channels. Recall that this storage will also be used to store smart contracts from all channels the peer is joined to. Keep in mind that we estimate a "small" transaction to be in the range of 10,000 bytes (10k). As the default storage is 100G, this means that as many as 10 million total transactions will fit in peer storage before it will need to be expanded (as a practical matter, the maximum number will be less than this, as transactions can vary in size and the number does not include smart contracts). While 100G might therefore seem like much more storage than is needed, keep in mind that storage is relatively inexpensive, and that the process for increasing it is more difficult (require command line) than increasing CPU or memory. 
 CouchDB container CPU and memory When you anticipate a high volume of queries against a large state database. This effect can be mitigated somewhat by using [indexes](https://hyperledger-fabric.readthedocs.io/en/release-2.2/couchdb_as_state_database.htmlcouchdb-indexes). Nevertheless, high volumes might strain CouchDB, which can lead to query and transaction timeouts. 
 CouchDB (ledger data) storage When you expect high throughput on many channels and don't plan to use indexes. However, like the peer storage, the default CouchDB storage is 100G, which is significant.
Red Hat® OpenShift® cluster RHEL7/RHEL8 and CoreOS 2 
 IBM Cloud Kubernetes cluster Ubuntu 18 2 









 Data Security Broker Manager and Data Security Broker Shield Sizing Guidelines 

The factors that affect the sizing of the Data Security Broker deployments consist of the Data Security Broker Manager management console and one or more Data Security Broker Shield proxies. Each component has its own resource needs depending on the anticipated workloads.





 Data Security Broker Manager 

In general, resources allocated to a Data Security Broker Manager deployment needs to be scaled with the number of managed Data Security Broker Shields and the number of concurrent users using the Data Security Broker Manager.





 Data Security Broker Shield 

The general rule for Data Security Broker Shield sizing, to handle peak utilization scenarios, is to match the sum of all Data Security Broker Shield's memory and CPU allocations to that of the database instance. The initial vCPU and memory requests for the pod installation can start low and can be scaled up based on utilization, based on pod scaling policies, and depending on the workload in a particular installation. Resource allocation to Data Security Broker Shield deployments typically scales with the expected maximum number of concurrent connections.

Data Security Broker Shield consists of a single container that runs in its own pod. The Data Security Broker Shield pod can be in the same or different cluster but must have network connectivity to Data Security Broker Manager.





 Recommended sizing for Kubernetes or Red Hat OpenShift Deployments for Data Security Broker Manager and Data Security Broker Shield: 

4 CPU, 8 GB Memory





 Setting up minimum permissions required to install, set up, and access Data Security Broker 

As an IBM Cloud user, you need to set the follwoing minimum permissions to install, set up and access Data Security Broker. By using the following steps and the information in the table, assign the required permissions:



1. Log into your IBM Cloud account and click Manage -> Access (IAM).
2. In the Manage access and users dashboard, click View all in the My user details section.
3. In the Access tab, click Assign access +. From the Table 1, select a service and click Next.
4.
You add [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-about-tags) to your volumes and specify the same tags in a backup policy. When the tags match, a backup is triggered based on the backup plan schedule. You can [view backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs) to see the progress of the operation. The Snapshot for VPC service is used to create the backup. The entire contents of the volume are copied and retained for the number of days or total number of backups that are specified in the backup plan. When the retention period is reached, the older backups are deleted.
* What resources are backed up?

Block Storage for VPC data and boot volumes with user tags that match the tags in a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-policies) are backed up.
* How do enable my volumes to be backed up?

Enabling your backups is two-part process. First, you [specify user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies) on the Block Storage for VPC volumes that you want to back up. You then [create a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create) and specify these tags, which identify the volumes that you're backing up. Within a policy, you create a [backup plan](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create&interface=uibackup-plan-ui) to schedule backups of these resources. You can schedule backups to be taken every daily, weekly, or monthly.
* How many backups can I create?

You can create up to 750 backups per volume per account.
NetworkDisabled Boolean Displays true if the networking is disabled for the container and false if the networking is enabled for the container. 
 OnBuild Array of strings Displays the ONBUILD metadata that was defined on the image Dockerfile. 
 OpenStdin Boolean Displays true if the standard input stream is opened and false if the standard input stream is closed. 
 Shell Array of strings Displays the shell-form of RUN, CMD, ENTRYPOINT. 
 StdinOnce Boolean Displays true if the standard input stream is closed after the attached client disconnects and false if the standard input stream stays open. 
 StopSignal String Describes the UNIX® stop signal to send when to stop the container. 
 StopTimeout Integer Displays the timeout in seconds to stop a container. 
 Tty Boolean Displays true if a pseudo-tty is allocated to the container and false if not. 
 User String Displays the user that runs commands inside the container where the image is used. 
 Volumes Key-Value map Displays the list of volume mounts that are mounted to a container. 
 WorkingDir String Displays the working directory inside the container where specified commands are run. 







 Healthcheck field details 



Table 5. Available fields and data types in Healthcheck

 Field Type Description 

 Interval Integer (64 bit) Displays the time to wait between two health checks in nanoseconds. 
 Retries Integer Displays the number of consecutive failures that are needed to consider a container as not working correctly. 
 Test Array of strings Displays how to run the health check test. The following options are available.<br><br><br><br> * {} inherit the health check.<br> * {"NONE"} the health check is disabled.<br> * {"CMD", args...} exec arguments directly.<br> * {"CMD-SHELL", command} run the command with the system's default shell.<br><br><br> 
 Timeout Integer (64 bit) Displays the time to wait, in nanoseconds, before the health check fails. 







 RootFS field details 



Table 6. Available fields and data types in RootFS

 Option Type Description
Deleting a document that is associated with an annotation task and human annotation has begun 

If the document you want to delete is associated with an annotation task and human annotation has begun, complete these steps to delete the document.

Do not delete a task if human annotation is in progress. If you do, you will lose the work that is in progress.



 Procedure to follow 



1. Tell the human annotators to ignore the unwanted document in the set.
2. After all annotation work is complete on the other documents, and the human annotators submit all the documents to add the set to the ground truth, [review and accept the submitted documents](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-build-groundtruthwks_haaccuracy).
3. [Resolve any annotation conflicts](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-build-groundtruthwks_haadjudicate).
4. When all the documents are part of the ground truth and the task is complete, delete the task as described in [Deleting a document that is associated with an annotation task and human annotation has not begun](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-documents-for-annotationdeletenoannop).
5. Delete the document as described in [Deleting a document that has not been associated with an annotation task](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-documents-for-annotationdeletenotask).

You can confirm that the annotations on the remaining documents are not lost by downloading the document sets and reviewing the documents in the gt folder.











 Data model
Log in as a Knowledge Studio administrator and select your workspace.
2. Select the Assets> Documents > Document sets tab.
3. Select the document set that contains the document you want to delete. The document set opens.
4. Find the document that you want to remove, and then click Delete.









 Deleting a document that is associated with an annotation task and human annotation has not begun 

If the document you want to delete is associated with an annotation task and human annotation has not yet begun, complete these steps to delete the document.



 Procedures 



1. Log in as a Knowledge Studio administrator and select your workspace.
2. Delete the annotation task:

a. Open the Machine Learning Model > Annotations page. Click the Annotation Tasks tab.

b. Find the annotation task that the document is associated with, click the Show menu icon on the task, and then click Delete.
3. Delete the document as described in [Deleting a document that has not been associated with an annotation task](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-documents-for-annotationdeletenotask).
4. After you delete the document, recreate the annotation task and associate the same annotation set, which now has one less document in it.









 Deleting a document that is associated with an annotation task and human annotation has begun 

If the document you want to delete is associated with an annotation task and human annotation has begun, complete these steps to delete the document.

Do not delete a task if human annotation is in progress. If you do, you will lose the work that is in progress.



 Procedure to follow 



1. Tell the human annotators to ignore the unwanted document in the set.
2.
Tekton Pipelines environment and resources 

The following information and resources are available by default to an IBM Cloud® Continuous Delivery Tekton PipelineRun.



 PipelineRun annotations 

Table 1 describes the annotations that are included in a Tekton PipelineRun.



Table 1. PipelineRun annotations

 Run Annotation Description 

 devops.cloud.ibm.com/build-number The build number for the pipeline. This number is the cumulative total of pipeline runs from all triggers. 
 devops.cloud.ibm.com/listener The Tekton eventlistener that is mapped to the trigger that initiated this pipeline run. 
 devops.cloud.ibm.com/pipeline-id The unique ID of the pipeline that is used for this run. 
 devops.cloud.ibm.com/trigger-name The name of the trigger that initiated this pipeline run. 
 devops.cloud.ibm.com/trigger-type The type of the trigger that initiated this pipeline run. The type can be either manual, timer, scm, or generic. 
 devops.cloud.ibm.com/triggered-by The user who initiated the trigger. This value is the IBMId of either the user who pressed run for manual triggers, the user who last saved the trigger for timer triggers, or the user who performed the Git action for scm triggers. This value is empty for generic triggers. 
 devops.cloud.ibm.com/pipeline-run-url The URL of the details page for this pipeline run. 
 devops.cloud.ibm.com/tekton-pipeline The unique ID of this pipeline run. 





 Accessing annotations 

You can access annotations from the tasks within your pipeline definition YAML file. The following example shows how to access the devops.cloud.ibm.com/build-number annotation. To provide that annotation as an environment variable, replace it with one of the run annotations from Table 1. PipelineRun annotations.

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
name: simple-task
spec:
steps:
- name: simple-step
image: ubuntu