vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI







 Setting a rotation policy 

You can set an automatic rotation policy for a root key either by setting an instance policy on your IBM® Key Protect for IBM Cloud® instance or, if you have the correct role, by setting the policy at key creation time.

Recall from [Rotating your root keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-rotation) that regularly rotating root keys shortens the cryptoperiod of a key and therefore can be used as a general security policy as well as in specific cases such as personnel turnover, process malfunctions, or the detection of a security issue.

If you do not have Manager level of permission necessary to set a rotation policy, you can still manually rotate your keys any time as long as you have at least the Writer level of permission. Check out [Manually rotating keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-rotate-keys) for more information about this process. Also, check out [Understanding user roles and resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-manage-access) for more information about the manager, writer, and other roles regarding access to resources like keys, instances, and accounts.

There are a few different ways to set a rotation policy:



* [Set a rotation policy on your IBM® Key Protect for IBM Cloud® instance](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-rotation-policymanage-policies-instance). This ensures that every key that is created has the rotation policy unless the policy is overridden at key-creation time by a Manager.
* [Set a rotation policy at key creation time](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-rotation-policymanage-policies-creation-time). This allows for the adjustment of the rotation policy for a particular key to be applied during the creation of a key.
You must have manager role to create a team in a monitoring instance.

An administrator or a manager of an IBM Cloud Monitoring instance must switch to the Monitor Operations team before he can create teams and manage existing teams.

Complete the following steps to create a team:



1. [Launch the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launchlaunch).
2. Click the user icon. This is the icon with the initials of the logged on user. Then click Settings.
3. Click Teams. The list of existing teams is displayed.
4. Click Add Team. The team configuration page is displayed.
5. Configure the team details.



* Choose a color.
* Enter the name of the team
* [Optional] Enter a description for this team.
* [Optional] Set the Default team parameter if you want this team to become the default team for new users.
* Set the Default Entry Point to specify the view in the web UI that opens every time a user logs in. By default, the Explore view is set.



6. Configure the team scope.



* [Optional] Set Scope by to specify the level of data that members of the team have access to. Valid values are Host and Container.

If the parameter is set to Host, members can see all Host-level and Container-level information.

If the parameter is set to Container, members can see only Container-level information.
* Set the Scope to limit what data users can see. You can set one or more conditions by specifying expressions for metrics.

By default, the scope is set to everywhere.
* [Optional] Enable or disable Sysdig captures. Check this box to allow this team to take IBM Cloud Monitoring captures.

Capture files will only be visible to members of this team.

Captures include detailed information from every container on a host, regardless of the team’s scope.
* [Optional] Enable or disable Infrastructure Events. Check this box to allow members to view all custom infrastructure events from every user and monitoring agent.
The default value is 10.

max-inactivity
: Set the maximum time in minutes that the cluster autoscaler pod runs without any recorded activity before the pod is automatically restarted. The default value is 10m.

max-failing-time
: Set the maximum time in minutes that the cluster autoscaler pod runs without a completed action before the pod is automatically restarted. The default value is 15m.

customImageVersion
: To override the default installation version, specify the version of the cluster autoscaler Helm chart that you want to install. There is no default value for this parameter.

maxRetryGap
: Set the maximum time in seconds to retry after failing to connect to the service API. Use this parameter and the retryAttempts parameter to adjust the retry window for the cluster autoscaler. The default value is 60.

retryAttempts
: Set the maximum number of attempts to retry after failing to connect to the service API. Use this parameter and the maxRetryGap parameter to adjust the retry window for the cluster autoscaler.| The default value is 32.

workerpools
: The worker pools that you want to autoscale, including their minimum and maximum number of worker nodes per zone. . These settings are mirrored in the [cluster autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-enable) config map. To set the worker pool, format the option as follows: --set workerpools[0].<pool_name>.max=<number_of_workers>,workerpools[0].<pool_name>.min=<number_of_workers>,workerpools[0].<pool_name>.enabled=(true|false) Understanding the --set workerpools options:
: workerpools[0]: The first worker pool to enable or disable for autoscaling.
*  CLI
*  API







  Setting the Admin Password 

The IBM Cloud® Messages for RabbitMQ service is provisioned with an admin user.

You must set the admin password before you can use it to connect. To set the password through the IBM Cloud dashboard, select Manage from the service dashboard to open the management panel for your service. Open the Settings tab, and use the Change Database Admin Password panel to set a new admin password.

![The Change Database Admin Password Panel in Settings](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/images/settings-admin-password.png){: caption="Figure 1. The Change Database Admin Password Panel in Settings" caption-side="bottom"}



  Setting the admin password through the CLI 

Use the cdb user-password command from the [Cloud Databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference) to set the admin password with the command line.

For example, to set the admin password for a deployment named "example-deployment", use the following command.

ibmcloud cdb user-password example-deployment admin <newpassword>





  Setting the admin password via 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 /deployments/{id}/users/{username} endpoint to set the admin password.

curl -X PATCH https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/users/admin' -H "Authorization: Bearer $APIKEY" -H "Content-Type: application/json" -d '{"password":"newrootpasswordsupersecure21"}'

For more information, see the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apiset-database-level-user-s-password).
* UI
* CLI
* API
* Terraform







 Assigning access to catalogs 

As the account owner, you assign users specific catalog management access depending on what tasks they are performing. To streamline the process of assigning access, you can use access groups to organize a set of users into a single entity. That way, you can assign a single policy to the group one time, and then add or remove users from the group as needed.

For more details, see [Managing access in IBM Cloud](https://cloud.ibm.com/docs/account?topic=account-cloudaccess).



 Setting up your access groups in the console 

See the following sections for details about creating your access groups and assigning specific IAM policies to each one.



 Administrator access in the console 

Administrator access is required for setting account-level filters to the IBM Cloud catalog.



1. Log in to your IBM Cloud account.
2. Go to Manage > Access (IAM) > Access groups in the IBM Cloud console.
3. Click Create.
4. Enter private-catalog-admins as the group name, and click Create.
5. Click Access > Assign access.
6. Select Catalog Management from the list of services.
7. Select the catalog that you want users to access.
8. In the Platform access section, select the Administrator role.
9. Click Review.
10. Click Add to add your policy configuration to your policy summary.
11. Assign.







 Editor access in the console 

Editor access is required for creating private catalogs, setting filters at the private catalog level, adding your software to your private catalog, and updating, deprecating, and restoring your software.



1. Go to Access groups, and click Create.
2. Enter private-catalog-editors as the group name, and click Create.
3. Click Access > Assign access.
4. Select Catalog Management from the list of services.
5. Select the catalog that you want users to access.
6. In the Platform access section, select the Editor role.
"delete_after": 20
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f/plans/4cf9171a-0043-4434-8727-15b53dbc374c",
"id": "4cf9171a-0043-4434-8727-15b53dbc374c",
"lifecycle_state": "stable",
"name": "my-policy-plan",
"resource_type": "backup_policy_plan"
}
]
}

To retrieve information about a single plan, specify the plan ID in the request:

curl -X GET "$vpc_api_endpoint/v1/backup_policies/{backup_policy_id}/plans/{plan_id}?version=2022-12-16&generation=2"







 Retrieving a backup plan with the fast restore option 

You can see information about the zone in which fast restore backup snapshots are being created and the number of snapshots in each zone.

Make a GET /backup_policy/{backup_policy_id}/plans/{plan_id} call. In the response, the clone_policy property shows the zone in which the snapshot clone for fast restore is created and the maximum number of recent snapshots per volume that keeps clones.

You can also retrieve all plans for a backup policy and view plans you set up for backup snapshot clones. For more information, see the [List all plans for a backup policy](https://cloud.ibm.com/apidocs/vpc/latestlist-backup-policy-plans) in the API reference.

Example call:
Comparison of backups and snapshots

 Feature Backup Snapshot 

 Backs up Block Storage for VPC boot and data volumes. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) 
 Manually restore a volume from a snapshot. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) 
 Back up data by a schedule. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) 
 Back up data immediately. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/checkmark-icon.svg) 
 Data is copied at a specific point in time. !
See the following example of targeting a region other than the default us-south.

provider "ibm" {
region = "eu-de"
}

To update a snapshot, use the ibm_is_snapshot resource. You can change the name of the snapshot, the fast restore zones, and tags. However, changing resource_group and source_volume values forces Terraform to destroy the snapshot and create a different snapshot.

resource "ibm_is_snapshot" "example" {
name = "my-snapshot"
source_volume = ibm_is_volume.example.id
}

For more information about the arguments and attributes, see [ibm_is_snapshot](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_snapshot).





 Adding tags to a snapshot in the UI 

You can add [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutstorage-about-user-tags) and [access management tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutstorage-about-user-tags) to your Block Storage for VPC snapshots. You can add user tags to an existing snapshot or when you create a snapshot. The tags can be used by a backup policy to create backups of the snapshot.



 Adding user tags from the snapshots list screen 

Use the following steps to add user tags from the snapshots list screen.



1. Go to the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-view&interface=uisnapshots-vpc-view-list-ui).
2. Locate an available snapshot created by user. (Snapshots that were created by a backup policy are identified as created by Backup policy.)
3. In the Tags column, snapshots with tags show a number that indicates the tags that are already applied.
VPC infrastructure services use a regional specific based endpoint, which targets to us-south by default. If your VPC is created in another region, make sure to target the right region in the provider block in the provider.tf file.

See the following example of targeting a region other than the default us-south.

provider "ibm" {
region = "eu-de"
}

To apply user tags to a volume, use the ibm_is_volume resource. The following example specifies the volume r010-bdb8fc70-8afb-4622-826a-d65a9fc477a4 and the tags env:test, bkp:test, and bcp:test to be attached to the volume.

resource "ibm_is_volume" "example" {
name = "example-volume"
profile = "10iops-tier"
zone = "us-south-1"
tags = ["dev:test"]
}

For more information about the arguments and attributes, see [ibm_is_volume](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/ibm_is_volume).





 Next steps 



* [Manage your backup policies and plans](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-manage).
* [Create extra backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan).
* [Restore a volume from a backup snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore).
Use this option when you're not sure which virtual server instance you want to attach the volume to. Or, if you want to restore data from an unattached volume that was detached from an instance.

To restore a stand-alone data volume from a snapshot, make a POST /volumes request and specify the ID, CRN, or URL of the snapshot in the source_snapshot property. The restored volume capacity (in GBs) must be at least the snapshot's minimum_capacity.

The following example request creates a 100-GB volume that is based on a 5 IOPS/GB profile. It specifies a different root key than the original snapshot. The source snapshot is specified by ID.

curl -X POST "$vpc_api_endpoint/v1/volumes/?version=2022-06-14&generation=2" -H "Authorization: $iam_token" -H "Content-Type: application/json" -d '{
"name": "volume-from-snapshot-1",
"capacity": 100,
"profile": {
"name": "5iops-tier"
},
"zone": {
"name": "us-south-1"
},
"encryption_key":{
"crn":"crn:[...]"
},
"source_snapshot:" {
"id": "bdcdc984-ba4e-4aef-84fb-e8448c3116b1"
}
}







 Restoring a volume from a snapshot with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

VPC infrastructure services use a regional specific based endpoint, which targets to us-south by default.
Profile Select [Tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) and select the IOPS tier list. If your performance requirements don't fall within a predefined IOPS tier, select [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) and select an IOPS value within the range for that volume size. 
 Encryption Provider-managed encryption with IBM-managed keys is enabled by default on all volumes. <br>You can also choose a Key Management Service by selecting either (Key Protect or Hyper Protect Crypto Services), and then specify your own encryption key. <br>For a one-time setup procedure, see [Prerequisites for setting up customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-planningbyok-encryption-prereqs). <br>For more information about locating up the CRN for an existing key, see [Key Protect - Retrieving your instance ID and cloud resource name (CRN)](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID) and [Hyper Protect Crypto Services - Viewing details about a key](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-key-details). 



If you created volume snapshots previously, the option to import one becomes available. Click the Snapshots toggle, and select a snapshot from the list. You can filter this list for snapshots with fast restore. Then, complete the required fields and click Create to provision the volume. A Block Storage for VPC volume is created and attached to the virtual server instance. On the instance details page, the Data volumes list is updated to show the new volume
* HA - Supports 2, 4 and 8 node HA configurations or single node if no HA is required
* Protocols - iSCSI, NFS v3 and v4, and SMB/CIFS
* Protected - Integrated NetApp® Snapshot™ copies, local and remote backup, disaster recovery, and volume encryption
* Efficient - Thin provisioning, cloning, deduplication, and compression
* Cost - Available in CapEx and OpEx models and is charged on a $GB Basis
* Replication - Supports SnapMirror; also achieved by using vRealize Automation External link icon (vRA).
* Resiliency in a non-HA configuration single point of failure include enclosure hardware. Or, resiliency in an HA configuration, no single point of failure



For more information about how to request ONTAP Select, see [NetApp ONTAP Select](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-netapp).





 NetApp private storage 

You must purchase a NetApp device from NetApp or IBM Cloud®. You need to install it in one of the colocation sites that are near your IBM Cloud® data center and connect it by using Direct-Link Colocation or Direct-Link Cloud.

For more information about connecting to VMware with NetApp, see the following links.



* [NetApp Private Storage for IBM Cloud®](http://www.netapp.com/us/solutions/cloud/private-storage-cloud/softlayer.aspx)
* [Solution brief: NetApp Private Storage for IBM Cloud®](http://www.netapp.com/us/media/ds-3619_tcm10-127472.pdf)
* Recommended workloads - Tier 1
* Performance - Dependent on NetApp model
* Scalability - Supports extra of drives and frames for increased capacity and IOPS
* Protocols: - iSCSI, NFS, and SMB
* Cost - High for both CapEx and OpEx
* HA - Dual heads and controllers
The size is inherited from the source volume. 
 Source volume Shows the boot or data volume from which the snapshot was created. Click the name of the volume to see its [details](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage). 
 Fast restore status Status of restore as enabled, pending, or disabled. 
 Requested Date and time when the snapshot was requested. 
 Created by Shows whether the snapshot was created by the user or a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-concepts). 
 Snapshot copies Number of copies that a snapshot has in other regions. 
 Actions menu Click the actions menu icon to display a menu of context-specific actions.<br><br><br><br> * [Create snapshot copy](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=uicrsnapshots-vpc-create-ui)<br> * Copy the Cloud Resource Name (CRN).<br> * [Create volume](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restoresnapshots-vpc-restore-ui).<br> * [Edit fast restore](https://test.cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-edit-fast-restore).<br> * [Delete the snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-vpc-delete-snapshot-ui).<br> * [Delete all snapshots for a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-vpc-delete-all-ui).<br><br><br>
You can now [list all jobs for a backup policy](https://cloud.ibm.com/apidocs/vpc/latestlist-backup-policy-jobs) or [retrieve a backup policy job](https://cloud.ibm.com/apidocs/vpc/latestget-backup-policy-job). A backup policy job is triggered when a scheduled backup snapshot is being created or deleted. If the create or delete action is successful, the job contains information about the backup snapshot that was created or deleted. If the job ran unsuccessfully, the job contains the reason for the failure. For more information, see [Viewing backup jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs).







 13 December 2022 



 For all version dates 

Health states for block storage volumes. When you [list all volumes](https://cloud.ibm.com/apidocs/vpc/latestlist-volumes) or [retrieve volume details](https://cloud.ibm.com/apidocs/vpc/latestget-volume), the responses now include health_state and health_reasons properties. For more information, see [Block storage volume health states](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=apiblock-storage-vpc-health-states).







 15 November 2022 



 For all version dates 

Access management tag support. As described in [Authorization](https://cloud.ibm.com/apidocs/vpc/latestapi-authorization) in the VPC API reference, you can now use [IBM Cloud Identity and Access Management](https://cloud.ibm.com/docs/account?topic=account-iamoverview) to control access to VPC resources by using access management tags. For details, see [Managing IAM access for VPC Infrastructure Services](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started&interface=apiiam-access-management-tags).
If you created snapshots in a different region, expand the list and select the region.
3. As your list of snapshots grows, use the filter to indicate the number of snapshots to display per page. Use the page navigation arrows to move forward and back through the list.



Table 1 describes the information for all snapshots in the list of snapshots.



Table 1. List of all snapshots

 Field Description 

 Name The name that you provided when you created the snapshot. Click the name of the snapshot to see its [details](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-viewsnapshots-vpc-view-snapshot-ui). 
 Status Status of the snapshot, depending on whether it's usable (active status), unusable, or being created. For more information, see [Snapshot statuses](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-vpc-status). 
 Encryption Shows [IBM-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-about&interface=uivpc-provider-managed-encryption) or [customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-about&interface=uivpc-customer-managed-encryption). The encryption is inherited from the source volume. 
 Size Size of the snapshot in GBs. The size is inherited from the source volume. 
 Source volume Shows the boot or data volume from which the snapshot was created. Click the name of the volume to see its [details](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage). 
 Fast restore status Status of restore as enabled, pending, or disabled. 
 Requested Date and time when the snapshot was requested.