vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing quota limits for storage and pull traffic 

You can limit the amount of storage and pull traffic that can be used in your IBM Cloud account by setting and managing custom quota limits in IBM Cloud® Container Registry.



 Setting quota limits for storing and pulling images 

You can limit the amount of storage and pull traffic to your private images by setting your own quota limits.

When you upgrade to the IBM Cloud Container Registry standard plan, you benefit from unlimited amount of storage and pull traffic to your private images. To avoid exceeding your preferred payment level, you can set individual quotas for the amount of storage and pull traffic. Quota limits are applied to all

namespacesthat you set up in IBM Cloud Container Registry. If you're using the free service plan, you can also set custom quotas within your free amount of storage and pull traffic.

To set a quota, complete the following steps.



1. Log in to IBM Cloud.

ibmcloud login
2. Review your current quota limits for storage and pull traffic.

ibmcloud cr quota

Your output looks similar to the following example.

Getting quotas and usage for the current month, for account '<account_owner> Account'...

QUOTA LIMIT USED
Pull traffic 5.1 GB 0 B
Storage 512 MB 511 MB

OK
3. Change the quota limit for storage and pull traffic. To change the pull traffic usage, specify the traffic option, and replace <traffic_quota> with the value in megabytes that you want to set for the pull traffic quota. If you want to change the amount of storage in your account, specify the storage option, and replace <storage_quota> with the value in megabytes that you want to set.

If you are on the free plan, you cannot set your quota to an amount that exceeds the free tier. The free tier allowance for storage is 512 MB and traffic is 5120 MB.

ibmcloud cr quota-set --traffic <traffic_quota> --storage <storage_quota>

Example to set your quota limit for storage to 600 megabytes, and the pull traffic to 7000 megabytes:

ibmcloud cr quota-set --storage 600 --traffic 7000
Ordering Snapshot space with Terraform 

When you provision a storage volume with Terraform, use the ibm_storage_file resource and specify the snapshot_capacity argument. The following example defines 10 GB snapshot space.

resource "ibm_storage_file" "fs_endurance" {
type = "Endurance"
datacenter = "dal09"
capacity = 20
iops = 0.25

 Optional fields
allowed_virtual_guest_ids = ["28961689"]
allowed_subnets = ["10.146.139.64/26"]
allowed_ip_addresses = ["10.146.139.84"]
snapshot_capacity = 10
hourly_billing = true
}

If you want to increase the snapshot space, update the snapshot_capacity arguement with a larger number and apply the changes.

For more information about the arguments and attributes, see [ibm_storage_file](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_file).
Limit Volume Size limitVolumeSize Config Maximum requestable volume size (in Gibibytes) and qtree parent volume size true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Fail provisioning if usage is above this percentage. true 80% 
 NFS Mount Options nfsMountOptions Config The NFS mount options. true nfsvers=4 









 Storage class reference for NetApp ONTAP-NAS 

Before you deploy an app that uses the sat-netapp storage classes, review the following notes.



* By default, the sat-netapp-file-gold storage class doesn't include any QoS limits (unlimited IOPS).
* To use the sat-netapp-file-silver and sat-netapp-file-bronze storage classes, you must create corresponding silver and bronze QoS policy groups on the storage controller and define the QoS limits. To create a policy group on the storage system, log in to the system CLI and run the netapp1::> qos policy-group create -policy-group <policy_group_name> -vserver <svm_name> [-min-throughput <min_IOPS>] -max-throughput <max_IOPS> command.
* The min-throughput option is supported only on all-flash systems. For more information about creating and managing QoS Policy groups, see the [ONTAP 9 Storage Management documentation](https://docs.netapp.com/us-en/ontap/index.html).
* To use an encrypted storage class, NetApp Volume Encryption (NVE) must be enabled on your storage system by using either the NetApp ONTAP onboard key manager or a supported (off-box) third-party key manager, such as IBM 's TKLM key manager. To enable the onboard key manager, run the netapp1::> security key-manager onboard enable command. For more information about configuring encryption, see the [ONTAP 9 Security and Data Encryption documentation](https://docs.netapp.com/us-en/ontap/security-encryption/index.html).
--size SIZE
--access-control-mode value
--mount-targets value
[--name NAME]
[--initial-owner-gid INITIAL_OWNER_GID ]
[--initial-owner-uid INITIAL_OWNER_UID]
[--user-tags USER_TAGS]
[--mount-targets TARGETS_JSON | @TARGETS_JSON_FILE]
[--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME]
[--output JSON] [-q, --quiet]

This example creates a file share with two mount targets.

ibmcloud is share-create --name my-file-share-8 --zone us-south-1 --profile tier-3iops --size 40 --user-tags env:dev,env:prod --mount-targets '[{"name": "my-target121","vpc": {"name": "vpcl"}},{"name": "my-target122","vpc": {"name": "vpc2"}}]'
Creating file share my-file-share-8 under account vpc1 as user user@mycompany.com...

ID 0e04ca62-e02a-4319-9551-380c7f7cd87f
Name my-file-share-8
CRN crn:[...]
Lifecycle State pending
Zone us-south-1
Profile tier-3iops
Size(GB) 40
IOPS 3000
User Tags env:dev,env:prod
Encryption provider_managed
Mount Targets ID Name VPC ID VPC Name
87171615-f8b4-4ccd-a216-bab12eb1a973 my-target121 81ee2425-7c2f-4042-9d8f-d02b0ee8886c vpc1
* The total size limit of all non-HTML fields in uploaded and crawled documents is 1MB, which is equivalent to 1,048,576 bytes, and the total size limit of all HTML fields in these documents is 5MB. If you exceed either limit, you receive an error message stating The document has fields/HTML fields that exceed the 1 MB/5 MB limit., and the document is not ingested. For assistance on increasing either size limit, contact the IBM Support Center]] ! ! ! ! ! ! ! ]! ! ! ! ! ! .<-- </ul> -->Also see the issues identified in all previous releases.<-- </section "id="section-29nov2019ki" "> --><-- <section "id="section-30aug2019ki" "> --> 2.0.1, 30 August 2019 <-- <ul> --> * After you create a Machine Learning enrichment using a IBM Watson® Knowledge Studio model, two identically named enrichments may display on the Enrich fields page. This will not affect the enrichments, but it is best to use only one of them to select and apply the enrichment to one or more fields. * If a web crawl appears to be stuck processing at a fixed number of documents, and the message displayed on the Logs page is The ingestion job <jobid> is terminated incorrectly, contact IBM support for assistance restarting the crawl. * If one or more of your collections is trained, the training data from one of those collection may display on the Train page of an untrained collection. Refresh the page to clear that training data.
If you use the IBM Cloud console, complete the following steps:



1. In the Apps Dashboard, select your app. The app details page opens.
2. In the runtime pane, you can reduce the maximum memory limit or the numbers of app instances, or both, for your app.



If you use the cf command line interface, complete the following steps:



1. Check how much memory is being used for your apps. The cf apps command lists all the apps that you deployed in your current space. The status of each app is also displayed.

cf apps
2. To reduce the amount of memory that is used by your app, reduce the number of app instances or the maximum memory limit, or both:

cf push appname -p app_path -i instance_number -m memory_limit
3. Restart your app for the changes to take effect.







 Can I use sample scripts to build and deploy my application? 

The [open-toolchain/commons](https://github.com/open-toolchain/commons) GitHub repo contains a collection of common scripts that you can use in toolchains and pipelines. For example, you can use one of the shell scripts that is contained in this repo within your own toolchains in various ways.





 How do I bring my own code and deploy it by using Continuous Delivery 

You can choose any of the following options to deploy your own code to Continuous Delivery:



* Create a toolchain by using one of the available templates (dependent on the deployment target and tool integrations). On the Create a Toolchain page, select the appropriate provider for your source repository, and then specify the link to your source code repo. After you create your toolchain, you might need to adjust the pipeline scripts for your deployment goals.
* Create an empty toolchain, and then add tool integrations to deploy your app. For more information about using this method to deploy your code to Continuous Delivery, see [Continuous Deployment to Kubernetes](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-continuous-deployment-to-kubernetes).
ibmcloud is target --gen 2







 Attaching a Block Storage for VPC volume from the CLI 

To attach a volume to a virtual server instance in the current resource group, run this command.

ibmcloud is instance-volume-attachment-add NAME INSTANCE_ID VOLUME_ID [--auto-delete true | false] [--json]

NAME is the name that you provide for the volume attachment and INSTANCE_ID is the ID of the virtual server instance. The VOLUME_ID specifies the volume that you are attaching. If you want the volume to automatically delete when the virtual server instance is deleted, specify --auto-delete true.

To see a list of available virtual server instances, run the ibmcloud is instances command. Check out the following example.

$ ibmcloud is instances
Listing instances in all resource groups and region us-east under account Test Account as user test.user@ibm.com...
ID Name Status Reserved IP Floating IP Profile Image VPC Zone Resource group
0757_506a787d-0672-4209-854b-3e280ec50b44 test-pbalak-rhel running 10.241.0.4 169.63.96.188 bx2-2x8 ibm-redhat-9-0-minimal-amd64-2 test-pbalak1 us-east-1 defaults
0757_4fc00b09-c967-46bf-9203-d17a08078d1d test-pbalak-rhel2 running 10.241.0.5 150.239.86.22 bx2-2x8 ibm-redhat-9-0-minimal-amd64-2 test-pbalak1 us-east-1 defaults
0757_11f5db7f-35a1-4678-bcbd-c85204e09507 kj-test-ro running 10.241.0.5 - bx2d-2x8 ibm-ubuntu-18-04-5-minimal-amd64-1 test-vpc-blu-wdc us-east-1 defaults
* CLI
* API







 Managing storage limits 

By default, you can provision a combined total of 700 Block Storage for Classic and File Storage for Classic volumes globally. By following this process, you can increase the number of volumes you can provision.

For more information about increasing your storage volume capacity beyond 12 TB, see [expanding File Storage for Classic capacity](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacityincreasecapacityover12TB).

If you're unsure how many volumes you have, you can confirm the numbers by using multiple methods.



 Confirming your current limit and provisioning count from the CLI 



 SLCLI 

You can list the number of your volumes by using the [volume-limits](https://softlayer-python.readthedocs.io/en/latest/cli/file/file-volume-limits) command in slcli (version 5.8.5 or higher).

 slcli file volume-limits

The output looks similar to the following example.

[{'datacenterName': 'global', 'maximumAvailableCount': 700, 'provisioned Count':117}]
:............:.......................:..................:
: Datacenter : maximumAvailableCount : ProvisionedCount :
:............:.......................:..................:
: global : 700 : 117 :
:............:.......................:..................:





 IBM Cloud CLI
The deployment has three members, with 3072 MB of RAM disk allocated in total. The "per member" allocation is 1024 MB of RAM and 1024 MB of disk. The minimum value is the lowest the total allocation can be set. The step size is the smallest amount by which the total allocation can be adjusted.

The cdb deployment-groups-set command allows either the total RAM or total disk allocation to be set, in MB. For example, to scale the memory of the "example-deployment" to 2048 MB of RAM for each memory member (for a total memory of 6144 MB), you use the command:
ibmcloud cdb deployment-groups-set example-deployment member --memory 6144





 Scaling in the API 

The Foundation Endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API. Use it with the /groups endpoint if you need to manage or automate scaling programmatically.

To view the current and scalable resources on a deployment,

curl -X GET -H "Authorization: Bearer $APIKEY" 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups'

To scale the memory of a deployment to 2048 MB of RAM for each memory member (for a total memory of 6144 MB).

curl -X PATCH 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups/member' -H "Authorization: Bearer $APIKEY" -H "Content-Type: application/json" -d '{"memory": {
"allocation_mb": 6144
}
}'

For more information, see the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-available-scaling-groups-from-a-depl).
ibmcloud is share-mount-target-create my-new-share --subnet cli-subnet-1 --name my-mount-target-3 --vni-name cli-share-vni-1 --vni-rip my-reserved-ip --vni-sgs concrete-proudly-coastal-obvious,sg-vni --resource-group-name Default







 Create a file share with the API 

You can create file shares and mount targets by directly calling the REST APIs.

File Storage for VPC regional API is released as beta for customers with special approval to preview this feature. For more information about the file shares VPC API, see the [VPC API Beta reference](https://cloud.ibm.com/apidocs/vpc-beta).



 Before you begin 

Set up your API environment. Define variables for the IAM token, API endpoint, and API version. For instructions, see [Setting up your API and CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment).

As described in the [Beta VPC API](https://cloud.ibm.com/apidocs/vpc-beta) reference [versioning](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta) policy, support for older versions of the beta API is limited to 45 days. Therefore, beta API requests must specify a version query parameter date value within the last 45 days. You must also provide generation parameter and specify generation=2. For more information, see Generation in the [Virtual Private Cloud API reference](https://cloud.ibm.com/apidocs/vpcapi-generation-parameter).

A good way to learn more about the API is to click Get sample API call on the provisioning pages in IBM Cloud console. You can view the correct sequence of API requests and better understand actions and their dependencies.





 Create a file share with the API 

Make a POST /shares request to create a file share. Specify the size of the file share, a name, the IOPS profile, and zone.
The maximum length is 201 items. The minimum length is 0 items.

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





 Example 

ibmcloud secrets-manager secrets --offset=0 --limit=10 --sort=created_at --search=example --groups=default





 Example output 

Example secret metadata collection response

{
"first" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?limit=50"
},
"previous" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=50&limit=50"
},
"last" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=200&limit=50"
},
"limit" : 50,
"next" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=150&limit=50"
},
"offset" : 100,
"secrets" : [ {
"alt_names" : "s1.example.com", ".s2.example.com" ],
"common_name" : "example.com",
"created_at" : "2020-10-05T21:33:11Z",
Migrating an Enterprise plan to a Lite or Standard plan 

Migration from the Enterprise plans to IBM Cloudant Lite or Standard plans includes these tasks, which are described in the following steps.



 Step 1: Sign up for IBM Cloud 



1. Go to the [IBM Cloud Dashboard](https://cloud.ibm.com/).
2. Authenticate with your username and password.
The IBM Cloud Dashboard opens to the Resource list.







 Step 2: Create an IBM Cloudant instance 



1. Click Create resource.
2. Click Databases > Cloudant.

Zoom

![Select Databases > Cloudant dashboard as your instance.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/img0003.png)

Figure 1. IBM Cloudant Dashboard

For more information, see the [Getting started](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) tutorial.







 Step 3: Find out whether your application is ready for IBM Cloudant 



1. Revisit your application’s usage of IBM Cloudant to make sure it is ready to handle the capacity limits of the Standard plan. For more information, see [how the IBM Cloudant API works](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-ibm-cloud-publicprovisioned-throughput-capacity).
2. Verify that your application can handle a 429: too many requests HTTP response.



The following table provides more information about these HTTP responses:



Table 1. HTTP responses

 HTTP response Issue 

 429: too many requests Retrying requests that get a 429 response is acceptable for occasional traffic spikes that exceed your plan's capacity. If your application traffic is routinely generating 429 responses, you probably need to upgrade to a larger plan.
If the operation exceeds the limit, you receive a size limit exceeded error. If you receive this error, try reducing the size of your job or your job run in one of the following ways:



* If you are using commands and arguments, reduce the use of these options, make them shorter, or move them into the container image that is used by your job or job run.
* If you are using environment variables, use fewer environment variables or make them shorter. You can use secrets or configmaps to define environment variables and import them into the job by using the --env-from-secret or --env-from-configmap options with the [ibmcloud ce job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create), [ibmcloud ce job update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-update), [ibmcloud ce jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-submit), and [ibmcloud ce jobrun resubmit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-resubmit) commands.





For more information about job size limits, see [Job size limit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsjob_size_limit). For more information about running jobs, see [Running jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job).
* For batch requests, each object change is handled individually and the trigger is fired for each successful change event.
* All characters are permitted in an object key except for ASCII control character NUL.
* Naming limitations for Cloud Functions triggers can be found on the [System details and limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_fullnames) page.











 Configuring the IBM Cloud Object Storage package 

After you have [created an IBM Cloud Object Storage service instance](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-gs-devgs-dev-provision) and [created at least one bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storagegs-create-buckets), you can install the IBM Cloud Object Storage package into your namespace to work with your buckets and objects.

The installable IBM Cloud Object Storage package deploys a set of pre-built actions that you can use to work with your IBM Cloud Object Storage buckets and objects. These actions are executed in either Node.js or Python. You can select a runtime when you install the package. If you want to use a different runtime, you can use the [COS SDK](https://cloud.ibm.com/docs/cloud-object-storage/libraries?topic=cloud-object-storage-sdk-gs). You can also [build your own actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions) or [web actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions_web) to respond to the trigger.

For a list of the actions in the cloud-object-storage package, see [Available entities](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_actions).
:............:.......................:..................:
: global : 700 : 117 :
:............:.......................:..................:





 IBM Cloud CLI 

The volume-limits command is also available in the sl plug-in for IBM Cloud CLI (v1.0 or higher).

 ibmcloud sl block volume-limits
Datacenter MaximumAvailableCount ProvisionedCount
global 700 99







 Confirming your current limit and provisioning count with the API 



 REST API 

To directly get this information from the API, use the following method: [SoftLayer_Network_Storage/getVolumeCountLimits](https://sldn.softlayer.com/reference/services/SoftLayer_Network_Storage/getVolumeCountLimits/).

curl -u $SL_USER:$SL_APIKEY 'https://api.softlayer.com/rest/v3.1/SoftLayer_Network_Storage/getVolumeCountLimits.json'

SoftLayer_Container_Network_Storage_DataCenterLimits_VolumeCountLimitContainer[{"datacenterName":"global","maximumAvailableCount":700,"provisionedCount":99}]

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
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/icons/icon_hamburger.svg), select Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/icons/classic.svg).
2. Select Devices > Device List from the main menu. Find the device for which you want to add the backup service.
3. Click the Device name to go to the Device Details page.







 Adding IBM Cloud Backup for Classic service 



1. Click the Storage tab, and scroll down to locate the IBM Cloud Backup for Classic section.
2. Click the Add link.
3. In the window, select a location, and select a size.
4. Select Payment type, and click Continue.
5. Enter the Promo Code if you have one, and click Recalculate.
6. Review your order, and click the link to read the terms and conditions.
7. Click the checkbox if you agree with the terms and conditions.
8. Click Place Order.







 Confirming the IBM Cloud Backup for Classic upgrade 



1. Refresh the Device Details page, and ensure that the Storage tab is selected.
2. Inspect the IBM Cloud Backup for Classic section and verify that the size that was selected during the purchase process is displayed.

If the backup storage size continues to show a capacity of zero, a second page refresh might be needed.











 Provisioning IBM Cloud Backup for Classic from the CLI 

Before you begin, you must install the IBM Cloud CLI. For more information, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).