vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you [create a new VPC routing table](https://cloud.ibm.com/apidocs/vpc/latestcreate-vpc-routing-table) or [update an existing VPC routing table](https://cloud.ibm.com/apidocs/vpc/latestupdate-vpc-routing-table), the new route_internet_ingress property lets you route traffic that originates from the public internet. For more information, see [Creating a routing table by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-create-vpc-routing-table&interface=api) and limitations and guidelines for [Ingress routes](https://cloud.ibm.com/docs/vpc?topic=vpc-about-custom-routes&interface=uiroutes-ingress).







 4 October 2022 



 For all version dates 

Enhanced network interface support for flow logs. Flow logs are now collected for all network interfaces attached to a subnet, even if those network interfaces are in another account. As a result, flow logs for network interfaces associated with IBM Cloud Kubernetes Service (IKS)/Red Hat OpenShift Kubernetes Service (ROKS) worker nodes, load balancers, and VPN gateways are now collected. For example, if you have an existing [flow log collector](https://cloud.ibm.com/apidocs/vpc/latestget-flow-log-collector) that targets a VPC or subnet that also has attached IKS worker nodes, it will now collect flow logs for traffic flowing through those IKS worker nodes in those VPCs and subnets. For more information, see [Flow log limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations-flow-logs).







 27 September 2022 



 For all version dates 

Sharing images across accounts within an enterprise.
IA-5 (7) - No Embedded Unencrypted Static Authenticators 



  Control requirements 

IA-5 (7) - 0
:   The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys.





  NIST supplemental guidance 

Organizations exercise caution in determining whether embedded or stored authenticators are in encrypted or unencrypted form. If authenticators are used in the manner stored, then those representations are considered unencrypted authenticators. This is irrespective of whether that representation is perhaps an encrypted version of something else (e.g., a password).
The expiration field shows when the token expires as a UNIX timestamp that specifies the number of seconds since January 1, 1970 (midnight UTC/GMT).

In your application, check the access token's expiration time before you use it to make an authenticated request. If it is expired, you must refresh the access token before you can use it. You use the value of the refresh_token field to refresh the access token. For more information, see [Authenticating to Watson services](https://cloud.ibm.com/docs/watson?topic=watson-iam).







 11 May 2018 

New page for Discovery information security : Details about information security can be found at [Information security](https://cloud.ibm.com/docs/discovery?topic=discovery-information-security).

Fixed Knowlege Graph known issue : The following IBM Watson™ Discovery Knowledge Graph query_entities known issue is fixed with the 2018-05-04 API version update. This fix only applies if entities are ingested or replaced after 2018-05-04. Entities can be replaced by re-ingesting old documents or by ingesting new documents containing those entities. If old entities are not replaced, then query_entities return all uppercase with 2018-05-04 API version.

Improved entity names : All entity names were previously converted to camel case in query_entities. For example, the entity name "IBM Corporation" was converted to "Ibm Corporation". This is no longer the case.





 9 May 2018 

Change to sample document storage : Sample documents are now stored locally, in your browser's local roaming data folder.





 4 May 2018 

New Element Classification contract elements : Two additional contract elements are now supported in Element Classification: Attributes and Provenance. See [Understanding Contract Elements](https://cloud.ibm.com/docs/discovery?topic=discovery-element-classification) for details.





 26 April 2018 

Fixed ingestion normalization known issue : The following ingestion issue is fixed: In some cases where post-enrichment json_normalizations and/or normalizations were specified, the normalizations might be applied in the wrong order, possibly resulting in documents being indexed with unexpected field values.
In addition, prescriptive [deployment and configuration guidance](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deployment-setup-environment) is provided for the components in each of these reference architectures. The guidance is intended as an easier to consume supplement to the CIO templates that is more appropriate for architects and developers trying to build and implement applications for IBM Cloud for Financial Services.









 Becoming IBM Cloud for Financial Services Validated 

IBM Cloud for Financial Services Validated designates that an IBM Cloud service or ecosystem partner service has evidenced compliance to the controls of the IBM Cloud Framework for Financial Services and can be used to build solutions that might themselves be validated. Ecosystem partners who are interested in being IBM Cloud for Financial Services Validated are required to complete a CIO template for evaluation by IBM and to comply with the requirements of the IBM Cloud Framework for Financial Services.

Through the shared responsibility model of the IBM Cloud Framework for Financial Services and the surrounding standardized processes, financial institutions and ecosystem partners get benefits such as:



* Less time that is spent by ecosystem partners demonstrating compliance and more time delivering innovative services.
* Reduction in the time and effort by financial institutions to ensure the compliance of third-party vendors, and more time spent delivering new, innovative services to their customers.
* Streamlined procurement, contracting, and onboarding within the ecosystem that leads to reduced time to market for all parties.



In addition, ecosystem partners (even those who are not yet IBM Cloud for Financial Services Validated) are encouraged to [onboard to the IBM Cloud catalog](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-onboarding-to-catalog).





 Next steps 

If you plan to provide SaaS:



* Review [Best practices for software as a service](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practices), which represent a generic set of implementation principles that apply to SaaS applications on both reference architectures.
* Explore the [reference architectures](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-reference-architecture-overview) and deployment guidance
CM-8 (4) - Accountability Information 



  Control requirements 

CM-8 (4) - 0
:   The organization includes in the information system component inventory information, a means for identifying by [IBM Assignment: asset owner/custodian], individuals responsible/accountable for administering those components.





  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [IBM Cloud account setup](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setup)







  NIST supplemental guidance 

Identifying individuals who are both responsible and accountable for administering information system components helps to ensure that the assigned components are properly administered and organizations can contact those individuals if some action is required (e.g., component is determined to be the source of a breach/compromise, component needs to be recalled/replaced, or component needs to be relocated).
The Ingress timeout for the gRPC web proxy has been increased to avoid an error during smart contract instantiation. It is recommended that you apply this patch to your existing peer and ordering nodes.





 11 December 2019 

Miscellaneous bug fixes





 15 November 2019 

Service availability in two new regions

The IBM Blockchain Platform for IBM Cloud is now available to be provisioned in two new IBM Cloud regions: US East, and AP South. Refer to the [locations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-regions-locations) information to see the data centers that are available in those regions.





 06 November 2019 

Simplified component creation flows

Peer, CA and ordering service creation has been streamlined. Now, when you create a node, you have to select a checkbox to configure advanced deployment options.





 02 October 2019 

Peer, CA, and ordering node patch 1.4.3-0

Zone selection for ordering nodes

When multiple zones are configured in your Kubernetes cluster, you can now choose which zone to deploy your ordering node to. Spreading nodes across zones is useful for ensuring high availability of your blockchain network.

Ability to set peer to be an anchor peer when the peer joins the channel

Users can now choose to designate a peer to be an anchor peer when the peer is being joined to the channel, rather than after the peer has joined the channel. An anchor peer must exist for each organization in order for cross organizational gossip to work. [Anchor peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-channels-anchor-peers) are also required for private data and service discovery to work. [Learn how](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-join-peer).

Ability to add a peer to a channel from the Channels tab

A peer can now be joined to a channel directly from the Channels tab.
Logging with bare metal servers 

Use the IBM® Log Analysis service to monitor and manage logs from a bare metal server in a centralized logging system on the IBM Cloud.

These instructions are for Ubuntu Linux systems but can be used for other Linux systems.

You can collect and monitor system and application logs.

By default, the logging agent for Ubuntu monitors log files in the /var/log directory. For example, the Ubuntu system log (/var/log/syslog) is monitored by default.

On the IBM Cloud, configure a bare metal server to forward logs to an IBM Log Analysis instance by completing the following steps:



1. Provision a bare metal server running Ubuntu Linux.
2. Provision an instance of the IBM Log Analysis service.
3. Configure the logging agent in the bare metal server.
4. Optionally, add additional directories to be monitored by the agent.



Zoom

![Component overview on the IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/Log-Analysis-03-Ubuntu.svg)

Figure 1. Component overview on the IBM Cloud

In this tutorial, you will learn how to configure a bare metal server to forward logs to an IBM Log Analysis instance.



 Before you begin 

Read about IBM Log Analysis. For more information, see [About](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-startedgetting-started-ov).

Work in a [supported region](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).

You can send data from an Ubuntu instance that is located in the same region as your logging instance, in a different region, or not in the IBM Cloud.

Use a user ID that is a member, or an owner of, an IBM Cloud account.
* For example, MAS 8.10 (GA) will be released by IBM on 3/28/2023 and MAS-Dedicated 8.10 on 5/2/2023
* The release of MAS-Dedicated can be delayed beyond 30 days due to holidays and freeze periods. For example MAS 8.9 was released on 11/22/2022 and MAS Dedicated will be 1/17/2023





Table 1. MAS-Dedicated Release Planning

 Version MAS (GA) Release MAS-Dedicated Release Approx Upgrade Window 

 8.9 11/22/22 1/17/23 March to June 
 8.10 (LTS) 3/28/23 5/2/23 June to September 
 8.11 9/26/23 10/30/23 By Request after 10/30/23 



Planning Guidelines The following guidelines apply to planning for MAS upgrades:



* Clients must remain on a supported version. This means either be on n or n-1 or a Long Term Support version. For example once 8.13 is released, 8.11 is no longer in support so a customer will need to be on 8.12 before 8.13 is released.
* Long Term Support (LTS) releases are designated by development. 8.10 has been designated as a Long Term Support release. LTS releases are supported for up to three years. No new functionality will be delivered on this release, but fixes and security patches will be available and delivered to clients on LTS releases.
* Supporting Software such as Openshift and DB2 are on separate release schedules. These will be updated according the support policies of those teams. LTS releases will be updated to support newer versions of the supporting software. This means even if on a LTS release over the three years, there will still be a need to upgrade some elements.



Within these parameters:



* Clients can request specific dates for upgrading their environments. Clients on an LTS release can remain on that release for the time it is supported.
* Non production environments will be done during the week
* Production environments are typically done over the weekend
* Clients can determine the length of time between upgrading non production and production assuming the production upgrade happens prior to the existing version being out of support.
Viewing vCenter Server instances 

View the summary and detailed information of the VMware vCenter Server® instances that are provisioned for different user accounts.



 Procedure to view summary for vCenter Server instances 

To view a summary of all the vCenter Server instances that are provisioned for a user account, complete the following steps:



1. In the IBM Cloud® for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. From the console banner, click the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/i-avatar-icon.svg), and then click the Account field. Select the user account that you want to check instances for.
3. In the vCenter Server table, view the list of instances that are provisioned in the selected user account.





Table 1. vCenter Server instance items

 Item Description 

 Name The name of the instance. 
 Type The type of vCenter Server instance. Instance type is Single-zone or VMware Security and Compliance Readiness Bundle. 
 Version The release version that the instance was deployed in, or upgraded to. 
 Location The IBM Cloud data center where the instance is hosted. 
 Creation time The date and time when the instance was created. 
 Status The status of the instance. 



The instance can have different statuses.



Table 2. vCenter Server instances status descriptions

 Status Description 

 Creating The instance is being created. 
 Building The instance is being configured. 
 Available The instance is ready to use. 
 Modifying The instance is being modified. 
 Failed The creation, configuration, or modification process failed. 
 Deleting The instance is being deleted. 
 Deletion error An error occurred when the instance was being deleted. 
 Deleted The instance is deleted. 







 Procedure to view the property details for vCenter Server instances 

To view the property details of an instance, complete the following steps.



1. In the vCenter Server table, click an instance name.
2.
Transient virtual servers 

The IBM Cloud® Virtual Servers transient offering is a good option if you have flexible workloads and want cost savings. You save money by running your workload on a transient virtual server. Transient instances are provisioned when unused capacity is available. Therefore, when data center resources are needed for full, on-demand accounts, you can also lose those resources. Transient instances are de-provisioned on a first-on, first-off basis when those resources need to be reclaimed.

Transient virtual servers offer the following flexibility:



* Global availability

The transient virtual server offering is available in data centers across the globe.
* Cost savings

Transient virtual servers are ideal for nonproduction workloads. For example, you might use a transient instance to test and develop applications, or test scalability in environments that don't require constant uptime.



Transient instances are public instances that use SAN-backed storage. The following families of public instances are available for this offering.



Table 1. Public virtual server family selections

 Families Description 

 [Balanced](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilesbalanced) Best for common cloud workloads that require a balance of performance and scalability. Uses network-attached storage. 
 [Compute](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilescompute) Best for moderate to high web traffic workloads. 
 [Memory](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profilesmemory) Best for memory caching and real-time analytics workloads. 





 Notifications 

When configured, you can receive automated reclaim notifications that help you prepare and reduce lost data.
In addition, if you are the account owner or a user with the required access to manage other user's API keys in the account, you can use the View filter to list and manage those API keys.



 Required access for managing API keys 

By default, you always have access to create your own API keys, and then update and delete them as needed. You also can manage your own classic infrastructure API key and any users' classic infrastructure API keys who you are an ancestor of in the classic infrastructure user hierarchy, meaning you invited the user or someone you invited to the account invited the user, and so on.

If the Restrict API key creation IAM account setting is enabled, everyone in the account is blocked from creating API keys, including the account owner, unless they are assigned explicit access. For more information, see [Restricting users from creating API keys](https://cloud.ibm.com/docs/account?topic=account-allow-api-create).

If you are the account owner or a user with the required access, you can access other user's API keys or service ID API keys by using the View filter on the API keys page. You can edit or delete the API keys depending on your assigned access. You see only the filter options for the type of API keys that you have access to view and manage.



Table 1. Required access for API key management on the API keys page

 Filter options Displayed API keys Required access Allowed actions 

 My IBM Cloud API keys Your IBM Cloud API keys No access required View, create, edit, delete 
 All IBM Cloud user API keys All IBM Cloud API keys created by all users in the account Administrator role on the IAM Identity service View, edit, and delete 
 All service ID API keys All API keys created for service IDs in the account Administrator role on the IAM Identity service View, edit, and delete 
 Classic infrastructure API keys Your classic infrastructure API key and any classic infrastructure API keys for users who you are ancestor of in the user hierarchy No access required other than being an ancestor in the user hierarchy View details and delete
Viewing Cyber Recovery instances 

View the summary and detailed information of the Cyber Recovery instances that are provisioned for different user accounts.



 Procedure to view summary for Cyber Recovery instances 

To view a summary of all the Cyber Recovery instances that are provisioned for a user account, complete the following steps:



1. In the IBM Cloud® for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. From the console banner, click the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/i-avatar-icon.svg), and then click the Account field. Select the user account that you want to check instances for.
3. In the Cyber Recovery table, view the list of instances that are provisioned in the selected user account.





Table 1. Cyber Recovery instance items

 Item Description 

 Name The name of the instance. 
 Type The type of Cyber Recovery instance. Instance type is Single-zone. 
 Version The release version that the instance was deployed in, or upgraded to. 
 Location The IBM Cloud data center where the instance is hosted. 
 Creation time The date and time when the instance was created. 
 Status The status of the instance. 



The instance can have different statuses.



Table 2. Cyber Recovery instances status descriptions

 Status Description 

 Creating The instance is being created. 
 Building The instance is being configured. 
 Available The instance is ready to use. 
 Modifying The instance is being modified. 
 Failed The creation, configuration, or modification process failed. 
 Deleting The instance is being deleted. 
 Deletion error An error occurred when the instance was being deleted. 
 Deleted The instance is deleted. 







 Procedure to view the property details for Cyber Recovery instances 

To view the property details of an instance, complete the following steps.



1. In the Cyber Recovery table, click an instance name.
2. Under Properties, view the details for the instance.





Table 3. Cyber Recovery instance properties

 Property Description
The [Watson Assistant Continuous Improvement Best Practices Guide](https://github.com/watson-developer-cloud/assistant-improve-recommendations-notebook/raw/master/notebook/IBM%20Watson%20Assistant%20Continuous%20Improvement%20Best%20Practices.pdf) describes how to get the most out of these notebooks.





 Using the notebooks with Watson Studio 

The following notebooks are available:



* [Dialog skill analysis for Watson Assistant](https://dataplatform.cloud.ibm.com/exchange/public/entry/view/4d77701840fcb2f21587e39fdb887049)
* [Measure Watson Assistant Performance](https://dataplatform.cloud.ibm.com/exchange/public/entry/view/133dfc4cd1480bbe4eaa78d3f635e568).
* [Analyze Watson Assistant Effectiveness](https://dataplatform.cloud.ibm.com/exchange/public/entry/view/133dfc4cd1480bbe4eaa78d3f636921c)
* [Dialog Flow Analysis for Watson Assistant](https://dataplatform.cloud.ibm.com/exchange/public/entry/view/013c690997e27f3a8d9133265327a9e5)



If you choose to use the notebooks that are designed for use with Watson Studio, the steps are roughly these:



1. Create a Watson Studio account, [create a project](https://dataplatform.cloud.ibm.com/docs/content/wsj/getting-started/projects.html), and add a Cloud Object Storage account to it.
2. From the Watson Studio community, choose a notebook.

Early in the development process, use the Dialog skill analysis for Watson Assistant notebook to help you get started. It offers the following types of insights:



* Examines the terms that are correlated with each intent in your training data to find anomalies that might identify problems that you can investigate further.