vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Example request to create a version 4.10 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "odf-local", "storage-template-version": "4.10", "update-assignments": true, "user-config-parameters": { "entry.name": "AUTO-DISCOVER-DEVICES", { "entry.name": "OSD-DEVICE-PATH", { "entry.name": "NUM-OF-OSD", { "entry.name": "WORKER-NODES", { "entry.name": "ODF-UPGRADE", { "entry.name": "BILLING
You can give users access to view private catalogs and catalog filters, create private catalogs, add software to private catalogs, and set catalog filters.



Table 4. Roles and example actions for the catalog management service

 Roles Actions 

 Viewer View account-level filters set for the IBM Cloud catalog<br><br>View private catalogs 
 Operator Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters 
 Editor Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters 
 Administrator Set account-level filters for the IBM Cloud catalog<br><br>Create, update, and delete private catalogs<br><br>Publish IBM-approved products<br><br>Assign access policies 
 Publisher Publish products that are approved by IBM from a private catalog 







 Context-based restrictions 

You can give users access to view, create, update, and remove network zones. To create a context-based restriction rule for a service, you must be assigned an IAM policy with the Administrator role the service you are creating a rule against. For example, if you want to create a rule to protect a Key Protect instance, you must be assigned the Administrator role on the Key Protect service and the Viewer role or higher on the Context-based restrictions service.

The Viewer role on the Context-based restrictions service allows you to add network zones to your rule.



Table 5. Roles and example actions for the context-based restrictions service

 Roles Actions 

 Viewer View network zones 
 Editor View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 
 Administrator View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 







 Enterprise 

You can use the Enterprise service to assign users access to manage an enterprise by creating accounts within the enterprise, assigning accounts to account groups, naming account groups, and more. This type of policy works only if it is assigned within the enterprise account.



Table 6.
[Save icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/icon_save.png). A Manage spaces link is displayed beneath the Spaces slider control, and a Spaces link is added to the navigation list. You can manage your Spaces by clicking either of these links.

Spaces are enabled for your Catalog, and a default Space, called New Space is created.



For more information about using syndication, see the Knowledge Center topics, [Using syndication in IBM API Connect](https://www.ibm.com/support/knowledgecenter/SSFS6T/com.ibm.apic.apionprem.doc/capic_syndication_using.html).





 Configuring a Developer Portal 

A Developer Portal is the place where your plans are published for application developers to access and use.

You can build a customized Developer Portal for application developers to use. You have full administrative control over appearance, content, user settings, and configuration settings.

In addition to allowing application developers to find and use APIs, the Developer Portal provides more features such as forums, blogs, comments, ratings, and an OpenAPI UI for APIs.



1. In the API Manager UI, select the Catalog that you want to work with.
2. Select the Settings tab.
3. Click Portal.
4. In the Portal Configuration section, select IBM Developer Portal. The Portal URL is displayed.
5. Click Save. You are sent an email that contains a one-time login link for the Developer Portal web admin user.
6. Click the link that is sent in the email and follow the instructions to reset your password.



Your Developer Portal is configured. You can find the URL for the Developer Portal in the subject line of the email that you received. You can also find the URL in the API Manager UI by clicking Portal > Settings.
You can give users access to view private catalogs and catalog filters, create private catalogs, add software to private catalogs, and set catalog filters.



Table 5. Roles and example actions for the catalog management service

 Roles Actions 

 Viewer View account-level filters set for the IBM Cloud catalog<br><br>View private catalogs 
 Operator Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters 
 Editor Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters 
 Administrator Set account-level filters for the IBM Cloud catalog<br><br>Create, update, and delete private catalogs<br><br>Publish IBM-approved products<br><br>Assign access policies 
 Publisher Publish products that are approved by IBM from a private catalog 







 Context-based restrictions 

You can give users access to view, create, update, and remove network zones. To create a context-based restriction rule for a service, you must be assigned an IAM policy with the Administrator role the service you are creating a rule against. For example, if you want to create a rule to protect a Key Protect instance, you must be assigned the Administrator role on the Key Protect service and the Viewer role or higher on the Context-based restrictions service.

The Viewer role on the Context-based restrictions service allows you to add network zones to your rule.



Table 6. Roles and example actions for the context-based restrictions service

 Roles Actions 

 Viewer View network zones 
 Editor View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 
 Administrator View network zones<br><br>Create network zones<br><br>Update network zones<br><br>Remove network zones 







 Enterprise 

You can use the Enterprise service to assign users access to manage an enterprise by creating accounts within the enterprise, assigning accounts to account groups, naming account groups, and more. This type of policy works only if it is assigned within the enterprise account.



Table 7.
* UI
* CLI
* API
* Terraform







 Managing replica file shares 

Manage replica file shares by removing the replication relationship to create two independent file shares. The replica file share becomes read/write, and you can update and delete the share.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.

You need Administrator or Editor IAM user roles to create and manage file share replicas and the replication relationship. For a list of these roles and actions, see [IAM roles for creating and managing file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifile-storage-vpc-iam).



 Remove the replication relationship 

You can remove replication by removing the replication relationship between the source file share and replica file share. The operation is called splitting the file shares. Data is no longer synced between the file shares. Removing the replication relationship creates two independent, read/write file shares. You can separately manage each file share, expand capacity and adjust IOPS, and create replicas.

Use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=terraformfs-remove-replication-ui), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=terraformfs-remove-replication-cli), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=terraformfs-remove-replication-api) to remove the replication relationship. You can also specify that the source and replica file shares are split if a [failover](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover) operation does not succeed.
For more information, see [Remove the replication relationship in the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=clifs-remove-replication-cli).

ibmcloud is share-delete <SHARE_ID>









 Manage file shares and mount points with the API 

By using the API, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-file-share-api).
* [Add mount target to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=apifs-create-mount-target-api).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-mount-target-api).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-update-profile-api)
* [Delete mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-mount-target-api).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingdelete-file-share-api).
* [Manage file share user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-add-tags-api).



To see information about the File Storage for VPC API methods, see the following section in the [API reference](https://cloud.ibm.com/apidocs/vpc-betalist-share-profiles).

File Storage for VPC regional API is available for customers with special approval to preview this feature.
Keeping policies in a draft state give you the time to design and configure the policies that you need without affecting your running compliance scans.



 Accessing Posture Policies 

To access the Posture Policies:



1. Open the [Workload Protection UI](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-launch).
2. Hover over the Policies icon ![Policies icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/policies.png) and click Policies in the Posture section. The configured policies are displayed.







 Creating a custom policy 

You can create a custom policy by duplicating an existing policy or creating a new policy from the beginning. Choose one of the following options:



* [Creating a custom policy from scratch](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-posture-policy-create).
* [Creating a custom policy from a template](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-posture-policy-create-template).







 Deleting policies 

Deleting an active policy deletes the policy and policy's evaluation history.

You can delete only custom policies.



1. Open your policy by [accessing the Posture Policies view](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-posture-policiesaccess-posture-controls) and clicking the policy that you want to delete.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/icons/action-menu-icon.svg) next to the selection to delete.
To list Satellite storage configurations, run ibmcloud sat storage assignment ls.

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

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





 Example 

ibmcloud sat storage assignment get --assignment my-assignment







 ibmcloud sat storage assignment ls 

List your Satellite storage assignments.

ibmcloud sat storage assignment ls [--output OUTPUT] (--cluster CLUSTER_ID | --config CONFIG |--location LOCATION | --service-cluster-id CLUSTER) [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--output OUTPUT
: Prints the command output in the provided format. Available options: json

--cluster CLUSTER_ID
: The ID of a Satellite cluster that you created for which you want to list the assignments. To find the cluster ID, run ibmcloud oc cluster ls --provider satellite. If you do not include this option, you must specify the --config option, the --location option, or the --service-cluster-idoption.

--config CONFIG
: The name or ID of a Satellite storage configuration for which you want to list the assignments. To list available storage configurations, run ibmcloud sat storage config ls. If you do not include this option, you must specify the --cluster option, the --location option, or the --service-cluster-id option.

--location LOCATION
: The name of the Satellite location for which you want to list the assignments. To list the available locations, run ibmcloud sat location ls. This option is not available for service admin.
SLCLI commands for File Storage for Classic 

You can use the SLCLI to accomplish tasks that are normally handled through the [IBM Cloud® console](https://cloud.ibm.com/cloud-storage/file). For example, from the SLCLI you can place orders for new volumes, snapshot space and replication, update authorizations, and cancel volumes.

For more information about how to install and use the SLCLI, see [Python API Client](https://softlayer-python.readthedocs.io/en/latest/cli/).



 Access-related SLCLI commands 



* [Managing File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingstorage)

slcli file access-authorize
slcli file access-list
slcli file access-revoke







 Replication-related SLCLI commands 



* [Replication-related SLCLI commands](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replication)

slcli file replica-failback
slcli file replica-failover
slcli file replica-locations
slcli file replica-order
slcli file replica-partners







 Snapshots-related SLCLI commands 



* [Ordering Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-ordering-snapshots)

slcli file snapshot-order
* [Managing Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingSnapshots)

slcli file snapshot-cancel
slcli file snapshot-create
slcli file snapshot-delete
slcli file snapshot-disable
slcli file snapshot-enable
slcli file snapshot-list
slcli file snapshot-restore







 Volume-related SLCLI commands
Configure your File Storage for Classic as described in [Accessing File Storage for Classic on Red Hat Enterprise Linux®](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingLinux) and [Mounting NFS File Storage for Classic in CentOS](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mountingCentOS). Mount the volume to /backup and configure it in the file system table (/etc/fstab) to enable mounting on start.

By default, NFS downgrades any files that were created with the root permissions to the nobody user. To allow root clients to retain the root permissions on the NFS share, no_root_squash needs to be added to /etc/exports.
4. Optional. Copy existing backups to the new storage. Use rsync for example:

rsync -avz /var/lib/psa/dumps /backup/psa/dumps

This command compresses and transmits your data, and it preserves as much as possible, except hard links. It also provides information about what files are being transferred plus a brief summary at the end.
5. Edit /etc/psa/psa.conf to point the DUMP_D value at the new target.



* It appears as: DUMP_D /backup/psa/dumps.



6. Optional. As dictated by your particular use case and business needs, remove the old storage from the server and cancel it from the account.
Example request to create a version 22.04 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "netapp-ontap-san", "storage-template-version": "22.04", "update-assignments": true, "user-config-parameters": { "entry.name": "MANAGEMENTLIF", { "entry.name": "DATALIF", { "entry.name": "SVM", { "entry.name": "LIMITVOLUMESIZE", { "entry.name": "LIMITAGGREGATEUSAGE","user-secret-parameters": { "entry.name": "USERNAME",{ "entry.name": "PASSWORD",}

Example request to create a version 22.10 configuration.
AU-4 - Audit Storage Capacity 



  Control requirements 

AU-4 - 0
:   The organization allocates audit record storage capacity in accordance with [Assignment: organization-defined audit record storage requirements].





  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [Audit logging of application provider events and SIEM](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit-provider)
*  [Audit logging of IBM Cloud events](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit)
*  [IBM Cloud account setup](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setup)







  IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



*  Check whether Cloud Object Storage quota enforcement is off for buckets that are configured to use Activity Tracker Event Routing
*  Check whether Cloud Object Storage buckets with a quota have threshold-based alerts enabled







  NIST supplemental guidance 

Organizations consider the types of auditing to be performed and the audit processing requirements when allocating audit storage capacity. Allocating sufficient audit storage capacity reduces the likelihood of such capacity being exceeded and resulting in the potential loss or reduction of auditing capability.
* UI
* CLI
* API







 Scaling Disk, Memory, and CPU 

You can manually adjust the amount of resources available to your IBM Cloud® Databases for Redis deployment to suit your workload and the size of your data.



 Resources Breakdown 

Databases for Redis deployments have two data members in a cluster, and resources are allocated to both members equally. For example, the minimum storage of a Redis deployment is 2048 MB, which equates to an initial size of 1024 MB per member with 512 MB increments available. The minimum RAM for a Redis deployment is 2048 MB, which equates an initial allocation of 1024 MB per member with 124 MB increments available.

Billing is based on the total amount of resources that are allocated to the service.

When you [provision](https://cloud.ibm.com/docs/databases-for-redis?topic=cloud-databases-provisioningprovisioning) a deployment, you can select the initial resource allocation of disk and memory. After provision, you can scale your deployment as it needs more resources.



 Disk Usage 

By default, Databases for Redis uses disk for data persistence. Your disk allocation per data member has to be enough to store your data. When you add disk to the total allocation, it adds it to both members equally.

Disk allocation also affects the performance of the disk, with larger disks having higher performance. Baseline Input-Output Operations per second (IOPS) performance for disk is 10 IOPS for each GB. Scale disk to increase the IOPS your deployment can handle.

If you have configured Redis as a cache, persistence been disabled on your deployment. If you re-enable Redis persistence, be sure to scale your disk first to prevent losing data.

You cannot scale down storage. You can recover space by backing up and restoring to a new deployment.





 Memory 

By default, your deployment is configured with a noeviction policy so your memory resources should be scaled to fit your data set. Each data node contains a copy of your data, so the total amount of memory you use is approximately twice the size of your data set. When you add memory to the total allocation, it adds memory to both members equally.
Example request to create a version 4.12 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "odf-remote", "storage-template-version": "4.12", "update-assignments": true, "user-config-parameters": { "entry.name": "OSD-SIZE", { "entry.name": "OSD-STORAGE-CLASS", { "entry.name": "NUM-OF-OSD", { "entry.name": "WORKER-NODES", { "entry.name": "ODF-UPGRADE", { "entry.name": "BILLING-
Example request to create a version 4.12 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "odf-local", "storage-template-version": "4.12", "update-assignments": true, "user-config-parameters": { "entry.name": "AUTO-DISCOVER-DEVICES", { "entry.name": "OSD-DEVICE-PATH", { "entry.name": "NUM-OF-OSD", { "entry.name": "WORKER-NODES", { "entry.name": "ODF-UPGRADE", { "entry.name": "BILLING
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasstorage-netapp-ontap-nas-include-assignment-create-api)
* [Deploying an app that uses ONTAP-NAS storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nassat-storage-netapp-nas-deploy-2104)
* [Removing NetApp ONTAP-NAS storage from your apps](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-nas-rm-2104)



* [Removing the NetApp ONTAP-NAS storage assignment and configuration from the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-nas-template-rm-cli-2104)
* [Removing the NetApp ONTAP-NAS storage assignment and configuration from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-nas-template-rm-ui-2104)



* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-parameter-reference)



* [21.04 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-ontap-nas-21.04-parameters)