vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-faqstopic_admin)
* What is Event Streams's availability behavior?

If you write Event Streams apps, use this information to understand what normal Event Streams availability behavior is and what your apps are expected to handle.



 APIs 

As part of the regular operation of Event Streams, the nodes of the Kafka clusters are occasionally restarted. In some cases, your apps will be aware as the cluster reassigns resources. Write your apps to be resilient to these changes and to be able to reconnect and retry operations.



* What is Event Streams's maximum message size?

Event Streams's maximum message size is 1 MB, which is the Kafka default.
* What are Event Streams's replication settings?

Event Streams is configured to provide strong availability and durability. The following configuration settings apply to all topics and cannot be changed:



* replication.factor = 3
* min.insync.replicas = 2



* What are the restrictions and defaults for topics and partitions?



* Topic names are restricted to a maximum of 100 characters.
* The default number of partitions for a topic is one.
* Each IBM Cloud space has a limit of 100 partitions. To create more partitions, you must use a new IBM Cloud space.



* How do I check which Event Streams plan I've provisioned?

To confirm which type of Event Streams plan you've provisioned (Lite, Standard, or Enterprise), complete the following steps:



1. In the IBM Cloud console, navigate to the instance of Event Streams that you want to check.
2. Click the Plan tab in the navigation pane on the left. The Current plan section displays your plan type.



* Can I change my Event Streams plan using the IBM Cloud console?

Yes, but only if you are moving from the Lite plan to the Standard plan.



1. In the IBM Cloud console, navigate to the instance of Event Streams Lite plan that you want to change.
2. Click the Plan tab in the navigation pane on the left.
IBM Cloud Schematics Workspaces are provided to you at no cost. However, when you decide to apply your Terraform template in IBM Cloud by clicking Apply plan from the workspace details page or running the ibmcloud schematics apply command, you are charged for the IBM Cloud resources that are described in your Terraform template. Review available service plans and pricing information for each resource that you are about to create. Some services come with a limit per IBM Cloud account. If you are about to reach the service limit for your account, the resource is not provisioned until you increase the service quota, or remove existing services first.

The Schematics ibmcloud terraform command usage displays warning and deprecation message as Alias Terraform are deprecated. Use schematics or sch in your command.





 Does IBM Cloud Schematics support multiple Terraform provider versions? 

Yes, IBM Cloud Schematics supports multiple Terraform provider versions. You need to add Terraform provider block with the right provider version. By default the provider run current version 1.21.0, and previous four versions such as 1.20.1, 1.20.0, 1.19.0, 1.18.0 are supported.

Example for a multiple provider configuration:

terraform{
required_providers{
ibm = ">= 1.21.0" // Error !! version unavailable.
ibm = ">= 1.20.0" // Execute against latest version.
ibm = "== 1.20.1" // Executes version v1.20.1.
}
}

Currently, version 1.21.0 is released. For more information, see [provider version](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall_provider).





 How do I generate IAM access token, if client ID bx is used? 

To create IAM access token, use export IBMCLOUD_API_KEY=<ibmcloud_api_key> and run the command.
create a Cloud Object Storage (COS) instance
 "lite" is the pricing plan and "global" is the region
$ COS_NAME=my-cos-1

$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

Creating service instance my-cos-1 in resource group Default of account <account name> as <email address>...
OK
Service instance my-cos-1 was created.
Name: my-cos-1
ID: crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8::
GUID: 4b636e74-f3ca-40bb-80b8-3bd21801ccb8
Location: global
State: active
Type: service_instance
Sub Type:
Allow Cleanup: false
Locked: false
Created at: 2020-06-15T16:03:39Z
Updated at: 2020-06-15T16:03:39Z
Last Operation: Status create succeeded Message Completed create instance operation

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=4b636e74-f3ca-40bb-80b8-3bd21801ccb8

 create a Key Management Service (KMS) service instance
 "tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1

$ ibmcloud resource service-instance-create $KMS_NAME kms tiered-pricing us-south

Creating service instance my-kms-1 in resource group Default of account <account name> as <email address>...
OK
Service instance my-kms-1 was created.
Name: my-kms-1
FAQs - Lite plan 

This is a collection of frequently asked questions (FAQ) about the IBM® Db2® on Cloud Lite plan.



 Will my free plan expire? 

You can continue using the free plan for as long as you need. However, you must reactivate the free plan every 45 days. This reactivation process keeps resources available for other users by turning off inactive usage.

When your plan nears its reactivation date, you will receive a reactivation request at the email address that you provided when creating the instance. Alternatively, you can reactivate in your Db2 on Cloud console.





 Will my data be deleted? 

After you create a Lite instance, you have 45 days before the next reactivation.



* If you do not reactivate, your Lite plan will be disabled, but IBM Cloud still has your data. You will then have 60 days to reactivate your account.
* If you don't reactivate within 60 days, your account and data will be deleted. We will send you multiple emails reminding you to reactivate.



Each time you reactivate, the day counter resets, and you'll have another 45 days before being disabled (and 60 days before deletion).





 How can I download a backup of my data on the Lite plan? 

Here are two simple options for backing up Lite plan data:



* Use Db2 tools like the command line tool (clp) or IBM Data Studio to do an export. You can then import at another time.
* To quickly make a backup, use the Web console, run a query, then download the results to a CSV file.







 Can I change the email I use for reactivation? 

Create a new Lite instance with the email you want to use going forward. If needed, first back up your data, delete your current Lite plan instance to create a new one, then load your data. You cannot change the email address associated with an existing Db2 Lite instance if you have only a Lite account with community support.





 I am having trouble with reactivation. What should I do? 

If you have trouble with reactivation of a Lite plan instance, you can delete that faulty instance and create a new one.
You cannot create new service instances that use the Lite plan type in any location, including London. Use the new Plus plan and its associated 30-day free trial to explore new features and a simpler way to build that is available with the latest version of the product.





 22 September 2022 

Plus plan supports more entity extractors
: The maximum number of entity extractors that you can create with a Plus plan increased from 3 to 6.

You cannot apply a Smart Document Understanding model to Microsoft Excel files
: The quality of structural analysis that can be produced for Excel files is not sufficient. Starting on 22 September 2022, you cannot apply an SDU model to Excel files. This change does not impact Excel files in collections where an SDU model was applied before 22 September 2022.





 16 September 2022 

In-context document preview is now available for PDF files that are crawled
: When you click to view a passage from a search result that is extracted from a PDF document, a document preview page is displayed that shows the returned passage in the context of the original PDF page. The in-context view is available for PDF files to which a Smart Document Understanding model is applied.





 15 August 2022 

SDKs were updated to reflect the latest API changes.
: The following [Discovery v2 API](https://cloud.ibm.com/apidocs/discovery-data) changes are now reflected in the SDKs:



* Use the new document classifier API to get, add, update, or delete a document classifier.
* A new document status API is available. You can use it to get a list of the documents in a collection and to get details about a single document.
* You can now get, add, and remove a stop words or expansion list for a collection.
* A smart_document_understanding field is returned with the Get collection method. This new field specifies whether an SDU model is enabled for the collection and indicates the model type.
* A similar parameter is available from the Query method. Use it to find documents that are similar to documents of interest to you.
* The suggested_refinements parameter of the Query method is deprecated. The suggested_refinements parameter was used to identify dynamic facets from Premium plan data.
Node.js no longer uses nvm to manage different node.js versions. It provides the current LTS version of Node.js at the time that it was built. And it is still based on ubi8 because ubi9 doesn't provide the correct version of openssl.

This image also contains the Terraform CLI.

The IBM Cloud CLI provides code risk analysis commands. You can use the IBM Cloud CLI to analyze your code for vulnerabilities and compliance with certain rules. Code Risk Analyzer is available in all IBM Cloud regions where toolchains are supported. For more information about Code Risk Analyzer, see [Code Risk Analyzer plug-in](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin).

This image includes the following tools:

 node --version
v18.15.0

 npm --version
9.5.0

 jq --version
jq-1.6

 yq --version
yq (https://github.com/mikefarah/yq/) version v4.33.2

 kubectl version --output=yaml --client
clientVersion:
buildDate: "2023-03-15T13:39:54Z"
compiler: gc
gitCommit: 0ce7342c984110dfc93657d64df5dc3b2c0d1fe9
gitTreeState: clean
gitVersion: v1.25.8
goVersion: go1.19.7
major: "1"
minor: "25"
platform: linux/amd64
kustomizeVersion: v4.5.7

 buildctl --version
buildctl github.com/moby/buildkit v0.11.5 252ae63bcf2a9b62777add4838df5a257b86e991

 helm version --client
To check your account type, go to [IBM Cloud](https://cloud.ibm.com/login) and click Management > Account > Account settings.
2. If you have a Lite account and want to use Hyper Protect Crypto Services, [upgrade your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account) to a Pay-As-You-Go or Subscription account. You can also [apply your promo code](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-applying-promo-codes) if you have one.







 Provisioning an instance of Hyper Protect Crypto Services Standard Plan 

You can provision an instance of Hyper Protect Crypto Services Standard Plan from either the IBM Cloud console or CLI.



 Using the IBM Cloud console 

To provision an instance of Hyper Protect Crypto Services Standard Plan from the IBM Cloud console, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).
2. Click Create resource to view the list of services that are available on IBM Cloud.
3. Under Category, select Security.
4. From the list of services displayed, click the Hyper Protect Crypto Services tile.
5. On the service page, select the Standard pricing plan.
6. Fill in the form with the details that are required.



* Under Region, select a [region](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regions) that you want to create your Hyper Protect Crypto Services resources in.

Currently, the us-south and us-east regions are enabled with recovery crypto units by default, which means, when a service instance is provisioned in either regions, you are enabled with the option to back up your master keys in the recovery crypto units located in both regions.
[Architecture Overview of VMware with NSX-T on IBM Cloud VPC](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vpc-ryo-diagrams-aod-nsx-t-based.svg)

Figure 2. Architecture Overview of VMware with NSX-T on IBM Cloud VPC

These two architectures serve as the baseline designs for deploying VMware on IBM Cloud VPC. The deployment architectures provide the foundation for the roll-your-own VMware solution in VPC.

You can alter and customize the architecture to meet your design goals within the limits of IBM Cloud VPC, IBM Cloud bare metal server for IBM Cloud VPC and VMware capabilities.



 Related links 



* [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers)
* [IBM Cloud Direct Link overview](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
* [IBM Cloud Transit Gateway overview](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started)
* [IBM Cloud VPC VPN overview](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-overview)
* [VPC IaaS endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpcinfrastructure-as-a-service-iaas-endpoints)
from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_partition_view(
db='products',
ddoc='appliances',
include_docs=True,
limit=10,
partition_key='small-appliances',
view='byApplianceProdId'
).get_result()

print(response)

postPartitionViewOptions := service.NewPostPartitionViewOptions(
"products",
"small-appliances",
"appliances",
"byApplianceProdId",
)
postPartitionViewOptions.SetIncludeDocs(true)
postPartitionViewOptions.SetLimit(10)

viewResult, response, err := service.PostPartitionView(postPartitionViewOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(viewResult, "", " ")
fmt.Println(string(b))

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.

See the example to retrieve a list of the first 10 documents from a database, applying the user-created getVerifiedEmails view.

Client libraries use POST method instead of GET because they have the same behavior.



* Curl
* Java
* Node
* Python
* Go
Classic Delivery Pipeline overview 

IBM Cloud® Continuous Delivery includes the Classic Delivery Pipeline to build, test, and deploy in a repeatable way with minimal human intervention. In a pipeline, sequences of stages retrieve input and run jobs, such as builds, tests, and deployments.

You can work with both Classic and Tekton delivery pipelines by using the browser, or by using the [IBM Cloud CLI Developer Tools (ibmcloud dev) commands](https://cloud.ibm.com/docs/ContinuousDelivery?topic=cli-idt-cli). You can also work with Tekton delivery pipelines by using the [Tekton pipeline HTTP API and SDKs](https://cloud.ibm.com/apidocs/tekton-pipeline), or by using the [IBM Cloud Terraform Provider](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-terraform-setup). For more information about Tekton delivery pipelines, see [Working with Tekton pipelines](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelinesconfigure_tekton_pipeline).

Your permissions to view, modify, or run a pipeline are based on the access control for the toolchain that owns the pipeline. For more information about access control for toolchains, see [Managing access to toolchains in resource groups](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-toolchains-iam-security).

You can specify the scripts to run in many of the job types that are provided by the pipeline, giving you direct control over what is run by the job. These scripts run in a Docker image that contains a number of standard development tools, including tools that are required for interacting with the IBM Cloud runtimes.
Service plans 

Different pricing plans are available that you can choose for an IBM Log Analysis instance. Each plan defines the number of days that data is retained for search, the number of users allowed to manage the data, and the logging features that are enabled.



Table 1. List of service plans

 Plan Number of days that data is available for search Number of users per plan Plan Name Plan ID 

 HIPAA 30 day log search 30 25 hipaa-30-day a9b3eb07-5096-448b-ba34-53711d74742b 
 30 days log search 30 Unlimited 30-day deda35aa-662b-4b06-9f6e-05e0b55cc577 
 14 days log search 14 Unlimited 14-day 0b3a45e0-def0-4935-8c74-26976f281751 
 7-day log search 7 Unlimited 7-day 209cbd52-f3e2-47cb-94ce-6b84fafcf22b 
 Lite Data is not available for search 1 lite abcf7f02-de22-4c7f-98a1-e8a592093d83 



IBM Log Analysis offers a Lite plan that you can use to view your logs as they pass through the system. You can view logs by using log tailing. You can also design filters to prepare for upgrading to a longer retention period plan. You cannot use an instance on the Lite plan to receive streamed data. This plan has a 0-day retention period.



 Features by plan 

The following tables outline the different features that are included in each service plan:



Table 2. List of features available for each service plan

 Feature HIPAA 30 day log search plan 30 day log search plan 14 days log search plan 7 days log search plan Lite plan 

 Live streaming tail !
[Hardware options for worker nodes in a standard cluster](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/cs_clusters_hardware.png)

Figure 1. Hardware options for worker nodes in a standard cluster



 What flavors are available to me? 

Classic standard clusters can be created on [virtual](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesvm) and [bare metal](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesbm) worker nodes. If you require additional local disks, you can also choose one of the bare metal flavors that are designed for [software-defined storage](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodessds) solutions, such as Portworx. Depending on the level of hardware isolation that you need, virtual worker nodes can be set up as shared or dedicated nodes, whereas bare metal machines are always set up as dedicated nodes. If you create a free classic cluster, your cluster is provisioned with the smallest virtual worker node flavor on shared infrastructure.

VPC clusters can be provisioned as standard clusters on shared [virtual](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesvm) worker nodes only, and must be created in one of the supported [multizone locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-vpc). Free VPC clusters are not supported.

VPC clusters can be provisioned using virtual worker nodes on standard infrastructure or dedicated hosts. Free VPC clusters are not supported.





 Can I combine different flavors in a cluster? 

Yes.
Users might have the following questions when planning to migrate their code to Qiskit Runtime:



* Which channel should I use?

After deciding to use Qiskit Runtime primitives, the user must determine whether to access Qiskit Runtime through IBM Cloud or IBM Quantum Platform. Some information that might help you decide includes:

- The available plans:
- Qiskit Runtime is available in both the Open (free access) or Premium (contract-based paid access) plan on IBM Quantum Platform. See [IBM Quantum access plans](https://www.ibm.com/quantum/access-plans){: external} for details.
- Qiskit Runtime is accessible through the Lite (free access) or Standard (pay-as-you-go access) plan in IBM Cloud. See [Plans](/docs/quantum-computing?topic=quantum-computing-plans) for details.
- The use case requirements:
- IBM Quantum Platform offers a visual circuit composer (Quantum Composer) and a Jupyter Notebook environment (Quantum Lab).
- IBM Cloud offers a cloud native service that is ideal if users need to integrate quantum capabilities with other cloud services.
* How do I set up my channel?

After deciding which channel to use to interact with Qiskit Runtime, you can get set up on either platform using the instructions below:

- To get started with Qiskit Runtime on IBM Quantum Platform, see [Experiment with Qiskit Runtime](https://quantum-computing.ibm.com/services/resources/docs/resources/runtime/start){: external}.
- To get started with Qiskit Runtime on IBM Cloud, see the [Getting Started guide](/docs/quantum-computing?topic=quantum-computing-get-started).
* Should I modify the Qiskit Terra algorithms?

As of v0.22, [Qiskit Terra algorithms](https://github.com/Qiskit/qiskit-terra/tree/main/qiskit/algorithms) use Qiskit Runtime primitives. Thus, there is no need for users to modify amplitude estimators or any other Qiskit Terra algorithms.
For the standard plan, you can configure the quotas. For more information, see [About IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview).



1. Take one of the following actions:



* Delete unused images from the IBM Cloud Container Registry namespace to increase the available space.
* Upgrade from the free plan to the standard plan.
* Increase the quotas of the IBM Cloud Container Registry namespace.



The image URL is included in the error message to help you identify which IBM Cloud Container Registry namespace is affected. The namespace can be in a different IBM Cloud account than your IBM Cloud Code Engine project.
2. After you complete the corrective actions, use the [ibmcloud ce buildrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-buildrun-submit) command to submit a new build run. For the buildrun submit command, you must specify the --build option to provide the name of your build configuration. You can optionally specify the --name option to provide the name for this build run. If you specify the --name option, make sure that you use a different build run name from the failed build run, or ensure that you delete the failed build run by using the [ibmcloud ce buildrun delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-buildrun-delete) command. For example,

ibmcloud ce buildrun submit --build <BUILD_NAME> --name <BUILDRUN_NAME>







 Resolution for build source not specified correctly 

The typical reason that this error occurs is that the build source is not located in the root directory of the Git repository, but in a child directory. If the build source does not reside inside the root directory, then specify the location in the build.



1.