vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: If you see this or similar error messages when working in the tooling, it might mean that your session has expired. Log out by choosing Log out from the User information icon, and then log back in.





 8 December 2017 

Log data access across instances (Premium users only)
: If you are a Watson Assistant Premium user, your premium instances can optionally be configured to allow access to log data from workspaces across your different premium instances.

Copy nodes
: You can now duplicate a node to make a copy of it and its children. This feature is helpful if you build a node with useful logic that you want to reuse elsewhere in your dialog. See [Copying a dialog node](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-tasksdialog-tasks-copy-node) for more information.

Capture groups in pattern entities
: You can identify groups in the regular expression pattern that you define for an entity. Identifying groups is useful if you want to be able to refer to a subsection of the pattern later. For example, your entity might have a regex pattern that captures US phone numbers. If you identify the area code segment of the number pattern as a group, then you can subsequently refer to that group to access just the area code segment of a phone number. See [Defining entities](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-creating-task) for more information.





 6 December 2017 

IBM Cloud® Functions integration (Beta)
: Call IBM Cloud® Functions (formerly IBM OpenWhisk) actions directly from a dialog node. This feature enables you to, for example, call an action to retrieve weather information from within a dialog node, and then condition on the returned information in the dialog response. Currently, you can call an action from a Cloud Functions instance that is hosted in the US South region from Watson Assistant instances that are hosted in the US South region. See [Making programmatic calls from a dialog node](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-actions-client) for more details.





 5 December 2017 

Redesigned UI for Intents and Entities
The following components are ordered and included in the Juniper vSRX service:



 Virtual machines 



* vSRX is deployed as a pair of VMs configured for High Availability.
* Each VM is configured with 6 CPUs, 16 GB of memory, and 16 GB of storage. When installed on a cluster with 25 Gb uplink speed, each VM is configured with 10 CPUs, 16 GB of memory, and 16 GB of storage.







 High availability 

For installations on the management cluster, the two vSRX nodes are deployed with DRS rules. This deployment ensures that the VMs reside on two physically separate hosts and do not migrate, that is, they’re pinned. If a host must be replaced or redeployed, you must adjust the preconfigured DRS rules before you can proceed.





 Networking 

The vSRX appliance can be accessed for administration purposes by either the J-Web console interface or direct ssh access. You can find the IP address information and credentials on the service details page.





 License and fees 

Two license types are offered:



* Standard
* Content Security Bundle



Each license type includes a different set of features and options. The Content Security Bundle license includes all the features and options in the Standard license and extra features, such as:



* AppSecure
* UTM
* SSL Proxy



On 25 Gb uplink speed clusters, only the Content Security Bundle license is available.

For more information about the features and options in each license, see [Choosing a vSRX License](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-startedchoosing-license).

Two licenses of the selected type are ordered, one for each of the appliance nodes.

You cannot change the licensing level after service installation. To change the licensing level, you must delete the existing service and reinstall the service by using a different licensing option.

If you need to extend your license after expiration, you can update your vSRX license key.
: Enter the number of replicas for your data that you want to store across different worker nodes. Allowed numbers are 1,2, or 3. For example, if you enter 3, then your data is replicated across three different worker nodes in your Portworx cluster. To store your data highly available, use a multizone cluster and replicate your data across three worker nodes in different zones. You must have enough worker nodes to fulfill your replication requirement. For example, if you have two worker nodes, but you specify three replicas, then the creation of the PVC with this storage class fails.

parameters.secure
: Specify whether you want to encrypt the data in your volume with IBM Key Protect. Choose between the following options.



* true: Enter true to enable encryption for your Portworx volumes. To encrypt volumes, you must have an IBM Key Protect service instance and a Kubernetes secret that holds your customer root key. For more information about how to set up encryption for Portworx volumes, see [Encrypting your Portworx volumes](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_encryption).
* false: When you enter false, your Portworx volumes are not encrypted. If you don't specify this option, your Portworx volumes are not encrypted by default. You can choose to enable volume encryption in your PVC, even if you disabled encryption in your storage class. The setting that you make in the PVC take precedence over the settings in the storage class.



parameters.priority_io
: Enter the Portworx I/O priority that you want to request for your data. Available options are high, medium, and low. During the setup of your Portworx cluster, every disk is inspected to determine the performance profile of the device. The profile classification depends on the network bandwidth of your worker node and the type of storage device. Disks of SDS worker nodes are classified as high.
Setting up multiregion High Availability (HA) deployments for the ordering service 

In this tutorial, you learn how to set up a Raft ordering service with five ordering nodes that span multiple regions for maximum high availability.

Zoom

![Architectural diagram](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/mr-ha-os.png)

Figure 1. A diagram that shows the architecture of a multiregion ordering service

The diagram shows a multiregion ordering service that includes five ordering nodes that are spread across three Kubernetes clusters in three different regions. For simplicity, this tutorial assumes that all the ordering nodes are contributed by the same organization. The setup requires a single Certificate Authority (CA), created in one cluster and imported into the blockchain consoles on the other two clusters.

Throughout this tutorial we refer to two types of nodes: "ordering nodes" and "worker nodes". Ordering nodes belong to a Raft ordering service cluster. Worker nodes refer to the Kubernetes component that hosts the pods where the ordering nodes are deployed.

After you understand how to spread the ordering nodes across regions, it is possible for separate organizations to contribute ordering nodes and generate certificates by using their own CAs. This advanced configuration is not covered in this tutorial, but you can learn more about it in the [Next steps](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-hadr-mr-osibp-console-hadr-mr-os-next).

Although you cannot choose which worker node an ordering node is deployed to, the console is configured with an anti-affinity policy. This means that for high availability, whenever you deploy a blockchain node on a multi-node cluster, the console attempts to spread ordering nodes that belong to the same organization across the worker nodes if sufficient resources are available. If your cluster is configured with multiple zones, you can designate which zone the ordering node is deployed to when you create it, or you can let the console choose for you.
Messages for RabbitMQ Connection Limits 

At provision, Messages for RabbitMQ has four different endpoints and sets the maximum number of connections per node and for each endpoint as follows:



* HTTPS: 1024 x 3 nodes = 3072
* AMQPS: 20000 x 3 nodes = 60000
* MQTTS: 20000 x 3 nodes = 60000
* STOMPS: 20000 x 3 nodes = 60000



If the number of connections to the database exceeds the connection limit, new connections fail and return an error.





 Monitoring for High-Availability 

Messages for RabbitMQ has [IBM Log Analysis integration](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=cloud-databases-logging) so that you can view live and historical logs.

Checking your deployment's logs helps you monitor the state of HA and replication for your deployment. If you are having persistent issues with your applications, logs can also provide insight to what is happening on your databases when you are experiencing connection failures or other disruptions.



 RabbitMQ Reliability Guide 

The RabbitMQ Documentation provides an excellent [Reliability Guide](https://www.rabbitmq.com/reliability.html) that covers a wide range of topics that are related to making sure that your cluster is functioning and your data is resilient. It also covers features that are available to you as a user to monitor the deployment, connections, queues, and messages to ensure smooth operations.







 High availability, disaster recovery, and SLA resources 

Messages for RabbitMQ deployments conform to the IBM Cloud Databases [HA, DR, and SLA](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-ha-dr) terms.
Getting started with subnets and IPs 

IBM Cloud® offers three types of subnets, with each type providing IP addresses to resources in different ways. A brief description of their capabilities and distinct lifecycles follows.



* Primary subnets - Automatically assigned to meet the IP addressing needs of other services, such as bare metal servers and virtual server instances. These subnets are automatically assigned and removed by IBM Cloud.
* Secondary subnets - Purchased and routed by you, and canceled when no longer needed. There are two routing options:



* Portable - IP addresses are available to all resources on a VLAN.
* Static - IP addresses are available to the resource identified as the routing endpoint.



* Global IP addresses - Unique routing behavior that uses IBM Cloud's backbone, which provides IP addresses to the resource identified as the routing endpoint.



Review each type in detail at [About subnets and IPs](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ips) to learn about aspects such as IPv4 versus IPv6 and public versus private network availability.



 Before you begin 

Ensure you have the "Add/Upgrade Services" permission, which is set through the [IBM Cloud IAM users permissions panel](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra).





 Ordering secondary subnets 

Take the following steps to order a secondary subnet.



1. Determine what [type of secondary subnet](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipssecondary-subnets) you need.
2. [Order](https://cloud.ibm.com/networking/subnets/provision) a secondary subnet. See [Ordering secondary subnets and IPs](https://cloud.ibm.com/docs/subnets?topic=subnets-order-subnets) for details about ordering secondary subnets with different types and routing options.







 Next steps
[Accessing the cluster master with admission controllers and webhooks](https://cloud.ibm.com/docs/openshift?topic=openshift-access_webhooksaccess_webhooks)



* [Can I create my own admission controllers?](https://cloud.ibm.com/docs/openshift?topic=openshift-access_webhooksaccess_webhooks_create_controllers)
* [What are the best practices for using webhooks?](https://cloud.ibm.com/docs/openshift?topic=openshift-access_webhookswebhook-best-practice)
* [What other types of apps use admission controllers?](https://cloud.ibm.com/docs/openshift?topic=openshift-access_webhooksaccess_webhooks-app-use-controllers)
* [I need help with a broken webhook. What can I do?](https://cloud.ibm.com/docs/openshift?topic=openshift-access_webhooksaccess_webhooks-help)



[Accessing private clusters by using the WireGuard VPN](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-access-wireguardcluster-access-wireguard)





 Managing the cluster and worker node lifecycle 

[Adding worker nodes and zones to clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersadd_workers)



* [Adding worker nodes by resizing an existing worker pool](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool)
* [Adding worker nodes in VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersvpc_pools)
5. Compare the infrastructure accounts.



* If the worker nodes are in the linked infrastructure account: Use the ibmcloud oc credential unset[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_credentials_unset) to resume using the default infrastructure credentials that are linked with your Pay-As-You-Go account.
* If the worker nodes are in a different infrastructure account: Use the ibmcloud oc credential set[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_credentials_set) to change your infrastructure credentials to the account that the cluster worker nodes are provisioned in, which you found in the previous step.

If you no longer have access to the infrastructure credentials, you can open an IBM Cloud support case to determine an email address for the administrator of the other infrastructure account. However, IBM Cloud Support can't remove the orphaned cluster for you, and you must contact the administrator of the other account to get the infrastructure credentials.
* If the infrastructure accounts match: Check the rest of the worker nodes in the cluster and see if any are assigned to different infrastructure account. Make sure that you checked the worker nodes in the cluster that have the credentials issue. Review other [common infrastructure credential issues](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errors).



6. Now that the infrastructure credentials are updated, retry the blocked action, such as updating or deleting a worker node, and verify that the action succeeds.
7. If you have other clusters in the same region and resource that require the previous infrastructure credentials, repeat Step 3 to reset the infrastructure credentials to the previous account. Note that if you created clusters with a different infrastructure account than the account that you switch to, you might orphan those clusters.

Tired of switching infrastructure accounts each time you need to perform a cluster or worker action? Consider re-creating all the clusters in the region and resource group in the same infrastructure account.
IBM Watson® Assistant for IBM® Cloud Private version 1.0.0.1 runs on IBM Cloud Private 2.1.0.3
: A revised Helm chart (version 1.0.0.1) was published, which improves the installation process.





 26 September 2018 

IBM Watson® Assistant for IBM® Cloud Private 1 is available
: IBM Watson® Assistant for IBM® Cloud Private version 1 runs on IBM Cloud Private 2.1.0.3.

Introducing the Build tab
: The IBM Watson® Assistant tool includes a Build tab that offers pre-built intents you can add to your workspace from a content catalog, the ability to define your own intents and entities, and has a graphical user interface you can use to build a dialog. The following key features are also available:



* Dialog: Digression and disambiguation support, nodes with slots, rich responses (including Connect to human agent)
* Entities: Contextual entities, system entities for currency, date, number, percentage, and time.
* Intents: Content catalog



Features not included
: These features are not available from IBM® Cloud Private, but are available in the public IBM Cloud instance at the time of this release:



* There are no metrics or analytics capabilities. Therefore, the Improve tab is not included in the tool.
* There are no deployment connectors or built-in integrations available. You must build a custom client application that can host the assistant. As a result, the Deploy tab is not included in the tool.
* You cannot search within the tool.
* The @sys-person and @sys-location system entities are not supported.
* You cannot make programmatic calls to Cloud Functions actions from the dialog.
* No entity synonym recommendations are available.
* No intent conflict detection is available.
This allows you to choose which Watson Assistant algorithm to apply to your future trainings. For more information, see [Algorithm version and training](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-algorithm-version).





 9 August 2022 

New API methods
: The v2 API now supports new Environments and Releases methods:



* Environments: Retrieve information about the environments associated with an assistant.
* Releases: Retrieve information about the releases (versions) that have been published for an assistant, and assign an available release to an environment.



For more information, see the v2 [API Reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2).





 5 August 2022 

Initial value of session variables
: You can now set the initial value of a session variable to an expression. For more information, see [Creating a session variable](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-infocreate-session-variable).

Uploading intents
: If you created intents in the classic Watson Assistant experience, you can migrate your intents to actions in the new Watson Assistant experience. This can provide a helpful starting point when you are ready to start building actions in the new experience. For more information, see [Uploading intents as actions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-upload-download-actionsupload-download-actions-upload-intents).





 19 July 2022 

Changes to publishing and environments
: You can now publish versions of your content without assigning to the live environment, allowing you to make continuous updates before customers see it in production. Also, the formerly separate pages for your draft and live environments now appear as tabs on a single Environments page, from which you can set up unique configurations for building and testing in the draft environment, and for your customers in the live environment. For more information, see the [Publishing overview](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish-overview).

Logs reader role
Next, the Store calls the Dialog microservice to generate the appropriate response to return to the customer. The Store microservice stores the assistants, skills, and workspace definitions in a PostgreSQL database. The Store microservice saves the state of the session (from the v2 API) in the Redis data store.
* TAS: Performs model inferencing, which means it identifies the best-matching intents and entities in the user input. TAS stands for Train and Serve, but it mostly serves up the existing models. The TAS microservice loads the models from MinIO storage into memory and runs the models to find intents. The TAS microservice is called from the NLU microservice by using LiteLinks. TAS and the ED-MM microservices are based on a model-mesh pattern. (For more information, see [Model mesh](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-architecturearchitecture-model-mesh).) If needed, TAS calls other microservices from the language understanding pipeline. Specifically, it calls SireG for tokenization, ED-MM for contextual entities (by using gRPC), and Spellcheck to correct misspellings. For intent recogniton, the TAS microservice requires word-embeddings data, which is provided by the CLU Embedding microservice.
* TF-MM: The tensor flow model mesh microservice manages the universal sentence encoder and auto-encoder models to improve off-topic and irrelevant intent recognition. Introduced with the 1.5.0 release.
* UI: The web application that virtual assistant builders use to create skills and assistants.







 Data sources 

The Watson Assistant microservices use the following resources:



* Elastic: The elastic data store stores customer messages. These user conversation logs that can be reviewed from the Analtyics page or searched from the /logs API endpoint. Introduced with the 1.5.0 release.
* Etcd: A popular distributed key-value storage solution.
v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1updateworkspace)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodeupdateworkspace)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javaupdateworkspace)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythonupdateworkspace) 
 Delete workspace Delete a workspace from the service instance. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1deleteworkspace)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodedeleteworkspace)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javadeleteworkspace)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythondeleteworkspace) 
 List intents List the intents for a workspace. v1 [cURL](https://cloud.ibm.com/apidocs/assistant/assistant-v1listintents)[node](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=nodelistintents)[java](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=javalistintents)[python](https://cloud.ibm.com/apidocs/assistant/assistant-v1?code=pythonlistintents) 
 Create intent Create a new intent.
[checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Import, add (including from content catalog), edit, or delete intents or intent examples ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Export intents ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Manage intent conflicts ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Open and view entities ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![checkmark icon](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) !