vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<br><br> * Activate a subscription code<br><br><br> With an IBM Cloud subscription, you get discounted usage for platform services and support by committing to a minimum spending commitment for a certain period of time. After you buy a subscription for platform or support credit, you must add the credit to your account by applying a subscription code to your stand-alone account or enterprise. Applying the code ensures that the credit is added to your account, and you don't have unexpected overage charges. Make sure to add any purchased subscriptions to your account before creating resources. For more information, see [applying subscription codes](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscription_code). 
 <br><br> * Create and configure an enterprise<br><br><br> When you create an enterprise, the account that you used to initiate the process is automatically added to the enterprise, and a new enterprise account is created to manage the billing for the enterprise. Follow the steps in the [Setting up an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-enterprise-tutorial) documentation to create an enterprise. Keep in mind that when using an enterprise, users within each account in the enterprise can create, use, and collaborate on resources just as they can in a stand-alone account. 
 <br><br> * Assign enterprise access to users<br><br><br> If you chose to create an enterprise, you might require that administrators manage the enterprise performing functions, such as creating account groups, creating and managing accounts. Review the access that is required, and add users as needed. For more information, see [Assigning access for enterprise management](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-assign-access-enterprise). 
 <br><br> * Create resource groups<br><br><br> Use resource groups to organize an account's resources for access control and billing purposes. For example, creating a resource group per project allows costs to be tracked at the project level even when your resources are distributed across regions.
With this consumption model, you pay only for the compute resources that you use, in an hourly pricing model.
* Reserved. With this consumption model, you can reserve compute resources in advance to ensure that your capacity is available when you need it. Billing for Reserved is available monthly, yearly, or on a multi-year basis. Other resources, such as storage and egress, are billed per usage, regardless of the consumption model.



* Why do I want to subscribe to VMware Shared?

With VMware Shared, you can extend your VMs to the Cloud with ultimate capacity flexibility and scalability. Whether you are looking to begin your cloud journey with a Development or Test environment, a disaster recovery site, or a full enterprise-grade hybrid cloud transformation, VMware Shared provides a cost-effective and self-service way to start moving your VMs to the cloud within minutes.

With IBM managing the infrastructure up to the hypervisor, you do not need to worry about managing patches, upgrades, and monitoring, which gives you more time and resources to focus on innovation. In addition, with a native like VMware experience, you can use your existing VMware resources and skill sets.
* What user accounts do I need for VMware Shared?



* IBMid account. This account is required to access the IBM Cloud for VMware Solutions console. The console is a stand-alone user interface that is separate from the IBM Cloud infrastructure customer portal. For more information, see [Getting started](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-getting-started).
* IBM Cloud account. This account is required for provisioning. You can sign up for an IBM Cloud account by using an existing IBMid or by creating a new IBMid.
* IBM Cloud infrastructure account. This account is used to log in to the IBM Cloud infrastructure customer portal that provides some additional function to manage infrastructure products and services. You can get an IBM Cloud infrastructure account by upgrading your IBM Cloud account to a billable account, or by linking your existing IBM Cloud infrastructure account with your IBM Cloud account. The IBM Cloud infrastructure account that you are using must meet certain requirements.
To learn more about this integration, check out the [Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-ingress-types) or [Red Hat OpenShift on IBM Cloud documentation](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-roks4).





 23 March 2022 

Standard and Trial pricing plans
: You can now create an unlimited number of Secrets Manager service instances by choosing the Standard pricing plan. For more information about pricing in Secrets Manager, check out the [announcement blog](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-secrets-manager-new-pricing-model).

If you're an existing Secrets Manager Lite plan user, be sure to upgrade your instance to the Standard plan before 22 May 2022 if you'd like to maintain access. For more information, see the previous [release note](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-release-notessecrets-manager-feb2322).

Osaka and Toronto availability
: You can now create a Secrets Manager service instance in the Osaka (jp-osa) and Toronto (ca-tor) regions.

For more information, see [Regions and endpoints](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-endpoints).





 15 March 2022 

Tutorial series: Set up alerts for expiring certificates
: Looking for examples that can help you to send Secrets Manager notifications to GitHub or Slack? Check out the new [tutorial series](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-expiring-secrets-part-1) that guides you through:



* Enabling [Event Notifications](https://cloud.ibm.com/docs/event-notifications) for Secrets Manager
* Using [Cloud Functions](https://cloud.ibm.com/docs/openwhisk) to create a GitHub issue when a secret is about to expire
When the app is deployed, if it has a web interface (for example, a Java™ web app), or other REST-based services (such as mobile services exposed publicly to the mobile app), users of the app can communicate with the app by using HTTP requests.

Zoom

![Invoking an IBM Cloud app](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public/images/execute.png)

Figure 3. Invoking an IBM Cloud app

Each app can have one or more URLs associated with it, but they must all point to the IBM Cloud endpoint. When a request comes in, IBM Cloud examines the request, determines which app it is intended for, then selects an instance of the app to receive the request.



 Cloud Foundry architecture in IBM Cloud 

In general, you don't have to worry about the operating system and infrastructure layers when apps are run on IBM Cloud in Cloud Foundry. Layers such as root file systems and middleware components are abstracted so that you can focus on your app code. However, you can learn more about these layers if you need specifics on where your app is running.

See [Viewing IBM Cloud infrastructure layers](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-howworkviewinfra) for details.

As a developer, you can interact with the IBM Cloud infrastructure by using a browser-based user interface. You can also use a Cloud Foundry command-line interface, called cf, to deploy web apps.

Clients, which can be mobile apps, apps that run externally, apps that are built on IBM Cloud, or developers that are using browsers, interact with the IBM Cloud-hosted apps. Clients use REST or HTTP APIs to route requests through IBM Cloud to one of the app instances or the composite services.

The following figure shows the high-level Cloud Foundry architecture on IBM Cloud.

Zoom

!
Then, in the Overview page, click estimate the cost of this app to see the price of SDK for Node.js runtime and Support, and the total monthly price of your app.

Or, in the Pricing Sheet page, type the monthly usage of the runtime and services of your app. For example, 3 instances of SDK for Node.js with 1 GB memory for each instance. The monthly price is calculated and displayed.

You can also calculate your app cost manually by adding up the prices of your runtimes and services and deducting the free allowance. For more information, see Calculating your costs manually.





 Removing apps 

As you build more apps, the quota might approach your limits. However, some apps that you might no longer use still occupy the quota. It’s easy to delete apps to free up some spaces in IBM Cloud at any time.

In the IBM Cloud console, go to the app Overview page, click the menu icon, and delete the app that you no longer use. You can also use the ibmcloud cf delete command to delete apps.
Create and send push notifications to Android mobile using Event Notifications 

Create an Event Notifications service, add a push destination for Firebase Cloud Messaging (FCM), and send messages to Android devices.



 What is Event Notifications? 

Event Notifications is an event notification routing service that notifies you of critical events that occur in your IBM Cloud account or triggers automated actions by using webhooks. You can filter and route event notifications from IBM Cloud services like Availability Monitoring, to email, SMS, push notifications, and webhooks.





 How do clients use Android Push Notifications? 

The following diagram shows you how clients use Android Push Notifications.

Zoom

![How clients use push notifications](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-how-send.svg)

Figure 1. How clients use push notifications





 Objectives 

This tutorial shows you how to send push notifications as follows:



* Create a mobile app with Event Notifications.
* Get FCM credentials.
* Download the code and complete the notifications setup.
* Configure and send Android Push Notifications to a mobile device.







 Before you begin 

You must have the following prerequisites in place:



* Download and install [Android Studio](https://developer.android.com/studio/index.html) so that you can import and enhance your code.
* A Google account to log in to Firebase console to get your project_id, private_key, and client_email.
* An IBM Cloud account. If you do not have one, [create an IBM Cloud account](https://cloud.ibm.com/).



The instructions used in this document uses FCM's HTTP v1 API. The HTTP v1 API has advantages such as secure access tokens, efficient customizations, and future proof as well as more extendable client platform versions.
Error handing for Cloud Functions 

IBM Cloud® Functions provides error handling through the execution status of each function invocation. Error handling is provided by Cloud Functions for invocations that are exposed through the Cloud Functions API, SDK, CLI, or the console. For more information about the various error types, see [Action executions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_exec).

In addition, the Cloud Functions service automatically reports errors to the Monitoring service. You can set up the built-in integration for the Monitoring service with the IBM Cloud® Functions service to automatically react to error messages. For more information about setting up an alert through a subsequent action invocation, see [IBM Cloud Monitoring](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-alerts-notify).

To handle errors, choose one of the following options.



1. Handle application errors programmatically within the action implementation itself and handle service errors through the Cloud Functions service API, CLI, SDK, or console by leveraging the automatically set Cloud Functions execution status.
2. Use the built-in integration with the IBM Cloud Monitoring service to define a subsequent action to be invoked in response to the error. All configuration and execution occurs service-side. For more information, see [IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-notifications) and [Monitoring Cloud Functions entities with IBM Cloud Monitoring](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-monitor-functions).
3. Handle errors programmatically by including the Composer library within the action implementation. By using the library, you can chain together a sequence of actions or define other types of control-flow logic. When you use this library, all execution of the [error-handling code occurs service-side](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_composererror-handling) and there are no additional components that you must manage.
Third-party services that offer paid usage-based pricing plans receive disbursements through an Electronic Funds Transfer (EFT). To set up this method to receive disbursements in IBM Cloud Partner Center Sell, you must submit the EFT form when you set up your first usage-based pricing plan. You can download the form from the Payments to me page.





 When are disbursements sent to me? 

If any disbursements are due to a third-party provider, they are sent on the last business day of the second calendar month. For example, March activity would be paid on the last calendar day of May, unless the last day of the month falls on a weekend or holiday. In this case, disbursements are sent on the next business day. Disbursements are calculated from beginning of the month to the end of the month.





 What is the fee structure? 

Disbursements are paid against revenue recognized by IBM® in a royalty month. IBM pays a third-party provider for each sale of a product as follows:



* As-a-service products: 87% of net revenue
* Software products: 80% of net revenue







 Can a third-party provider run activity reports and payout reconciliations? 

We are adding features to support reports in the near future. Disbursements are based on the quantities that you submit to the usage metering service and the price that is defined when you set up your pricing plan in Partner Center. Third-party disbursements are calculated as a percentage of the net revenue for each product sold by IBM for a given calendar month. Net revenue is defined as the revenue recognized by IBM or an IBM affiliate calculated using applicable discounts, refunds, returns, offsets, and other adjustments determined in accordance with the current revenue recognition policies of IBM and its affiliates and the controlling accounting principles. For full detail regarding payouts, refer to the Digital Platform Reseller Agreement that must be signed in Partner Center to offer usage-based pricing.





 How can I generate a new IBM Cloud Identity and Access Management API Key? 

You're given your API Key when you enable IAM. It is critical that you save the API Key. The value is not shown again.
To use IBM Quantum systems, you need to upgrade to an IBM pay-as-you-go cloud account and use the Standard plan.
* Do I get a monthly bill and what does it look like for Qiskit Runtime with IBM Cloud®?

You will receive a monthly invoice that provides details about your resource charges. You can check how much you've spent at any time on the [IBM Cloud Billing and usage page](https://cloud.ibm.com/billing).

You can set up spending notifications to get notified when your account or a particular service reaches a specific spending threshold that you set. For information, see the [IBM Cloud account Type description](https://cloud.ibm.com/docs/account?topic=account-accounts). IBM Cloud® spending notifications trigger only after cost surpasses the specified limit.
* Are there countries from which the Qiskit Runtime service is not available?

Qiskit Runtime (beta) is unavailable from the following countries (as of April 2022): Armenia, Azerbaijan, Belarus, Cambodia, China (including Hong Kong S.A.R. of the PRC), Cuba, Georgia, Iraq, Iran, Kazakhstan, Kyrgyzstan, Laos, Libya, Macao S.A.R. of the PRC, Moldova, Mongolia, Myanmar (Burma), North Korea, Russia, Sudan, Syria, Tajikistan, Turkmenistan, Ukraine, Uzbekistan, Venezuela, Vietnam, and Yemen.
* Currently, two quantum systems are accessible through Qiskit Runtime. Will there be more systems and systems with more qubits available in the future?

Yes. We expect to make more systems available through Qiskit Runtime, including larger systems when available. The price might vary as larger and more capable systems come online.
* How are jobs prioritized, as the available quantum systems are shared among all users in the Qiskit Runtime service?

Jobs are prioritized through a first in first out method.
* Can I choose a specific system from those offered by Qiskit Runtime?

Yes. Qiskit Runtime allows you to specify the system on which your Qiskit program should be run. But it is not necessary to do so.
For client-side entities like mobile apps, websockets are not used. Instead, an API call fetches the current configuration state when a user opens the app, or brings it to the foreground. You can also programmatically call the App Configuration to retrieve the most recent configuration state.
* How to view usage metrics for App Configuration?

View basic historical App Configuration usage metrics on the IBM platform [Billing and Usage dashboard](https://cloud.ibm.com/billing/usage). If you need more sophisticated monitoring, create an IBM Cloud Monitoring instance from the [Observability](https://cloud.ibm.com/observe) section of the IBM Cloud console.
* How to predict App Configuration cost?

The simplest way to estimate cost for any IBM Cloud managed service is to use the [IBM Cloud Cost Estimator tool](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-cost).

Guidelines to help you predict cost in more detail:

The Application Instance cost is a fixed monthly cost. If you delete an App Configuration instance mid-month, the monthly Application Instance charge is pro-rated. To predict month instance cost, you must be aware of the number of App Configuration instances you have and what pricing plan is assigned to each.

See all your existing instances in the IBM Cloud Console Resource List in the Services Section. Determine your plan either by clicking the Resource List row that contains your App Configuration instance to reveal an information slide-out, or go to the instance dashboard and look in the Plan section.

Some App Configuration pricing plans have a monthly Application Instance price and others do not. If the plan you select has an instance price, the price for the instance includes a set number of entity IDs and API calls that are included in the instance price. If you exceed the included allotment, your instance continues to operate normally but you accumulate an overage charge based on the published rate for entity IDs and API calls.

The Active Entity ID cost is based on the number of unique entities that interact with your App Configuration instance during the month. Entities self-identify when an API call is made, and each instance of your application provides a unique entity ID.
* Your IBM Cloud Object Storage bucket must be a regional bucket and must be in the same region as your Cloud Functions namespace. Cross-region and single-site buckets are not supported.
* You must [assign the Notifications Manager](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_auth) role to your Cloud Functions namespace for your IBM Cloud Object Storage.







 1. Assigning the Notifications Manager role to your Cloud Functions namespace 

Before you can create a trigger to listen for bucket change events, you must assign the Notifications Manager role to your Cloud Functions namespace. As a Notifications Manager, Cloud Functions can view, modify, and delete notifications for a Cloud Object Storage bucket. You can assign the Notifications Manager role from either the console or the CLI. Once assigned, the Notifications Manager role cannot be removed from your Cloud Functions namespace. Removing the role disables the trigger.

Only account administrators can assign the Notifications Manager role.

What happens when I assign the Notifications Manager role?
: When you assign the Notifications Manager role to your Cloud Functions namespace, you can then create triggers for any regional buckets in your IBM Cloud Object Storage instance that are in the same region as your Cloud Functions namespace.
: You can assign the Notifications Manager role to all instances of Cloud Functions for all instances IBM Cloud Object Storage, but you can only create triggers for regional buckets that are in the same supported regions as your Cloud Functions namespaces.



 Assigning the Notifications Manager role with the console 



1. Navigate to the Grant a Service Authorization page in the [IAM dashboard](https://cloud.ibm.com/iam/authorizations/grant).
2. From Source service, select Functions. Then, from Source service instance, select a Cloud Functions namespace. Note: Only IAM-enabled namespaces are supported.
3. In Target service, select Cloud Object Storage, then from Target service instance, select your IBM Cloud Object Storage instance.
4. Assign the Notifications Manager role and click Authorize.
** [Preview the IBM Blockchain Platform at no charge](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-free) for 30 days when you link your IBM Blockchain Platform service instance to an IBM Cloud Kubernetes free cluster. Performance is limited by throughput, storage and functionality. IBM Cloud will delete your Kubernetes cluster after 30 days and you cannot migrate any nodes or data from a free cluster to a paid cluster.

Your actual costs will vary depending on additional factors such as transaction rate, the number of channels you require, the payload size on the transactions, and the maximum number of concurrent transactions. The pricing examples above are based on an IBM Cloud Kubernetes single-zone cluster only. If you chose a multi-zone cluster, there are extra fees for the additional zones and the required multi-zone load balancer. IBM Cloud IP allocation charges are not included and considered negligible.

There is no limit to the number of service instances that you can provision and associate to a single Kubernetes cluster. But you need to ensure that adequate resources are available by monitoring the CPU, memory, and storage usage to avoid disruption of service. The IBM Blockchain Platform nodes do not have to be in their own cluster. You can have other IBM Cloud services running in the same cluster that your blockchain components are running in, but again you need to ensure that you have adequate compute and storage to address all the requirements of all service instances.

Interested in more pricing examples? See the Reference topic on [Detailed pricing scenarios](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-detailed-pricing) for additional configurations and prices.

Ready to get started? Check out [Getting started with IBM Blockchain Platform](https://cloud.ibm.com/docs/blockchain?topic=blockchain-get-started-ibp) to see the options.





 Default resource allocations 

The values in the following table are useful to estimate the hourly cost of your custom network based on CPU, compute, and storage.