vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Therefore, you must [create a channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-channel) or [join a channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-join-networkibp-console-join-network-join-peer-org2) by using your console.
* The IBM Blockchain Platform supports smart contracts written in JavaScript, TypeScript, Java, and Go. When you are allocating resources to your peer node, it is important to note that JavaScript and TypeScript smart contracts require more resources than contracts written in Go.







 Step one: Write and package your smart contract 

The IBM Blockchain console manages the deployment of smart contracts rather than development. If you are interested in developing smart contracts, you can get started using tutorials provided by the Hyperledger Fabric community and tooling provided by IBM.



* To learn how smart contracts can be used to conduct transactions among multiple parties, see the [Developing applications topic](https://hyperledger-fabric.readthedocs.io/en/release-1.4/developapps/developing_applications.html) in the Hyperledger Fabric documentation.
* When you are ready to start building smart contracts, you can use the [IBM Blockchain Visual Studio code extension](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscode) to start building your own smart contract project. You can also use that extension to [connect directly to your network from Visual Studio Code](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-connecting-ibp) and explore the inline tutorials.
* For a quick tutorial on developing smart contracts, see [Develop a smart contract with the IBM Blockchain Platform VS Code extension](https://developer.ibm.com/tutorials/ibm-blockchain-platform-vscode-smart-contract/).
RabbitMQ Major versions are the first two numbers in a major.x.patch version number. v3.11, TBD Backup taken and access removed 
 MySQL** Major versions are the first two numbers in a major.x.patch version number. v5.7, TBD Backup taken and access removed 



IBM Cloud® Databases for DataStax is deprecated and no longer supported as of 30 June 2024. For more information, see the [deprecation details](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-deprecationdep_details).

**For more information, see [MySQL 8 GA](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-mysql8-ga).

Any actions taken after a database EOL date happen over several days after the EOL date. We try, but cannot guarantee, to make these upgrades outside of business hours in the local regions. If you want more control over the upgrade process of your database instance, we recommend that you upgrade following our [backup and restore process](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups) before the EOL date of your database version.





 Major versioning End of Life 

You receive multiple notifications when a major version reaches its End of life. You can typically expect:



* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
v5.0, TBD Automatically upgraded in place to next Major version only for Redis 4 to Redis 5 
 RabbitMQ Major versions are the first two numbers in a major.x.patch version number. v3.11, TBD Backup taken and access removed 
 MySQL** Major versions are the first two numbers in a major.x.patch version number. v5.7, October 2023 Backup taken and access removed 



**For more information, see [MySQL 8 GA](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-mysql8-ga).

Any actions taken after a database EOL date happen over several days after the EOL date. We try, but cannot guarantee, to make these upgrades outside of business hours in the local regions. If you want more control over the upgrade process of your database instance, we recommend that you upgrade following our [backup and restore process](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups) before the EOL date of your database version.





 Major versioning End of Life 

You receive multiple notifications when a major version reaches its End of life. You can typically expect:



* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page.
On rare occasions, failure can result, impacting your availability. If a failure occurs, the database is disabled, and you need to restore from backup. We recommend self-migrating before the end of support date.





 Major versions defined 



Table 1. Major versions for Cloud Databases

 Database Versioning Schema Next Known End of Life Version and Date End of life procedure 

 DataStax Major versions are the first number in a major.minor.patch version number. v6.8.x, March 2026 Backup taken and access removed 
 Elasticsearch Major versions are the first number in a release.version.maintenance version number. v7.9, November 2023; v7.10, November 2023; v7.17, TBD Backup taken and access removed 
 EnterpriseDB Major version is defined by the first number in the version number. v12, December 2024 Backup taken and access removed 
 etcd Major versions are the first number in a major.minor.patch version number. v3.3, unplanned Backup taken and access removed 
 MongoDB Major versions are the first two numbers in a major.x.patch version number. In cases where x is even, it is a stable release suitable for production. Even x versions are the only ones available on Cloud Databases. v4.2, July 2023; v4.4, January 2024; v5, September 2024 Automatically upgraded in place to next Major version 
 PostgreSQL Major version is defined by the first number in the version number. v11, TBD Backup taken and access removed 
 Redis Major versions are the first number in a major.minor.patch version number. v5.0, TBD Automatically upgraded in place to next Major version only for Redis 4 to Redis 5 
 RabbitMQ Major versions are the first two numbers in a major.x.patch version number. v3.11, TBD Backup taken and access removed 
 MySQL** Major versions are the first two numbers in a major.x.patch version number. v5.7, October 2023 Backup taken and access removed
On rare occasions, failure can result, impacting your availability. If a failure occurs, the database is disabled, and you need to restore from backup. We recommend self-migrating before the end of support date.





 Major versions defined 



Table 1. Major versions for Cloud Databases

 Database Versioning Schema Next Known End of Life Version and Date End of life procedure 

 DataStax Major versions are the first number in a major.minor.patch version number. v6.8.x, March 2026 Backup taken and access removed 
 Elasticsearch Major versions are the first number in a release.version.maintenance version number. v7.9, November 2023; v7.10, November 2023; v7.17, TBD Backup taken and access removed 
 EnterpriseDB Major version is defined by the first number in the version number. v12, December 2024 Backup taken and access removed 
 etcd Major versions are the first number in a major.minor.patch version number. v3.3, unplanned Backup taken and access removed 
 MongoDB Major versions are the first two numbers in a major.x.patch version number. In cases where x is even, it is a stable release suitable for production. Even x versions are the only ones available on Cloud Databases. v4.2, July 2023; v4.4, January 2024; v5, September 2024 Automatically upgraded in place to next Major version 
 PostgreSQL Major version is defined by the first number in the version number. v11, TBD Backup taken and access removed 
 Redis Major versions are the first number in a major.minor.patch version number. v5.0, TBD Automatically upgraded in place to next Major version only for Redis 4 to Redis 5 
 RabbitMQ Major versions are the first two numbers in a major.x.patch version number. v3.11, TBD Backup taken and access removed 
 MySQL** Major versions are the first two numbers in a major.x.patch version number. v5.7, TBD Backup taken and access removed 



IBM Cloud® Databases for DataStax is deprecated and no longer supported as of 30 June 2024.
Click Update now to initiate the update when you're ready.

With the update initiated, a progress window is presented under the Notifications icon.

Zoom

![Update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_primary_update.jpg)

Figure 9. Primary site system update information





 Primary site update completion 

Upon completion of a successful update, a Success! window appears.

Zoom

![Primary site successful update](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_primary_success.jpg)

Figure 10. Primary site successful update
Release notes for IBM Cloud® Databases for MySQL 

Use these release notes to learn about the latest updates to IBM Cloud® Databases for MySQL that are grouped by date or build number.



 03 July 2023 

Upgrading to a new Major Version
: Once a major version of a database is at its End Of Life (EOL), upgrade to a current major version. For more information, see [Upgrading to a new Major Version](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-mysql-upgrading).





 22 May 2023 

Setting up disk alerts for disk utilization tutorial
: In this tutorial, you use the IBM Cloud API and the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) to set up an alert that emails you whenever the disk utilization of your database exceeds 90%. This specific example creates an alert on a Databases for Elasticsearch deployment, but it is applicable to all the databases in the IBM Cloud Databases catalog. For more information, see [Setting up disk alerts for disk utilization](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-disk-util-alert-tutorial).





 09 March 2023 

Configuring Your IBM Cloud® Databases for MySQL time zone settings
: At provisioning, a Cloud Databases deployment is configured to Coordinated Universal Time. Reconfiguring your time zone is a persistent change, which must be undertaken for each of your Cloud Databases deployments. Configure your time zone with the Cloud Databases [API](https://cloud.ibm.com/apidocs/cloud-databases-api/cloud-databases-api-v5introduction) or the [CLI](https://cloud.ibm.com/docs/databases-cli-plugin).
: Updates the cAdvisor plug-in to use TLS 1.2.

Disruptive
: None





 01 April 2019 

The following changes occurred for the 3100ddb62580a9f46ffdff7bab2ebec40b164de6 Fluentd component.

Non-disruptive changes
: Updates the Fluentd service account.

Disruptive
: None





 18 March 2019 

The following changes occurred for the c85567b75bd7ad1c9428794cd63a8e239c3fd8f5 Fluentd component.

Non-disruptive changes
: Removes the dependency on cURL for [CVE-2019-8323](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8323).

Disruptive
: None





 18 February 2019 

The following changes occurred for the 320ffdf87de068ee2f7f34c0e7a47a111e8d457b Fluentd component.

Non-disruptive changes
: Updates Fluentd to version 1.3. - Removes Git from the Fluentd image for [CVE-2018-19486](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19486).

Disruptive
: None





 01 January 2019 

The following changes occurred for the 972865196aefd3324105087878de12c518ed579f Fluentd component.

Non-disruptive changes
: Enables UTF-8 encoding for the Fluentd in_tail plug-in. - Minor bug fixes.

Disruptive
: None
* Patch releases for MAS or any Apps have to be requested via an [IBM support case](https://www.ibm.com/mysupport)
* 1 week of advance notice is needed in ticket for Patch release update
* If Patch contains security fixes or any security fix available, IBM SRE team will apply fix as soon as its available. No exceptions.







 Shared Cluster Deployment Customers 

Shared Cluster Upgrade Policy

The following guidelines apply to MAS-MS (Shared Cluster) release schedule:



* MAS-MS comes out on the first Tuesday 30 days after MAS (GA) release.
* For example, MAS 8.10 (GA) will be released by IBM on 3/28/2023 and MAS-MS 8.10 on 5/2/2023
* The release of MAS-MS 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-MS Release Planning

 Version MAS (GA) Release MAS-MS Release 

 8.9 11/22/22 1/17/23 
 8.10 (LTS) 3/28/23 5/2/23 
 8.11 9/26/23 10/30/23 



Planning Guidelines

The following guidelines apply to planning for MAS upgrades:



* Upgrade schedules are set by IBM & communicated via [Client Communications Center (CCC)](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center)
* Upgrade schedules are non-negotiable
* All client stakeholders must register to receive CCC notifications & communications
* IBM will share long-range anticipated upgrade windows upon request via ticket
* Timing is subject to change at IBM’s sole discretion based on software availability & other factors



Non-Production Upgrades



* Clients will be notified via CCC at least 5 business days prior to non-production environment upgrades
* All non-production environments will be upgraded concurrently, without exception
* Non-Production environments are upgraded during weekdays.



Production Upgrades



* Production environments will be upgraded no earlier than 4 weeks after the non-production upgrade
[Update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_recovery_update.jpg)

Figure 6. Recovery site system update information





 Recovery site update completion 

Upon completion of a successful update, a Success! window appears.

Zoom

![Recovery site successful update](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_recovery_success.jpg)

Figure 7. Recovery site successful update





 Update the primary site after updating the recovery site 

The console on the Primary node displays a system update through the Notifications icon.

The primary site must only be updated when it's Active and after the recovery site has been updated first.

The following screenshot shows the console is for the Primary node in Dallas and is in Active mode.

Zoom

![Primary version update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_primary_info.jpg)

Figure 8. Primary site version update information

Clicking View details brings up the System update information window that displays the new Db2 version of Db2 on Cloud.





 Updating primary site 

Click Update now to initiate the update when you're ready.

With the update initiated, a progress window is presented under the Notifications icon.

Zoom

![Update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_primary_update.jpg)
: Updates Ruby packages - [CVE-2019-8320])[https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8320](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8320)){: external} - [CVE-2019-8321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8321) - [CVE-2019-8322](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8322) - [CVE-2019-8323](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8323) - [CVE-2019-8324](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8324) - [CVE-2019-8325](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8325)

Disruptive
: None





 11 April 2019 

The following changes occurred for the d9af69e286986a05ed4a50469585b1cf978ddb1d Fluentd component.

Non-disruptive changes
: Updates the cAdvisor plug-in to use TLS 1.2.

Disruptive
: None





 01 April 2019 

The following changes occurred for the 3100ddb62580a9f46ffdff7bab2ebec40b164de6 Fluentd component.

Non-disruptive changes
: Updates the Fluentd service account.

Disruptive
: None





 18 March 2019
[Successful](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ss_success.png)

Figure 4. Successful Update







 DR plan updates 

Updates to DR instances must always be applied at the Recovery site first, while it's in Standby mode, before applying to the Primary site in Active mode.



 Notification 

For self-serve updates, you are notified of an instance system update through the Notifications icon in the upper right of the console on both the Primary and Recovery sites.





 Update the recovery site first 

The console on the Recovery node displays a system update through the Notifications icon. The following screenshot shows the console is for the Recovery node in London and is in Standy mode.

Zoom

![Recovery version update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_recovery_info.jpg)

Figure 5. Recovery site version update information

Clicking View details brings up the System update information window that displays the new Db2 version of Db2 on Cloud.





 Updating recovery site 

Click Update now to initiate the update when you're ready.

With the update initiated, a progress window is presented under the Notifications icon.

Zoom

![Update information](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ssu_dr_recovery_update.jpg)

Figure 6. Recovery site system update information





 Recovery site update completion 

Upon completion of a successful update, a Success! window appears.

Zoom

!
: Updates the Fluent config map to always ignore pod logs from IBM namespaces, even when the Kubernetes master is unavailable.

Disruptive
: None





 21 May 2019 

The following changes occurred for the c16fe1602ab65db4af0a6ac008f99ca2a526e6f6 Fluentd component.

Non-disruptive changes
: Fixes a bug where worker node metrics did not display.

Disruptive
: None





 10 May 2019 

The following changes occurred for the 60fc11f7bd39d9c6cfed923c598bf6457b3f2037 Fluentd component.

Non-disruptive changes
: Updates Ruby packages - [CVE-2019-8320](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8320) - [CVE-2019-8321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8321) - [CVE-2019-8322](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8322) - [CVE-2019-8323](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8323) - [CVE-2019-8324](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8324) - [CVE-2019-8325](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8325)

Disruptive
: None





 08 May 2019 

The following changes occurred for the 91a737f68f7d9e81b5d2223c910aaa7d7f91b76d Fluentd component.

Non-disruptive changes
Change log for version 5.1, released 9 February 2023 



* Updates the snapshot size to reflect actual source volume size.
* Improves the resize method when creating a volume from a snapshot.
* Updates the Kubernetes dependency to 1.25.
* Adds support for configuring the log level for sidecars from the configmap.
* Makes the ibmc-vpcblock-snapshot class the default Volumesnapshotclass.
* Adds the priorityClass in the deployment file for controller and node pods.
* Updates the driver to read the node instance ID from the node spec provider ID instead of node labels.
* Fixes a bug in volume expansion for raw block volumes.
* Removes the preStop hook for the csi-driver-registrar.









 Version 5.0 



 Change log for version 5.0.16_127, released 21 June 2023 



* Updates the following sidecar images:



* storage-secret-sidecar to v1.2.24.
* csi-node-driver-registrar to v2.7.0.
* livenessprobe to v2.9.0.
* csi-provisioner to v3.4.1.
* csi-attacher to v4.2.0.
* csi-resizer to v1.7.0.
* csi-snapshotter to v6.2.1.



* Updates the UBI image 8.8-860.
* Updates Golang to 1.19.10.
* Public and Private Networking - Databases for etcd is integrated with [Service Endpoints](https://cloud.ibm.com/docs/databases-for-etcd?topic=cloud-databases-service-endpoints). You can select whether to use connections over the public network, the IBM Cloud internal network, or both.
* Dedicated Cores - Allocating dedicated cores to your deployment introduces hypervisor-level isolation to your database instance by using isolated virtual machines to ensure that your data processing remains separated from other customers. It also provides a guaranteed minimum number of CPUs to your deployment. Deployments with dedicated cores in the same Resource Group and IBM Cloud Region might share a virtual machine.







 Data Resilience 



* [Backups](https://cloud.ibm.com/docs/databases-for-etcd?topic=cloud-databases-dashboard-backups) are included in the service. Databases for etcd backups reside in [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage&cloud-object-storage-about-cloud-object-storage) and are also [encrypted](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-security).
* All Databases for etcd deployments are configured with replication to provide both data resilience and [high-availability](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-high-availability). Deployments contain a cluster with three nodes where all the nodes store data and maintain state with a quorum.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database node resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the nodes are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Databases for etcd.