vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The IBM Semeru Open J9 alternate JRE is changed to ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 7 February 2023 

Updated Liberty buildpack v3.78-20230124-2119
: The alternate Liberty runtime version is changed to 23.0.0.1. The default Liberty runtime is unchanged [22.0.0.12](https://openliberty.io/blog/2022/11/22/22.0.0.12.html).



* To specify the monthly runtime set the following two variables and restage your application:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* The IBM JRE version remains unchanged 8 SR7 FP20 and the IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.17_8_openj9-0.35.0.
* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.17_8_openj9-0.35.0



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 30 January 2023 

Billing changes at End-of-Support
: IBM Cloud Foundry will end support on 1 June 2023. Any application instances still running on or after that date will be billed $0.35 USD per gigabyte hour.
* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 30 January 2023 

Billing changes at End-of-Support
: IBM Cloud Foundry will end support on 1 June 2023. Any application instances still running on or after that date will be billed $0.35 USD per gigabyte hour. For more information see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).





 14 December 2022 

Updated Liberty buildpack v3.77-20221207-2115
: The alternate and default Liberty runtime version is unchanged [22.0.0.12](https://openliberty.io/blog/2022/11/22/22.0.0.12.html).



* To specify the monthly runtime set the following two variables and restage your application:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* The IBM JRE version is changed to 8 SR7 FP20 and contains the fixes for the following security vulnerabilities:



* [CVE-2022-3676](https://www.ibm.com/support/pages/node/6839777)
* All applicable Java SE CVEs published by Oracle in the [October 2022 Critical Patch Update](https://www.oracle.com/security-alerts/cpuoct2022.html)



* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.17_8_openj9-0.35.0



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"
You can bring your own ESX license, but you need to open a ticket with Support to inform them of the change.



* Recommended workloads - Tier 3
* Performance - Limited dependent on RAID and disk type. SSDs present a cost increase for better performance.
* Scalability - Limited to the number of drive slots in the chassis
* Protocols - Not applicable
* Cost: Low capital expenditure (CapEx) and operating expenditure (OpEx)
* HA - Not available
* Replication - [vSphere Replication Virtual Appliance](https://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-E654F2D8-7D56-4A81-9568-E85172A7022D.html)
* Reliability - Multiple single points of failure







 vSAN [1] 

With vSAN, you have the following options.



* Recommended workloads - Tier 1
* Performance - 90 K+ IOPS per host (depends on host configuration)
* Scalability - v5.5 virtual machine disk (VMDK) up to 2 TB; v6.0 VMDK up to 62 TB. Scale out with more nodes.
* Protocols - Proprietary
* Cost - Medium for both CapEx and OpEx
* HA - Supported for both host and disk failures. Failure domains are supported from v6 of VMware.
* Replication - [vSphere Replication Virtual Appliance](https://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-E654F2D8-7D56-4A81-9568-E85172A7022D.html)
* Replication and disaster recovery
* Reliability - Tolerates up to three host failures with seven or more hosts. Failure domains were introduced in v6 of VMware.



The most recent version of vSAN is available from the IBM Cloud® catalog with CPU license billing base.
[Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-private_endpoints_only).





 11 February 2022 

Support for syslog private endpoints
: IBM Log Analysis now supports syslog private endpoints. [Learn more about syslog private endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_syslog_private_endpoints).





 3 February 2022 

Changes to Tokyo syslog IP addresses
: The [IP addresses used for the syslog-a.jp-tok.logging.cloud.ibm.com endpoint](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_syslog) have changed. If your service is configured to use specific IP addresses or firewall to a specific IP address, then modification to the new IP addresses will be required.





 31 January 2022 

Index rate analysis to alert on unexpected data volume spikes
: You can configure index rates alerts in your IBM Log Analysis instance to monitor and be alerted of unexpected spikes in your data volumes. Use the index rate to analyze and predict costs that are associated with storage of searchable data. [Learn more about index rate analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-control_usage_index_rate).

Managing and limiting data usage
: In your IBM Log Analysis instance, you can use the usage quota settings to control how much data is stored so you can manage your data cost while still being able to view and retain the data that you need. [Learn more about usage quotas](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-control_usage_quotas).





 4 October 2021 

API for archiving
: Documentation of API changes supporting archiving is generally available. [Learn more about the archiving API](https://cloud.ibm.com/apidocs/log-analysisget-v1-config-archiving).
vCenter Server multizone BOM 

New deployments of vCenter Server multizone instances are no longer supported. You can still add and delete clusters, add and remove ESXi servers, and add and delete storage for existing multizone instances.

Review the Bill of Materials (BOM) for VMware vCenter Server® multizone instances.



 Components 

The following components are available for vCenter Server multizone instances:



* VMware vSphere® 7.0 Update 1c
* VMware Aria components



* VMware Aria® Operations™ 8.2
* VMware Aria Operations™ for Logs 8.4
* VMware Aria Operations™ for Networks 4.8



* VMware NSX-T™ 3.2.0.1. NSX-V is not supported.
* Skylake and Cascade Lake when available. Skylake 4110 is supported for the witness and management clusters only.
* Optane drives are the only supported option for VMware vSAN™ cache disks.
* vSAN with the options of RAID 1, RAID 5, and RAID 6.
* Licensing:



* vSAN Enterprise.
* VMware NSX® Enterprise or Enterprise Plus.
* Bring Your Own Licenses (BYOL) is not supported.



* HA Active Directory with two virtual machines or two VSIs distributed between the two workload sites.





 Component naming conventions 



Table 1. Component naming conventions

 Component Format Example 

 Hostname <host_prefix><host_number> host01.subdomain.domain 
 Stretched cluster name <instance>-mgmt-<datacenter-region> mcv1-dal 
 Cluster and management component <instance>-<cluster>-<datacenter>-<component> mcv1-mgmt-dal10-private <br>DAL10-DVS 









 Instance sizing considerations 

The witness and management clusters can be deployed either by using NFS storage, with a minimum of two nodes required, or by using vSAN storage, with a minimum of four nodes required. Conversion of the witness or management clusters from NFS to vSAN is not supported or offered.
The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.









 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [Adding, viewing, and deleting clusters for vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_addingviewingclusters)
* [Place a host in maintenance mode](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.resmgmt.doc/GUID-8F705E83-6788-42D4-93DF-63A2B892367F.html)
* [Enhanced vMotion Compatibility (EVC) processor support](https://kb.vmware.com/s/article/1003212)
Changes since version 1.10.5_1518

 Component Previous Current Description 

 systemd 229 230 Updated systemd to fix cgroup leak. 
 Kernel 4.4.0-127 4.4.0-133 Updated worker node images with kernel update for [CVE-2018-3620,CVE-2018-3646](https://ubuntu.com/security/notices/USN-3741-1). 







 Change log for worker node fix pack 1.10.5_1518, released 13 August 2018 

The following table shows the changes that are in the worker node fix pack 1.10.5_1518.



Table 1. Changes since version 1.10.5_1517

 Component Previous Current Description 

 Ubuntu packages N/A N/A Updates to installed Ubuntu packages. 







 Change log for 1.10.5_1517, released 27 July 2018 

The following table shows the changes that are in patch 1.10.5_1517.



Table 1. Changes since version 1.10.3_1514

 Component Previous Current Description 

 Calico v3.1.1 v3.1.3 See the Calico [release notes](https://docs.tigera.io/archive/). 
 IBM Cloud Provider v1.10.3-85 v1.10.5-118 Updated to support Kubernetes 1.10.5 release. In addition, LoadBalancer service create failure events now include any portable subnet errors. 
 IBM Cloud File Storage for Classic plug-in 320 334 Increased the timeout for persistent volume creation from 15 to 30 minutes. Changed the default billing type to hourly. Added mount options to the pre-defined storage classes. In the NFS file storage instance in your IBM Cloud infrastructure account, changed the Notes field to JSON format and added the Kubernetes namespace that the PV is deployed to. To support multizone clusters, added zone and region labels to persistent volumes.
: Faster recovery time, as the data is already replicated to the backup MZR. There is still some latency related to the time it takes to reconfigure the database to an HA configuration.

Impacts
: Cost. To support the recovery time objective the only viable option is the active/hot standby model.
: Development teams need to update their deployment pipelines to also deploy their apps to the standby IBM Cloud Code Engine project every time they deploy to production. And, validate that it was successful.
: Manual intervention is required to trigger and monitor the promotion of the read-only replica to leader status.

For more details, see [Configuring read-only replicas](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-read-only-replicas).

Here are the basic steps:



1. Create instance in primary MZR (for example, Dallas)
2. Create read-only replica in DR MZR (for example, Washington, DC) Read-only replica is a single zone instance
3. If primary MZR is unavailable, promote read-only replica to leader. Now, DR MZR becomes the leader.



* This updates the config in the DR MZR to be MZR resilient, meaning additional nodes are added.
* This takes a full backup of the database in the DR MZR
* DR MZR becomes the leader, and ties to original leader in primary MZR are broken



* Original instance in primary MZR can be deleted. This deletes all backups in the primary MZR.
* If original instance is not deleted (for example, backups are still available) a new instance can be created by restoring from a backup, should that become necessary.



* The backups that are taken in the original MZR are still accessible even if that MZR is unavailable; they are stored in cross-regional IBM Cloud Object Storage buckets.



4. If a read-only replica is promoted to leader, the original leader is no longer viable.
5.
US Health Insurance Portability and Accountability Act (HIPAA) support is available for Premium plans in the Washington, DC location created on or after 1 April 2019. See [Enabling EU and HIPAA supported settings](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedeu-hipaa-supported) for more information.





 GDPR in Knowledge Studio 

IBM Watson® Knowledge Studio provides a graphical interface through which you can access and delete uploaded artifacts that contain data. The following artifacts can be uploaded to Knowledge Studio:



* Type systems
* Dictionaries
* Documents



If you receive a request to delete data, complete the following steps:



1. [Delete the applicable artifact](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-artifacts).
2. [Retrain and redeploy the model](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-train-ml).
3. [Delete previous versions of the model that used the deleted data](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-improve-mlwks_maversions).
: US Health Insurance Portability and Accountability Act (HIPAA) support is now available for Premium plans that are hosted in the Dallas (us-south) location. For more information, see [Health Insurance Portability and Accountability Act (HIPAA)](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-information-securityhipaa).





 16 September 2021 

New beta Czech and Netherlands Dutch next-generation models
: The service now supports the following new next-generation language models. Both new models are beta functionality.



* Czech: cs-CZ_Telephony. The new model supports low latency.
* Netherlands Dutch: nl-NL_Telephony. The new model does not support low latency.



For more information about all available next-generation language models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

Updates to Korean and Brazilian Portuguese next-generation models
: The following next-generation models have been updated:



* The Korean model ko-KR_Telephony now supports low latency.
* The Brazilian Portuguese model pt-BR_Telephony has been updated for improved speech recognition.



Defect fix: Correct interim results and low-latency documentation
: Defect fix: Documentation that describes the interim results and low-latency features with next-generation models has been rewritten for clarity and correctness. For more information, see the following topics:



* [Interim results and low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interim), especially [Requesting interim results and low latency](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-interiminterim-low-latency)
* [How the service sends recognition results](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-websocketsws-results)



Defect fix: Improve speakers labels results
The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.







 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [Planning for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Deleting clusters from vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingclusters)
* [Place a host in maintenance mode](https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.resmgmt.doc/GUID-8F705E83-6788-42D4-93DF-63A2B892367F.html)
* [Enhanced vMotion Compatibility (EVC) processor support](https://kb.vmware.com/s/article/1003212)
* [Feature support by billing type](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-storage-prepodf-essentials-vs-advanced)
* [Deploying OpenShift Data Foundation](https://cloud.ibm.com/docs/openshift?topic=openshift-ocs-storage-prepodf-deploy-options)





 Setting up OpenShift Data Foundation for VPC clusters 

[Deploying OpenShift Data Foundation on VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcdeploy-odf-vpc)



* [Prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcocs-storage-vpc)



* [Optional: Setting up an IBM Cloud Object Storage service instance](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-create-cos)
* [Optional: Setting up encryption by using Hyper Protect Crypto Services or Key Protect](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-create-hscrypto-vpc)



* [Installing the OpenShift Data Foundation add-on from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcinstall-odf-console-vpc)
* [Installing the add-on from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcinstall-odf-cli-vpc)
* [Creating your ODF custom resource](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcocs-vpc-deploy-crd)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 IAM enabled ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 



In stand-alone accounts, you control access to resources by grouping them in resource groups, and configuring IAM policies that you assign to users and service IDs directly or through access groups. These policies define the level of access to work with services in the account. For example, you might have a stand-alone account where you run your development, pre-production, and production services and applications.

By using an enterprise management account strategy, you achieve greater isolation of resources. When you configure a multitiered hierarchy of accounts, you get the flexibility to separate your development environments into separate tiers, or isolate by Line of Business (LoB) applications and services, or a combination of both. Each account retains the features of a stand-alone account, and you can still manage billing and payments from the root enterprise account.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 IAM enabled ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 



In stand-alone accounts, you control access to resources by grouping them in resource groups, and configuring IAM policies that you assign to users and service IDs directly or through access groups. These policies define the level of access to work with services in the account. For example, you might have a stand-alone account where you run your development, pre-production, and production services and applications.

By using an enterprise management account strategy, you achieve greater isolation of resources. When you configure a multitiered hierarchy of accounts, you get the flexibility to separate your development environments into separate tiers, or isolate by Line of Business (LoB) applications and services, or a combination of both. Each account retains the features of a stand-alone account, and you can still manage billing and payments from the enterprise account.

In addition to these benefits, when you look into auditing and how it fits with any of these management strategies, consider the following that will be covered later in more detail:



* Auditing events are collected and available per location (region) through 1 single auditing instance. You do not have the ability to split events from different services running in the same region to multiple instances.
Managing authentication to your Event Streams instances 

Event Streams supports 2 [SASL](https://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer)(Simple Authentication and Security Layer) mechanisms as the authentication methods to Event Streams instances by default: PLAIN and OAUTHBEARER.

Kafka client configured with SASL PLAIN uses IAM API key as a plain text password in the authentication process, Event Streams sends API key to IAM for verification. Once authenticated, this client will keep connected and will not require re-authentication until it is disconnected and wants to re-connect.

Kafka client configured with SASL OAUTHBEARER uses IAM access token in the authentication process, Event Streams verifies the token via IAM public key. Since IAM access token has expiration time (usually at 1 hour), Kafka client is required to re-generate a new token and go through the authentication process again when previous token is approaching expiration time. This approach provides better security comparing to SASL PLAIN in 2 ways: 1. API key always stays at client side to generate access token and is no longer sent to Kafka brokers over network, this removes the risk of API key exposure. 2. Authentication process happens at a regular basis when access token is expiring, this minimizes the risk of token exposure.

For more secure authentication, SASL OAUTHBEARER is the only recommended authentication method for Kafka clients. See [Configuring your Kafka API client](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-kafka_usingkafka_api_client) how to configure SASL OAUTHBEARER in Kafka clients.

Enterprise users have the option to disable SASL PLAIN in their Enterprise instances. Use command:

ibmcloud resource service-instance-update <instance-name> -p '{"iam_token_only":true}'





 Managing authorization to your Event Streams resources 

You can secure your Event Streams resources in a fine-grained manner to manage the access that you want to grant each user to each resource.