vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* For general guidance about adding audio to a custom acoustic model, see [Guidelines for adding audio](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audioResourcesaudioGuidelines).
* For more information about the maximum amount of audio that you can add to a custom acoustic model, see [Maximum hours of audio](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audioResourcesaudioMaximum).





 Monitoring the add audio request 

The service returns a 201 response code if the audio is valid. It then asynchronously analyzes the contents of the audio file or files and automatically extracts information about the audio such as length, sampling rate, and encoding. You cannot train the custom model until the service's analysis of all audio resources for current requests completes.

To determine the status of the request, use the GET /v1/acoustic_customizations/{customization_id}/audio/{audio_name} method to poll the status of the audio. The method accepts the customization ID of the custom model and the name of the audio resource. Its response includes the status of the resource, which has one of the following values:



* ok indicates that the audio is acceptable and analysis is complete.
* being_processed indicates that the service is still analyzing the audio.
* invalid indicates that the audio file is not acceptable for processing. It might have the wrong format, the wrong sampling rate, or not be an audio file. For an archive file, if any of the audio files that it contains are invalid, the entire archive is invalid.



The content of the response and location of the status field depend on the type of the resource, audio or archive.



* For an audio-type resource, the status field is located in the top-level (AudioListing) object.

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/acoustic_customizations/{customization_id}/audio/audio1"

IBM Cloud Pak for Data
"network_type": "unbound_gre_tunnel",
"base_network_type": "classic",
"remote_bgp_asn": 65010,
"remote_gateway_ip": "10.242.63.12",
"remote_tunnel_ip": "192.168.129.1",
"zone": {
"name": "us-south-1"
}
}







 Response 

The following response results show after you initiate the request:



Table 3. Initating request response

 Response body Details 

 name <br>Always included* <br>Name The user-defined name for this transit gateway connection. <br>Possible values:1 ≤ length ≤ 63, Value must match the regular expression: ^([a-zA-Z] 
 network_type <br>Always included* <br>string Defines what type of network is connected through this connection. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [unbound_gre_tunnel] <br>Example:unbound_gre_tunnel 
 id <br>Always included* <br>string The unique identifier for this transit gateway connection <br>Example:1a15dca5-7e33-45e1-b7c5-bc690e569531 
 created_at <br>Always included* <br>date-time The date and time that this connection was created. 
 base_network_type <br>string Defines what type of network the GRE tunnel is targeting. This field only applies to unbound_gre_tunnel type connections. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [classic] <br>Example:classic 
 local_bgp_asn <br>integer The local network BGP ASN. This field only applies to network type gre_tunnel and unbound_gre_tunnel connections. <br>Example:64490
When you configure your account to be HIPAA enabled, consider the following information:



* You can filter on HIPAA Enabled services in the catalog. Accounts that enable the HIPAA Supported setting still have access to the full catalog of services.
* You indicate to IBM that your account stores protected health information (PHI).
* You digitally accept the IBM Business Associate Addendum (BAA) for covered entities.



Enable this setting only if you or your company is a covered entity as defined by HIPAA. If you or your company is a business associate of a covered entity, [contact IBM Cloud Sales](https://www.ibm.com/account/reg/us-en/signup?formid=MAIL-wcp) to accept the applicable BAA. For more information about HIPAA definitions of covered entities and business associates, see the [US Department of Health & Human Services](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html) website.







 Define the logging instances strategy 

IBM Log Analysis collects and aggregates logs in one centralized logging system.



* Log data is hosted on the IBM Cloud.
* Data is collocated in the location where an IBM Log Analysis instance is provisioned.





 Locations 

You can provision instances of the IBM Log Analysis service in any of the supported locations in the IBM Cloud. For more information, see [Locations](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).

Per location (region), you can provision 1 or more logging instances.



* You can collect logs from custom applications and services that run in the IBM Cloud or outside, and forward them to any logging instance in your account.
* Only 1 instance in a location can be configured to collect logs automatically from [IBM Cloud enabled services](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services) in that IBM Cloud location.
* Each location represents the geographic area where your IBM Log Analysis requests are handled and processed for that instance, and where data is resident.
* Each MZR location has three different data centers for redundancy.
The spec.status field will contain details of your component's status:



* errorCode
* lastHeartbeatTime: when the controller last reconciled the component
* message: long explanation of the status type
* reason: short explanation of the status
* status: "true" or "false" based on if status is valid
* version: the product (IBP) version of the component
* versions: the operand version of the component
* type: describes the current status of the component



* Deploying: component pod(s) spinning up but not yet running and ready
* Deployed: component pod(s) are running
* Precreated: (specific to the Orderer) Orderer is waiting for the genesis block to be created
* Error: component hit an error during reconcile, or a certificate has expired
* Warning: one or more of the component's certificate will be expiring within 30 days (by default)
* Initializing: component is being reconciled again due to spec updates in the pre-reconcile checks





* Do you support using certificates from non-IBM Certificate Authorities?

Yes, you can bring your own certificates if they are issued by a CA that is X.509 compliant. The CA should sign by using ECDSA and the defaults should be set to use P256 curve. See this topic about [Using certificates from an external CA with your peer or ordering node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-third-party-ca).
* What is the recommended way to manage private keys?

Because private keys are not stored by the platform, users are responsible for downloading and securing their private key. Therefore, when a higher level of security is required for private keys, an HSM is recommended. An HSM is a hardware appliance that performs cryptographic operations and provides the capability to ensure that the cryptographic keys never leave the HSM. Hyperledger Fabric supports HSM devices that implement the PKCS #11 standard. PKCS #11 is a cryptographic standard for secure operations, generation, and storage of keys.
See [Customize the data displayed for a view](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-tutorial-use-logdnaLA-customize-log-format) for information on extracting log fields.
6. Scroll to the end of the page and click Build Parsing Template. A Reference Line for your log records is displayed.
7. Click the the Pencil icon ![Pencil icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/pencil.png) and enter a name for your parsing rule.

If you name a template before you click Build Parsing Template, the name is not changed.
8. Choose the Extract values by delimiter extractor.
9. For Delimiter specify a , (comma). A preview of the output delimited by a comma is presented for your review.
10. Choose one of the entries. For example, if your log contains a field called message you might select that line.
11. For Choose an Operator select Extract Values by Delimiter.
12. For Delimiter specify a delimiter that makes sense for your selected entry. For example, a reasonable delimiter might be a : (colon). A preview of the delimited output is presented for your review.
13. Select an entry containing a date value.
14. For Choose an Operator select Trim Value. Using the index range specify a starting and ending character position so only the date is retained in the displayed output.
15. For Choose an Operator select Capture in Field to set the name of the field that will capture this information.
16. For Field Name specify a name that you will use to reference this type of information.
17. At the end of the page click Proceed to Validation.
18.
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--name NAME
: Required. The name of the secret to add the field to.

--namespace NAMESPACE
: Required. The namespace that the secret is deployed to.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress secret field ls command 

ibmcloud oc ingress secret field ls --cluster a11a11a11a111a1a111a --name my-secret --namespace default







 ibmcloud oc ingress secret field rm 

Virtual Private Cloud

Classic infrastructure

ibmcloud oc ingress secret field rm --cluster CLUSTER --name NAME --namespace NAMESPACE [--field-name NAME]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--name NAME
: Required. The name of the secret to remove the field from.

--namespace NAMESPACE
: Required. The namespace that the secret is deployed to.

--field-name NAME
: The name of the field to remove. To see a list of fields, run [ibmcloud oc ingress secret field ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_secret_field_ls).



 Example ingress secret field rm command 

ibmcloud oc ingress secret field rm --cluster a11a11a11a111a1a111a --name my-secret --namespace default --field-name test-field-name







 ibmcloud oc ingress secret get 

Virtual Private Cloud

Classic infrastructure
* Indicates to IBM that your account stores protected health information (PHI)
* Digitally accepts the IBM Business Associate Addendum (BAA) for covered entities



Enable this setting only if you or your company is a covered entity as defined by HIPAA. If you or your company is a business associate of a covered entity, [contact IBM Cloud Sales](https://www.ibm.com/account/reg/us-en/signup?formid=MAIL-wcp) to accept the applicable BAA. For more information about HIPAA definitions of covered entities and business associates, see the [US Department of Health & Human Services](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html) website.

Accounts that enable the HIPAA Supported setting still have access to the full catalog of services.





 Step 2. Provision your IBM Cloud Activity Tracker instances with the HIPAA service plan 

The HIPAA plan allows a maximum of 25 team members per instance. If you need to grant permissions to more than 25 users, [open a support ticket](https://cloud.ibm.com/docs/get-support).

Choose any of the following methods to provision an instance of the IBM Cloud Activity Tracker service: [Provisioning an instance through the Observability dashboard](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-provisionprovision_ui)[Provisioning an instance through the catalog](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-provisionprovision_catalog)[Provisioning an instance through the CLI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-provisionprovision_cli)

Make sure that your naming convention for IBM Cloud Activity Tracker instances does not include PII information. Choose the HIPAA service plan for your Activity Tracker instances.



 Step 3. Label your service (optional) 

Set the tag HIPAA to the IBM Cloud Activity Tracker instances that you provision in your account.

Complete the following steps:



1.
serviceName.objectType.action

Where



* servicename is the name of the service.

There is an exception on the servicename that is set for actions reported by the VPC infrastructure. The format of the servicename is composed of 2 parts that are separated by a dot (.).
* objectType describes the resource or resource attribute on which the action is requested.
* action defines the task requested by the initiator.

Some valid actions are: activate, add, bulkdelete, create, read, update,delete, backup, build, capture, clear, commit, configure, deploy, disable, enable, get, import, inspect, list, monitor, pull, push, restore, start, stop, undeploy, receive, reimport, remove, send, set, setkeyfordeletion, set-on, set-off, authenticate, renew, revoke, allow, deny, evaluate, notify, reset, rotate, ack-delete, ack-restore, ack-disable, ack-enable, ack-rotate, edit, publish, authorize, write, pause, resume, unsetkeyfordeletion, failover, split



For more information about action values that are generated by services, see [Services generating events](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_servicescloud_services).

For example, a sample action is iam-am.policy.create.





 correlationId (string) 

This field indicates the unique GUID that you can use to correlate events across multiple services in your account.





 dataEvent (boolean) 

This field specifies the type of event, whether it is a management event or a data event.



* For a management event, this field is set to false.
* For a data event, this field is set to true.







 eventTime (string) 

This field indicates the timestamp when the event was created.

The timestamp that you see for an event in the UI is set from eventTime and indicates the time when the event was created.

The date is represented as Universal Time Coordinated (UTC).

The format of this field is:
serviceName.objectType.action

Where



* servicename is the name of the service.

There is an exception on the servicename that is set for actions reported by the VPC infrastructure. The format of the servicename is composed of 2 parts that are separated by a dot (.).
* objectType describes the resource or resource attribute on which the action is requested.
* action defines the task requested by the initiator.

Some valid actions are: activate, add, bulkdelete, create, read, update,delete, backup, build, capture, clear, commit, configure, deploy, disable, enable, get, import, inspect, list, monitor, pull, push, restore, start, stop, undeploy, receive, reimport, remove, send, set, setkeyfordeletion, set-on, set-off, authenticate, renew, revoke, allow, deny, evaluate, notify, reset, rotate, ack-delete, ack-restore, ack-disable, ack-enable, ack-rotate, edit, publish, authorize, write, pause, resume, unsetkeyfordeletion, failover, split



For more information about action values that are generated by services, see [Services generating events](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_servicecloud_services).

For example, a sample action is iam-am.policy.create.





 correlationId (string) 

This field indicates the unique GUID that you can use to correlate events across multiple services in your account.





 dataEvent (boolean) 

This field specifies the type of event, whether it is a management event or a data event.



* For a management event, this field is set to false.
* For a data event, this field is set to true.







 eventTime (string) 

This field indicates the timestamp when the event was created.

The timestamp that you see for an event in the UI is set from eventTime and indicates the time when the event was created.

The date is represented as Universal Time Coordinated (UTC).

The format of this field is:
The uppercase variables in the following section indicate that these parameters need to be set as environment variables on the virtual server instances to simplify the setup of the cluster.



1. Log in to [Workspaces - Power Systems Virtual Server](https://cloud.ibm.com/power/workspaces) and search for your Workspace.
2. The tile for the workspace contains the CRN, click Copy to copy the CRN and paste it to a temporary document.

The CRN has multiple sections that are divided by a colon. The base format of a CRN is:

crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource

service-name
: The fifth field of the CRN of the workspace is always power-iaas, the service name.

location
: The sixth field is the location, which needs to be mapped to the region.

scope
: The seventh field is the Tenant ID.

service_instance
: The eighth field is the Cloud Instance ID or GUID.
3. Set IBMCLOUD_CRN to the full CRN and GUID to the content of the service_instance field.
4. Set the CLOUD_REGION to the prefix that represents the geographic area of your service instance to target the correct [Power Cloud API endpoint](https://cloud.ibm.com/apidocs/power-cloudendpoint).

CLOUD_REGION when you use a public network
: For a public network, map the location to its respective geographic area (us-east, us-south, eu-de, lon, tor, syd, or tok).

CLOUD_REGION when you use a private network
: For a private network, map the location to its respective geographic area (us-east, us-south, eu-de, eu-gb, ca-tor, au-syd, jp-tok, jp-osa, br-sao, or ca-mon).
5. On the tile for the workspace, click View Instances.
6.
* keys is an array whose elements are arrays of the form [key, id], where key is a key that is emitted by the map function, and id identifies the document from which the key was generated values is an array of the values that are emitted for the respective elements in keys, for example: reduce([ key1,id1], key2,id2], key3,id3] ], [value1,value2,value3], false).



2. When rereduce is true:



* keys is null.
* values is an array of the values that are returned by previous calls to the reduce function, for example: reduce(null, [intermediate1,intermediate2,intermediate3], true).





Reduce functions must return a single value, suitable for both the value field of the final view, and as a member of the values array that is passed to the reduce function.

Often, reduce functions can be written to handle rereduce calls without any extra code, like the summation function in the earlier example. In such cases, the rereduce argument can be ignored.

By feeding the results of reduce functions back into the reduce function, MapReduce can split up the analysis of huge data sets into discrete, parallel tasks, which can be completed much faster.

When you use the built-in reduce function, if the input is invalid, the builtin_reduce_error error is returned. More detailed information about the failure is provided in the reason field. The original data that caused the error is returned in the caused_by field.

See an example reply:

{
"rows": [
{
"key": null,
"value": {
"error": "builtin_reduce_error",
"reason": "The _sum function requires that map values be numbers, arrays of numbers, or objects. Objects can't be mixed with other data structures. Objects can be arbitrarily nested, if the values for all fields are themselves numbers, arrays of numbers, or objects.",
"caused_by":
{
"a": 1
},
{
"a": 2
},
{
The new SPP is automatically added as a member of the PG policy. 
 Different server (Anti-affinity) Configure the new SPP on a different host than all host identified by all the existing PG members. The new SPP is automatically added as a member of the PG policy. 





 Creating a shared processor pool placement group 

To create an SPP PG, complete the following steps:



1. Go to Shared processor pools in the Power Systems Virtual Server user interface under Compute.
2. Click the Pool placement groups tab.
3. Click Create group.
4. In the Create new pool placement group window, enter the following details:



Table 4. Create a new SPP PG field description

 Field Description 

 Name Enter a name that is unique within your cloud account. <br>Use a minimum of 2 characters and a maximum of 12 characters. Alphanumeric characters are not allowed and underscore (‘_’) is only allowed as a special character. 
 Policy Same Server (Affinity) <br>Different server (Anti-affinity) 



5. Click Create.



You get notified when the new SPP PG is created.





 Adding a shared processor pool to a the placement group 

You can add an SPP as a member, to an existing SPP PG if the host of the SPP follows the affinity policy of the group. If the PG policy is set to Same server (affinity), all SPPs that are added as a member of the placement group must remain on the same host. If the PG policy is set to Different server (anti-affinity), the SPP is deployed on a different host other than all its group members.

To add an SPP to an existing SPP PG, complete the following steps:



1. Go to Shared processor pools in the Power Systems Virtual Server user interface under Compute.
2. Click the Pool placement groups tab.
3. Select an existing pool placement group to which you want to add an SPP.
4. Select one of the following options:





Table 5. Add SPP to an SPP PG: field description

 Field Description 

 Add existing You can choose from existing SPPs.
Bulk operations 

Use the bulk document API to create and update multiple documents at the same time within a single request. The basic operation is similar to creating or updating a single document, except that you batch the document structure and information.

When you create new documents, the document ID is optional. For updating existing documents, you must provide the document ID, revision information, and new document values.

A special case of bulk operations is the [_bulk_get](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-bulk-operationsthe-bulk_get-endpoint) endpoint.



 Bulk request structure 

For both inserts and updates, the basic structure of the JSON document in the request contains the following fields:



Table 1. Basic bulk request structure

 Field Description Type Optional 

 docs List of document objects Array of objects No 



It is best not to use the new_edits field. By default, if conflicts exist, document updates fail and return an error to the client. However, this option applies document revisions without checking for conflicts, so it is easy to accidentally end up with many conflicts.

Each docs array object has the following structure:



Table 2. Structure of the docs array object

 Field Description Type Optional 

 _id Document ID String Optional only for new documents. Otherwise, it's mandatory. 
 _rev Document revision String Mandatory for updates and deletes, not used for new documents. 
 _deleted Determines whether the document must be deleted. Boolean (Optional) The default value is false. 



Recall that for a partitioned database the _id field is formed from a partition key part and a document key part.

See an example of using HTTP to create, update, or delete multiple documents:

POST /$DATABASE/_bulk_docs HTTP/1.1
Content-Type: application/json

See an example of using the command line to create, update, or delete multiple documents:



* Curl
* Java
* Python
* Go
* Node