vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* numeric_value: An integer or double that expresses the numeric value of the value key.
* unit: A string that lists the unit of the value that was found in the normalized text.

The value of unit is the [ISO-4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) that is identified for the currency amount (for example, USD or EUR). If the service cannot disambiguate a currency symbol (for example, $ or £), the ambiguous symbol itself is stored as the unit value.



* provenance_ids: An array that contains zero or more keys. Each key is a hashed value that you can send to IBM to provide feedback or receive support.
* location: The location of the contract term as defined by its begin and end indexes.



* contract_currencies: An array that identifies the document's contract currency or currencies.



* confidence_level: The confidence level of the identification of the contract currency. Possible values include High, Medium, and Low.
* text: A contract currency, which is listed as a string.
* text_normalized: The normalized text, if applicable. It is listed as a string in [ISO-4217](https://www.iso.org/iso-4217-currency-codes.html) format
* provenance_ids: An array that contains zero or more keys. Each key is a hashed value that you can send to IBM to provide feedback or receive support.
* location: The location of the contract currency as defined by its begin and end indexes.



* document_structure: An object that describes the structure of the input document.



* section_titles: An array that contains one object per section or subsection that is detected in the input document. Sections and subsections are not nested. Instead, they are flattened out and can be placed back in order by using the begin and end values of the element and the level value of the section.



* text: A string that lists the section title, if detected.
* location: The location of the title in the input document as defined by its begin and end indexes.
Known issues 

Known issues might change over time, so check back occasionally.



 Network load balancer known issues 

Issue: When you create a listener for a network load balancer, you can specify a protocol of tcp or udp. However, each listener in the network load balancer must have a unique port. For network load balancer limitations, see [IBM Cloud Network Load Balancer for VPC limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-limitations).





 resource_type known issues 

Issue: Currently, not all operations that return responses with embedded VPCReference and SubnetReference schemas include the documented resource_type sub-property.

Workaround: Before developing a client that makes use of the resource_type property of the VPCReference or SubnetReference schemas, check that the property is included in the responses returned for the operations used by your client.





 Reserved IP known issues 

The following issues apply to reserved IPs. These issues will be resolved in a future release.

Issue: Reserved IP addresses that are bound to VPN gateways, IKS worker nodes, or DNS service instances will appear as having no target (the target property is not included when retrieving the reserved IP resource).

As a result, such reserved IP addresses may appear to be unbound. Despite appearing to be unbound, these reserved IP addresses cannot be deleted until their target resource is deleted.

In the console, reserved IP addresses that are labeled "unbound" might be bound to a resource that can't be displayed.

Issue: The instance metadata API does not currently support reserved IPs.

Workaround: Continue to use the primary_ipv4_address property to retrieve the IP address for each network interface on an instance. See the [VPC Metadata API](https://cloud.ibm.com/apidocs/vpc-metadata).
Example: ibmc-file-bronze.



 10 IOPs tier 

Name
: ibmc-vpc-block-10iops-tier
: ibmc-vpc-block-retain-10iops-tier
: ibmc-vpc-block-metro-10iops-tier
: ibmc-vpc-block-metro-retain-10iops-tier
: ibmc-vpcblock-odf-10iops
: ibmc-vpcblock-odf-ret-10iops

File system
: ext4

Corresponding Block Storage for VPC tier
: [10 IOPS/GB](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers)

Volume binding mode
: ibmc-vpc-block-10iops-tier: Immediate
: ibmc-vpc-block-retain-10iops-tier: Immediate
: ibmc-vpc-block-metro-10iops-tier: WaitForFirstConsumer
: ibmc-vpc-block-metro-retain-10iops-tier: WaitForFirstConsumer
: ibmc-vpcblock-odf-10iops: WaitForFirstConsumer
: ibmc-vpcblock-odf-ret-10iops: WaitForFirstConsumer

Reclaim policy
: ibmc-vpc-block-10iops-tier: Delete
: ibmc-vpc-block-retain-10iops-tier: Retain
: ibmc-vpc-block-metro-10iops-tier: Delete
: ibmc-vpc-block-metro-retain-10iops-tier: Retain
: ibmc-vpcblock-odf-10iops: Delete
: ibmc-vpcblock-odf-ret-10iops: Retain

Billing
: Hourly





 5 IOPs tier 

Name
: ibmc-vpc-block-5iops-tier
: ibmc-vpc-block-retain-5iops-tier
(https://cloud.ibm.com/docs-content/v1/content/a6478671e8f845a84102d9cf49bf28ee7f4f3227/security-compliance/images/access-model.svg)

Figure 1. Attachment hierarchy

Attachment A
: In Attachment A, the target scope is the full enterprise. As you can see, all account groups and accounts that exist within the enterprise are evaluated. That is, unless they have been purposefully excluded.

Attachment B
: The target scope of Attachment B is a specific account group within an enterprise. As you can see, the resources in the account group are now being evaluated against the profile that is selected during Attachment A and are evaluated according to the profile selected when Attachment B was created.

Attachment C
: The target scope of Attachment C is a child account. This attachment was created in the account, outside of the context of the enterprise. As you can see, Attachment A is monitoring the resources in the same account, but because Attachment C is created at the account level, resource groups are able to be seen and excluded.

To view the results of an evaluation, you look in the account where the attachment was created. If you use the previous image as an example, attachment A and B's results would exist within the enterprise account, and the enterprise account is charged for the evaluation. However, attachment C's results would exist within the child account.
Tier String None GlacierJobParameters Optional, and if left blank will default to the value associated with the storage tier of the policy that was in place when the object was written. If this value is not left blank, it must be set to Bulk if the transition storage class for the bucket's lifecycle policy was set to GLACIER, and must be set to Accelerated if the transition storage class was set to ACCELERATED. 



A successful response returns a 202 if the object is in the archived state and a 200 if the object is already in the restored state. If the object is already in the restored state and a new request to restore the object is received, the Days element will update the expiration time of the restored object.

Syntax

POST https://{endpoint}/{bucket}/{object}?restore path style
POST https://{bucket}.{endpoint}/{object}?restore virtual host style

<RestoreRequest>
<Days>{integer}</Days>
<GlacierJobParameters>
<Tier>Bulk</Tier>
</GlacierJobParameters>
</RestoreRequest>

Examples

Sample Request

POST /images/backup?restore HTTP/1.1
Host: s3.us.cloud-object-storage.appdomain.cloud
Date: Wed, 7 Feb 2018 19:50:00 GMT
Authorization: {authorization string}
Content-Type: text/plain
Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
Content-Length: 305

<RestoreRequest>
<Days>3</Days>
<GlacierJobParameters>
<Tier>Bulk</Tier>
</GlacierJobParameters>
</RestoreRequest>

Sample Response

HTTP/1.1 202 Accepted
Date: Wed, 7 Feb 2018 19:51:00 GMT
Connection: close



* Java
* Python
* Node



public RestoreObjectRequest(String bucketName,
String key,
int expirationInDays)

response = client.restore_object(
Reconcile your device-level permissions on specific devices to manage their bandwidth and membership in pools.
* Why don't I see the same number of devices as displayed on the devices count?

This issue might be due to permission restrictions because some users do not have permission to view specific devices. This issue might also be the result of devices that were reclaimed in the middle of the billing cycle, but are still contributing to the cost of the pool.
* What kind of devices generate bandwidth?

Compute devices use bandwidth. For example, devices that generate bandwidth include bare metal servers, virtual servers, firewalls (FSA 10G), and Netscaler devices.
* Why doesn't the allocation display the same value that I ordered?

The allocation that is shown is related to the proration policy. For example, imagine that you order 20 TB of bandwidth on the 15th of the month. The allocation that is shown on the bandwidth summary page will show 10 TB until the next billing cycle. Then, the allocation displays the full amount of what was ordered.
* What is the maximum number of devices that I can attach to a bandwidth pool?

You can attach an unlimited number of devices to a bandwidth pool.
* Is there a charge for traffic on the Classic Private Network?

There is no charge for traffic between Virtual Servers for Classic or Bare Metal Servers for Classic, on the Classic Private network, within the same Classic account.



Citrix Netscaler VPX



* What is Citrix Netscaler VPX?

Citrix NetScaler is an application delivery controller that makes applications five times better by accelerating performance, ensuring application availability and protection and substantially lowering operational costs. Choose the best Citrix NetScaler edition that meets your application requirements, and deploy it on the appropriate dedicated system for your performance needs. To learn more about Citrix NetScaler, refer to the [NetScaler page](http://www.citrix.com/products/netscaler-application-delivery-controller/overview.html) on the Citrix website.
* Why is load balancing needed?

Load balancing traffic has become a key aspect of many customer implementations as it distributes application requests and loads over multiple servers. It also provides a number of benefits to the overall topology including:



* Security.
* region and zone: If you want all your stateful set replicas and PVCs to be created in one specific zone, add both labels. You can also specify the zone and region in the storage class that you use. If you don't specify a zone and region and you have a multizone cluster, the zone in which your storage is provisioned is selected on a round-robin basis to balance volume requests evenly across all zones.
* billingType: Enter the billing type that you want to use for your PVCs. Choose between hourly or monthly. If you don't specify this label, all PVCs are created with an hourly billing type.



labels
: In the spec template metadata section, enter the same labels that you added to the spec.selector.matchLabels section.

affinity
: In the spec template spec section, specify your anti-affinity rule to ensure that your stateful set pods are distributed across worker nodes and zones. The example shows an anti-affinity rule where the stateful set pod prefers not to be scheduled on a worker node where a pod runs that has the app: nginx label. The topologykey: failure-domain.beta.kubernetes.io/zone restricts this anti-affinity rule even more and prevents the pod to be scheduled on a worker node if the worker node is in the same zone as a pod that has the app: nginx label. By using this anti-affinity rule, you can achieve anti-affinity across worker nodes and zones.

name
: In the spec volume claim templates metadata section, enter a name for your volume. Use the same name that you defined in the spec.containers.volumeMount.name section. The name that you enter here is used to create the name for your PVC in the format: <volume_name>-<statefulset_name>-<replica_number>.

storage
: In the spec volume claim templates spec resources requests section, enter the size of the block storage in gigabytes (Gi).

iops
Select metered to charge per GB and non-metered for a flat rate. Required.

--bgp-asn BGP_ASN
: Specify either the default value of 64999, or select an ASN from allowed ranges. Required.

--port-id PORT_ID
: Port ID for the gateway. Required when type is connect. Required.

--routing ROUTING
: Gateway routing of resources (global | local). Select global to connect resources across regions. Required.

--speed-mbps SPEED_MBPS
: Specify a value for the speed. Required.

--bfd-interval value
: Configures the minimum interval (in milliseconds) between the transmitted and received BFD packets. Range [300 - 255000]

--bfd-multiplier value
: The number of BFD packets not received by a neighbor that causes the originating interface to be declared down. Range [1 - 255]

--bgp-base-cidr BGP_BASE_CIDR
: Specify the BGP Base CIDR.

--bgp-cer-cidr BGP_CER_CIDR
: Specify the BGP customer edge router CIDR.

--bgp-ibm-cidr BGP_IBM_CIDR
: Specify the BGP IBM CIDR.

--connection CONNECTION_TYPE:
: Type of network connection that you want to bind to your direct link. One of: direct, transit.

--default-export-route-filter value
: Default export route filter. One of permit, deny.

--default-import-route-filter value
: Default import route filter. One of permit, deny.

--resource-group-id RESOURCE_GROUP_ID
: Resource group ID for this resource. If unspecified, the account's default resource group is used.

--help|-h
: Get help on this command.

--output value
: Specify whether you want the output displayed in JSON format.
* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-ubuntu-migrateubuntu-migrate-prereqs)
* [Migration steps](https://cloud.ibm.com/docs/containers?topic=containers-ubuntu-migrateubuntu-migrate-steps)
* [Removing your old worker pools](https://cloud.ibm.com/docs/containers?topic=containers-ubuntu-migrateubuntu-migrate-removal)









 Managing cluster costs 

[Understanding costs for your clusters](https://cloud.ibm.com/docs/containers?topic=containers-costscosts)



* [Understanding costs by component](https://cloud.ibm.com/docs/containers?topic=containers-costscosts-for-clusters)



* [Worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-costsnodes)
* [What is the difference between virtual and physical machines?](https://cloud.ibm.com/docs/containers?topic=containers-costsphysical-vs-virtual)
* [Public bandwidth](https://cloud.ibm.com/docs/containers?topic=containers-costsbandwidth)
* [Subnet IP addresses](https://cloud.ibm.com/docs/containers?topic=containers-costssubnet_ips)
* [Multizone load balancer](https://cloud.ibm.com/docs/containers?topic=containers-costsmzlb_pricing)
* [Storage](https://cloud.ibm.com/docs/containers?topic=containers-costspersistent_storage)
* [IBM Cloud services](https://cloud.ibm.com/docs/containers?topic=containers-costsservices)
* [Operators and other third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-costsoperators_pricing)
: ibmc-vpc-block-5iops-tier: Delete
: ibmc-vpc-block-retain-5iops-tier: Retain
: ibmc-vpc-block-metro-5iops-tier: Delete
: ibmc-vpc-block-metro-retain-5iops-tier: Retain
: ibmc-vpcblock-odf-5iops: Delete
: ibmc-vpcblock-odf-ret-5iops created: Retain

Billing
: Hourly





 Custom 

Name
: ibmc-vpc-block-custom
: ibmc-vpc-block-retain-custom
: ibmc-vpcblock-odf-custom
: ibmc-vpcblock-odf-ret-custom

File system
: ext4
: Corresponding Block Storage for VPC tier
: [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom)

Volume binding mode
: ibmc-vpc-block-custom: Immediate
: ibmc-vpc-block-retain-custom: Immediate
: ibmc-vpc-block-metro-custom: WaitforFirstConsumer
: ibmc-vpc-block-metro-retain-custom: WaitForFirstConsumer
: ibmc-vpcblock-odf-custom: WaitForFirstConsumer
: ibmc-vpcblock-odf-ret-custom: WaitForFirstConsumer

Reclaim policy
: ibmc-vpc-block-custom: Delete
: ibmc-vpc-block-retain-custom: Retain
: ibmc-vpc-block-metro-custom: Delete
: ibmc-vpc-block-metro-retain-custom: Retain
: ibmc-vpcblock-odf-custom: Delete
: ibmc-vpcblock-odf-ret-custom: Retain

Billing
: Hourly





 General purpose 

Name
: ibmc-vpc-block-general-purpose
* 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 

When you delete a bandwidth pool or remove a device from a bandwidth pool, the deletion and removal aren't instantaneous. These actions are scheduled to take place on the date of your next billing anniversary. For more information, see [Deleting bandwidth pools](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-how-to-delete-bw-pools) and [Removing devices from bandwidth pools](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-how-to-remove-devices-from-bw-pools).

In the time between your requests and the completion of these requests on your billing anniversary, you can unschedule your requests. For more information, see [Unscheduling deletion of bandwidth pools](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-how-to-unscedule-deletion-bw-pools) and [Unscheduling device removal from bandwidth pools](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-how-to-unschedule-device-removal-from-bw-pools).





 Use cases 

The following use cases describe common situations for managing bandwidth metering.
policyResource := &iampolicymanagementv1.V2PolicyBaseResource{
Attributes: []iampolicymanagementv1.V2PolicyAttribute{
accountIDResourceAttribute, serviceNameResourceAttribute},
}
weeklyConditionAttribute := &iampolicymanagementv1.V2PolicyAttribute{
Key: core.StringPtr("{{environment.attributes.day_of_week}}"),
Operator: core.StringPtr("dayOfWeekAnyOf"),
Value: []int{1,2,3,4,5},
}
startConditionAttribute := &iampolicymanagementv1.V2PolicyAttribute{
Key: core.StringPtr("{{environment.attributes.current_time}}"),
Operator: core.StringPtr("timeGreaterThanOrEquals"),
Value: core.StringPtr("09:00:00+00:00"),
}
endConditionAttribute := &iampolicymanagementv1.V2PolicyAttribute{
Key: core.StringPtr("{{environment.attributes.current_time}}"),
Operator: core.StringPtr("timeLessThanOrEquals"),
Value: core.StringPtr("17:00:00+00:00"),
}
policyRule := &iampolicymanagementv1.V2PolicyBaseRule{
Operator: core.StringPtr("and"),
Conditions: []iampolicymanagementv1.V2PolicyAttribute{
weeklyConditionAttribute, startConditionAttribute, endConditionAttribute},
}

options := iamPolicyManagementService.NewV2CreatePolicyOptions(
"access",
* Tier 3: The price per time-series is 0.03 USD for 1M to 10M time-series per month.
* Tier 4: The price per time-series is 0.02 USD for more than 10M time-series per month.



* Containers are priced as follows: 5.23 USD per 10 containers per month.
* API calls are priced as follows: The price for API calls is 0.01 USD per 1000 API calls per month.



Each measure is priced independently when there is an overage.

Platform metrics are an additional source of time-series. They are priced based on the tiers.

A host can be a container, a virtual machine, a bare metal, or any metrics source where you install a monitoring agent.

Data is collected and retained per the standard guidelines across all plans. For more information see [data collection](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mng-datadata-collection) and [data retention](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mng-datadata_storage_retention).

Prometheus remote write cost is based on metric ingestion. The price is calculated the same as for metrics collected using the agent with IBM Cloud Monitoring.





 Calculating time series pricing units 

Pricing units are comprised of time-series.

A time-series is a series of data-points ordered by time. It is a unique combination of a metric name and label key-value pairs. For example: website_failedRequest |region='Asia', customer_ID='abc'.

The same metric name can produce multiple time-series when the metric and label values differ.

For example, the following are 4 unique time series:

metric_name{datacenter=”dc-1”, zone=”zone1”} 23
metric_name{datacenter=”dc-2”, zone=”zone1”} 34
metric_name{datacenter=”dc-3”, zone=”zone2”} 43
metric_name{datacenter=”dc-4”, zone=”zone2”} 23
Bandwidth pool highlights include:



* defined geographically (charges vary depending on the region of your pool)
* allocated a bandwidth amount that's the sum of allocations for devices in the pool
* billed a pool overage fee when bandwidth usage exceeds bandwidth allocation
* billed a membership fee per device in the pool



100 percent of the bandwidth from each server added to a bandwidth pool is added to the pool's collective bandwidth allocation.

Zoom

![Adding servers with individual bandwidth allocations to a bandwidth pool](https://cloud.ibm.com/docs-content/v1/content/62b0b227c55ca35d2081883daccc11ef3a59022a/bandwidth-metering/images/comparing-bw-services.svg)

Figure 1. Adding servers with individual bandwidth allocations to a bandwidth pool

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 allow other devices in the pool to use the remaining bandwidth. This action can prevent that device's pre-purchased bandwidth allocation from being under-utilized. A similar benefit can occur in months during which the device risks exceeding its allocation. Including the device in the bandwidth pool with devices that have unused bandwidth can prevent the device with heavy use from incurring an overage.





 Managing bandwidth metering 

Follow these steps to manage bandwidth metering in your account:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. From the console, click the Navigation menu ![Navigation menu](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) and select Classic Infrastructure.
3. Select Network > Bandwidth.



Zoom

!
_interface_reserved_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_network_interface_reserved_ip)<br> * [ibm_is_instance_network_interface_reserved_ips](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_network_interface_reserved_ips)<br> * [ibm_is_instance_network_interfaces](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_network_interfaces)<br> * [ibm_is_instance_profile](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_profile)<br> * [ibm_is_instance_profiles](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_profiles)<br> * [ibm_is_instance_template](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_instance_template)<br> * [ibm_
: ibmc-vpc-block-retain-10iops-tier: Retain
: ibmc-vpc-block-metro-10iops-tier: Delete
: ibmc-vpc-block-metro-retain-10iops-tier: Retain
: ibmc-vpcblock-odf-10iops: Delete
: ibmc-vpcblock-odf-ret-10iops: Retain

Billing
: Hourly





 5 IOPs tier 

Name
: ibmc-vpc-block-5iops-tier
: ibmc-vpc-block-retain-5iops-tier
: ibmc-vpcblock-odf-5iops
: ibmc-vpcblock-odf-ret-5iops created

File system
: ext4

Corresponding Block Storage for VPC tier
: [5 IOPS/GB](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers)

Volume binding mode
: ibmc-vpc-block-5iops-tier: Immediate
: ibmc-vpc-block-retain-5iops-tier: Immediate
: ibmc-vpc-block-metro-5iops-tier: WaitforFirstConsumer
: ibmc-vpc-block-metro-retain-5iops-tier: WaitForFirstConsumer
: ibmc-vpcblock-odf-5iops: WaitForFirstConsumer
: ibmc-vpcblock-odf-ret-5iops created: WaitForFirstConsumer

Reclaim policy
: ibmc-vpc-block-5iops-tier: Delete
: ibmc-vpc-block-retain-5iops-tier: Retain
: ibmc-vpc-block-metro-5iops-tier: Delete
: ibmc-vpc-block-metro-retain-5iops-tier: Retain
: ibmc-vpcblock-odf-5iops: Delete