vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Your files must be placed in the /tmp/.schematics folder and the size limit is set to 10 MB. Schematics backups and restores all the files in the /tmp/.schematics folder.





 How do I identify the best way to synchronize a deleted resource with the Terraform state? 

Currently, the IBM Cloud Schematics service does not support the ability to import or synchronize the IBM Cloud resource state into the Schematics Workspace. It is planned in the future roadmap.





 How do I overcome the request exceeds the Cluster resource quota of '100' for the account in any region? 

Error: Request failed with status code: 403, ServerErrorResponse: {"incidentID":"706efb2c-3461-4b9d-a52c-038fda3929ea,706efb2c-3461-4b9d-a52c-038fda3929ea","code":"E60b6","description":"This request exceeds the 'Cluster' resource quota of '100' for the account in this region. Your account already has '100' of the resource in the region, and the request would add '1'. Revise your request, remove any unnecessary resources, or contact IBM support to increase your quota.","type":"General"}

You see this quota validation error when the Cluster resource quota of 100 for the account in this region is exceeded. You can consider deleting the existing resources and try running operation again.





 While creating Red Hat OpenShift or Kubernetes resources, can I tune 90 minutes time out to higher? 

Yes, you can increase the timeout for Red Hat OpenShift or Kubernetes resources. For more information, see [ibm_container_vpc_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_vpc_clustertimeouts) provides the following Timeouts configuration options.





 How can I rectify the 403 Error while validating the location in the account. Verify you have permission to the location in the global catalog settings?
Volumes that were created by using an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers-beta) can be expanded to the maximum size for its IOPS tier:



* A general-purpose, 3 IOPS/GB profile can be expanded up to 16,000 GB.
* A 5 IOPS/GB profile can be expanded up to 9,600 GB.
* A 10 IOPS/GB profile can be expanded up to 4,800 GB.



IOPS values are automatically adjusted for tiered profiles, based on the size of the volume. For example, if you expand a volume that was created by using a 5 IOPS/GB profile from the original size of 250 GB to the expanded size of 1,000 GB, it has a max IOPS of 5,000 IOPS (1,000 GB capacity x 5 IOPS). Because a 5 IOPS/GB volume can potentially expand to 9,600 GB, the max IOPS would adjust to 48,000 IOPS. While the volume capacity is immediately changed, to realize increased IOPS, you must restart the instance.

Volumes that are created from a [Custom profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) can be expanded within their custom IOPS range. Depending on the range you originally set, this range can be up to 16,000 GB. IOPS remains constant at the level that you set when you created the custom volume. You can later increase or decrease IOPS, based on the new size of the volume. 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.
* UI
* CLI
* API
* Terraform







 Expanding Block Storage for Classic Capacity 

With this feature, current IBM Cloud® Block Storage for Classic users can expand the size of their existing Block Storage for Classic in GB increments up to 12 TB immediately. They don't need to create a duplicate or manually migrate data to a larger volume.

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

The upgrade process is not instantaneous. You can expect to see the updated size in the UI or through the API in a short while after you put in the modification request. Resizing does not cause an outage or lack of access to the storage, so you can continue your operations as normal while you wait. When the expansion is complete, the host Operating system must rescan the volume, and reload the multipath device map to reflect the change in size. You must resize the partition and the file system to allocate the new unused capacity.



 Advantages of Expandable Storage 



* Cost management – You might know of a potential for growth of your data, but you need a smaller amount of storage to start. The ability to expand allows our customers to save on cost of storage, and later grow to accommodate their needs.
* Growing Storage needs - Customers who experience rapid data growth need a way to quickly and easily increase the size of their storage to manage it.







 Effects of expanding storage capacity on Replication 

The expand action on the primary storage results in automatic resizing of the replica.





 Limitations 

Storage that was provisioned before the release of this feature, during April 2017 - 14 December 2017, can be increased to 10 times its original size and no more. Storage that was provisioned after 14 December 2017 can be increased up to 12 TB.

Existing size limitations for Block Storage for Classic that was provisioned with Endurance still apply (up to 4 TB for 10 IOPS tier and up to 12 TB for all other tiers).





 Resizing storage in the UI 



1. From the IBM Cloud® console, click the menu!
To set a limit on how much storage is available for the bucket, set the --set quotaLimit=trueVPC clusters only: To enable authorized IPs on VPC, set the --set bucketAccessPolicy=true option.



If you don't set the --set quotaLimit=true option during installation, you can't set quotas for your PVCs.

Example helm ibmc install commands for OS X and Linux

helm ibmc install ibm-object-storage-plugin ibm-helm/ibm-object-storage-plugin --set license=true [--set quotaLimit=true/false] [--set bucketAccessPolicy=false] [--set allowCrossNsSecret=true/false]

quotaLimit
: A quota limit sets the maximum amount of storage (in bytes) available for a bucket. If you set this option to true, then when you create PVCs, the quota on buckets created by those PVCs is equal to the PVC size.

allowCrossNsSecret
: By default, the plug-in searches for the Kubernetes secret in namespaces other than the PVC namespace. If you set this option to false the plug-in searches for the Kubernetes secret in only the PVC namespace.

Example helm install command for Windows.

helm install ibm-object-storage-plugin ./ibm-object-storage-plugin --set dcname="${DC_NAME}" --set provider="${CLUSTER_PROVIDER}" --set workerOS="${WORKER_OS}" --region="${REGION} --set platform="${PLATFORM}" --set license=true [--set bucketAccessPolicy=false]

DC_NAME
: The cluster data center. To retrieve the data center, run oc get cm cluster-info -n kube-system -o jsonpath="{.data.cluster-config.json}{'n'}". Store the data center value in an environment variable by running SET DC_NAME=<datacenter>.
* Action: List all Topic.

ibmcloud event-notifications topic list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]
* Parameters to provide:

--limit LIMIT (int64)
: The page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset OFFSET (int64)
: 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 topic get 



* Action: Get specific Topic.

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

--id ID (string)
: Unique identifier for topic. 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}/.

--include INCLUDE (string)
: Include sub topics.

The default value is ``.
curl "https://$ACCOUNT.cloudant.com/$DATABASE/_partition/$PARTITION_KEY/_design/$DDOC/_search/$INDEX_NAME?include_docs=true&query=":"&limit=1"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.PostPartitionSearchOptions;
import com.ibm.cloud.cloudant.v1.model.SearchResult;

Cloudant service = Cloudant.newInstance();

PostPartitionSearchOptions searchOptions =
new PostPartitionSearchOptions.Builder()
.db("<db-name>")
.partitionKey("<partition-key>")
.ddoc("<ddoc>")
.index("<index-name>")
.query(":")
.includeDocs(true)
.limit(1)
.build();

SearchResult response =
service.postPartitionSearch(searchOptions).execute()
.getResult();

System.out.println(response);

import { CloudantV1 } from '@ibm-cloud/cloudant';

const service = CloudantV1.newInstance({});

service.postSearch({
db: '<db-name>',
partitionKey: '<partition-key>',
ddoc: '<ddoc>',
index: '<index-name>',
query: ':',
includeDocs: true,
limit: 1
}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_search(
db='<db-name>',
ibmcloud sl file volume-count [OPTIONS]

Command options:

-d, --datacenter
: Filter by datacenter shortname.





 ibmcloud sl file volume-limits 

Display the global maximum volume count for the account and the number of Block Storage and File Storage volumes that are already provisioned.

ibmcloud sl file volume-limits

Examples:

ibmcloud sl file volume-limits

This command lists the storage limits for this account.





 ibmcloud sl file volume-list 

List file storage:

ibmcloud sl file volume-list [OPTIONS]

Command options:

-u, --username
: Filter by volume username.

-d, --datacenter
: Filter by data center shortname.

-t, --storage-type
: Filter by type of storage volume, options are: performance, endurance.

-o, --order
: Filter by ID of the order that purchased the file storage.

--sortby
: Column to sort by. Default: id. Options are: id, username, datacenter, storage_type, capacity_gb, bytes_used, ip_addr,active_transactions, created_by, mount_addr.

--column
: Column to display. Options are: id, username, datacenter, storage_type, capacity_gb, bytes_used, ip_addr, active_transactions,mount_addr, created_by, notes. This option can be specified multiple times.

Examples:

ibmcloud sl file volume-list -d dal09 -t endurance --sortby capacity_gb

This command lists all endurance volumes on the current account that are located in data center dal09, and sorts them by capacity.





 ibmcloud sl file volume-convert 

Convert a dependent duplicate volume to an independent volume:

ibmcloud sl file volume-convert VOLUME_ID

Examples:

ibmcloud sl file volume-convert 12345678

Convert a dependent duplicate 12345678 to an independent volume.





 ibmcloud sl file volume-detail 

Display details for a specified volume:
Logs that exceed the set limit are truncated, so any new log entries are ignored, and a warning is added as the last output of the activation to indicate that the activation exceeded the set log limit. 10 0 10 
 memory The memory limit M is in the range from [128 MB..2048 MB] and is set per action in MB. A user can change the memory limit when an action is created. A container cannot use more memory than is allocated by the limit. 256 128 2048 
 minuteRate No more than N activations can be submitted per namespace per minute. The rate limit N is set to 5000 and limits the number of action invocations in 1-minute windows. A CLI or API call that exceeds this limit receives an error code corresponding to HTTP status code 429: TOO MANY REQUESTS. This limit value is fixed, but can be increased if a business case can justify higher safety limit values. See [Increasing fixed limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_fixed) for instructions on how to increase this limit. 5000 1 5000 
 openulimit The maximum number of open files for an action is 1024 (for both hard and soft limits). This limit is fixed and cannot be changed. When an action is invoked, the docker run command uses the argument --ulimit nofile=1024:1024 to set the openulimit value. For more information, see the [docker run](https://docs.docker.com/engine/reference/commandline/run/) command line reference documentation. 1024 0 1024 
 parameters The maximum size of the parameters that can be attached in MB. The size limit for the total parameters on creating or updating of an action, package, or trigger is 5 MB. An entity with too large parameters is rejected on trying to create or update it. This limit is fixed and cannot be changed. 5 0 5 
 proculimit The maximum number of processes available to the action container is 1024. This limit is fixed and cannot be changed.
<br><br> * JSON file that you downloaded from a Knowledge Studio workspace.<br> * ZIP file that you downloaded from the Human Annotation Tool (HAT)<br><br><br> JSON To avoid visual overload for human annotation, define no more than 50 entity types and 50 relation types. File size limitation for uploading a type system: 20 MB 
 Dictionary management Upload a CSV dictionary file in read-only mode or a ZIP of dictionaries that you downloaded from another workspace. Create a new dictionary, and then upload a CSV file of term entries or add term entries to it. Dictionary file:<br><br><br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries downloaded from another workspace<br><br><br><br>Term entries file:<br><br><br><br> * CSV file in UTF-8 format<br><br><br> <br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries to use in another workspace<br><br><br> File size limitations:<br><br><br><br> * 1 MB per CSV term entries file<br> * 16 MB per CSV read-only dictionary file<br> * 15,000 entries per dictionary, except a read-only dictionary<br> * 64 dictionaries per workspace<br><br><br> 







 Machine learning model 

Table 2: Machine learning model



 Task Typical usage Supported input formats Supported output formats Limits and requirements 

 Document management Upload a small, representative subset of documents Upload documents that contain annotations previously added by a human annotator, a machine learning model, or a UIMA analysis engine You cannot ingest the entire corpus from IBM Watson Explorer for calculating high value documents for annotation.
Limits when sending logs 

There are limits when you send send logs to an IBM® Log Analysis instance.

Body size
:   Maximum size of 10 MB at ingestion.

Message size
:   Maximum size of 16 KB at ingestion. After 16K, the ingested data is truncated.

Metadata size
:   Maximum size of 32 KB.

Hostname length
:   Maximum size of 256 characters.

App name length
:   Maximum size of 512 characters.

Log Level
:   Maximum size of 80 characters.

Tags
:   Maximum size of 80 characters.

Depth of nested fields
:   The maximum number of nested fields that are parsed at ingestion is 3.

Number of unique fields
:   A maximum of 500 fields are indexed per day.
Created 2022-02-24T16:43:47+05:30
Zone us-south-1
Volume Attachment Instance Reference Attachment type Instance ID Instance name Auto delete Attachment ID Attachment name
boot 0716_84f99419-554d-4c05-bea0-7034d1c40ed3 vsi-1 true 0716-ee0ca315-7a21-42e2-99f7-b68377bbffe0 boot-vol-name

Operating system ubuntu-20-04-amd64
Source image ID Name
9f6b534b-6061-40f4-ac42-5aba4dd0da7f ubuntu-20-04-3-minimal-amd64-1

Active true
Busy false
Tags -







 Increasing boot volume capacity with the API 



 Increasing boot volume capacity when you create an instance with the API 

When you create an instance by making a POST instances request, you can specify larger boot volume capacity for any of these contexts: when you create the instance from an image, a source boot volume, or an instance template. Specify a boot volume name and capacity in the boot-volume-attachment property. The capacity for the boot volume must be at least the image's minimum provisioned size, which is the default if you don't specify capacity.

The following example creates a virtual server instance from an image, with a boot volume that has 250 GB capacity.

curl -X POST "$vpc_api_endpoint/v1/instances?version=2022-02-01&generation=2" -H "Authorization: $iam_token" -d '{
"boot_volume_attachment": {
"volume": {
"capacity": 250",
"encryption_key": {
"crn": "crn:[...]"
},
"name": "my-boot-volume",
"profile": {
"name": "general-purpose"
}
}
},
"image": {
How can I address storage space limits? 

Depending on your subscription plan, you might reach the storage limit that is specified for your plan and be prevented from completing tasks.

  What’s happening 

You might see a message about exceeding the allowed storage space when you attempt to perform one of these tasks:



*  Upload documents or dictionaries
*  Deploy a model or version a model
*  Run a pre-annotator on documents



  Why it’s happening 

The storage limit is met or exceeded if the action proceeds.

  How to fix it 

The largest consumers of storage space are machine learning and rule-based models. To free up space, you can take the following actions:



*  Delete snapshot versions of any models that you do not expect to need to revert to.
*  Delete any models that you do not need.
*  If your models are too important to delete, consider upgrading your plan to one that provides a larger allotment of storage space.



After you remove models or model versions, wait an hour before you retry the action that resulted in the error message. It can take up to an hour for the storage space that you freed up to be available for use.

To manage your monthly bill, if the Admin role is assigned to you and you have a Premium or Standard account, you can set a storage limit on the Service Details page in Knowledge Studio. To see the Service Details page and set the storage limit, from the top navigation bar in Knowledge Studio, click the Settings icon, click the View/modify service details link, and then click the Set storage limit link.
^'"<>{}\x00-\x1F]*$/\.
--location (string): The location where the project's data and tools are created. Required.
The maximum length is 12 characters. The minimum length is 0 characters. The value must match regular expression /^$|^(us-south|us-east|eu-gb|eu-de)$/.
--name (string): The name of the project. Required.
The maximum length is 64 characters. The minimum length is 1 character. The value must match regular expression /^(?\s)(?.\s$)^'"<>{}\x00-\x1F\+$/\.
--description (string): A brief explanation of the project's use in the configuration of a deployable architecture. It is possible to create a project without providing a description.
The maximum length is 1024 characters. The minimum length is 0 characters. The value must match regular expression /^$|^(?\s).\S$/.
--destroy-on-delete (bool): The policy that indicates whether the resources are destroyed or not when a project is deleted.
The default value is true.
--configs (ProjectConfigPrototype]]ProjectConfigPrototype] ! ! ): The project configurations. If configurations are not included, the project resource is persisted without this property.
The maximum length is 10000 items. The minimum length is 0 items.

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

IBM Cloud® Security and Compliance Center has the following known limits that might impact your experience.



Table 1. Security and Compliance Center limits

                            Limit                                                        

 Custom rules               500 per enterprise account  <br>100 per stand-alone account  
 Rule description           256 characters                                               
 Rule size                  4096 characters                                              
 Target                     1 per rule                                                   
 Condition                  16 per rule                                                  
 Property                   24 per condition                                             
 Label                      32 per rule                                                  
 Custom libraries           10 per enterprise account  <br>5 per stand-alone account     
 Library name               64 Characters                                                
 Library description        256 characters                                               
 Library size               Less than 1 MB                                               
 Profile name               64 characters                                                
 Profile description        256 Characters                                               
 Profile size               Less than 1 MB                                               
 Custom profiles            20 per enterprise account  <br>5 per stand-alone account     
 Control                    1200 per library  <br>600 per profile                        
 Control name               64 characters                                                
 Control description        256 characters                                               
 Specification              100 per control per library  <br>400 per control per profile 
 Specification description  256 characters                                               
 Assessment                 10 per specification per library or profile                  
 Attachment                 50 per account                                               
 Exclusion                  8 per attachment                                             
 Scan                       1 per attachment - at any time
The JSON cannot contain tabs, newlines, or carriage returns.

For dialog skills only: The maximum size for a skill JSON file is 10 MB. If you need to upload a larger skill, consider using the REST API. For more information, see the [API Reference](https://cloud.ibm.com/apidocs/assistant/assistant-v1?curl=createworkspace).
5. Click Upload and overwrite.

If you have trouble uploading a dialog skill, see [Troubleshooting skill upload issues](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-tasksskill-dialog-add-import-errors).
The JSON cannot contain tabs, newlines, or carriage returns.

For dialog skills only: The maximum size for a skill JSON file is 10 MB. If you need to upload a larger skill, consider using the REST API. For more information, see the [API Reference](https://cloud.ibm.com/apidocs/assistant/assistant-v1?curl=createworkspace).
5. Click Upload and overwrite.

If you have trouble uploading a dialog skill, see [Troubleshooting skill upload issues](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-tasksskill-dialog-add-import-errors).
X-Clv-Request-Id: 9fa96daa-9f37-42ee-ab79-0bcda049c671
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.129
X-Clv-S3-Version: 2.5
x-amz-request-id: 9fa96daa-9f37-42ee-ab79-0bcda049c671
Content-Type: application/xml
Content-Length: 374

<ListMultipartUploadsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Bucket>apiary</Bucket>
<KeyMarker/>
<UploadIdMarker/>
<NextKeyMarker>multipart-object-123</NextKeyMarker>
<NextUploadIdMarker>0000015a-df89-51d0-2790-dee1ac994053</NextUploadIdMarker>
<MaxUploads>1000</MaxUploads>
<IsTruncated>false</IsTruncated>
<Upload>
<Key>file</Key>
<UploadId>0000015a-d92a-bc4a-c312-8c1c2a0e89db</UploadId>
<Initiator>
<ID>d4d11b981e6e489486a945d640d41c4d</ID>
<DisplayName>d4d11b981e6e489486a945d640d41c4d</DisplayName>
</Initiator>
<Owner>
<ID>d4d11b981e6e489486a945d640d41c4d</ID>