vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Leaving an account 

As a user on IBM Cloud®, you can be a member of multiple accounts. If your projects and priorities change or you are added to an account by mistake, you can leave the account.

When you leave an account, all of your account-related data like IAM policies and API keys are deleted. This action can’t be undone, and an account owner must add you back if you want to join the account again.

To leave an account, complete the following steps:



1.  In the IBM Cloud console, switch to the account that you want to leave from the console menu bar.
2.  Go to Manage > Access (IAM) > Users in the IBM Cloud console, .
3.  Find your name in the users list.
4.  Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Remove user.
5.  Click Remove.



You can also remove yourself from an account on the [Verification methods and authentication factors](https://iam.cloud.ibm.com/mysecurity) page by clicking Show accounts, selecting the account, and clicking Leave. Confirm that you want to leave the account and click Yes.
AC-2 - Account Management 



 Control requirements 

The organization:

AC-2 (a)
: Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types];

AC-2 (b)
: Assigns account managers for information system accounts;

AC-2 (c)
: Establishes conditions for group and role membership;

AC-2 (d)
: Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account;

AC-2 (e)
: Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts;

AC-2 (f)
: Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions];

AC-2 (g)
: Monitors the use of information system accounts;

AC-2 (h)
: Notifies account managers:



1. When accounts are no longer required;
2. When users are terminated or transferred; and
3. When individual information system usage or need-to-know changes;



AC-2 (i)
: Authorizes access to the information system based on:



1. A valid access authorization;
2. Intended system usage; and
3. Other attributes as required by the organization or associated missions/business functions;



AC-2 (j)
: Reviews accounts for compliance with account management requirements [IBM Assignment: quarterly for privileged access; quarterly for any access to regulated systems, as specified by FS-ready public cloud customer vendor managers; annually for all other access]; and

AC-2 (k)
: Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group.





 Additional IBM Cloud for Financial Services specifications 



* Prior to production access, users must be onboarded and registered in the customer's access management system.
accountIDResourceAttribute, serviceNameResourceAttribute}
}

options := iamPolicyManagementService.NewCreatePolicyOptions(
"access",
[]iampolicymanagementv1.PolicySubject{policySubjects},
[]iampolicymanagementv1.PolicyRole{policyRoles},
[]iampolicymanagementv1.PolicyResource{policyResources},
)

policy, response, err := iamPolicyManagementService.CreatePolicy(options)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(policy, "", " ")
fmt.Println(string(b))

const policySubjects = [
{
attributes:
{
name: 'iam_id',
value: 'IBMid-123453user',
},
],
},
];
const policyRoles = [
{
role_id: 'crn:v1:bluemix:public:metrics-router::::serviceRole:Viewer',
},
];
const accountIdResourceAttribute = {
name: 'accountId',
value: 'ACCOUNT_ID',
operator: 'stringEquals',
};
const serviceNameResourceAttribute = {
name: 'serviceName',
value: 'metrics-router',
operator: 'stringEquals',
};
const policyResources = [
{
attributes: accountIdResourceAttribute, serviceNameResourceAttribute]
},
];
const params = {
type: 'access',
subjects: policySubjects,
roles: policyRoles,
You can assign a managed key or target keystore only in one vault. When you connect to an external keystore, you also need to assign it to a vault first.

You can create different vaults based on your organizational or security needs. For example, you can create a vault for each business unit. In this way, you set access control policies at a vault level, and key administrators of each business unit have access only to the keys and keystores that are assigned to the vault of their business unit.

For more information about creating and managing access to vaults, see [Creating vaults](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-create-vaults) and [Granting access to vaults](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-grant-access-vaults).
* Managed keys

A managed key is a key that is created in and assigned to a vault. You can manage the lifecycle of a managed key and activate it in multiple keystores in the same vault. You can use a managed key for encryption and decryption only when it is activated in at least one target keystore. Activating a managed key in multiple keystores in the same vault enables key redundancy. To use a managed key for encryption and decryption, activate it in one or more keystores within the same vault first.

For more information about creating managed keys, see [Creating and activating managed keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-create-managed-keys).
* Target keystores

A target keystore is keystore that is assigned to a vault. You need to create an internal keystore in only one vault, or assign an external keystore to a vault when you connect your service instance to it.

You need to activate a key in a keystore before you can encrypt or decrypt data by using the key.



* Internal keystores

An internal keystore is a keystore that is created in your Hyper Protect Crypto Services instance.
The first step in our example is to create two separate resource groups. The first resource group is for the dedicated host. The second resource group is for the dedicated host group.



 Creating a dedicated host resource group 

Complete the following steps to create a resource group for the dedicated host.



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/login).
2. Click Manage > Account.

Zoom

![Manage list](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/click_manage.png)

Figure 1. Manage menu
3. From the Account page, click Resource groups > Create.
4. Give the resource group a unique name such as Admin resources.
5. Click Add.







 Creating a dedicated host group resource group 

Complete the following steps to create a resource group for the dedicated host group.



1. Click Manage > Account.
2. From the Account page, click Resource groups > Create.
3. Give the resource group a unique name such as Users resources.
4. Click Add.









 Step 2: Creating a dedicated host and dedicated host group 

When you create a dedicated host, you assign it to a resource group. As part of the dedicated host creation process, you define a dedicated host group for the dedicated host. You can assign the dedicated host group to a separate resource group, so you can apply permissions separately for the dedicated host and the dedicated host group. Complete the following steps to create a dedicated host and dedicated host group in their respective resource groups, Admin resources and Users resources.



1. Click the menu icon!
Using your own OS license or subscription 

When you create an image template with a Virtual Hard Disk (VHD) image, you can opt to provide your own RHEL operating system license through the [Red Hat Cloud Access](https://www.redhat.com/en/technologies/cloud-computing/cloud-access) subscription or a Windows license through the Microsoft Enterprise Agreement.

If you deploy an image in IBM Cloud® that indicates you are using your own license, the following support terms exist:



* IBM supports hypervisors, provisioning instances, importing images, rebooting an image, reloading an OS, and capturing an image.
* The company from which you buy the operating system license supports the image itself.



When you provide your own license for an image, the following restrictions apply to the image:



* The image is a private image. It can't be shared publicly.
* The image can't have any software add-ons included. Add-ons must be installed after the image is provisioned.





 Using Red Hat Cloud Access 

For more information about our certification as a Red Hat Enterprise Linux cloud provider, see [Infrastructure as a Service (IaaS)](https://access.redhat.com/ecosystem/cloud-provider/2262101).





 Using your own Windows license 

The following operating systems are supported:



* Windows Server 2019
* Windows Server 2016
* Windows Server 2012
* Windows Server 2012 R2



If you have questions about your existing Windows license eligibility or reporting requirements, contact your Microsoft representative. When you create an image template by using your own Windows license, you must provision that image on a dedicated host. You can't provision a public instance or a dedicated instance that is auto-assigned to a host when you use an image under your own Windows license. Additionally, when you create or update a Windows image template under your own license, the Windows image can't be a cloud-init image.





 Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu.
You can create one of the following connections:



* Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per Direct Link gateway.
* VPC networks allow you to connect to your account’s VPC resources.



You cannot request a connection to a network in another account when you create a gateway. However, you can request a connection to a network in another account after a gateway is provisioned. You also can create classic infrastructure and VPC connections after a gateway is created. To learn more, see [Adding virtual connections to a Direct Link gateway](https://cloud.ibm.com/docs/dl?topic=dl-add-virtual-connection).
* Select Transit Gateway to bind your direct link to transit gateways. You can bind your direct link to one or more local gateways, or one global gateway.

If you select Transit Gateway as the type of network connection, you must also initiate a Direct Link connection through the [IBM Cloud Transit Gateway console](https://cloud.ibm.com/interconnectivity/transit) from the same IBM Cloud account. For instructions, see [Adding a connection](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-adding-connections).



11. An order summary shows pricing estimates for your review. Read and agree to the [Direct Link prerequisites](https://cloud.ibm.com/docs/dl?topic=dl-ibm-cloud-dl-prerequisites) and review Cloud Services [Terms](https://www.ibm.com/software/sla/sladb.nsf/sla/bm-8695-01). Then, click Create to complete your order.

If you want to add GB egress data to your estimate, click Add to estimate to calculate the cost. You can also click the About tab for links to Direct Link pricing tables and other helpful resources.



Complete your connection, using the following instructions.





 Completing the connection 

After you submit your Direct Link order, the Direct Link table indicates an LOA creation in progress connection status.
[Create an action](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/actions-templates-create.png)

Create an action
4. On Quick start with templates, click a template to read details about what it does. Or, you can click the checkbox to select the template right away.

If you choose a starter kit template, these actions require you to add a custom extension before you add the actions from the starter kit. For more information, see [Starter kit extension setup](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templatesactions-templates-extension-setup).

Zoom

![Quick start with templates](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/actions-templates-quick-start-2.png)

Quick start with templates
5. Review the details of the template, then click Select this template.

Zoom

![Template details](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/actions-templates-review-2.png)

Template details
6. Your list of selected templates includes all the ones that you chose. You can select as many templates as you want. If you change your mind, click the trash can icon to remove a template from the list.

Zoom

!
You can enable a VPC for classic access only while you are creating it. In addition, you can have only one classic access VPC in your account at any time.
6. Optional: Default address prefixes. Disable this option if you don't want to assign default subnet address prefixes to each zone in your VPC. After you create your VPC, you can go to its details page and set your own subnet address prefixes. If you do disable this option, the New subnet for VPC section will be hidden, and will require manual definition after the VPC is created. Leave the default value.

If you want to create the subnet and your own subnet address prefixes later, become familiar with important details of VPC networking. For more information, see [About networking for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpc) and [Designing an addressing plan for a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-addressing-plan-design).





 New subnet for VPC 



1. Enter a unique Name for the VPC subnet, for example, sap-subnet1.
2. Select a Resource group for the subnet. For this example, keep the value default.
3. Select a Location for the subnet, for example, LON, London 3. The location consists of a region and a zone.

The region that you select is used as the region of the VPC. All additional resources that you create in this VPC are created in the selected region.
4. Enter an Address prefix, Number of addresses, and an IP range for the subnet. The IP range is entered in CIDR notation, for example: 10.240.0.0/24. In most cases, you can use the default IP range. If you want to specify a custom IP range, you can use the IP range calculator to select a different address prefix or change the number of addresses.

A subnet cannot be resized after it is created.
5.
Networking design considerations 

The SAP systems in a landscape have specific requirements for servers, operating systems, network setup, and supported storage.

In some regards, SAP workloads that use a Cloud Service Provider (such as IBM Cloud® for SAP) Infrastructure-as-a-Service is similar to existing practices (over many decades) for running SAP workloads that use an external data center or a data center provider. An SAP landscape has specific requirements for connectivity, between hosts within Cloud IaaS and to external systems, IBM Cloud® for SAP provides a rich set of functions beyond hosting of SAP systems to improve your SAP landscape.

To assist your project's planning phase, the below sections provide IBM Cloud® for SAP portfolio design considerations for Networking.



 Preface: units of measure for data/information 

Often the throughput Network Storage is shown in Mbps or Gbps.

It is important to note, that Mb (Megabits) is a decimal prefix and MiB (Mebibyte) is a binary prefix so they are on different scales. More confusion arises because MiB (Mebibyte) was commonly known in Microsoft Windows as Megabyte.

For future reference throughout the networking documentation, Mb (Megabits) and MiB (Mebibyte) is used based on the system of units (SI) defined by IEC and adopted by IEEE, ISO, and NIST.

For example,:



* 100 Mbps (Megabits per second), would be 12 MiB/s (Mebibyte per second)
* 1000 Mbps (Megabits per second) also known as 1 Gbps (Gigabits per second), would be 120 MiB/s (Mebibyte per second)
* 10 Gbps (Gigabits per second), would be 1200 MiB/s (Mebibyte per second)







 Networking connectivity considerations 

For an overview of the connectivity options available, see [Determining access to your SAP system landscape](https://cloud.ibm.com/docs/sap?topic=sap-determine-access).

SAP Systems are often the focal point of business operations, with a great number of integrated applications (including legacy applications).
Storage design considerations 

The SAP systems in a landscape have specific requirements for servers, operating systems, network setup, and supported storage.

For SAP workloads that use a Cloud Service Provider, Infrastructure-as-a-Service is similar to existing practices used to run SAP workloads in external data centers or by a data center provider. An SAP landscape has specific requirements for connectivity, between hosts within Cloud IaaS and to external systems. IBM Cloud® for SAP provides a rich set of functions to improve your SAP landscape, beyond hosting SAP systems.

To assist your project's planning phase, the below sections provide IBM Cloud® for SAP portfolio design considerations for Storage.



 Preface: units of measure for data/information 

Storage performance refers to the read/write performance from storage file system. Often the throughput Network Storage is shown in Mbps or Gbps, whereas for Local Disk storage is shown in MiB/s.

It is important to note, that Mb (Megabits) is a decimal prefix and MiB (Mebibyte) is a binary prefix so they are on different scales. More confusion arises because MiB (Mebibyte) was commonly known in Microsoft Windows as Megabyte.

For future reference throughout the storage documentation, Mb (Megabits) and MiB (Mebibyte) is used based on the system of units (SI) defined by IEC and adopted by IEEE, ISO, and NIST.

For example:



* 100 Mbps (Megabits per second), would be 12 MiB/s (Mebibyte per second)
* 1000 Mbps (Megabits per second) also known as 1 Gbps (Gigabits per second), would be 120 MiB/s (Mebibyte per second)
* 10 Gbps (Gigabits per second), would be 1200 MiB/s (Mebibyte per second)







 Storage configuration for SAP HANA 

With any SAP HANA certified profile that is listed as Appliance, storage is already provided or must be attached precisely as described.

When you provision more storage for an SAP HANA instance, you must adhere to mandatory TDI storage requirements.
To scale the memory of a deployment to 13312 MB of RAM for each memory member (for a total memory of 39936 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": 39936
}
}'

More information is in the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-available-scaling-groups-from-a-depl).
To scale the memory of a deployment to 4096 MB of RAM for each memory member (for a total memory of 12288 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": 12288
}
}'

More information is in the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-available-scaling-groups-from-a-depl).
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
}
}'

More information is in the [API Reference](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-available-scaling-groups-from-a-depl).
--ephemeral-storage, --es
: The amount of ephemeral storage to set for runs of the job. Use M for megabytes or G for gigabytes. This value is optional.

--force, -f
: Do not verify the existence of specified configmap and secret references. Configmap references are specified with the --env-from-configmap option. Secret references are specified with the --env-from-secret or --registry-secret options. This value is optional. The default value is false.

--image, -i
: The name of the image that is used for runs of the job. The format is REGISTRY/NAMESPACE/REPOSITORY:TAG where REGISTRY and TAG are optional. If REGISTRY is not specified, the default is docker.io. If TAG is not specified, the default is latest. The image option is required if the --build-source option is not specified. This value is optional.

--instances, --is
: Specifies the number of instances that are used for runs of the job. When you use this option, the system converts to array indices. For example, if you specify instances of 5, the system converts to array-indices of 0 - 4. This option can only be specified if the --array-indices option is not specified. This value is optional. The default value is 1.

--maxexecutiontime, --met
: The maximum execution time in seconds for runs of the job. This option can only be specified if mode is task. This value is optional. The default value is 7200.

--memory, -m
: The amount of memory that is set for runs of the job. Use M for megabytes or G for gigabytes. For valid values, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). This value is optional. The default value is 4G.

--mode
[IO utilization in percent 60-minute average](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_disk_io_utilization_percent_average_60m) 
 [IOPS read and write total count for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_disk_iops_read_write_total) 
 [Max allowed memory for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_memory_limit_bytes) 
 [Total disk space for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_disk_total_bytes) 
 [Used CPU for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_cpu_used_percent) 
 [Used disk space for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_disk_used_bytes) 
 [Used memory for an instance.](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-monitoringibm_messages_for_rabbitmq_memory_used_bytes) 





 IO utilization in percent 5-minute average 

How much disk I/O has been used over 5 minutes as a percentage of total disk I/O available.



Table 2. IO utilization in percent 5 minute average metric metadata

 Metadata Description