vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The name of an audio file that is contained in an archive-type resource can include a maximum of 128 characters. This includes the file extension and all elements of the name (for example, slashes).

The following example from [Add audio to the custom acoustic model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-acousticaddAudio) adds an application/zip file that contains audio files in audio/l16 format that are sampled at 16 kHz:

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/zip" --header "Contained-Content-Type: audio/l16;rate=16000" --data-binary @audio2.zip "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: application/zip" --header "Contained-Content-Type: audio/l16;rate=16000" --data-binary @audio2.zip "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"





 Guidelines for adding audio 

The improvement in recognition accuracy that you can expect from using a custom acoustic model depends on a number of factors. These factors include how much audio data the custom acoustic model contains and how similar that data is to the audio that is being transcribed. The improvement also depends on whether the custom acoustic model is trained with a corresponding custom language model.

Follow these guidelines when you add audio resources to a custom acoustic model:



* Add at least 10 minutes of audio that includes speech, not silence.

The quality of the audio makes a difference when you are determining how much to add. The better the model's audio reflects the characteristics of the audio that is to be recognized, the better the quality of the custom model for speech recognition. If the audio is of good quality, adding more can improve transcription accuracy. But adding even five to ten hours of good quality audio can make a positive difference.
{site.data.keyword.attribute-definition-list}}



  Troubleshooting custom images 

When you create or manage custom images, you might encounter issues. Issues, symptoms, likely causes, and resolutions are described in the following sections.



  Cannot retrieve a volume in a specified region 

You are trying to create a custom image from a volume that does not have 100 GB capacity. When you try to select a volume that is not the right capacity to create your image, the system cannot retrieve it.

When you create a customer image from an existing boot volume, the image inherits the encryption from the originating volume. If the boot volume was encrypted by a customer-managed root key, the new customer image is also encrypted with the same key. If the volume had the default, IBM-managed encryption, and you specify a new customer key, the new custom is encrypted by the customer-managed key. The volumes that are to be used as the source for new encrypted images with customer keys must have 100 GB capacity. Custom images can be between 10 - 250 GB but volumes that are intended to be the source for new encrypted images must be 100 GB capacity.

Specify a source volume with 100 GB capacity. Optionally, resize the source volume and try the request again.
multipart_chunksize=part_size
)

 create transfer manager
transfer_mgr = ibm_boto3.s3.transfer.TransferManager(cos_cli, config=transfer_config)

try:
 initiate file upload
future = transfer_mgr.upload(file_path, bucket_name, item_name)

 wait for upload to complete
future.result()

print ("Large file upload complete!")
except Exception as e:
print("Unable to complete large file upload: {0}".format(e))
finally:
transfer_mgr.shutdown()
Show more





 List items in a bucket (v2) 

The [S3.Client](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlclient) object has an updated method to list the contents ([list_objects_v2](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Client.list_objects_v2)). This method allows you to limit the number of records that are returned and retrieve the records in batches. This might be useful for paging your results within an application and improve performance.

def get_bucket_contents_v2(bucket_name, max_keys):
print("Retrieving bucket contents from: {0}".format(bucket_name))
try:
 create client object
cos_cli = ibm_boto3.client("s3",
ibm_api_key_id=COS_API_KEY_ID,
ibm_service_instance_id=COS_SERVICE_CRN,
config=Config(signature_version="oauth"),
endpoint_url=COS_ENDPOINT)

more_results = True
next_token = ""

while (more_results):
* host_bucket {: S3cmd} This is the same whether you use the example file or the one generated by running: s3cmd --configure.



Once those lines have been updated with the COS details from the Customer portal, you can test the connection by issuing the command s3cmd ls, which will list all the buckets on the account.

$ s3cmd ls
2017-02-03 14:52 s3://backuptest
2017-02-06 15:04 s3://coldbackups
2017-02-03 21:23 s3://largebackup
2017-02-07 17:44 s3://winbackup

The full list of options and commands along with basic usage information is available on the [s3tools](https://s3tools.org/usage) site.





 Multipart uploads with S3cmd 

A put command will automatically run a multi-part upload when attempting to upload a file larger than the specified threshold..

s3cmd put FILE [FILE...] s3://BUCKET[/PREFIX]

The threshold is determined by the --multipart-chunk-size-mb option:

--multipart-chunk-size-mb=SIZE
Size of each chunk of a multipart upload. Files bigger
than SIZE are automatically uploaded as multithreaded-
multipart, smaller files are uploaded using the
traditional method. SIZE is in megabytes, default
chunk size is 15MB, minimum allowed chunk size is 5MB,
maximum is 5GB.

Example:

s3cmd put bigfile.pdf s3://backuptest/bigfile.pdf --multipart-chunk-size-mb=5

Output:

upload: 'bigfile.pdf' -> 's3://backuptest/bigfile.pdf' [part 1 of 4, 5MB] [1 of 1]
5242880 of 5242880 100% in 2s 1731.92 kB/s done
Required.

The maximum length is 36 characters. The minimum length is 7 characters. The value must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|current|previous)$/.

--secret-version-action-prototype ([SecretVersionActionPrototype](https://cloud.ibm.com/docs/secrets-manager-cli-plugin?topic=secrets-manager-cli-plugin-secrets-manager-clicli-secret-version-action-prototype-example-schema))
: The request body to specify the properties of the action to create a secret version. Required.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --secret-version-action-prototype=@path/to/file.json.





 Example 

ibmcloud secrets-manager secret-version-action-create --secret-id=0b5571f7-21e6-42b7-91c5-3f5ac9793a46 --id=eb4cf24d-9cae-424b-945e-159788a5f535 --secret-version-action-prototype='{"action_type": "private_cert_action_revoke_certificate"}'





 Example output 

The request body of the action to revoke private certificate versions.

{
"action_type" : "private_cert_action_revoke_certificate",
"revocation_time_seconds" : 1667982994
}









 Secret locks 

Secure your secret data by attaching a lock to a secret version and preventing any modification or deletion.



 ibmcloud secrets-manager secrets-locks 

List the secrets and their locks in your Secrets Manager instance.
If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 validation_unique_failed 

Message: The field supplied must be unique.

You might have specified a name that is already in use. Try a different value.

Make sure your request conforms to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic). If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 version_not_supported 

Message Version specified is not supported. The version query parameter must be 2019-05-31 or later.





 volume_action_invalid_request 

Message: The volume cannot be attached or detached from the instance in its current status.

You cannot attach or detach a volume when the target instance is in deleting, pending, starting, stopping or restarting status, or it has another volume attachment in attaching or detaching status. If the status of the instance or volume attachment does not change, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 volume_attachment_delete_invalid_request 

Message: The volume attachment cannot be deleted.

This operation is not allowed. The boot volume's volume attachment cannot be deleted because the boot volume is required by the instance.





 volume_attachment_over_quota 

Message: The volume cannot be attached because the number of volume attachments would exceed the quota.

The quotas per instance are specified in [Quotas: Block storage volumes](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotasblock-storage-quotas).





 volume_attachment_update_invalid_request 

Message: The volume attachment could not be updated because the request is invalid.
The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

--type (string)
: Type of the integration KMS/hs-crypto.

The maximum length is 50 characters. The minimum length is 1 characters. Allowed values are KMS and hs-crypto.

--metadata ([IntegrationReplaceAttributes](https://cloud.ibm.com/docs/cli?topic=cli-event-notifications-clien-cli-integration-example-schema))
: Integration schema for update

Metadata required for integration.

--id (string)
: Unique identifier for integration. Required.

The maximum length is 100 characters. The minimum length is 1 character. The value must match regular expression /[a-zA-Z0-9-:_]/.



* Examples:



* The following example shows the format of the IntegrationReplaceAttributes object.

{
"endpoint" : "https://qa.us-south.kms.test.cloud.ibm.com",
"crn" : "crn of key protect/hpcs instance",
"root_key_id" : "root key id"
}











 ibmcloud event-notifications integration list 

List all Integrations.

ibmcloud event-notifications Integration list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]



 Command options 

--instance-id (string)
: Unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters.
The API call shows the combined number of Block Storage for Classic and File Storage for Classic.







 Requesting limit increase 

You can request a limit increase by submitting a support case in the [portal](https://cloud.ibm.com/unifiedsupport/cases/add). When the request is approved, you get a volume limit that is set for a specific data center.

To request a limit increase, open a support case and direct it to your sales representative.

In the ticket, provide the following information:



* Ticket Subject: Request to Increase Data Center Volume Count Storage Limit
* What is the use case for the additional volumes request?For example, your answer might be something similar to a new VMware® datastore, a new development and testing environment, an SQL database, or logging.
* How many extra Block volumes are needed by type, size, IOPS, and location?For example, your answer might be "25x Endurance 2 TB @ 4 IOPS in DAL09" or "25x Performance 4 TB @ 2 IOPS in WDC04".
* How many extra File volumes are needed by type, size, IOPS, and location?For example, your answer might be "25x Performance 20 GB @ 10 IOPS in DAL09" or "50x Endurance 2 TB @ 0.25 IOPS in SJC03".
* Provide an estimate of when you expect or plan to provision all of the requested volume increase.For example, your answer might be "90 days".
* Provide a 90-day forecast of expected average capacity usage of these volumes.For example, your answer might be "expect 25 percent to be used in 30 days, 50 percent to be used in 60 days and 75 percent to be used in 90 days".



Respond to all questions and statements in your request. They are required for processing and approval.

You're going to be notified of the update to your limits through the case handling process.
AttachDetachMaxRetryAttempt: "46" Total number of retries for for checking Attach/Detach Status. Default is 46 times i.e 7 mins (3 secs * 3 times + 6 secs * 6 times + 10 secs * 10 times)
AttacherWorkerThreads: "15" The number of goroutines for processing VolumeAttachments
AttacherKubeAPIBurst: "10" The number of requests to the Kubernetes API server, exceeding the QPS, that can be sent at any given time
AttacherKubeAPIQPS: "5.0" The number of requests per second sent by a Kubernetes client to the Kubernetes API server.
Requested resources per container
CSIDriverRegistrarCPURequest: "10m" container:csi-driver-registrar, resource-type: cpu-request
CSIDriverRegistrarMemoryRequest: "20Mi" container:csi-driver-registrar, resource-type: memory-request
NodeDriverMemoryRequest: "30m" container:iks-vpc-block-node-driver, resource-type: cpu-request
NodeDriverCPURequest: "75Mi" container:iks-vpc-block-node-driver, resource-type: memory-request
LivenessProbeCPURequest: "5m" container:liveness-probe, resource-type: cpu-request
LivenessProbeMemoryRequest: "10Mi" container:liveness-probe, resource-type: memory-request
SecretSidecarCPURequest: "10m" container:storage-secret-sidecar, resource-type: cpu-request
SecretSidecarMemoryRequest: "20Mi" container:storage-secret-sidecar, resource-type: memory-request
CSIProvisionerCPURequest: "20m" container:csi-provisioner, resource-type: cpu-request
CSIProvisionerMemoryRequest: "40Mi" container:csi-provisioner, resource-type: memory-request
CSIAttacherCPURequest: "15m" container:csi-attacher, resource-type: cpu-request
: The offset for paginated results.

The minimum value is 0.

--search SEARCH (string)
: The search string for filtering results.

The maximum length is 100 characters. The minimum length is 0 characters. The value must match regular expression /[a-zA-Z0-9]/.

[--instance-id INSTANCE-ID] (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.







 ibmcloud event-notifications subscription get 



* Action: Get specific Subscription.

ibmcloud event-notifications subscription get --id ID [--instance-id INSTANCE-ID]
* Parameters to provide:

--id ID (string)
: Unique identifier for subscription. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}/.

[--instance-id INSTANCE-ID] (string)
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.
Starting large file upload for py_large_file_722319147bba4fc4a6c111cc21eb11b5.bin to bucket: py.bucket.779177bfe41945edb458294d0b25440a
Large file upload complete!
Retrieving bucket contents from: py.bucket.779177bfe41945edb458294d0b25440a
Item: py_file_17b79068b7c845658f2f74249e14e267.txt (46 bytes).
Item: py_large_file_722319147bba4fc4a6c111cc21eb11b5.bin (20971520 bytes).
DONE!

Deleting item: py_large_file_722319147bba4fc4a6c111cc21eb11b5.bin from bucket: py.bucket.779177bfe41945edb458294d0b25440a
Item: py_large_file_722319147bba4fc4a6c111cc21eb11b5.bin deleted!
DONE!

Deleting item: py_file_17b79068b7c845658f2f74249e14e267.txt from bucket: py.bucket.779177bfe41945edb458294d0b25440a
Item: py_file_17b79068b7c845658f2f74249e14e267.txt deleted!
DONE!

Deleting bucket: py.bucket.779177bfe41945edb458294d0b25440a
Bucket: py.bucket.779177bfe41945edb458294d0b25440a deleted!
DONE!

Waiting for bucket "go.bucket645" to be created...
The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

--subject SUBJECT (string)
: The subject for notification.

The minimum length is 1 character.

[--severity SEVERITY] or --ce-ibmenseverity CE-IBMENSEVERITY (string)
: The level of severity for notification. Required.

The minimum length is 1 character. The value must match regular expression /[a-zA-Z 0-9-_/.

--id or --ce-id (string)
: The Notification ID. Required

The minimum length is 1 character. The value must match regular expression /a-zA-Z 0-9-_/.

--source SOURCE] or -ce-source CE-SOURCE (string)
: The source description. Required

The minimum length is 1 character. The value must match regular expression /a-zA-Z 0-9-_/.

--en-source-id] or --ce-ibmensourceid CE-IBMENSOURCEID (string)
: The source ID to be set for Notification source. Required.

The minimum length is 1 character. The value must match regular expression /a-zA-Z 0-9-_/.

--type TYPE] or --ce-type CE-TYPE] (string)
: The type of notification. Required.

The minimum length is 1 character. The value must match regular expression /a-zA-Z 0-9-_/.

--time TIME] or --time TIME] (string)
: The Timestamp to be set for notification. Required.

The minimum length is 1 character. The value must match regular expression /a-zA-Z 0-9-_/.
The minimum length is 2 characters. The value must match regular expression /^[0-9]+[s,m,h,d]{0,1}$/.

--allow-localhost (bool)
: This field indicates whether to allow localhost to be included as one of the requested common names.

--allowed-domains ([]string)
: The domains to define for the certificate template. This property is used along with the allow_bare_domains and allow_subdomains options.

The list items must match regular expression /(.?)/. The maximum length is 100 items. The minimum length is 0 items.

--allowed-domains-template (bool)
: This field indicates whether to allow the domains that are supplied in the allowed_domains field to contain access control list (ACL) templates.

--allow-bare-domains (bool)
: This field indicates whether to allow clients to request private certificates that match the value of the actual domains on the final certificate.

For example, if you specify example.com in the allowed_domains field, you grant clients the ability to request a certificate that contains the name example.com as one of the DNS values on the final certificate.

Important: In some scenarios, allowing bare domains can be considered a security risk.

--allow-subdomains (bool)
: This field indicates whether to allow clients to request private certificates with common names (CN) that are subdomains of the CNs that are allowed by the other certificate template options. This includes wildcard subdomains.

For example, if allowed_domains has a value of example.com and allow_subdomainsis set to true, then the following subdomains are allowed: foo.example.com, bar.example.com, .example.com.

Note: This field is redundant if you use the allow_any_name option.

--allow-glob-domains (bool)
: This field indicates whether to allow glob patterns, for example, ftp.example.com, in the names that are specified in the allowed_domains field.
The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

--type (string)
: Type of the integration KMS/hs-crypto.

The maximum length is 50 characters. The minimum length is 1 characters. Allowed values are KMS and hs-crypto.

--metadata ([IntegrationReplaceAttributes](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-cli-plugin-event-notifications-clien-cli-integration-example-schema))
: Integration schema for update

Metadata required for integration.

--id (string)
: Unique identifier for integration. Required.

The maximum length is 100 characters. The minimum length is 1 character. The value must match regular expression /[a-zA-Z0-9-:_]/.



* Examples:



* The following example shows the format of the IntegrationReplaceAttributes object.

{
"endpoint" : "https://qa.us-south.kms.test.cloud.ibm.com",
"crn" : "crn of key protect/hpcs instance",
"root_key_id" : "root key id"
}











 ibmcloud event-notifications integration list 

List all Integrations.

ibmcloud event-notifications Integration list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]



 Command options 

--instance-id (string)
: Unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters.
"href": "$vpc_api_endpoint/v1/share/profiles/tier-5iops",
"name": "tier-5iops",
"resource_type": "share_profile"
}
]
}





 How block size affects file share performance 

IOPS is based on a 16 KB block size for all profiles, with a 50-50 read/write random workload. Each 16 KB of data that is read or written counts as one read/write operation. A single write of less than 16 KB counts as a single write operation.

Baseline throughput is determined by the amount of IOPS multiplied by the 16 KB block size. The higher the IOPS you specify, the higher the throughput. Maximum throughput is 1536 MBps.

The block size that you choose for I/O from your application directly impacts storage performance. If the block size is smaller than the block size used by the profile to calculate the share’s bandwidth limit, the IOPS limit is reached before the throughput limit. Conversely, if the block size is larger, the throughput limit is reached before the IOPS limit.

Table 5 provides some examples of how block size and IOPS affect the throughput, calculated average I/O block size x IOPS = Throughput in MBps.



Table 5. How block size and IOPS affect throughput

 Block Size (KB) IOPS Throughput (MBps) 

 4 1000 4¹ 
 8 1000 8¹ 
 16 1000 16 
 32 500 16 
 64 250 16 
 128 128 16 
 512 32 16 
 1024 16 16 



¹If your cap is 1000 IOPS or 16 KB block size, the throughput caps at whatever limit is reached first.

Maximum IOPS can still be obtained when you use smaller block sizes, but throughput is less. The following example shows how throughput decreases for smaller block sizes, when max IOPS is maintained.



* 16 KB * 6000 IOPS == 94 MBps
* 8 KB * 6000 IOPS == 47 MBps
* 4 KB * 6000 IOPS == 23 MBps







 Next steps