vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You receive an error message that contains memory parameter must be between .25 G and 32 G or cpu parameter must be between .0125 and 8.0.For more information about Code Engine limits for apps, see [Application limits and defaults for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitslimits_application).
6. The resource quota for apps or app revisions is reached and the app (or app revision) is not created. Code Engine has quotas for apps and revisions of the apps within a project. For more information about Code Engine limits, see [Project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).
7. If the image for your app is located in Docker Hub and you receive a similar error message that indicates you have reached your Docker pull rate limit.

429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit ”



 How to fix it 

Try one of these solutions.



1. To determine whether the name of your app is unique within the project, use the ibmcloud ce app list command to list all defined apps and check whether an app with the same name exists. If an app with the same name exists, use the ibmcloud ce app delete --name APP_NAME to delete the old app. The name of the app must be unique within your project.
2. To confirm that the name of your app is valid, check that the name of your app consists of lowercase alphanumeric characters, '-', and that the name starts and ends with an alphabetic character.
3. To confirm that the image for your app exists, review the error message for information about the failure.

a. To deploy applications in Code Engine, you need to first create a container image that has all the runtime artifacts your application needs to run, such as runtime libraries.
<-- </section "id="section-project-config-install-cli-output" "> --><-- </section "id="section-project-cli-config-install-command" "> --><-- <section "id="section-project-cli-config-uninstall-command" "> --> ibmcloud project config-uninstall Destroy a project's configuration resources. The operation destroys all the resources that are deployed with the specific configuration. You can track it by using the get project configuration API with full metadata. ibmcloud project config-uninstall --project-id PROJECT-ID --id ID
<-- <section "id="section-project-config-uninstall-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--id (string): The unique config ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! ! ! +$/.
<-- </section "id="section-project-config-uninstall-cli-options" "> --><-- <section "id="section-project-config-uninstall-examples" "> --> Example ibmcloud project config-uninstall --project-id=exampleString --id=exampleString
Options: id, name, created, size_bytes
-h, --help Show this message and exit.

Notifications are sent when you reach three different space thresholds – 75 percent, 90 percent, and 95 percent.



* At 75 percent capacity, a warning is sent that snapshot space usage exceeded 75 percent. To remediate, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule. If you reduce the snapshot data or increase the space, the warning system is reset, and no autodeletion occurs.
* At 90 percent capacity, a second warning is sent when snapshot space usage exceeded 90 percent. Like with reaching 75 percent capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
* At 95 percent capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95 percent. Snapshots continue to be deleted each time usage exceeds 95 percent until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.



If snapshot space utilization increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if utilization jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%. The system skips the 90%-exceeded warning.

By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time.

To check whether the notifications are enabled for the storage volume, use the following command.

 slcli block snapshot-get-notification-status
VPC clusters: App URL character length DNS resolution is managed by the cluster's [virtual private endpoint (VPE)](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_vpe), which can resolve URLs up to 130 characters. If you expose apps in your cluster with URLs, such as the Ingress subdomain, ensure that the URLs are 130 characters or fewer. 







 Update after master 

The following table shows the actions that you must take after you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.20

 Type Description 

 Unsupported:kubectl autoscale --generator removed The deprecated --generator option is removed from the kubectl autoscale command. If your scripts rely on this option, update them.
The throughput multiplier is 16 KB for 3 IOPS/GB or 5 IOPS/GB tiers, or 256 KB for 10 IOPS/GB or custom IOPS tiers. The higher the IOPS that you specify, the higher the throughput. Maximum throughput is 1024 MBps.

The application I/O size directly impacts storage performance. If the application I/O size is smaller than the throughput multiplier that is used by the profile to calculate the volume’s bandwidth limit, the IOPS limit is reached before the throughput limit. Conversely, if the application I/O size is larger, the throughput limit is reached before the IOPS limit.

The following table provides some examples of how application I/O size and provisioned IOPS affect the throughput, which is calculated as average application I/O size x IOPS = Throughput in MBps.



Table 1. Examples of how application I/O size and IOPS affect the throughput

 Average I/O Size (KB) IOPS Throughput (MBps) 

 4 (typical for Linux®) 1,000 4¹ 
 8 (typical for Oracle) 1,000 8¹ 
 16 1,000 16 
 32 (typical for SQL Server) 500 16 
 64 250 16 
 128 128 16 



¹If your cap is 1,000 IOPS or 16 K average I/O size, the throughput caps at whatever limit is reached first.

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



* 16 KB * 6,000 IOPS == 94 MBps
* 8 KB * 6,000 IOPS == 47 MBps
* 4 KB * 6,000 IOPS == 23 MBps
When exceeded, throttling is applied by slightly delaying the responses to requests, effectively applying a gentle brake to producers and consumers until the bandwidth is reduced.





 Partitions 

Hundred partitions for each service instance.





 Retention 

A maximum of 1 GB for each partition.





 Consumer groups 

A maximum of 1000 consumer groups. When the limit is exceeded, the GROUP_MAX_SIZE_REACHED error is returned to the client.





 Other limits 



* Maximum message size: 1 MB
* Maximum concurrently active Kafka clients: 500
* Maximum request rate [HTTP Produce API]: 100 per second
* Maximum request rate [HTTP Admin API]: 10 per second
* Maximum record key size when you use REST Producer API is 4 K.
* Maximum record value size when you use REST Producer API is 64 K.









 Enterprise plan 



 Network throughput 

Network throughput capacity is based on the peak maximum. Each peak maximum has a recommended maximum for typical production workloads.



Table 1. Network throughput capacity on Enterprise

 Peak Maximum Recommended maximum 

 150 MB/s (75 MB/s producing and 75 MB/s consuming) 100 MB/s (50 MB/s producing and 50 MB/s consuming) 
 300 MB/s (150 MB/s producing and 150 MB/s consuming) 200/s (100 MB/s producing and 100 MB/s consuming) 
 450 MB/s (225 MB/s producing and 225 MB/s consuming) 300 MB/s (150 MB/s producing and 150 MB/s consuming) 



Throughput is expressed as the number of bytes per second that can be both sent and received in a service instance. The throughput capacity can be selected when the service instance is created, and later scaled as demands increase.

Throughput capacity cannot be scaled down. To move to a lower throughput capacity would require creating a new Event Streams service instance at the lower capacity unit.

The recommended maximum figure is based on a typical workload and considers the possible impact of operational actions such as internal updates or failure modes, like the loss of an availability zone. If the average throughput exceeds the recommended figure, a loss in performance might be experienced during these conditions.
: The maximum memory limit in MB for your action. The default is 256 MB.

--native
: You can use the --native argument as shorthand for --docker openwhisk/dockerskeleton. By using this argument, you can create and deploy an executable that runs inside the standard Docker action SDK. \n - When you create a Docker image, an executable is created inside the container at /action/exec. Copy the /action/exec file to your local file system and compress it into exec.zip. \n - Create a Docker action that receives the executable as initialization data. The --native argument replaces the --docker openwhisk/dockerskeleton argument.

--paramKEYVALUE, -pKEYVALUE
: Parameter VALUES in the KEYVALUE format. This flag is optional.

--param-fileFILE, -PFILE
: A JSON file that contains parameter KEYS and VALUES. This flag is optional.

--sequenceACTION_NAME, ACTION_NAME
: Create an action sequence and include the names of the related actions. Separate the ACTION_NAMEs by commas.

--timeoutLIMIT, -tLIMIT
: The timeout LIMIT in milliseconds. The default value is 60000 milliseconds. When the timeout is reached, the action is terminated.

--web yes|true|raw|no|false
: Treat the action as a web action, a raw HTTP web action, or as a standard action. Specify yes or true for a web action, raw for a raw HTTP web action, or no or false for a standard action. To secure your web action, also include the --web-secure option.

--web-secureSECRET
: Secure the web action. The VALUE for SECRET can be true, false, or any string. This option can be used only with the --web option.





 Example 

ibmcloud fn action create hello folder/hello_world.js

Output

ok: created hello
Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --input=@path/to/file.json.
--setting (ProjectConfigSettingCollection]]ProjectConfigSettingCollection] ): Schematics environment variables to use to deploy the configuration. Settings are only available if they were specified when the configuration was initially created.
The default value is ] . 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. --setting=@path/to/file.json.
--name (string): The configuration name.
The maximum length is 64 characters. The minimum length is 1 character. The value must match regular expression /^a-zA-Z0-9]a-zA-Z0-9-_ ] ] $/.
--labels ([string): The configuration labels.
The list items must match regular expression /^_\-a-z0-9:/=] ! +$/. The maximum length is 10000 items. The minimum length is 0 items.
--description (string): A project configuration description.
The maximum length is 1024 characters. The minimum length is 0 characters. The value must match regular expression /^$|^(?\s).\S$/.
--authorizations (ProjectConfigAuth]ProjectConfigAuth] ): The authorization for a configuration. You can authorize by using a trusted profile or an API key in Secrets Manager.
Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --authorizations=@path/to/file.json.
--compliance-profile (ProjectConfigComplianceProfile]ProjectConfigComplianceProfile] ! ! ): The profile required for compliance.
The API call shows the combined number of Block Storage for Classic and File Storage for Classic.







 Requesting volume limit increase 

You can request a provisioning limit increase by submitting a support case in the [console](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.

In the case, 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 (dev/test) 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 process.
fsf-tok0551b-fz.adn.networklayer.com:/2bca0419_3aef_40ca_b38f_8b9717c93905/BHB/mnt00002 /hana/log/BHB/mnt00002 nfs sec=sys,rw,vers=4,minorversion=1,hard,timeo=600,rsize=65536,wsize=65536,intr,noatime,lock 0 0



You cannot follow NetApp's recommendation regarding rsize and wsize option, these parameters are limited to 65536 by the file share implementation.

To fulfill SAP's requirements about storage layout and through-put and latency KPIs, see details here: [Persistent Data Storage in the SAP HANA Database](https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/be3e5310bb571014b3fbd51035bc2383.html)). In any case, they must comply with the TDI performance KPIs (see [SAP Note 2613646](https://launchpad.support.sap.com//notes/2613646)) verified by [SAP HANA Hardware and Cloud Measurement Tools](https://help.sap.com/docs/HANA_HW_CLOUD_TOOLS/02bb1e64c2ae4de7a11369f4e70a6394/7e878f6e16394f2990f126e639386333.html) and also ensure SAP's support for it. IBM Cloud recommends 10 IOPS per GB or Custom profile file shares for meeting SAP's KPIs.
Click the Upload icon ![Upload icon](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/upload-icon.png).
4. Select a file from your computer. The maximum CSV file size is 10 MB. If your CSV file is larger, consider splitting it into multiple files and uploading them separately.

The file is validated and uploaded, and the system trains itself on the new data.







 Using saved customer responses in steps 

After you save a customer response, it becomes available as a response type for any step. To use a previously saved customer response in a step:



1. In the step editor, click Define customer response.
2. In the list of customer response types, click Saved to see the available saved customer responses.

Zoom

![Step editor with saved customer responses](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/step-editor-saved-responses-2.png)

Step editor
3. Click the saved response that you want to use.



To remove a saved response from a step, click the Delete![Delete icon](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/remove-response-icon.png) icon. Removing a saved response from a step affects only the step that you are editing. It does not delete the saved response or remove it from any other steps.

To edit a saved response from a step, click Edit response. Keep in mind that if you edit a saved response, your changes affect all steps that use the response.
Note: If the --all-pages option is not set, the command will only retrieve a single page of the collection.

ibmcloud secrets-manager secret-locks --id ID [--offset OFFSET] [--limit LIMIT] [--sort SORT] [--search SEARCH]



 Command options 

--id (string)
: The ID of the secret. Required.

The maximum length is 36 characters. The minimum length is 36 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}/.

--offset (int64)
: The number of locks to skip.

The minimum value is 0.

--limit (int64)
: The number of secrets with locks to list.

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

--sort (string)
: Sort a collection of locks by the specified field in ascending order. To sort in descending order use the - character

Available values: created_at | updated_at | name

Usage: To sort a list of locks by their creation date, use ../locks?sort=created_at.

The maximum length is 17 characters. The minimum length is 4 characters. The value must match regular expression /^-?(created_at|updated_at|name)$/.

--search (string)
: Filter locks that contain the specified string in the field "name".

The maximum length is 128 characters. The minimum length is 2 characters. The value must match regular expression /(.?)/.

--all-pages (bool)
: Invoke multiple requests to display all pages of the collection for secret-locks.





 Example
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5/volume_attachments/4cbb38bc-57d5-4121-a796-d5b10cf0810a",
"id": "<4cbb38bc-57d5-4121-a796-d5b10cf0810aAttachment ID>",
"instance": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5",
"id": "8f06378c-ed0e-481e-b98c-9a6dfbee1ed5",
"name": "my-instance-1"
},
"name": "my-volume-attachment-1",
"type": "data"
}],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Expand block storage volumes with Terraform 

To increase the capacity of a volume, use the ibm_is_volume resource. When applied, the following example updates the capacity to 8,000 GB.

resource "ibm_is_volume" "storage" {
name = "demo-volume-update"
size = 8000
profile = "general-purpose"
zone = "us-south-2"
}
Environment variable values can have a maximum length of 12288.

--outbound-only
: If this parameter is set, only outbound connections are allowed from your Hyper Protect Virtual Server instance. Use the internal IP address to connect to this Virtual Server from other Virtual Servers created by the same IBM Cloud account in the same region.

For example:

ibmcloud hpvs instance-create MyHPVS lite-s dal13 -g Default --ssh "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCgguQtzV39LpP/iHAtjwo+4Z5QdASG73dwBlFIsTn5kPOaVYFHhzhvA/xMbLqDpxfYP/YzwU4rXNXMhCr4hlsruPXt5Ak4y83GmnNL8e+oq8lxU/afymje4PcYLnkm8WQvkreIEBaB73VOUKiLSSbdVljUk6a1LB347bCf72Oob8JpY4Pb3N4idrigSoCc+V4JVkz4pXD2Hoyar4J5I2527Ho+vUqdf5FoK9mFRUqtI8NTLKynL2/qVsCgTeUxnOknDjPE0+nqwyNI4toYozcISYb63K9Je6UBT4JaIQXMbdMhDH00wVH7R26SamKqS2iazcUBnZgN4//Vnic+US90ybsqvTuP/OQpHXwfdjshOEsz5PULZKbWgidsfA7aW3pjv1uijCPIrTFOsaAPktMCzhfJzaeFC0VIXweN7/2PT/Zl7U9Ys36CmmLaXfLotXxPWmbGUyRfavPN1Znhqph7v9w94E7JcngQ7sn+l+nkpYg5qdcBFZZ3kNhT4PVRbXE=" --hostname "test.ibm.com"
X-Clv-Request-Id: c8be10e7-94c4-4c03-9960-6f242b42424d
Accept-Ranges: bytes
Server: Cleversafe/3.9.1.114
X-Clv-S3-Version: 2.5
ETag: "765ba3df36cf24e49f67fc6f689dfc6e-2"
Content-Type: application/xml
Content-Length: 364

<CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Location>http://s3.us.cloud-object-storage.appdomain.cloud/zopse/multipart-object-123</Location>
<Bucket>some-bucket</Bucket>
<Key>multipart-object-123</Key>
<ETag>"765ba3df36cf24e49f67fc6f689dfc6e-2"</ETag>
</CompleteMultipartUploadResult>





 Abort incomplete multipart uploads 

A DELETE request issued to an object with query parameter uploadId deletes all unfinished parts of a multipart upload.

Syntax

DELETE https://{endpoint}/{bucket-name}/{object-name}?uploadId={uploadId}= path style
DELETE https://{bucket-name}.{endpoint}/{object-name}?uploadId={uploadId}= virtual host style

Example request

DELETE /some-bucket/multipart-object-123?uploadId=0000015a-df89-51d0-2790-dee1ac994053 HTTP/1.1
Authorization: Bearer {token}
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response

HTTP/1.1 204 No Content
You can choose an IOPS that is a multiple of 100 within the specified range. The IOPS that you choose is static and does not scale with the size of the storage. For example, if you choose 40Gi with 100 IOPS, your total IOPS remains 100. The IOPS to gigabyte ratio also determines the type of hard disk that is provisioned for you. For example, if you are using 500Gi at 100 IOPS, your IOPS to gigabyte ratio is 0.2. Storage with a ratio of less than or equal to 0.3 is provisioned on SATA hard disks. If your ratio is greater than 0.3, then your storage is provisioned on SSD hard disks.



Table of custom storage class size ranges and IOPS

 Size range in gigabytes IOPS range in multiples of 100 

 20-39 Gi 100-1000 IOPS 
 40-79 Gi 100-2000 IOPS 
 80-99 Gi 100-4000 IOPS 
 100-499 Gi 100-6000 IOPS 
 500-999 Gi 100-10000 IOPS 
 1000-1999 Gi 100-20000 IOPS 
 2000-2999 Gi 200-40000 IOPS 
 3000-3999 Gi 200-48000 IOPS 
 4000-7999 Gi 300-48000 IOPS 
 8000-9999 Gi 500-48000 IOPS 
 10000-12000 Gi 1000-48000 IOPS 





5. Choose if you want to keep your data after the cluster or the persistent volume claim (PVC) is deleted.



* If you want to keep your data, then choose a retain storage class. When you delete the PVC, only the PVC is deleted. The PV, the physical storage device in your IBM Cloud infrastructure account, and your data still exist. To reclaim the storage and use it in your cluster again, you must remove the PV and follow the steps for [using existing block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting_block).