vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Storage volumes differ in performance, depending on their IOPS tier (see [Tiered IOPS profiles](https://cloud.ibm.com/docs/vpc-on-classic-block-storage?topic=vpc-on-classic-block-storage-block-storage-profiles-gen1tiers-gen1) or selecting a [custom size](https://cloud.ibm.com/docs/vpc-on-classic-block-storage?topic=vpc-on-classic-block-storage-block-storage-profiles-gen1custom-gen1) (in GB and IOPS) that is based on the size of the storage.

If you need more than the initially provisioned storage in your virtual server, you can attach extra volumes to a virtual server later. Contact [IBM Cloud Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatargetting-support) for extension options if the attached storage is insufficient for your workload.

For more information, see [Getting started with Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-getting-startedgetting-started) and [Getting started with IBM Cloud File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedgetting-started).





 Compute 

Three primary types of IaaS are available within the IBM Cloud Classic Infrastructure:



1. Bare Metal server
2. Classic Virtual Servers (not SAP certified)
3. VMware, available in two options:



* Intel Bare Metal and VMware vSphere (ESXi OS), requires manual VMware setup and configuration
* IBM Cloud for VMware Solutions Dedicated





Bare Metal and both VMware options are SAP-certified.

Classic Virtual Servers are not SAP-certified. For this type of IaaS, the IBM Cloud VPC Infrastructure environment provides Intel Virtual Servers which are SAP-certified.
Coordinator node type Select either storage optimized or compute optimized. Recommend storage optimized to reduce promo credit consumption. 
 Number of coordinator nodes By default, it is one. 
 Resource units Displays the cost per hour for the type and number of coordinator nodes that you selected 
 Worker node type Select either storage optimized or compute optimized. Recommend storage optimized to reduce promo credit consumption. 
 Number of worker nodes By default, it is one. Select the required number of worker nodes. Adding more worker nodes increases the cost per hour and the consumption of your promo code credit. 



If you add more than one worker nodes, engines or if you choose compute optimized, the cost per hour increases and drains the promo code credit. For the trial, it is recommended to go with a single Presto engine (memory or storage optimized) that has one head node and one worker node.

Support services are required and cannot be turned off. They consume 3 RU/Hr. A Presto engine (memory or storage optimized) with one head node and one worker node each consumes 2.8 RU/Hr.



1. After configuring the resources from the Pricing Estimator details, you can scroll to the Estimate summary for the total estimated cost per hour.

Example: For a sample configuration below, the total cost estimate is : 8.6 RU/Hr.



Table 1. Sample Configuration

 Field Field values 

 Coordinator node type Storage optimized 
 Number of coordinator nodes 1 
 Resource units Displays 2.8 RU/Hr 
 Worker node type Storage optimized 
 Number of worker nodes 1 
 Resource units Displays 2.8 RU/Hr 





The following image displays watsonx.dataIBM Cloud® catalog page.

Zoom

![Catalogpage](https://cloud.ibm.com/docs-content/v1/content/4c3c4670556d1cad9f530a5c8a9edd2e63919b83/watsonxdata/images/happy_path_screen.svg)

Figure 2. Price estimator
* z/OS - Experimental Deleting a subnet through the user interface might not work as expected when you delete an existing VPC. You can use the command ibmcloud is subnet-delete as the workaround.







 Compute restrictions 



* Every x86-based profile has a network performance value of 2 Gbps per vCPU, with a cap of 80 Gbps.
* Each x86-based network interface has a network performance cap of 16 Gbps.
* Start and Stop actions are not registered under virtual server instance activity in the UI.
* Activity Tracker logs (request logs and resource lifecycle event logs) are not available.
* Updating the profile of a created instance is not supported.
* The placement group of the instance can't be changed after an instance is provisioned with a placement group. You must delete the instance to remove it from the placement group.
* API support for creating new instances from an existing boot volume is temporarily suspended. For more information, see the [API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log).







 Storage restrictions 

Block storage volume names must be unique across the entire VPC infrastructure. A volume that is created on VPC compute resources can't have the same name as a volume created on the classic infrastructure. For more information about volume naming, see [Guidelines for naming volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagevolume-name-conventions).





 LinuxONE (s390x processor architecture) virtual server instance restrictions 

The following feature is not supported:



* Dedicated hosts
* VPC Instance Metadata service.







 z/OS virtual server instance restrictions 



* For limitations of z/OS virtual server instances, see [IBM Wazi as a Service documentation](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=known-limitations).
For more information about creating a version for the catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --total-volume-bandwidth: The amount of bandwidth (in megabits per second) that is allocated exclusively to instance storage volumes. An increase in this value results in a corresponding decrease to total network bandwidth.
* --boot-volume: BOOT_VOLUME_JSON|@BOOT_VOLUME_JSON_FILE, boot volume attachment in JSON or JSON file. For the data schema, see the boot_volume_attachment property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --volume-attach: VOLUME_ATTACH_JSON|@VOLUME_ATTACH_JSON_FILE, volume attachment in JSON or JSON file, list of volumes. For the data schema, see the volume_attachments property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --keys: Comma-separated IDs or names of SSH keys. SSH keys can either be of type RSA or Ed25519. Ed25519 can be used only if the operating system supports this key type. Ed25519 can't be used with Windows or VMware images.
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
* --subnet: ID or name of the subnet.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
: Provide a comma-separated list of pricing plans that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--provider PROVIDER (optional)
: Provide a comma-separated list of providers that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--release RELEASE (optional)
: Provide a comma-separated list of categories that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--type TYPE (optional)
: Provide a comma-separated list of software types that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.







 ibmcloud catalog filter delete 

Run the following command to delete an applied filter. This filter defaults to the account level unless a catalog is specified. As a result, the filter is reset to include all products in the public catalog.

ibmcloud catalog filter delete --catalog CATALOG



 Command options 

--catalog CATALOG
: The catalog name or ID.

--account-group ACCOUNT GROUP
: The account group name or ID. This option applies only to enterprise accounts.







 ibmcloud catalog filter offering 

Update the filter to include or exclude a particular product and any applicable pricing plans. This filter defaults to the account level unless a catalog or account group is specified.

ibmcloud catalog filter offering --offering PRODUCT-NAME



 Command options 

--catalog CATALOG
: The catalog name or ID.

--account-group ACCOUNT GROUP
: The account group name or ID. This option applies only to enterprise accounts.

--plans-list PLANS LIST
: A comma-separated list of plan IDs or names to include or exclude.

--offering OFFERING
: The product name or ID.

--include
: The default value is true if a flag is not provided. Valid values are true and false. If set to true, the product and plans provided are visible to users in the account. If set to false, the product and plans aren't visible to users in the account.
Or, if you want to explore everything that IBM Cloud has to offer, go to the catalog to browse over 350 unique products [Click Catalog menu item]. Choose from our broad portfolio of managed services [Click Services], explore software products to take advantage of simplified installation [Click Software], or consult with IBM Cloud experts [Click Consulting]. If you're just here to try it out, filter the catalog by products that offer Lite plans, which are free to use [Click Services, and select the Lite pricing plan option].

When you're working in IBM Cloud [Click IBM Cloud menu option], check out your dashboard to get a high-level overview of your account's resources, users, support cases, compliance monitoring, and usage, with quick links out to each area. You can tailor the information that's displayed to only what you need by creating custom dashboards and adding widgets for specific resources, team notes, management tasks, and more [Click the Actions menu icon > Create dashboard > Management > Create].

For any account management tasks that you need to take care of, go to Manage > Account [Click Manage menu option > Account]. Here you can create and manage your resource groups, Cloud Foundry orgs, create tags to organize resources, manage your account settings, and more.

From the same Manage menu, you can go to Billing and usage [Click Manage menu option > Billing and usage] to view your usage, view invoices, and set spending notifications to help keep track of your costs.

Then, through the Manage > Access (IAM) option [Click Manage menu item > Access (IAM)], you can invite users to your account and manage their access to account resources including IAM-enabled, Cloud Foundry, and classic infrastructure resources.

In a connected world, security is more important than ever, and we've built it right into the platform [Click Menu icon > Security and Compliance]. With the IBM Cloud Security and Compliance Center [Click Dashboard], you can set up a unified dashboard to monitor security and compliance, govern configuration, and gain insights into threats.

If you prefer to work from the command line [Click IBM Cloud Shell menu item], you can manage your IBM Cloud account and resources from your browser with IBM Cloud Shell.
* Fixed: Fixed-rate pricing is based on an agreed upon monthly charge that isn't adjusted.
* Metered: Metered-usage pricing is based on the number of GB hours that are consumed for runtimes and the number of IP addresses and storage for containers.
* Tiered: Some pricing plans are based on a tiered pricing model, so you can get a volume-based discount according to your actual usage. Services might offer simple, graduated, or block tier pricing plans.
* Reserved: Reserved pricing is based on a long-term commitment for a service, so you can get a discounted price. With a reserved plan, you get a dedicated service instance that is easy to set up, deploy, and deliver in the public IBM Cloud environment.







 Managing your payments 

If you're a new Pay-As-You-Go account owner that is located in the US and you are paying with a credit card, you can replace your current card with a new one or edit the details of an existing card. In either case, you manage your credit card from the [Payments](https://cloud.ibm.com/billing/payments) page in the IBM Cloud console.

If you own one of the following accounts, in the IBM Cloud® console, you can go to Manage > Billing and usage to make a one-time payment, change your credit card details, view your billing items, and manage your invoices.



* New and existing Pay-As-You-Go accounts based in the US with any payment method other than a credit card
* New and existing Pay-As-You-Go accounts not based in the US
* New and existing Subscription accounts worldwide



The process for updating a credit card requires a manual review that might take a few days to process. To view your open change request cases, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).

You might manage your payment method on a separate billing platform. You can easily register, update, or delete a payment method by going to [IBM Billing](https://myibm.ibm.com/billing/).
When you have a Subscription account, you buy a subscription for an amount of credit to spend on resource usage within a certain time period. In exchange for this spending commitment, you get a discount on your usage costs. For example, you might buy a subscription for $12,000 USD a year that comes with a 10% discount. No matter when you incur usage costs within that year, you get fixed billing for the subscription amount, such as $1,000 a month. This account type is a good fit for enterprise organizations with large cloud workloads that want the predictability of fixed billing for their financial planning.

In addition to the two billable account types, customers that have a Subscription account can sign up for the Enterprise Savings Plan billing model. This billing model is similar to a Subscription account with a few added benefits. The following table details the two billable account types and billing model.



Table 1. Comparative analysis of account types

 Pay-As-You-Go Subscription Enterprise Savings Plan 

 Monthly billing Timely billing Timely billing 
 Invoiced on monthly consumption Invoices independent of usage Invoiced on monthly consumption 
 Best suited for developers and companies Best suited for enterprise organizations Best suited for both developers and enterprise organizations 





 Estimating your costs 

After you select the type of account that fits your organization's needs, it's time to understand how you will be charged for it. With an IBM Cloud billable account, you're charged for the compute, containers, and services that your organization consumes. You might be invited by other IBM Cloud users to participate in organizations under a different account. The usage for the apps or services that you use in the organizations that you're invited to are charged to the account that contains those organizations.

The following are the various charging types:



* Fixed: Fixed-rate pricing is based on an agreed upon monthly charge that isn't adjusted.
* Metered: Metered-usage pricing is based on the number of GB hours that are consumed for runtimes and the number of IP addresses and storage for containers.
* Tiered: Some pricing plans are based on a tiered pricing model, so you can get a volume-based discount according to your actual usage. Services might offer simple, graduated, or block tier pricing plans.
All plans for a product use either global or per location. By selecting per location, you can specify different regions or data centers for each plan that you add.
8. Link a broker to the plan.

If you haven't finished adding a broker to your account, you will not see this option, and you can continue and save your pricing plan. However, you can't complete your pricing plan until the broker is added and linked to your plan.
9. Click Save.







 Adding a paid pricing plan 

By adding a usage-based pricing plan, you are indicating that you offer your product as a paid integrated product, and customers need to pay to use it. All information that is entered on the Add plan panel is displayed to customers in the IBM Cloud catalog to help them purchase your service.

When you add a usage-based pricing plan, you provide your suggested retail pricing information. However, IBM reserves the right to set the final pricing for any product that is offered to customers in the IBM Cloud catalog.

To add a paid pricing plan for your service, complete the following steps:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select the product that you're onboarding, and click Pricing.
3. Click Add plan.
4. Select Usage-based.
5. Enter a name for your plan.
6. Describe the details of your plan.
7. Choose the locations where your plan is available. All plans for a product use either global or per location. By selecting per location, you can specify different regions or data centers for each plan that you add.
8. Select a broker to link to the plan.

If you haven't finished adding the broker to your account, you will not see this option, and you can continue and save your pricing plan.
Release notes for Hyper Protect Crypto Services 

Stay up to date with the new features that are available for IBM Cloud® Hyper Protect Crypto Services.



 1 June 2023 

Updated

: Pricing plan for Unified Key Orchestrator
: The pricing plan has been updated for Unified Key Orchestrator. You can find more details on the [service catalog page](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services).

For a detailed pricing sample, see [How am I charged for my use of Hyper Protect Crypto Services with Unified Key Orchestrator?](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-faq-pricing&interface=uifaq-how-charge-hpcs-uko).





 24 May 2023 

Updated

: Master key rotation support for all regions
: You are now able to rotate master keys when you are using the Unified Key Orchestrator service plan or your service instance that has EP11 keystores enabled in all supported regions. Previously, it was only available in Frankfurt, Germany.

For a list of supported regions, see [Regions and locations](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regions&interface=ui). For more information about how master key rotation works, see [Master key rotation introduction](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-master-key-rotation-intro).





 24 March 2023 

Added: Master key rotation for Unified Key Orchestrator
: You can now rotate master keys on demand to meet industry standards and cryptographic best practices in your Hyper Protect Crypto Services with Unified Key Orchestrator instance. You can understand how keys are protected during master key rotation and use the IBM Cloud console to view the progress. For more information about how master key rotation works, see [Master key rotation introduction](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-master-key-rotation-intro).

Added: Master key rotation for EP11 keystores
"tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1

$ ibmcloud resource service-instance-create $KMS_NAME kms tiered-pricing us-south

Creating service instance my-kms-1 in resource group Default of account <account name> as <email address>...
OK
Service instance my-kms-1 was created.
Name: my-kms-1
ID: crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:b3933ab0-d579-46fc-8ed5-351aea657b9a::
GUID: b3933ab0-d579-46fc-8ed5-351aea657b9a
Location: us-south
State: active
Type: service_instance
Sub Type: kms
Allow Cleanup: false
Locked: false
Created at: 2020-06-15T16:04:40Z
Updated at: 2020-06-15T16:04:40Z
Last Operation: Status create succeeded Message Completed create instance operation

 capture the Key Protect (KP) instance id (GUID)
$ KP_INSTANCE_ID=b3933ab0-d579-46fc-8ed5-351aea657b9a

 create a policy for COS to read KMS; source is COS, target is KMS
$ ibmcloud iam authorization-policy-create cloud-object-storage kms Reader --source-service-instance-id $COS_INSTANCE_ID --target-service-instance-id $KP_INSTANCE_ID

Creating authorization policy under account ea998d3389c3473aa0987652b46fb146 as <email address>...
OK
Authorization policy 18cfc980-4458-4313-972e-93f312cdcd81 was created.
Default is terminal compatible and the only supported alternative is JSON, for example, --output json.





 Output 

The command returns the following output:

Account: The IBM Cloud catalog is visible to all users in this account.

Filter:
Including IBM Cloud catalog

Type Include Tags
Pricing plan false Free
Provider false Third Party







 ibmcloud catalog filter create 

Run the following command to create a new filter. If a filter exists, this command overrides the current filter.

ibmcloud catalog filter create [--catalog CATALOG] [--category CATEGORY] [--compliance COMPLIANCE] [--deployment-target TARGET] [--exclude-list LIST] [--include-all ALL] [--include-list LIST] [--offering-format FORMAT] [--pricing-plan PLAN] [--provider PROVIDER] [--release RELEASE] [--type TYPE]



 Command options 

--catalog CATALOG (optional)
: Specify the catalog name or ID. If not specified, the filter is created at the account level.

--account-group ACCOUNT GROUP
: The account group name or ID. This option applies only to enterprise accounts.

--hide-ibm-catalog (optional)
: By default, the catalog is visible to all users in this account. By providing this flag, you can make products available only to the users you choose by turning off visibility to the IBM Cloud catalog and adding the products to your private catalogs.

--include-all BOOLEAN (optional)
: Default is true if flag not provided. Valid values are true and false. If set to true, the filter defaults to include the entire public catalog, and subsequent filters are excluded. If set to false, the filter excludes the entire public catalog, and subsequent flags are included. For more information, see [Managing catalog settings](https://cloud.ibm.com/docs/account?topic=account-filter-account).

--offering-format FORMAT (optional)

--category CATEGORY (optional)
: Provide the category that best fits how users might use your product.
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb145:390086ac-76fa-4094-8cf3-c0829bd69526:key:9cca88c9-019e-4f0a-9e76-8e657c6b9720"
}

 delete the key
$ ibmcloud kp key delete 9cca88c9-019e-4f0a-9e76-8e657c6b9720 --output json

{
"id": "9cca88c9-019e-4f0a-9e76-8e657c6b9720"
}





 Example 3 

Delete a root key that is registered with another cloud resource.

 create a Cloud Object Storage (COS) instance
 "lite" is the pricing plan and "global" is the region
$ COS_NAME=my-cos-1

$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=9d4353d8-6b85-4689-90dd-1ccfb4a275ab

 create a Key Management Service (KMS) instance
 "tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1

$ ibmcloud resource service-instance-create $KMS_NAME kms tiered-pricing us-south

 capture the Key Protect (KP) instance id (GUID)
$ KP_INSTANCE_ID=b0d84b32-09d0-4314-8049-da78e3b9ab6f

 create a policy for COS to read KMS; source is COS, target is KMS (Key Protect)