vania-janet/multiturn-rag-retrieval-data huggingface dataset:
From 1 February 2022, both [tagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) and [untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_untagged) images are charged for.

Quota limits and billing are scoped to the specific registry instance (one of the regional registries or the global registry) that you're currently working with. Quota settings must be managed separately for your account in each registry instance. For more information, see [Regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions).

Pull traffic across public connections counts toward usage and quota. Pull traffic across private connections doesn't count.

The following example is for pushing images:
: You push an image to your namespace that is based on the Ubuntu image. The Ubuntu image contains several layers. Because you do not have these layers in your account yet, the amount of storage that these layers require is added to your monthly usage.

Later, you create a second image that is based on the Ubuntu image. You change the Ubuntu base image, such as by adding more commands or files to your Dockerfile. Each change represents a new image layer. When you push the second image, Container Registry recognizes that all layers of the base Ubuntu image are already stored in your account. You're not charged for storing these layers a second time, even if you pushed your image to another namespace. Container Registry determines the size of all new layers and adds the amount of storage to your monthly usage.



 Billing for storage and pull traffic 

Depending on the service plan that you choose, you are charged for the storage and pull traffic that you use per month in each region.



 Storage charges 

Every IBM Cloud Container Registry service plan comes with a certain amount of storage that you can use to store your Docker images in the namespaces of your IBM Cloud account. If you're on the standard plan, you are charged by GB-Months of usage.
CANIUSE-LITE
(http://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30000979.tgz),
FOOTER.JS [React-Router] (https://github.com/ReactTraining/react-router)

END OF CREATIVE COMMONS ATTRIBUTION 4.0 GENERIC NOTICES AND INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.5 GENERIC

The Program includes some or all of the following works licensed under
the Creative Commons.
The url to the license is https://creativecommons.org/licenses/by-sa/2.5/legalcode

Template:CSSData [postcss-reduce-initial]
(http://registry.npmjs.org/postcss-reduce-initial/-/postcss-reduce-initial-4.0.3.tgz)

END OF CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 2.5 GENERIC NOTICES AND INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

CREATIVE COMMONS ATTRIBUTION SHARE ALIKE 3.0 GENERIC

The Program includes some or all of the following works licensed under
the Creative Commons.
The url to the license is https://creativecommons.org/licenses/by-sa/3.0/legalcode

REGULAR_EXPRESSIONS [posix-character-classes]
Viewing billing and usage information (ibmcloud billing) 

Use the following commands from the IBM Cloud® Command Line Interface to retrieve resource usage and billing information.



 ibmcloud billing account-usage 

Show monthly usage of the current account (account admin only):

ibmcloud billing account-usage [-d YYYY-MM] [--output FORMAT] [-q, --quiet]



 Command options 

-d MONTH_DATE (optional)
: Display data for the month and date that is specified by using the YYYY-MM format. If not specified, usage of the current month is shown.

--output FORMAT (optional)
: Specify output format. Accepted inputs are JSON and CSV.

-q, --quiet (optional)
: Suppress verbose output.





 Examples 

Show current account's usage and cost report in 2016-06:

ibmcloud billing account-usage -d 2016-06







 ibmcloud billing org-usage 

Show monthly usage for an org (account admin or org billing manager only):

ibmcloud billing org-usage ORG_NAME [-d YYYY-MM] [--output FORMAT] [-q, --quiet]



 Command options 

ORG_NAME (required)
: Name of the org.

-d MONTH_DATE (optional)
: Display data for the month and date that is specified by using the YYYY-MM format. If not specified, usage of the current month is shown.

--output FORMAT (optional)
: Specify output format. Only JSON is supported.

-q, --quiet (optional)
: Suppress verbose output.







 ibmcloud billing resource-group-usage 

Show monthly usage for a resource group (account admin or resource group admin only):

ibmcloud billing resource-group-usage GROUP_NAME [-d YYYY-MM] [--output FORMAT] [-q, --quiet]



 Command options 

GROUP_NAME (required)
: Name of the resource group.

-d MONTH_DATE (optional)
It allows to see any differences in the amount of data that is sent to the service from different users (IAM IDs) and if required, guides the setting of any quotas needed.





 IAM ID bytes out per second 

The number of bytes out per second from an IAM ID.



Table 28. The number of bytes out per second per IAM ID

 Metadata Description 

 Metric Name ibm_eventstreams_iam_id_bytes_out_per_second 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance, Service instance name, Iam Id 



This is for information to help you monitor trends in your usage, particularly if any IAM IDs are consuming unusually more throughput than expected. It allows to see any differences in the amount of data that is sent from the service to different users (IAM IDs) and if required, guides the setting of any quotas needed.





 IAM ID bytes in quota used percentage 

The percentage of bytes in quota used per IAM ID. Where a bytes in quota was set for a user (IAM ID), this value shows the percentage of that quota being used.



Table 29. The percentage of bytes in quota used per IAM ID

 Metadata Description 

 Metric Name ibm_eventstreams_iam_id_bytes_in_quota_used_percentage 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance, Service instance name, Iam Id 



This is for information to help you monitor trends in your usage, particularly if any IAM IDs are producing close to their quota limits. Quota metrics might sometimes exceed 100 %. Kafka quotas use sampling and are applied asynchronously. For some workloads, especially where data is sent in large batches, this may result in small deviations from the limit.





 IAM ID bytes out quota used percentage 

The percentage of bytes out quota used per IAM ID. Where a bytes out quota was set for a user (IAM ID), this value shows the percentage of that quota being used.



Table 30. The percentage of bytes out quota used per IAM ID

 Metadata Description
These service providers are already connected to the IBM Cloud network that uses multi-tenant, high capacity links (also known as network-to-network interfaces, or NNI).

To get started using IBM Cloud Direct Link Connect, follow these [instructions](https://cloud.ibm.com/docs/dl?topic=dl-how-to-order-ibm-cloud-dl-connect) for ordering the service.





 Learn more 



* IBM Cloud highly recommends that you establish a second, diverse direct link to prevent outages, whether unplanned, or planned due to maintenance. For more information, see [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link).
* If you require a diverse, redundant, or multi-cloud deployment for Direct Link Connect, see [Alternatives for your Direct Link Connect deployment](https://cloud.ibm.com/docs/dl?topic=dl-alternatives-for-your-ibm-cloud-direct-link-deployment).
* For more information about Direct Link offerings, see our [FAQs](https://cloud.ibm.com/docs/dl?topic=dl-faqs).



Currently, there isn't a migration path from Direct Link on Classic offerings to Direct Link. You must order a new Direct Link Dedicated or Direct Link Connect connection.
FortiGate Virtual Appliance on IBM Cloud overview 

FortiGate® Virtual Appliance on IBM Cloud deploys a pair of FortiGate Virtual Appliances to your environment, which can help you reduce risk by implementing critical security controls within your virtual infrastructure. FortiGate Virtual Appliance on IBM Cloud is a non-IBM product that is offered under terms and conditions from Fortinet, not IBM.



* You can install multiple instances of this service as needed. You can manage this service by using the FortiOS web Client or the CLI through SSH.
* For VMware vCenter Server® with NSX-T™ instances, FortiGate Virtual Appliance is supported for NSX-T 3.1 or later and for VMware vSphere® 7.0.
* For existing vCenter Server with NSX-V instances V4.7 and earlier, FortiGate Virtual Appliance is supported for vSphere 6.7.



IBM Cloud® for VMware Solutions offers promotions for some add-on services. Promotional pricing offers a number of months at no cost for a service licenses, if the service has license charges. For more information, see [Promotions for VMware Solutions add-on services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-service-promotions).

The FortiGate Virtual Appliance version available for deployment is 7.2.5.



 Technical specifications for FortiGate Virtual Appliance 

For more information about resource requirements and capacity checking for some services, see [Resource requirements for add-on services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-resource-requirements).

The following components are ordered and included in the FortiGate Virtual Appliance service:



 Virtual machines 



* All options include a pair of virtual machines (VMs).
* 2, 4, 8, 16, or 32 CPUs per VM. The number depends on the deployment size.
* 4, 6, or 12 GB RAM per VM.
After logging in to IBM Cloud, select IBM Informix on Cloud from the catalog tab. Set your Datacenter location from the available dropdown menu. Select one of the four plans that are listed which do not read Contact IBM Sales and click CREATE. The currently supported plans are Small, Medium, Large, and Extra Large. The Extra Large plan is a bare metal system. The Small, Medium, and Large plans are on a virtual machine. A page then appears, displaying a detailed summary about your chosen plan. If you have a trial IBM Cloud account, you can expect a message that outlines the details about your trial. Review this information.
2. When the system is ready, it will be indicated as such in the list of services on the IBM Cloud console. From this point, information about accessing the system can then be obtained in either of two ways:



* In the IBM Cloud console, create a connection between the ready Informix on Cloud service instance and any application, and then view the application’s “informix_on_cloud” environment variable.
* Wait for the welcome email.
: Updated the provider requirements, such as examples for installing RHEL packages on GCP hosts before you attach the host to your Satellite location.

Service requirements
: Added that you can provision up to [40 IBM Cloud service instances per Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-requirementsreqs-services).







 August 2020 

Review the release notes for August 2020.



 21 August 2020 

Review the release notes for 21 August 2020.

New! IBM Cloud Satellite is now available as a closed beta.
: For more information about the service and how it works, see the [Satellite product page](https://www.ibm.com/product/satellite). To register for the beta, go [here](https://cloud.ibm.com/satellite/overview).
Tutorials library

Filter:

Type



1. 10-minute tutorials
2. Lite plan



Categories



1.
AI / Machine Learning
2.
Analytics
3. Blockchain
4.
Compute
5.
Containers
6.
Databases
7.
Developer tools
8.
Integration
9.
Internet of Things
10.
Logging and monitoring
11.
Networking
12.
Platform
13.
Security
14.
Solutions
15.
Storage



Featured[Setting up your IBM Cloud account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started)![Default illustration.](https://cloud.ibm.com/media/docs/images/homepage/tutorial-default.svg)Setting up your IBM Cloud account

This tutorial walks you through the steps for setting up an account in IBM Cloud.



* 1 hour



[Deploy microservices with OpenShift](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-openshift-microservices)![Architecure diagram of an example microservice environment.](https://cloud.ibm.com/media/docs/images/homepage/featuredtutorial2.svg)Deploy microservices with OpenShift

This tutorial demonstrates how to deploy applications to Red Hat OpenShift on IBM Cloud.

Red Hat OpenShift on IBM Cloud Kubernetes service

+3

,Kubernetes service,Cloudant



* 3 hours



[Build a database-driven Slackbot](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-slack-chatbot-database-watson)![Architectural diagram of a Slackbot built with DB2, Cloud Functions, and Watson Assistant.]
Release notes for CIS 

Use these release notes to learn about the latest updates to IBM Cloud® Internet Services that are grouped by date.



  21 June 2023 

Enterprise Tier plans released
:   Released the new [Enterprise Tier plans](https://cloud.ibm.com/docs/cis?topic=cis-transition-plans), which will replace the current Enterprise Package, Enterprise GLB, and Enterprise Security plans.





  16 March 2023 

Standard Next plan released
:   Released the new [Standard Next plan](https://cloud.ibm.com/docs/cis?topic=cis-transition-plans), which will replace the current Standard plan.





  23 March 2022 

Alert policies
:   Added UI support for creating and managing alert policies.

Logpush workflow updates
:   Updated Logpush UI, and included IBM Log Analysis instance support.





  8 March 2022 

Log Analysis integration with Logpush
:   Added Log Analysis instance support to the API and CLI for creating and configuring Logpush jobs.





  2 March 2022 

New security alerts API
:   Added API for creating and configuring security alerts.





  5 November 2021 

New API for notifications
:   Added API for creating and configuring notifications.





  11 May 2021 

Service clock synchronization
:   Add service clock synchronization information.
[Multiple accounts for Satellite reference architecture](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/resource-organization/satellite-accounts-multiple-with-one-resource-group-beta2.drawio.svg)

Figure 4. Multiple accounts for Satellite reference architecture







 Scaling the number of deployments within an account 

If for some reason you do not want to use an [enterprise account](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationenterprises) and you have a limited number of consumers, then you might also consider a variation where you maintain separate resource groups for each deployment within an account.



 VPC reference architecture 

For the VPC reference architecture, this variation is shown in the following diagram. In this case, we still have a test and production account, but we create two new resource groups for each deployment.

Zoom

![Using two accounts with multiple resource groups for VPC reference architecture](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/resource-organization/vpc-accounts-two-with-multiple-resource-groups-beta2.drawio.svg)

Figure 5. Using two accounts with multiple resource groups for VPC reference architecture

While this reduces the number of accounts you need, it can also become problematic because each account is subject to [quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas) for VPC.





 Satellite reference architecture 

For the Satellite reference architecture, we still have a test and production account. We then create one new resource group for each deployment as shown in the following diagram.

Zoom

!
(https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/single-tier.svg)

Figure 3. Deploying in single zone





 Scenario 2 - deploying in multiple zones with IBM Cloud Internet Services 

You can deploy your application as active-active across multiple zones by using a combination of IBM Cloud Internet Services and IBM Cloud Load Balancer. This method enables replication across multiple zones, increasing the availability of the application. Because of the active-active deployment, more devices are available for parallel processing, improving resiliency and performance. The likelihood of simultaneous failure across multiple zones is much less likely in comparison to a single zone. If a failure occurs in one of the zones, the failure is contained in that zone. Even though the capacity is reduced during a failure, the application is still active in the other zone.

Zoom

![Multiple-zone deployment.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/multi-zone-cis.svg)

Figure 4. Deploying in multiple zones with IBM Cloud Internet Services and IBM Cloud Load Balancer

By deploying across multiple zones you can also take advantage of server pools and origins, which are part of IBM Cloud Cloud Internet Services (CIS). allow DevOps to integrate, validate, and deploy new software features. More information is covered in a later section of this document.





 Scenario 3 - deploying in multiple zones with IBM Cloud Load Balancer 

You can also deploy your application in multiple zones by using only IBM Cloud Load Balancer rather than a combination of IBM Cloud Internet Services and IBM Cloud Load Balancer. This deployment scenario is less ideal, but is more cost-effective. You should consider this method only for less critical and less sensitive applications, such as internal applications.

Zoom

![Multiple-zone deployment.]
Train and run machine learning models directly in the Db2 Warehouse on Cloud engine, using SQL, Python, or R. Db2 Warehouse on Cloud also supports spatial analytics with Esri compatibility, including Esri data types such as GML, and integration with Jupyter Notebooks.







 Plans and configurations 

Db2 Warehouse on Cloud offers several elastic data warehouse configurations to meet your workload requirements.

When you deploy your configuration on IBM Cloud, the following three plans are available:



* Flex One: a single-partitioned plan designed for growing enterprises and new data warehouse projects.
* Flex: a multi-partitioned plan designed for storage-dense workloads, inexpensive querying of large data sets, and development and test environments.
* Flex Performance: a multi-partitioned plan designed for high-performance, production workloads that prioritize compute performance over storage density.



When you deploy your configuration on Amazon Web Services, you choose a starting value for compute. The minimum required quantity of block storage is determined by the quantity of compute resources you choose. With the current generation of plans, you also have the option to store your data on cloud object storage. All instances on AWS are multi-partitioned.





 Supported cloud providers and data centers 

Db2 Warehouse on Cloud can be deployed on both IBM Cloud and Amazon Web Services.



 Availability of plans in IBM Cloud data centers 

The following table provides information about the availability of the various Db2 Warehouse on Cloud plans by IBM Cloud data centers that are located in geographical regions:



Table 1. IBM Cloud data centers supporting Db2 Warehouse on Cloud service plans

 Db2 Warehouse on Cloud plans Asia/Pacific Europe North/Central America South America 

 Flex Tokyo Frankfurt Dallas (us-south) *NA 
 Washington D.C. (us-east) 
 Flex Performance Tokyo Frankfurt Dallas (us-south) *NA 
 Washington D.C. (us-east) 
 Flex One Tokyo Frankfurt Dallas (us-south) *NA 
 London Toronto 
 Washington D.C. (us-east) 



*NA = Not available at this time
* [Plan your infrastructure provider](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-provider)
* [Plan for a multizone location](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-multizone)
* [Plan your host systems](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-compatible)



* [Planning your operating system](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfras-plan-os)



* [Deciding whether to enable Red Hat CoreOS support for your location](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planenable-coreos-loc)



* [Deciding how to create your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plancreate-options)



* [On-premises infrastructure](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plancreate-options-onprem)
* [Cloud provider infrastructure](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plancreate-options-cloud)



* [Providing Satellite with credentials to your cloud provider](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-credentials)







 Preparing your host infrastructure 

[Host system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqshost-reqs)



* [Computing characteristics](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-compute)
* [Red Hat CoreOS (RHCOS) packages and other machine configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqsreqs-host-packages-rhcos)
About IBM Cloud Satellite for Event Streams 

The IBM Cloud Satellite® plan for IBM® Event Streams for IBM Cloud® deploys functionality similar to the Enterprise plan into Satellite locations of your choice. Using IBM Cloud Satellite®, you can create a hybrid environment that brings the scalability and on-demand flexibility of public cloud services to the applications and data that run in your secure private cloud.

For a detailed comparison of the Event Streams plans and the functionality of each, refer to [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choose).

The Event Streams Satellite plan does not yet provide the compliance certifications that the Enterprise or Standard plans conform to.



 Overview 

To deploy Event Streams into a Satellite location, the following high-level steps must be completed and are detailed in [Provisioning Event Streams for Satellite](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-satellite-provisioning):



1. Provision a Satellite location and its control plane in your account. It enables you to bring your own hosts to the IBM Cloud® and provision IBM Cloud services onto your hosts.
2. Set up service-to-service authorization between Event Streams and Satellite in your account.
3. Provision and attach host compute infrastructure to your Satellite location. Event Streams uses the hosts when it is provisioned. Event Streams provides high availability by using multi-zone region deployment to protect against single points of failure. You must provision and balance the host compute infrastructure for the zones in your Satellite location. Host compute requirements are listed in the provisioning details.
4. Provision an Event Streams service instance in your account and a service cluster in your Satellite location.
5. Configure block storage for your Satellite location that Event Streams then allocates during the service instance provision process. Event Streams uses the block storage for the retention of your message data.

The block storage capacity cannot be scaled up for the initial release of Satellite plan for Event Streams.

Event Streams stores three replicas of your message data to ensure the highest level of resilience across three availability zones.