vania-janet/multiturn-rag-retrieval-data huggingface dataset:
A billable queue manager is charged based on the number of Virtual Processor Core (VPC) hours that it is active - for example, a Large size queue manager is charged at four times (4x) the rate of a Small size queue manager. The hourly cost is dependent on your local currency and can be seen in the Pricing Plan at the bottom of the [MQ service catalog page](https://cloud.ibm.com/catalog/services/mq), where you can select your country or region.

You can see details of your billable usage in the [IBM Cloud usage dashboard](https://cloud.ibm.com/account/usage) at the Account or Resource Group level.

If you cannot see your MQ usage on the dashboard, but have deployed a billable queue manager, ensure you have selected to view the usage for your resource group, e.g. Under the Usage Dashboard title, in the Group: dropdown menu, select Resource Groups then default.





 Queue manager resources 

The following table provides information about the resources available to each queue manager size and performance results based on testing:



 Lite<br><br>[1] Extra Small Small Medium Large 

 VPC <br><br> * <br><br><br> 0.5 1 2 4 
 Memory (RAM GB) <br><br> * <br><br><br> 1 1 2 4 
 Disk Size (GB) <br><br> * <br><br><br> 20 20 40 40 
 Disk performance (IO operations per second - IOPS) <br><br> * <br><br><br> 80 200 400 400 
 TCP non-persistent message throughput <br><br>[2] 10000 <br>per month 800 <br>per second 1500 <br>per second 3000 <br>per second 6000 <br>per second 
 TCP persistent message throughput <br><br>[3] 10000 <br>per month 50 <br>per second 100 <br>per second 400 <br>per second 1000 <br>per second
If you are using the IBM Cloud CLI or API you must also create an instance group manager. For more information, see [Setting up auto scale with the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-groupsetting-up-auto-scale-with-the-cli).
* How much am I charged for using auto scale?

Auto scale for VPC is free, but you are charged for the resources that you consume. For example, you are charged for virtual server instances that are created in the instance group.
* How does auto scaling work?

You set scaling policies that define your desired average utilization for metrics like CPU, memory, and network usage. The policies that you define determine when virtual server instances are added or removed from your instance group.

Auto scale uses the following computation to determine how many instances are running at any given time:

Σ(Current average utilization of each instance)/target utilization = membership count

For more information about how it works, see [Auto Scale for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-groupauto-scale-vpc).
* What permissions do I need for using auto scale?

You can check the required permissions for actions on instance templates, instance groups, instance group managers, memberships, and policies in the [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls). For more information about using IBM Cloud Identity and Access Management (IAM) to assign users access, see [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).
* Can I set multiple scaling policies?

You can set scaling policies for these metrics: CPU utilization (%), RAM utilization (%), Network in (Mbps), Network out (Mbps).
About pricing 

The pricing model for Key Protect instance depends on where the service is deployed and reflects the differing use cases and infrastructure requirements of cloud-based deployments compared to deployments into a user owned and managed infrastructure.

If your instance is deployed in an IBM Cloud location (for example, in us-south), you are charged per account based on how many key versions you have combined in all of your Key Protect instances. You are not charged per instance. If the service is deployed into a user-managed Satellite location, you are charged a flat rate for the service (regardless of the number of instances) and an additional rate for the total allotment of keys (also known as your “quota”) you have selected for that location.

For more information about pricing for Key Protect on IBM Cloud, check out [Pricing for Key Protect on IBM Cloud](https://cloud.ibm.com/docs/key-protect?topic=key-protect-pricing-plan).

For more information about pricing for Key Protect on Satellite, check out [Pricing for Key Protect on Satellite](https://cloud.ibm.com/docs/key-protect?topic=key-protect-pricing-plan-satellite).
When you provision a virtual server instance that supports the suspend billing feature, the usage times are calculated per second, for both the in use time and suspended time of your virtual server instance. Even if you never initiate the suspend billing feature by powering off your instance, the billing is calculated per second of the instance's lifecycle.



 Minimum usage charge 

Virtual server instances that support suspend billing have a minimum usage charge. This minimum usage charge is applied when a virtual server instance is powered off during its billing cycle whether the server was used or not.



* If usage is fewer than 25% of the allotted hours, you are charged the minimum 25% of the allotted hours - no matter how few hours that the server used.
* If usage is greater than 25% of the allotted hours, you are billed for all of the hours that the server used.







 Billing invoice 

When you suspend billing on a virtual server, a few changes appear in your billing invoice. The relevant charges now appear as usage-based details. For example, you might see the following additions that reflect hours available, hours that were used, and total number of hours charged:

Computing instance usage...
RAM usage...
Operating system usage...







 Resource details 



 Storage 

When you suspend billing on a virtual server instance, the billing for the associated storage persists, but you cannot access the stored data while the virtual server instance is powered off. When you resume billing on the instance, you can access your data again.





 IP addresses 

All public IP addresses are retained for you when billing is suspended for your virtual server instance.





 Limitations 

Virtual server instances that are suspended continue to count toward your account-wide device quota. For more information about instance limits, see [FAQ: Virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-faqs-virtual-serversconcurrent).







 Next steps 

After you provision a virtual server that supports suspend billing, you can start suspend and resume billing on the device.

When billing is suspended on a virtual server instance, you can't complete all of the same actions on the instance until you resume billing for the device.
For example, you might see the following additions that reflect hours available, hours that instances were used, and total number of hours charged:

Computing instance usage...
RAM usage...
Operating system usage...







 Resource details 



 Storage 

When you suspend billing on a virtual server instance, the associated storage persists, but you can't access data while the virtual server instance is powered off. When you resume billing on the instance, you can then access your data, and normal billing begins again.





 IP addresses 

All network configurations and IPs (private IPs from the subnet range) remain unchanged while the instance is suspended.

You can use the [Activity Tracker](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events) to check the status of your instance.





 Limitations 

Suspended virtual servers continue to count toward your account-wide device quota.
Provision a Public Gateway and Floating IPs for VMware Virtual Machines 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

This tutorial is part of [series](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-objectives), and requires that you have completed the related tutorials in the presented order.

If your VMware Virtual Machines require public Internet Access, you need to use either Public Gateway (outbound) or Floating IP (inbound). This tutorial provides an example for these use cases for a VMware VM's VLAN NIC.



 Objectives 

If your VMware Virtual Machines require public Internet Access, you need to use either Public Gateway (outbound) or Floating IP (inbound). This tutorial will provide you examples how to configure internet access for your VMware Virtual Machines using these IBM Cloud VPC network constructs.

Zoom

![Deploying Public Gateway and/or Floating IPs for a VMware Virtual Machines](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/Self-Managed-Simple-20210813v1-Non-NSX-based-VMs-pgw.svg)

Figure 1. Deploying Public Gateway and/or Floating IPs for a VMware Virtual Machines





 Before you begin 

This tutorial requires:



* Common [prereqs](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-prereqs) for VMware Deployment tutorials in IBM Cloud VPC
The VLAN network that you create are on that default, redundant uplink. You don’t need to manage uplink redundancy because redundancy is automatic.

For more information, see [Networking overview for Bare Metal Servers on VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-network).
* What storage replication is supported for Bare Metal Servers for VPC?

Replication isn't supported.
* What is the size of the boot drive for Bare Metal Servers for VPC?

The boot disk is 960 GB. You can configure each image differently for its partition sizes.

Bare Metal Servers for VPC supports only UEFI images.
* How does billing work?

You are billed for Bare Metal Servers for VPC based on the server profile that you selected. Billing stops only when you delete the bare metal server. Powering off the server doesn't change billing. For more information about billing and pricing, contact your IBM Sales representative.

You are also billed for other VPC services and resources that are attached to any bare metal servers. For more information about pricing for Bare Metal Servers on VPC, see [Pricing](https://www.ibm.com/cloud/vpc/pricing).
* How is billing for bare metal severs different from virtual server instances?

The main difference between virtual server instances and the bare metal servers is that powering off a bare metal server has no effect on the billing cycle. Meaning that hourly billed servers still accrue at the normal rate whether the server is powered off or on. The billing stops only when the bare metal server is deleted.
* How do I view my invoices?

To view your account invoices, follow these steps.



1. Go to the [IBM Cloud console ![External link icon](https://cloud.ibm.com/icons/launch-glyph.svg)](https://%7BDomainName%7D),
2. Then, click Manage > Billing and Usage.



Each account receives a single bill.
Provision NFS storage and attach to cluster 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

File Storage in IBM Cloud VPC is available for customers with special approval to preview this service in the selected regions. Contact your IBM Sales representative if you are interested in getting access.

This tutorial is part of [series](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-objectives), and requires that you have completed the related tutorials in the presented order.

In this tutorial, an NFS file share is created in IBM Cloud VPC and it is attached to a VMware cluster as a Datastore. This phase is optional, if you use vSAN as your preferred storage option.



 Objectives 

In this tutorial, an IBM Cloud VPC file share is created and you will attach this to the VMware Cluster as a datastore via NFS.

Zoom

![NFS as a Datastore](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/Self-Managed-Simple-20210813v1-VPC-nfs.svg)

Figure 1. NFS as a Datastore



1. Create file share in IBM Cloud VPC
2. Attach file share as a Datastore for a Compute Cluster in vCenter







 Before you begin 

This tutorial requires:



* Common [prereqs](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-prereqs) for VMware Deployment tutorials in IBM Cloud VPC
billingType: "hourly" The default billing policy used. User can override this default
encrypted: "false" By default, all PVC using this class will only be provider managed encrypted. The user can override this default
encryptionKey: "" If encrypted is true, then a user must specify the encryption key used associated KP instance
resourceGroup: "" Use resource group if specified here. else use the one mentioned in storage-secrete-store
zone: "" By default, the storage vpc driver will select a zone. The user can override this default
tags: "" A list of tags "a, b, c" that will be created when the volume is created. This can be overidden by user
classVersion: "1"
uid: "" The initial user identifier for the file share.
gid: "" The initial group identifier for the file share.
reclaimPolicy: "Delete"
allowVolumeExpansion: true
Show more

name
: Enter a name for your storage class.

profile
: Enter the profile that you selected in the previous step, or enter custom to use a custom IOPs value. To find supported storage sizes for a specific profile, see [Tiered IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). Any PVC that uses this storage class must specify a size value that is within this range.

encrypted
: In the parameters, enter true to create a storage class that sets up encryption for your File Storage for VPC volume. If you set this option to true, you must provide the root key CRN of your Key Protect service instance that you want to use in parameterencryptionKey.

encryptionKey
: If you entered true for parameters.encrypted, then enter the root key CRN of your Key Protect service instance that you want to use to encrypt your File Storage for VPC volume.

zone
: In the parameters, enter the VPC zone where you want to create the Block Storage for VPC instance.
Provision Bare Metal Servers for VPC network interfaces for NSX-T 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

This tutorial is part of [series](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-objectives), and requires that you have completed the related tutorials in the presented order.

In this tutorial, Bare Metal Servers for VPC VLAN network interfaces are created for NSX-T management and edge components. This phase is optional, if you plan to use NSX-T for your Virtual Machine networking.



 Objectives 

In the NSX-T deployment, multiple components will be attached to IBM Cloud VPC. These NSX-T components include:



* NSX-T Managers
* NSX-T Edge Transport Nodes
* NSX-T Host Transport Nodes (ESXi hosts)
* NSX-T Logical Router (Tier 0) uplinks



Each of these require one or more Bare Metal Servers for VPC VLAN interfaces to be created before you can start the actual NSX-T deployment and configurations. In this tutorial, you will create Bare Metal Servers for VPC network interfaces for NSX-T Managers and Transport Nodes.

Zoom

![VLAN interfaces for NSX-T deployment IBM Cloud VPC](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/Self-Managed-Simple-20210924v1-NSX-self-managed-mgmt.svg)

Figure 1. VLAN interfaces for NSX-T deployment IBM Cloud VPC
Metric Frequency Description 

 MAX_PRIVATE_NETWORK_ONE_G_COST Monthly Charge for private network endpoint at 1 GB uplink over a period of one month. 
 MAX_PRIVATE_NETWORK_TEN_G_COST Monthly Charge for private network endpoint at 10 GB uplink over a period of one month. 







 Licenses and fees for Veeam Availability Suite and Zerto 

Veeam® and Zerto usage incurs the following on-demand charges. You can view the charges on the IBM Cloud billing and usage view along with the usage and charges from all other IBM Cloud services.

In the IBM Cloud Usage view, locate the VMware Solutions service type. Locate the Organization plan to find the Veeam and Zerto usage across all virtual data centers in that organization. The virtual data center usage is located in a separate plan for either VMware Shared on-demand or VMware Shared Reserved.

Veeam

Zerto



Table 5. Licenses and fees for Veeam

 Metric Frequency Description 

 MAX_VEEAM_LICENSES Monthly Veeam license charge for every VM under backup. The monthly charge is for the highest number of VMs under backup at any time period in the month. 
 TOTAL_VEEAM_BLOCK_STORAGE_GB_HOURS Hourly Charge per GB of block storage used for all backups. 
 TOTAL_VEEAM_OBJECT_STORAGE_GB_HOURS Hourly Charge per GB of object storage used for all backups. 



No additional Veeam or Zerto usage charges for VMware Shared are incurred.

For the Veeam service, initially, all backups go to the block storage that is closest to their VM workloads. Backups that are a part of an inactive backup chain are immediately moved to Cloud Object Storage. The restore speed for these inactive backups might be impacted.

You can change how fast the inactive backup chains are moved to Cloud Object Storage by opening an IBM Cloud for VMware Solutions service ticket.





 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
One bare metal server with the configuration presented in [Technical specifications for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverviewvc_vcenterserveroverview-specs).





 Licenses and fees for expansion nodes 



* One vSphere Enterprise Plus 7.0 (NSX-T only)
* One NSX Service Providers Edition (Base, Advanced, or Enterprise) 6.4
* (For vSAN clusters) vSAN Advanced or Enterprise 6.6
* One Support and Services fee



You must manage the IBM Cloud for VMware Solutions components that are created in your IBM Cloud account only from the IBM Cloud for VMware Solutions console, not the IBM Cloud infrastructure customer portal, or any other means outside of the console. If you change these components outside of the IBM Cloud for VMware Solutions console, the changes are not synchronized with the console. Managing any IBM Cloud for VMware Solutions components, which were installed into your IBM Cloud account when you ordered the instance, from outside the IBM Cloud for VMware Solutions console can make your environment unstable. These management activities include:



* Adding, modifying, returning, or removing components
* Expanding or contracting instance capacity through adding or removing ESXi servers
* Powering off components
* Restarting services Exceptions to these activities include managing the shared storage file shares from the IBM Cloud infrastructure customer portal. Such activities include - ordering, deleting (which might impact data stores if mounted), authorizing, and mounting shared storage file shares.









 Support and Services fee 

VMware vCenter Server instances include a Support and Services fee that is charged per IBM Cloud bare metal server. This fee covers support from the IBM Cloud for VMware Solutions Support and Level 2 Support teams for any issues that pertain to automation in the platform and VMware products that are included in the solution.





 Technical specifications for vCenter Server multizone instances 

This information is provided as reference for existing vCenter Server multizone instances. New deployments of vCenter Server multizone instances are not supported.

The vCenter Server multizone architecture is an end-to-end reference architecture that provides automated failover for customer workloads.
The user enables two operational crypto units and two failover crypto units for cross-region high availability. The user also creates 10 KMS keystores and 12 GREP11 keystores. The first five keystores, including both KMS key rings and GREP11 keystores, are free of charge.



Table 1. A standard plan billing example of 30 days

 Pricing components Cost for 30 days (720 hours) 

 Operational crypto unit 1 $1533.6 (30x24x2.13) 
 Operational crypto unit 2 $1533.6 (30x24x2.13) 
 Failover crypto unit 1 $1533.6 (30x24x2.13) 
 Failover crypto unit 2 $1533.6 (30x24x2.13) 
 10 KMS key rings and 12 GREP11 keystores $3795 (5x0+15x225+2x210) 
 Total charge $9929.4 



* How am I charged for my use of Hyper Protect Crypto Services with Unified Key Orchestrator?

Each provisioned operational crypto unit is charged $2.13 USD per hour. After you connect to an external keystore of any type, the Unified Key Orchestrator base price of $5.00 USD/hour is charged.

The first 5 internal keystores and the very first external keystore are free of charge. Each additional internal or external keystore is charged with a tiered pricing starting at $225 USD or $70 USD per month, respectively. For keystores that are created or connected less than a month, the cost is prorated based on actual days within the month.

The detailed [pricing plan](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services) is available for your reference.

The following example shows a total charge of 30 days (720 hours). The user enables two operational crypto units in the service instance, and creates 22 internal keystores and 15 external keystores. The first 5 internal keystores and the first external keystore are free of charge.



Table 2. A Unified Key Orchestrator billing example of 30 days
Operational crypto unit 2 $1533.6 (30x24x2.13) 
 Failover crypto unit 1 $1533.6 (30x24x2.13) 
 Failover crypto unit 2 $1533.6 (30x24x2.13) 
 10 KMS key rings and 12 GREP11 keystores $3795 (5x0+15x225+2x210) 
 Total charge $9929.4 







 How am I charged for my use of Hyper Protect Crypto Services with Unified Key Orchestrator? 

Each provisioned operational crypto unit is charged $2.13 USD per hour. After you connect to an external keystore of any type, the Unified Key Orchestrator base price of $5.00 USD/hour is charged.

The first 5 internal keystores and the very first external keystore are free of charge. Each additional internal or external keystore is charged with a tiered pricing starting at $225 USD or $70 USD per month, respectively. For keystores that are created or connected less than a month, the cost is prorated based on actual days within the month.

The detailed [pricing plan](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services) is available for your reference.

The following example shows a total charge of 30 days (720 hours). The user enables two operational crypto units in the service instance, and creates 22 internal keystores and 15 external keystores. The first 5 internal keystores and the first external keystore are free of charge.



Table 2. A Unified Key Orchestrator billing example of 30 days

 Pricing components Cost for 30 days (720 hours) 

 Operational crypto unit 1 $1533.6 (30x24x2.13) 
 Operational crypto unit 2 $1533.6 (30x24x2.13) 
 22 internal keystores $3795 (5x0+15x225+2x210) 
 15 external keystores $980 (1x0+14x70) 
 Unified Key Orchestrator connection $3600 (30x24x5.00) 
 Total charge $11442.2