vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The following diagram demonstrates where the LoopBack application, API, and Product are deployed to after they are published from the developer toolkit CLI or UI.

![Diagram to show what is contained within a LoopBack project](images/loopback_project.png "A LoopBack project)



* IBM Cloud run time: The LoopBack app is deployed to the IBM Cloud run time of your choice.
* Gateway: The API is deployed to the gateway.



API Manager: The product is deployed to the API Manager where you can specify how it is used.

![Diagram showing where the LoopBack app, API, and product are deployed](images/Deployed.png" "LoopBack app, API, and product)

For more information about the tasks that are required to create APIs, see [Creating APIs](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-creating_apis).





 API management overview 

After a Product is staged and published, you can open the API Manager to manage security, rate limits, policies, and billing information, and then publish the Product to a Developer Portal.

As displayed in the following diagram, a Product contains a plan, which contains one or more APIs.

![Diagram showing what is contained in a Product](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/Product.png)



 Plans 

To make an API available to a customer, it must be included in a Plan. Plans are used to differentiate between different offerings. Plans can share APIs, but whether subscription approval is required depends upon the Plan itself. Additionally, you can enforce rate limits through Plans or through operations within a Plan's APIs that override the Plan's rate limit.

Plans can also specify billing costs for customers who use your Products. For example, you can define three different Plans for a single Product. Each Plan can have a different subscription cost and a different rate limit that targets different customers.





 Products 

Plans and APIs are grouped in Products.
Since 16 July 2018, new instances are provisioned into resource groups rather than Cloud Foundry spaces. Resource instances created before this date have an associated Cloud Foundry organization and space. Instances created after this date are associated with a resource group instead.
* Why can't I create new Standard plan instances on my Dedicated Hardware instances?

New Standard plan instances are provisioned into resource groups. In order to create these instances onto a Dedicated Hardware instance, the Dedicated Hardware instance must first be migrated into a resource group.

For more information about how to do this migration, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).

Once the Dedicated Hardware instance is migrated to a resource group, it appears in the Location drop-down menu when you create Standard plans.
* How can I migrate my Dedicated Hardware instances and the Standard plan instances that are hosted on them?

In theory, instances can be migrated to resource groups in any order. The following order for Dedicated Hardware instances and the Standard plan instances that are hosted on them is recommended:



1. Migrate Dedicated Hardware instances to a resource group. This migration allows new Standard plan instances to be created on the Dedicated Hardware.
2. Migrate Standard instances.



Lite plan instances and Standard plan instances that are not hosted on Dedicated Hardware can be migrated at any time.



Databases For MySQL



* Backing up Databases for MySQL FAQ

 Backing up Databases for MySQL FAQ 

Backups for Databases for MySQL deployments are accessible from the Backups tab of your deployment's dashboard.



MySQL version 8.0.29 contained a design flaw that can cause data corruption for tables with INSTANT ADD/DROP COLUMNS. The issues in MySQL 8.0.29 make this version unsafe to take backups. If Xtrabackup detects tables with instant add/drop columns, you see an error message like this:

[ERROR] [MY-011825] [Xtrabackup] Tables found:
Review the following differences between the installation profiles of version 1.5 of the managed IBM Cloud Kubernetes Service Istio and version 1.5 of the community Istio.

To see options for changing settings in the managed version of Istio, see [Customizing the version 1.5 Istio installation](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize).



Table 1. Differences between the managed IBM Cloud Kubernetes Service Istio and the community Istio

 Setting Differences in the managed Istio add-on 

 egressGateways[name: istio-egressgateway].enabled: true In the managed Istio add-on, the egress gateway is enabled by default. 
 istiod, istio-ingressgateway, and istio-egressgateway In the managed Istio add-on, istiod and all Istio ingress and egress gateways are set up for basic high availability support. High availability support on these components includes the following settings by default: node anti-affinity, HorizontalPodAutoscaler, PodDisruptionBudget, and automatic scaling of replicas. 
 prometheus.enabled: false In the managed Istio add-on, the Prometheus, Grafana, Jaeger, and Kiali monitoring components are disabled by default due to current security concerns in the community release of Istio that can't be adequately addressed for a production environment. 
 values.global.pilot.enableProtocolSniffingForInbound and values.global.pilot.enableProtocolSniffingForOutbound In the managed Istio add-on, protocol sniffing is disabled by default until the feature becomes more stable in the community Istio. 







 Change log for 1.5.10, released 1 September 2020 

Review the changes that are in version 1.5.10 of the managed Istio add-on.

Previous version
: 1.5.9

Current version
: 1.5.10

Updates in this version
Licensing 

Specify the licensing options for the VMware® components in the instance.



*  VMware vCenter Server® Standard 7.0
*  VMware vSphere® Enterprise Plus 7.0
*  VMware NSX-T 3.2 (Data Center SP Base, Data Center SP Professional, Data Center SP Advanced, or Data Center SP Enterprise Plus)



Small differences exist between NSX-T Data Center and Data Center SP editions. For more information, see [Product offerings for VMware NSX-T Data Center 3.2.x](https://kb.vmware.com/s/article/86095).

For Business Partner users, the vCenter Server license (Standard edition), the vSphere license (Enterprise Plus edition), and the VMware NSX® license are included and purchased on your behalf. You need to specify only the edition for the NSX license.

For users who are not Business Partners, use the IBM-provided VMware licenses for these components, which are included with purchase.

Bring Your Own License (BYOL) is no longer supported except for migrations or upgrades of existing BYOL clusters. Select I will provide and enter your own license key only if you are performing an upgrade or migration of an existing BYOL cluster.



  Related links 



*  [Consolidated cluster](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-cluster)
*  [Procedure to order vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure)
: All istio-monitoring support is deprecated in version 1.7 of the Istio add-on and is automatically removed in version 1.8 of the Istio add-on. To use monitoring with Istio, you must install the components separately from the Istio add-on.
: For more information, see the [Istio documentation](https://istio.io/latest/docs/ops/integrations/).
: The istio-ingressgateway-public-(n)-enabled and istio-ingressgateway-zone-(n) options in the [managed-istio-custom ConfigMap resource](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize) are generally available for production use.







 Version 1.6 (unsupported) 

Version 1.6 of the managed Istio add-on is unsupported. (: deprecated)



 Differences between version 1.6 of managed and community Istio 

Review the following differences between the installation profiles of version 1.6 of the managed IBM Cloud Kubernetes Service Istio and version 1.6 of the community Istio.

To see options for changing settings in the managed version of Istio, see [Customizing the Istio installation](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize).



Table 1. Differences between the managed IBM Cloud Kubernetes Service Istio and the community Istio

 Setting Differences in the managed Istio add-on 

 meshConfig.enablePrometheusMerge=true and values.telemetry.v2.enabled=true In the managed Istio add-on, support for telemetry with IBM Cloud Monitoring is enabled by default. This support can be disabled by [customizing the Istio installation](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize). 
 istio-ingressgateway and istio-egressgateway In the managed Istio add-on, placement of gateways on edge worker nodes is preferred, but not required.
At that time, any IBM Cloud Foundry application runtime instances running IBM Cloud Foundry applications will be permanently disabled, deprovisioned, and deleted. For more information about the deprecation, see [Deprecation of IBM Cloud Foundry](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).

To continue to use your IBM Cloud applications beyond 1 June 2023, you must migrate to resource groups before that date. Resource groups are conceptually similar to Cloud Foundry spaces. They include several extra benefits, such as finer-grained access control by using IBM Cloud Identity and Access Management (IAM), the ability to connect service instances to apps and service across different regions, and an easy way to view usage per group. For more information about migration, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).

The service performs no request logging
: The Language Translator service does not log any request data. You cannot opt in to request logging at the request level or at the account level.





 18 October 2022 

Most of the following changes were made available earlier. They are now documented.

New translation limits for Advanced and Premium plans
: The translation limits for service instances on the Advanced and Premium plans have increased. The Translate document method now enforces a document size limit of 50 MB for instances on the Advanced Plan, and 150 MB for instances on the Premium plan. The size limits for the Lite and Standard plans remain 2 MB and 20 MB respectively. For more information, see [Before you begin](https://cloud.ibm.com/docs/language-translator?topic=language-translator-document-translator-tutorialtranslate-prerequisites) in the topic Translating documents.

New support for additional subtitle file formats
: The service now supports additional subtitle formats:



* Apple® iTunes® Timed Text (.itt files)
* Distribution Format Exchange Profile (.dxfp and .xml files)
* Source Code Control (.scc files)
* Synchronized Accessible Media Interchange (.sami and .smi files)
For more information, see [Storage tiers](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-serverstorage-tiers).

If you previously deployed a VM on an old storage type (SSD or standard), no action is required. Your VM continues to run by using the old storage type. You can also add new disks from those legacy tiers.

The boot image storage type is predefined and cannot be chosen.





 How do I extend my AIX rootvg? 

By default, the system deploys 20 GBs for the AIX rootvg. You can extend the AIX rootvg by using the [extendvg](https://www.ibm.com/support/knowledgecenter/ssw_aix_72/e_commands/extendvg.html) command to add a physical volume.





 What's the difference between capped and uncapped shared processor performance? How do they compare to dedicated processor performance? 

When deploying a VM, customers can choose between dedicated, capped shared, or uncapped shared processors for their virtual CPUs (vCPUs). The following list provides a simplified breakdown of their differences:



* Dedicated: resources are allocated for a specific client (used for specific third-party considerations)
* Uncapped shared: shared among other clients
* Capped shared: shared, but resources do not expand beyond those that are requested (used mostly for licensing)



There is a core-to-vCPU ratio of 1:1. For shared processors, fractional cores round up to the nearest whole number. For example, 1.25 cores equals 2 vCPUs.
Clients are responsible for third-party licensing.
* What are the hardware specifications?

For more information, see [Hardware specifications](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-serverhardware-specifications).
* Do Power Systems Virtual Servers run in a multi-tenant environment?

Yes, Power Systems Virtual Server run in a multi-tenant environment.
* Are there bare-metal options?

There are no bare-metal options. The Power Systems Virtual Server offering focuses on virtual instances.
* Can you tell me more about the snapshotting, cloning, and restoring capabilities?

Power Systems Virtual Server provides the capability to capture full, point-in-time copies of entire logical volumes or data sets. Using IBM's FlashCopy feature, the [Power Systems Virtual Server API](https://cloud.ibm.com/apidocs/power-cloudintroduction) lets you create delta snapshots, volume clones, and restore your disks. To learn more, see [Snapshotting, cloning, and restoring](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-volume-snapshot-clone).
* What are the key differences between a snapshot and clone?

The key differences are as follows:



 Context Snapshot Clone 

 Definion A snapshot is a thin-provisioned group of volumes that cannot be attached to a host or accessed/manipulated. A clone is created from a snapshot and results in independent volumes which surface in the GUI and can be attached to hosts. 
 Primary function Revert or restore the source disks to a desired state Create a complete volume clone 
 Ease of creation Easy and quick process Three-step process and takes long time 
 Pricing Charged 30% of the regular storage rate target volume storage plus the GRS costs 



See [Snapshots, cloning, and restoring](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-volume-snapshot-clonevolume-snapshot-clone) for more detailed information.
* Is there any UI to perform snapshot or clone operations?

None.
Writing to databases 

You can specify database locations either by CRN URIs or by Db2 table URIs. Which one you choose depends on the target database plan and the access you have to that database. The number of parallel Db2 connections affects performance. The more parallel connections there are, the better the performance gets, depending on the allowed connections to Db2 and the current free resources of Data Engine. Check how many connections your [Db2 plan](https://cloud.ibm.com/catalog/services/db2) allows.



 CRN URI location 

If the Db2 on Cloud instance is in an IBM Cloud® account that is accessible to the SQL user, and if the SQL user can see the credentials for that instance (requires the Operator privilege), the user can specify the database location by using its instance CRN. The access to the database is performed with the username and password that is found in the service credentials for this Db2 instance. Newly created Db2 instances don't have any service credentials; to create them, select the instance in the IBM Cloud console and choose Service credentials > New credential.

You can optionally override the username and password in the credentials with a custom user and password or a custom API key. Store the password or key into IBM® Key Protect for IBM Cloud® and specify an [access secret clause](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referenceaccessSecrets) in your query. For more information, see the [security documentation](https://cloud.ibm.com/docs/sql-query?topic=sql-query-authentication).

This option is typically used with Db2 Lite plans, which provide restricted access for a single user in a shared database. It can also be used with Standard plans, but the service credentials for Standard plans always allow full administrator access. If the SQL user has only restricted access to the target database, use the subsequent "Db2 table URI location" option.

The CRN table has the form:

<db service crn>/<table name>

You retrieve the <db service crn> by opening the resource list in the IBM Cloud dashboard.
FAQs for Direct Link 

You can review answers to some frequently asked questions about IBM Cloud® Direct Link.



 How does the new Direct Link differ from Direct Link on Classic? 

The Direct Link offering differs from Direct Link on Classic in that Direct Link is decoupled from classic IaaS, and exists only in the local cross-connect router (XCR). This design enables native connectivity to VPC and future capabilities without being forced into the classic IaaS network.

Direct Link allows connectivity to both classic IaaS as well as VPCs, whereas IBM Cloud Direct Link on Classic always connects to the IaaS network and a global VRF first. IBM Cloud Direct Link on Classic can only reach the VPC on a limited basis using a feature named Classic Access and by adding global routing to the direct link. See [Setting up access to your Classic Infrastructure from VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure) for more information.

For more information about the differences between the new Direct Link offering and the classic version (Direct Link on Classic), see [How do I know which Direct Link solution to order?](https://cloud.ibm.com/docs/direct-link?topic=direct-link-get-started-with-ibm-cloud-direct-linkget-started-solution-to-order).





 Where can I find Direct Link pricing and what do I pay for? 

See the following FAQs for details.



 Where do I find cost estimates for Direct Link offerings? 

You can estimate the cost of a service using the cost estimator on the provisioning pages for Direct Link offerings. For example, log in to the [IBM Cloud Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link) and click Order Direct Link. Then, choose to order Direct Link Connect or Direct Link Dedicated. As you complete the ordering form, cost estimates appear in the Summary side panel.





 In terms of cost, what do I pay for? 

There are two pricing plans: metered and unmetered. Metered has a port fee and bill per GB egressed across the Direct Link.
Limitations and Exclusions 

Overview of what is excluded from the Managed Services TRIRIGA Application Suite Managed Services - Limitations and Exclusions

TRIRIGA Application Suite Managed Services is implemented using a defined set of technologies and operates within a security profile designed to ensure our client's data is secure and the applications operate efficiently and effectively. As a result of the decisions made regarding technologies and to meet the high security standards, there are differences between what is available using the Managed Services and what a client could do if they hosted and operated the Suite themselves.

The following items are not included or allowed in the TRIRIGA Application Suite Managed Services offering:



  Databases 

Only DB2 is supported. Oracle and SQLServer are not supported. Conversion services are available.





  3rd Party Applications 

TRIRIGA Application Suite Managed Services will not host or support any 3rd party application. 3rd Party applications hosted outside the MS environment can be integrated to applications with the Suite provided they follow standard integration protocols.





  Access 

Clients will not have access to the operating system, file system or overall administration of the Suite. DBAdmin access or direct updating of the database is not allowed.





  TAS Administrator Functions 

Direct access to the clusters is not available. Changes required must be submitted using the ticketing system and then the SRE team will execute.
* Download objects from the bucket
* Synchronize local files to a bucket
* Synchronize objects to another bucket
* Create an archive of a bucket



6. Right-click within the bucket and select Synchronize. A pop-up window opens where you can browse to the folder that you want to synchronize to the bucket. Select the folder and click Choose.
7. After you select the folder, a new pop-up window opens. Here, a drop-down menu is available where you select the synchronization operation with the bucket. Three possible synchronize options are available from the menu:



* Download: This downloads changed and missing objects from the bucket.
* Upload: This uploads changed and missing files to the bucket.
* Mirror: This performs both download and upload operations, ensuring that all new and updated files and objects are synchronized between the local folder and the bucket.









 How Object Storage is different from FTP 

Technically speaking, there are more differences than similarities between FTP and Object Storage. Starting from the convenience of not having to run a server application like ftpd and continuing through the security of using a secure protocol like HTTPS, the list of differences is lengthy and significant.





 Next Steps 

Can FTP provide an [API](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-compatibility-api) or [libraries](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-about)? We think not! Learn more about what is available for [developers](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-gs-dev) of IBM Cloud Object Storage.
FAQs for Knowledge Studio 

FAQs for IBM Watson® Knowledge Studio might include questions about data collection or plans. To find all FAQs for IBM Cloud®, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



 How do I set data collection options? 

For Lite and Standard plans, by default, Knowledge Studio uses client data to improve the service. This data is used only in aggregate. Client data is not shared or made public.

To prevent Knowledge Studio from using client data, you must opt out by using at least one of two ways:



* Clear the Data collection checkbox on the Service Details page in the Knowledge Studio application.
* As the owner of the Knowledge Studio service instance, opt out of all data collection for Watson services at https://cloud.ibm.com/watson/settings.



For Premium plans and Dedicated accounts, Knowledge Studio does not use client data to improve the service.

For more information, see the latest [Knowledge Studio service description](https://www.ibm.com/software/sla/sladb.nsf/searchsaas/?searchview&searchorder=4&searchmax=0&query=Knowledge+Studio).





 Can I deploy custom models across regions? 

Deployment of models across regions is not supported. A custom model can only be deployed to the same region as your Knowledge Studio instance.





 Can I access Knowledge Studio with an API? 

At this time, there is no API to interact with Knowledge Studio. To launch the Knowledge Studio application, you click Launch tool from within the Manage page for the Knowledge Studio service instance in the IBM Cloud console. Or you can copy the tool URL and use it to launch the application directly. For details, see [Launching the Knowledge Studio application](https://cloud.ibm.com/docs/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_tutintrolaunching-the-knowledge-studio-application).





 Can I change from a Standard to Lite plan? 

Downgrading your plan for Knowledge Studio is not supported.