vania-janet/multiturn-rag-retrieval-data huggingface dataset:
How can I add IBM services to my app, such as Watson? 

See [Adding services to apps](https://cloud.ibm.com/docs/containers?topic=containers-service-bindingadding_app).







 Planning highly available deployments 

The more widely you distribute your setup across multiple worker nodes and clusters, the less likely your users are to experience downtime with your app.

Review the following potential app setups that are ordered with increasing degrees of availability.

Zoom

![Stages of high availability for an app](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/cs_app_ha_roadmap-mz.png)

Figure 1. Stages of high availability for an app



1. A deployment with n+2 pods that are managed by a replica set in a single node in a single zone cluster.
2. A deployment with n+2 pods that are managed by a replica set and spread across multiple nodes (anti-affinity) in a single zone cluster.
3. A deployment with n+2 pods that are managed by a replica set and spread across multiple nodes (anti-affinity) in a multizone cluster across zones.



You can also [connect multiple clusters in different regions with a global load balancer](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmultiple-clusters-glb) to increase the high availability.



 How can I increase the availability of my app? 

Consider the following options to increase availability of your app.

Use deployments and replica sets to deploy your app and its dependencies
: A deployment is a Kubernetes resource that you can use to declare all the components of your app and its dependencies. With deployments, you don't have to write down all the steps and instead can focus on your app. When you deploy more than one pod, a replica set is automatically created for your deployments that monitors the pods and assures that the specified number of pods is up and running.
In a couple of scenarios a host (bare metal or VM) might lose connection to the storage briefly and as a result, the host considers that storage read-only to avoid data corruption. Most of the time the loss of connectivity is network-related but the status of the storage remains read-only from the host's perspective even when the network connection is restored. A restart of the host solves the read-only state issue.

This issue can be observed with hosts that have incorrect MPIO settings. When MPIO is not configured correctly, the host loses connection to the storage, and might not be able to reconnect to the storage when the connectivity issue is resolved.
* Can I attach the Block Storage for Classic with a single path? Do I need to use multipath?

It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service. For more information about configuring MPIO connections, see the following articles.



* [Mounting LUNs on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux)
* [Mapping LUNS on Microsoft® Windows®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingWindows)



* How can I configure and validate multipath connections to the Block Storage for Classic volume?

If MPIO is configured right, then when an unplanned disruption or a planned maintenance occurs, and one of the routes is taken down, the host can still access the attached storage through the second path. For more information about the MPIO settings, see the following articles.



* [Mounting LUNs on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux)
* [Verifying MPIO on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxverifyMPIOLinux)
You can select the assistant as the data source, and then filter the metrics by the appropriate dates to see only log data that was generated by the assistant while it was using the skill version.





 Show deployment IDs explained 

Applications that use the older v1 runtime API must specify a deployment ID in each messages sent using the /message API. This ID identifies the deployed app that the call was made from. The Analytics page can use this deployment ID to retrieve and display logs that are associated with a specific live application.

For assistants or custom apps that use the v2 version of the API, your assistant automatically includes an assistant ID with each /message call, so you can choose a data source by assistant name instead of using a deployment ID.

To add the deployment ID, v1 API users include the deployment property inside the metadata of the [context](https://cloud.ibm.com/apidocs/assistant/assistant-v1?curl=message), as in this example:

"context" : {
"metadata" : {
"deployment": "HelpDesk-Production"
}
}

![Premium plan only](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/premium0.png) For premium Watson Assistant instances that use the v1 API and specify a deployment ID with each /message call, you can ask IBM to configure your instances to allow you to access log data from deployed applications across different instances. (If your instances use the v2 API, you cannot get log data from across different instances.)

If log sharing is enabled, only someone with Manager service access to the current instance can view logs. The person can view logs from all of the instances that are being shared. Logs from across all of the participating instances are displayed, regardless of the current user's service level access to the other instances. Similarly, when someone with Manager service access to an instance sends a GET request to the v1 /logs API endpoint, logs from all instances that participate in log sharing are returned, regardless of the user's service level access to each instance.
* [Secrets](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appssecret) to set container environment variables.
* [Persistent volumes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appspv) that are mounted to the container for storage.







 How can I add IBM services to my app, such as Watson? 

See [Adding services to apps](https://cloud.ibm.com/docs/openshift?topic=openshift-service-bindingadding_app).







 Planning highly available deployments 

The more widely you distribute your setup across multiple worker nodes and clusters, the less likely your users are to experience downtime with your app.

Review the following potential app setups that are ordered with increasing degrees of availability.

Zoom

![Stages of high availability for an app](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/cs_app_ha_roadmap-mz.png)

Figure 1. Stages of high availability for an app



1. A deployment with n+2 pods that are managed by a replica set in a single node in a single zone cluster.
2. A deployment with n+2 pods that are managed by a replica set and spread across multiple nodes (anti-affinity) in a single zone cluster.
3. A deployment with n+2 pods that are managed by a replica set and spread across multiple nodes (anti-affinity) in a multizone cluster across zones.



You can also [connect multiple clusters in different regions with a global load balancer](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmultiple-clusters-glb) to increase the high availability.



 How can I increase the availability of my app? 

Consider the following options to increase availability of your app.
],
"final": true
}
]
}
Show more







 Low latency 

The low_latency parameter is available for most next-generation models. The parameter is not available with previous-generation models.

The next-generation multimedia and telephony models have generally faster response times than the previous-generation models. But there might be cases where you want to receive results even more quickly. With next-generation models that support low latency, you can set the low_latency parameter to true to receive results more quickly. For more information about the next-generation models that support low latency, see [Supported next-generation language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ngmodels-ng-supported).

With low latency, the service achieves faster results at the possible expense of transcription accuracy. When low latency is enabled, the service segments the audio into smaller chunks to optimize for speed over accuracy. This trade-off might be acceptable if your application needs lower response time more than it does the highest possible accuracy. For example, low latency is ideal for use cases such as closed captioning, conversational applications, and live customer service in the voice channel of the IBM Watson® Assistant service.

Omitting the low_latency parameter can produce more accurate results and is the recommended approach for most use cases. The low_latency parameter is false by default.

The nature of the response to a request that includes low latency depends on the interface that is used:



* With the HTTP interfaces, the service waits for all of the audio to arrive before sending a response. It then sends a single stream of bytes in response. The response can include multiple transcription elements with multiple final results, and it can be sent incrementally. But it is a single stream of data.
* With the WebSocket interface, the service sends final results as they become available. It can send multiple independent responses in the form of different streams of bytes.
Assessing your database compatibility 

IBM Database Conversion Workbench (DCW) is a no-charge plug-in that adds database migration capabilities to IBM Data Studio. You can download both Data Studio and Database Conversion Workbench from the web console.

To assess the compatibility of your database with Db2 and convert the SQL, you can also use the free, light-weight tool called [IBM Database Harmony Profiler](https://community.ibm.com/community/user/hybriddatamanagement/blogs/jordan-hodges1/2020/01/15/introducing-database-harmony-profiler).

For more information about the Database Conversion Workbench and Database Harmony Profiler, see: [IBM Database Conversion Workbench (DCW)](https://www.ibm.com/support/knowledgecenter/en/SSFMBX/com.ibm.swg.im.dashdb.apdv.porting.doc/doc/c_compat_dcw.html).
Assessing your database compatibility 

IBM Database Conversion Workbench (DCW) is a no-charge plug-in that adds database migration capabilities to IBM Data Studio. You can download both Data Studio and Database Conversion Workbench from the web console.

To assess the compatibility of your database with Db2 and convert the SQL, you can also use the free, light-weight tool called [IBM Database Harmony Profiler](https://community.ibm.com/community/user/hybriddatamanagement/blogs/jordan-hodges1/2020/01/15/introducing-database-harmony-profiler).

For more information about the Database Conversion Workbench and Database Harmony Profiler, see: [IBM Database Conversion Workbench (DCW)](https://www.ibm.com/support/knowledgecenter/en/SS6NHC/com.ibm.swg.im.dashdb.apdv.porting.doc/doc/c_compat_dcw.html).
Most of the time the loss of connectivity is network-related but the status of the storage remains read-only from the host's perspective even when the network connection is restored. A restart of the host solves the read-only state issue.

This issue can be observed with hosts that have incorrect MPIO settings. When MPIO is not configured correctly, the host loses connection to the storage, and might not be able to reconnect to the storage when the connectivity issue is resolved.





 Can I attach the Block Storage for Classic with a single path? Do I need to use multipath? 

It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service. For more information about configuring MPIO connections, see the following articles.



* [Mounting LUNs on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux)
* [Mapping LUNS on Microsoft® Windows®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingWindows)







 How can I configure and validate multipath connections to the Block Storage for Classic volume? 

If MPIO is configured right, then when an unplanned disruption or a planned maintenance occurs, and one of the routes is taken down, the host can still access the attached storage through the second path. For more information about the MPIO settings, see the following articles.



* [Mounting LUNs on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux)
* [Verifying MPIO on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxverifyMPIOLinux)
* [Mapping LUNS on Microsoft® Windows®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingWindows)
Publishing APIs created with IBM App Connect Professional in IBM API Connect 

With this tutorial, you can publish and manage REST APIs that you create with IBM App Connect Professional with IBM® API Connect for IBM Cloud®.



 Prerequisites 

You need valid accounts for IBM App Connect Professional on Cloud and for API Connect to complete this tutorial. Ensure that your REST API file conforms to version 2.0 of the OpenAPI specification. The format of the file can be JSON or YAML.

You can use IBM App Connect Professional to create REST APIs, which are specialized applications that can be used to expose integrations as a RESTful web service and can be called by HTTP clients. After you create the APIs, you can publish and manage them by using API Connect. The following list contains a few advantages of managing your APIs in API Connect:



* You can monitor the number of calls to your API.
* You can control the number of calls to your API.
* You can maintain multiple versions of an API.



For more benefits, see [Managing APIs](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-managing_apis). To create a REST API in IBM App Connect Professional and publish it to API Connect, complete the following steps:



1. Create the REST API by using IBM App Connect Professional.



1. Log in to the [App Connect Professional Web Management Console](https://www.ibm.com/cloud/app-connect) with your IBMid. For more information about how to complete the tasks for creating a REST API with IBM App Connect Professional Web Management Console, see [About management console settings](https://www.ibm.com/support/knowledgecenter/SS3LC4_7.5.2.0/com.ibm.wci.appliance.doc/About_the_WMC/consoleSettings.html) in the IBM Knowledge Center.
2. Select the Production tab, if it is not already selected.
3. Select Repository > Configurations in the navigation list.
4. Project Configurations screen, select the project that you are publishing to API Connect.
For the shipping company to work with global partners, the routing and scheduling systems required local modifications to fit each region’s language, regulations, and unique port logistics. Red Hat OpenShift on IBM Cloud offers global coverage in multiple regions, including North America, Europe, Asia, and Australia so that the apps reflected the needs of its partners, in each country.

IoT devices stream data that IBM® Event Streams for IBM Cloud® distributes to the regional port apps and associated Customs and Container manifest data stores. IBM® Event Streams for IBM Cloud® is landing point for IoT events. It distributes the events based on the managed connectivity that the Watson IoT Platform offers to IBM® Event Streams for IBM Cloud®.

After events are in IBM® Event Streams for IBM Cloud®, they're persisted for immediate use in port transit apps and for any point in the future. Apps that require the lowest latency directly consume in real time from the event stream (IBM® Event Streams for IBM Cloud®). Other future apps, such as analytics tools, can choose to consume in a batch mode from the event store with IBM Cloud® Object Storage.

Since shipping data is shared with the customers of the company, the Developers ensure that the customers can use APIs to surface shipping data in their own apps. Examples of those apps are mobile tracking apps or web e-commerce solutions. The Developers are also busy with building and maintaining the regional port apps that gather and disseminate the customs records and shipping manifests. In short, they need to focus on coding instead of managing the infrastructure. Thus, they chose Red Hat OpenShift on IBM Cloud because IBM simplifies infrastructure management.



* Managing Kubernetes master, IaaS, and operational components, such as Ingress and storage
* Monitoring health and recovery for worker nodes
* Providing global compute, so Developers aren't responsible for infrastructure in several regions where they need workloads and data to reside



To achieve global availability, the Development, Test, and Production systems were deployed across the globe in several data centers. For HA, they use a combination of multiple clusters in different geographic regions as well as multizone clusters. They can easily deploy the port app to meet business needs.



* In Frankfort clusters to comply with the local European regulations
* Ensure that you familiarize yourself with the VMware considerations and limitations for vCenter backup and restore.







 Summary 

With proper planning, you can ensure that your VMware instance can suffer the loss of its management components and recover successfully. Ensure to regularly monitor the success of your backup jobs and availability of your backup data. Ensure to test your backup and restore plan regularly, for both your management infrastructure and your workloads.





 Related links 



* [Overview of VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_overview)
* [Design overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-design_overview)
* [Scaling capacity](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_scaling)
For more information, see [Supported IBM Cloud locations](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).





 Is my location setup highly available? 

The IBM Cloud Satellite service architecture and infrastructure is designed to ensure reliability, low processing latency, and a maximum uptime of the service. By default, every location is managed by a highly available Satellite control plane that consists of a control plane master and worker nodes. For an overview of potential points of failures and your options to increase the availability of your location and control plane, see [High availability for IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-ha).





 What happens if my Satellite control plane becomes unavailable? 

Every location is securely connected to the IBM Cloud multizone region that manages your location by using the Satellite Link component. The link component runs in your control plane and is the main gateway for any communication between your Satellite location and IBM Cloud. If your Satellite location cannot communicate with the IBM Cloud multizone region anymore, your existing location workloads will continue to run, but you cannot make any configuration changes or roll out updates to the services and apps that run in your location.

For an overview of your options to make the Satellite control plane more highly available to prevent connectivity issues with your IBM Cloud multizone region, see [High availability for IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-ha).





 Does IBM support third-party and open source tools that I use with Satellite? 

See the [IBM open source and third-party policy](https://www.ibm.com/support/pages/node/737271).





 Why can't I install extra software like vulnerability scanning tools on my host? 

To add your own server as a host in your Satellite location, the host must meet certain [compute, storage, networking, and system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). These requirements specify the Red Hat software packages that must be installed on the Red Hat Enterprise Linux hosts.
However, IBM is offering promotional licensing at no cost for three months for three reusable concurrent migration licenses.
* What is the promotional license?

The promotional license is valid only for per-account and first-time users of the RMM server. After the three-month period, you need to purchase the license directly from RackWare.
* How does the reusable concurrent license work?

IBM and RackWare have put together a special license model. Typically, a license is a one-time use for each server migration. Whereas for IBM purposes, after a completed migration, the license can be reused for a different server migration. The original host that the license was assigned to just needs to be deleted from the RMM server database.

The number of concurrent migrations that can occur is limited up to the number of licenses procured.
* How do I obtain and activate my promotional license?

You can retrieve the promotional license through the discovery script that is part of the RMM software appliance. For more information on how to use the script, see [Bare metal to virtual server migration on a private network with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-pv-migration-private-network).
* What are the considerations or limitations for the physical to virtual migration?

For more information on considerations and limitations of the physical to virtual migration, see [Bare metal to virtual server migration overview](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-pv-migration-overview).
* Is the migration intrusive?

In most cases, the migration is not intrusive. The migration can be done when the server is up and running. The source server does need some free space to do an image capture of the server. In addition, RMM does require SSH (port 22) reachability to both server and target to perform the migration. The CPU consumption for image capture and copying to the target is minimal.
* Can RackWare RMM create the target virtual server instance?

Yes. With RMM Auto-Provision feature, you can create the target virtual server instance.
Emissions from key greenhouse gases are measured in metric tons of carbon dioxide-equivalent (kgCO2e). You can view your account's emissions data in the IBM Cloud console. Go to Manage > Billing and Usage > Carbon Calculator to view the following widgets:



* Total emissions: The total emissions are calculated by comparing the energy-related usage with data center energy sources. You can download the total emissions data in CSV format.
* Emissions by location: The energy consumption is calculated by using usage units such as CPU. Two or more resources are required to display the location data. The size represents how much energy is generated and the color represents the carbon intensity that is the emission rate for grams of carbon dioxide-equivalent emissions that are released per unit of energy produced.
* Emissions by service: The carbon emissions are broken down by service.
* Emissions by resource group: The carbon emissions are broken down by group. Most services are displayed by resource group. However, Cloud Foundry is displayed by organization, and Classic Infrastructure is displayed in a dedicated group. The emissions are displayed only if a group contains those services.



You must be assigned the viewer or higher role on the billing service to view and export the emissions data for the entire account. An account or billing administrator role is required to grant other users access to the Billing service. For more information about assigning access, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services&interface=apibilling-acct-mgmt-api).