vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can create one or more dedicated hosts in your IBM Cloud VPC by using the IBM Cloud console.

Before you can create a dedicated host, you need to [create an IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console).

If you do not already have a dedicated group, you must create it as part of this task. The profile family and class of the dedicated host and dedicated group must be the same. The profile that you select for the dedicated host when you create it determines the profiles that can be used for the dedicated group and for provisioning instances to hosts in the group. For example, if you select a memory profile for the dedicated host, the associated dedicated group and instances provisioned on hosts in the group must also be provisioned with memory profiles.

To create a dedicated host:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Dedicated hosts.
2. Click Create and enter the information in Table 1 on the New dedicated host for VPC page.
3. Click Create dedicated host when you are ready to provision.





Table 1. Dedicated host provisioning selections

 Field Value 

 Dedicated host name A unique resource name within the region is required for your dedicated host. If you don't specify a name, a name is generated and assigned to your dedicated host. 
 Resource group Select the resource group that contains the account resources and users that you want to be able to access the dedicated host. For more information about resource groups, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs). 
 Tags You can assign a label to this resource so that you can easily filter resources in your resource list.
This scenario shows how to invite a new IBM Cloud user to your account and give them access to VPC infrastructure so they can view, create, and update all VPC resources in the Default resource group.

To give a new user access to all VPC infrastructure resources:



1. Go to the [IAM Users](https://cloud.ibm.com/iam/users) page in the IBM Cloud console and click Invite users.
2. Enter the email addresses of the users that you want to invite in the Enter Email addresses section.
3. In the Assign users additional access section, select IAM services and complete the following tasks:



* From the What type of access do you want to assign? list, select VPC Infrastructure Services.
* From the Resource type list, select All resource types.
* In the Platform access area, select Editor.
* In the Resource group access area, select Viewer.
* In the Service access area, select Console Administrator.
* Scroll to the end of the page and click Add.
* In the Access summary side panel, review the details and click Invite.









 Limited access scenario 

This scenario shows how to give an existing user permission to create and manage only virtual server instances in the Default resource group. Before the user can create an instance and associate a floating IP, the user also needs access to related resources, such as the VPC and subnet in which the instance will be created.



1. Go to the [IAM Users](https://cloud.ibm.com/iam/users) page in the IBM Cloud console and select the user whose access you want to configure.
2. On the Access policies tab, click Assign access.
3. In the Assign users additional access section, select IAM services and complete the following tasks:



* From the What type of access do you want to assign? list, select VPC Infrastructure Services.
* From the in list, select Resource group: default.
* From the Resource type list, select All resource types.
* In the Platform access area, select Editor.
* Make sure that the Resource group access option is set to Viewer.
* In the Service access area, select Console Administrator.
How Event Streams uses limits and quotas 

Event Streams uses quotas to control the resources, such as network bandwidth, that a service can consume. The types and levels of quotas depend on whether you use the Lite, Standard, Enterprise, or Satellite plan.



 Lite plan 



 Network throughput 

A recommended maximum for network throughput is 100 KB per second. Throughput is expressed as the number of bytes per second that can be both sent and received in a cluster.

The recommended figure is based on a typical workload and considers the possible impact of operational actions such as internal updates or failure modes, like the loss of an availability zone. If the average throughput exceeds the recommended figure, a loss in performance might be experienced during these conditions.





 Partitions 

One partition for each service instance.





 Retention 

A maximum of 100 MB for the partition.





 Consumer groups 

A maximum of 10 consumer groups. When the limit is exceeded, the GROUP_MAX_SIZE_REACHED error is returned to the client.





 Other limits 



* Maximum message size: 1 MB
* Maximum concurrently active Kafka clients: 5
* Maximum request rate [HTTP Produce API]: 5 per second
* Maximum request rate [HTTP Admin API]: 10 per second
* Maximum record key size when you use REST Producer API is 4 K.
* Maximum record value size when you use REST Producer API is 64 K.









 Standard plan 



 Network throughput 

The maximum throughput for each service instance equates to 1 MB per second per partition up to a maximum of 20 MB per second. For example, for a service instance with 10 partitions, the maximum throughput is 10 MB per second and for 30 partitions it is 20 MB per second.

The throughput is measured separately for producers and consumers. When exceeded, throttling is applied by slightly delaying the responses to requests, effectively applying a gentle brake to producers and consumers until the bandwidth is reduced.





 Partitions 

Hundred partitions for each service instance.





 Retention 

A maximum of 1 GB for each partition.





 Consumer groups 

A maximum of 1000 consumer groups. When the limit is exceeded, the GROUP_MAX_SIZE_REACHED error is returned to the client.





 Other limits
The quotas can be specified in MB, GB, or TB. These are hard quotas.
3. Select what you would like to occur when the quotas are reached.

Discard logs when the Daily Usage Quota is reached until midnight UTC
: If selected, when the daily quota is reached within a 24-hour period at UTC, logs will no longer be saved.

Discard logs when the Monthly Usage Quota is reached until the next billing cycle
: If selected, when the monthly quota is reached before the end of the billing cycle, logs will no longer be saved.

If logs are not being saved they will still be available for live tail and alerting.

Verify all conditions and exclusion rules when selecting these options. Selecting these options will result in logs being discarded and not saved for searching, archiving, or streaming.
4. Click Apply to save your changes.







 Configuring usage quota exclusion rules 

If you want to take action prior to daily or monthly quota being reached, you can set up exclusion rules that operate as soft quotas.

These exclusion rules will allow you to discard specific non-critial logs before reaching the hard quota threshold.

For example, if the daily usage quote is 2 GB and your set an exclusion rule for 50%, IBM Log Analysis will apply the configured exclusion rule and no longer retain logs from the sources, apps, hosts, or queries specified in the rule.

You can specify up to 5 daily exclusion rules and 5 monthly exclusion rules.



 Daily exclusion rules 

To specify a daily exclusion rule, do the following from the Usage Quotas dialog:

Verify that each exclusion rule that you add behaves as expected. Improper configured exclusion rules can result in storing data not intended for storage.



1. In the Triggered Exclusion Rules section click Add daily rule.
2. Drag the slider to the percentage of the daily usage quota when you want the rule triggered. For example, 50%. If you try to set a percentage where an exclusion rule exists, you will be warned that the existing rule will be replaced.
3. Select the source of the logs you want to exclude.
4. Select the apps you want to exclude.
5.
Viewing usage details from the usage summary widget 

In the usage summary widget on the billing and usage dashboard, you get view of your actual and predicted spending trends.

The predicted usage for the next month is calculated by finding the trend from the usage of the last three months, including the current month. For example, if it's August, predicted usage is calculated based on usage trends in June, July, and August to find the predicted usage for September.

Let's say the usage is $950.00 USD for June, $1000.00 USD for July, and $1012.50 USD for August. The difference is calculated between the current month and the last month, and last month and the month before that. Then, the two calculations are averaged to find the trend. That trend amount of $1043.75 USD is the predicted next month's usage, with the following calculations:



* Change between August and July = $1012.50 - $1000.00 = $12.50 USD
* Change between July and June = $1000.00 - $950.00 = $50.00 USD
* Average change (trend) = ($12.50 + $50.00) / 2 = $31.25 USD



August usage ($1012.50) + Average change ($31.25) = The predicted usage for next month September ($1043.75 USD)





 Viewing usage details from the usage page 

In the Services section, you can view a list of your services and the estimated costs that are associated with those services. To view a summary of estimated charges for all instances of a specific resource, complete the following steps:



1. In the IBM Cloud® console, go to Manage > Billing and usage, and select Usage.
2. Click View plans to view all the instances of a specific type of resource.
3. To view a detailed summary of estimated charges for each instance of a specific resource type, click View details. You can also view the detailed monthly usage metrics for the selected instance.



If you have a Pay-As-You-Go account that isn't billed in US dollars or a Subscription account, the usage for all services is finalized by the 20th of the following month.
Checking your resource group quotas 

Quotas provide limits for accounts, IBM® Cloud Foundry orgs and spaces, and resource groups. This documentation discusses quotas for resource groups. For more information about IBM Cloud Foundry quotas, see [Creating your web app with the IBM Cloud console](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-getting-startedee_appui). Quotas are also different for IBM Cloud® Virtual Private Cloud. For more information, see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas).

Quotas for [resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs) limit the number of apps, instances, and memory allowed for that specific resource group. Each resource group in your account has a specific set of quotas. Standard quotas are for resource groups that are created by users with a Lite account, and Pay-As-You-Go quotas are for resource groups that are created with a Pay-As-You-Go account.

The following table shows resource group quota limits.



Table 1. Resource group quota limits

 Type Max apps Max instances per app Max app instances memory Total app memory Max service instances 

 Pay-as-you-go quota 100 32 512G 512G 30,000 
 Standard quota 4 2 1G 1G 1,000 



The following definitions explain the quota limit categories for resource groups.

Type
: Either Pay-As-You-Go quota for Pay-As-You-Go accounts or standard quota for Lite accounts.

Max Apps
: The maximum number of web applications that you can create in a resource group.

Max Instances Per App
: The maximum number of instances of the same web application that you can create in a resource group.

Max App Instance Memory
: The maximum amount of memory allowed for each individual web application instance.

Total App Memory
: The maximum amount of memory allowed for each individual web application.

Max Service Instances
: The maximum service instances per resource group. Service instances are different from web application instances.
The full monthly charge is applied, regardless of how much the instance is used.

Formula:



* If provisioned date is from the current month: (Unit Price) * (Number of days that are remaining in the month / Number of days in the month)
* If provisioned date is from the previous month: (Unit Price)



Given a 30-day month, see the following table to calculate the monthly prorated cost:



Table 7. Monthly prorated cost calculations

 Time Usage Calculation Quantity in dashboard 

 Month 1, Day 1 1 1 * (30/30) 1 
 Month 1, Day 16 1 1 * (16/30) 0.5 











 Pricing models 

The following table provides detailed information about the pricing models that are available. For many of the available metrics, you select an associated pricing model.



Table 8. Pricing models

 Model Description Calculation Example (5000 quantity) 

 Linear Multiply the unit price per resource (P) by the usage quantity (Q) to get the total amount (T) P * Q P=$1 T=1 * 5000 =$5000 
 Simple tier (granular tier) A P * Q model in which the unit price for all consumption is determined by the tier the quantity falls into. If Q is <=Q1, T=P1 * Q<br><br>If Q1 < Q <=Q2, T=P2 * Q<br><br>If Q2 < Q <=Q3, T=P3 * Q Q1=1000, P1=$1<br><br>Q2=2500, P2=$0.9<br><br>Q3=10000, P3=$0.75<br><br>T=$0.75 * 5000=$3750 
 Graduated tier (step tier) The price per unit varies as the quantity-consumed moves into different predefined tiers.
For more information, see [Ordering a Citrix Netscaler VPX](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-getting-startedordering-a-citrix-netscaler-vpx).





 About bandwidth pools 

Bandwidth pooling optimizes your bandwidth usage by "pooling" all of the bandwidth of individual servers together into a bandwidth pool.

The bandwidth usage of devices in a bandwidth pool is summed up as a whole, and overages are calculated only if the total bandwidth of all servers exceeds the total allocated bandwidth for all servers. For example, if a bandwidth pool had five servers, each with 2000 GB of bandwidth, and one server used 3000 GB of bandwidth while the other used only 1500 GB of bandwidth in a billing cycle, you are not billed for a pool overage. Your total usage would be 9000 GB and your total allocated bandwidth would be 10000 GB. You would receive a notification after 8,500 GB of bandwidth usage.

Notifications are sent to the account owner when the devices in the pool collectively use 85% of the pool's allotted bandwidth.

Bandwidth pools are beneficial when you have devices with variable month-to-month usage. In months during which the device uses little bandwidth, adding a device's individual bandwidth allocation to a bandwidth pool can prevent that device's bandwidth allocation from going to waste. In months during which the device risks exceeding its individual allocation, including the device in the bandwidth pool can prevent the device from receiving an overage fee. Bandwidth pools are defined geographically.

Certain actions and devices are not permitted in bandwidth pooling:



* devices billed hourly (fully metered) are not eligible for bandwidth pooling
* devices with unlimited bandwidth plans are not eligible for bandwidth pooling
* pool-to-pool device moves are not permitted in the same billing period



Devices billed hourly (fully metered) and devices with unlimited bandwidth are not eligible for bandwidth pooling.

For more information, see [Creating bandwidth pools](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-how-to-create-ibm-cloud-bandwidth-pools).





 About pool deletion and device removal
Managing usage quotas 

In IBM Cloud® Activity Tracker, you can use the Usage Quota settings to control how much data is stored so you can manage your data cost while still being able to view and retain the data you need.



 What are usage quotas? 

You can use the Usage Quotas feature to set daily or monthly thresholds for the volume of log files that are to be stored. When the threshold is exceeded, IBM Cloud® Activity Tracker will take the actions you configure.

You can configure the system to:



* Stop storing all logs when the threshold is exceeded.
* Stop storing specific logs based on exclusion rules.
* Create alerts when a usage quote threshold is met.



When you stop storing some or all logs, logs will still be available in the live tail but will be unavailable for historical or audit purposes. Logs that are not stored do not count towards your usage billing.

By setting Usage Quotas you can balance your organization's needs to view, alert, and maintain important logs while balacing the need to manage the cost of data storage.





 Types of usage quotas 

There are three types of usage quotas.

Hard quotas
: A hard quota will stop saving or archiving all logs when the configured daily or monthly quota threshold is reached.

Soft quotas
: A soft quota will stop saving or archiving logs based on the exclusion rules you define. These exclusion rules can be configured to specify which logs to store and which to discard. For example, you can specify exclusion rules to discard rules from a specific host, application, or other query.

Alert-only
: An alert-only quota will send an alert allowing logs to continue to be saved, and your data usage to grow, even though the defined threshold has been exceeded.





 Considerations when using usage quotas 

When you exclude logs using the Usage Quotas function, the excluded logs will not be archived or streamed.

When deciding to use Usage Quotas, consider the following:



* Usage Quotas configured actions are separate from any other [defined exclusion rules.]
Unlike Standard plan instances, One Rate instances provide allowances for [Class A and B request charges](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-billingbilling-request-classes) as well as egress charges. The thresholds for the allowances are dependant on total storage capacity.

It is not possible to convert an instance created under a One Rate plan to a Standard plan, or vice-versa.



 How allowances are calculated 

One Rate plans use an all-inclusive flat monthly rate which includes capacity, operational requests, and outbound bandwidth. The built-in allowances for outbound bandwidth are determined by the total capacity.

> Total Monthly Cost = Capacity Cost + API Cost (if # of API > allowance) + Bandwidth cost (if Bandwidth > allowance)



* Class A allowance: Number of Class A Requests < 100 x Storage (GB)
* Class B allowance: Number of Class B Requests < 1000 x Storage (GB)
* Bandwidth allowance: Bandwidth (GB) < Storage (GB)



Archive is supported but Restore charges are not included in the One Rate allowances





 How to provision a One Rate instance 

A One Rate instance is specified at the point of provisioning, similar to a Lite or Satellite instance.



1. Log in to [the console](https://cloud.ibm.com/).
2. Navigate to the catalog, by clicking Catalog in the navigation bar.
3. Look for the Object Storage tile in the storage section and select it.
4. Select IBM Cloud from the "Choose an Infrastructure" section.
5. Select One Rate from the plans.
6. Choose a name, resource group, and any desired tags.
7. Click Create and you're automatically redirected to your new instance.







 Special provisioning codes 

All buckets created in a One Rate plan must use a [specific provisioning code](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-classes) (also known as a storage class or location constraint).

North America

Europe

Asia



 Location Location Constraint
* UI
* CLI
* API







 Viewing your usage 

You can view your IBM Cloud® usage details from the billing and usage dashboard or from the Usage page in the console. Your usage details include a summary of estimated charges for all services and resources that are used per month in your organizations.



 Before you begin 

Ensure that you have the required access to view usage data for the resources. Access can be assigned at the account-level or to individual resource groups and Cloud Foundry orgs.



* To view usage for all resources in the account, you need an access policy with the Administrator role on the Billing account management service.
* To view usage only for specific IBM Cloud® Identity and Access Management (IAM) resources, you need the Viewer role on the resource group.
* To view usage only for specific Cloud Foundry services, the Billing manager role must be applied at the org level. Billing managers can see the details for only the organizations in which they are assigned the Billing manager role.



You can limit the access to view the usage for a specific resource group by assigning the viewer role or higher on all Identity and Access enabled services within that resource group.

For more information about access roles, see [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles) and [Cloud foundry access](https://cloud.ibm.com/docs/account?topic=account-cfaccess).





 Viewing service usage details in the console 

The usage summary widget provides a view of your month-to date-spending, last month spending, average monthly spending, and next month's predicted usage at a glance. For a more granular view of your usage and specific costs that are associated with services, view your usage from the usage page.



 Viewing usage details from the usage summary widget 

In the usage summary widget on the billing and usage dashboard, you get view of your actual and predicted spending trends.

The predicted usage for the next month is calculated by finding the trend from the usage of the last three months, including the current month. For example, if it's August, predicted usage is calculated based on usage trends in June, July, and August to find the predicted usage for September.
ibmcloud ks quota ls [--provider PROVIDER] [--output json]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--provider (classic | vpc-gen2)
: The infrastructure provider type to list quota and limits for.

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

Example:

ibmcloud ks quota ls







 subnets command 

Virtual Private Cloud

Classic infrastructure

List available subnets in all resource groups in your IBM Cloud infrastructure account.

ibmcloud ks subnets [--provider (classic | vpc-gen2)] [--vpc-id <VPC_ID> --zone <VPC_ZONE>] [--location LOCATION] [--output json] [-q]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--provider (classic | vpc-gen2)
: The infrastructure provider type to list subnets for. This option is required to list VPC subnets.

--vpc-id VPC_ID
: The ID of the VPC to list subnets for. This option is required when you specify the vpc-gen2 provider type. To list VPC IDs, run ibmcloud ks vpcs.

--zone VPC_ZONE
: The zone to list VPC subnets for. This option is required when you specify a VPC provider type.

-l, --location LOCATION
: Filter output by a specific location. To see supported locations, run ibmcloud ks locations. To specify multiple locations, use one option for each location, such as -l dal -l seo.

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

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

Example:

ibmcloud ks subnets -l ams03 -l wdc -l ap





 vlan commands 

Classic infrastructure