vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Gateway-enabled cluster controller 1232 1322 Updated to use Go version 1.15.10 and for [CVE-2021-23839](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23839), [CVE-2021-23840](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23840), and [CVE-2021-23841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23841). 
 IBM Cloud File Storage for Classic plug-in and monitor 388 389 Updated to use Go version 1.15.8. 
 IBM Cloud RBAC Operator 86de2b7 3dd6bbc Updated image for [CVE-2020-28851](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28851). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1165 1274 Fixed a bug that might cause version 2.0 network load balancers (NLBs) to crash and restart on load balancer updates. 
 OpenVPN Operator image v1.1.0 v1.2.0 Fixed a bug that could prevent worker node VPN updates. 







 Change log for worker node fix pack 4.4.33_1537_openshift, released 29 March 2021 

The following table shows the changes that are in the worker node fix pack 4.4.33_1537_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.4.33_1535_openshift

 Component Previous Current Description
Viewing flow log objects 

A flow log is a summary of the network traffic that is uniquely identified by a connection between two virtual network interface cards (vNICs), within a certain time window. A flow log describes traffic the firewall either accepts (relevant security groups or network ACLs) or rejects, but not both. It contains header information and payload statistics.

Currently, flow logs collect Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) traffic, but not Internet Control Message Protocol (ICMP) traffic.

Each flow log object contains individual flow logs. To view or analyze the flow logs, follow these steps.



1. Ensure that you created an instance of IBM Cloud® Data Engine. To create a service instance, see [Getting started with IBM Cloud Data Engine](https://cloud.ibm.com/docs/sql-query).

IBM Cloud Object Storage offers Lite (free) and Standard pricing plans. If you are using the Lite plan, you will not be able to perform tasks that are available with the Standard plan, such as creating tables or using SQL queries. Instead, see [Viewing generated flow log object files from the Object Storage bucket](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-analyze&interface=uiviewing-generated-flow-log-object-files-from-the-cos-bucket) and alternative methods documented in the following procedures.
2. Launch IBM Cloud® Data Engine.
3. Start querying flow logs from the bucket that you specified when [Creating a flow log collector](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-flow-log-collector).

To view the most frequent flow object, run the following query:

SELECT * FROM cos://<region>/<bucket>/ibm_vpc_flowlogs_v1/ STORED AS JSON ORDER BY stream-id LIMIT 1 INTO cos://<region>/<target_bucket>/result/ STORED AS JSON

Where:



* bucket - The bucket where your flow logs are stored.
etcd v3.4.24 v3.4.25 See the [etcd release notes](https://github.com/etcd-io/etcd/releases/v3.4.25). 
 IBM Cloud Controller Manager v1.23.17-10 v1.23.17-16 Updated support of the Kubernetes 1.23.17 release. Updated Go dependencies. Key rotation. 
 IBM Cloud RBAC Operator 778ef2b 4e2f346 Make armada-rbac-sync FIPS compliant 
 Key Management Service provider v2.6.5 v2.6.6 Updated Go to version 1.19.9 and updated dependencies. 
 OpenVPN client 2.6.4-r0-IKS-27 2.5.8-r0-IKS-674 Reverted to previous version. 
 OpenVPN server 2.6.4-r0-IKS-26 2.5.8-r0-IKS-673 Reverted to previous version. 
 Portieris admission controller v0.13.4 v0.13.5 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.5). 
 Red Hat OpenShift on IBM Cloud. 4.10.56 4.10.59 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-59). 







 Change log for worker node fix pack 4.10.59_1569_openshift, released 23 May 2023 

The following table shows the changes that are in the worker node fix pack 4.10.59_1569_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.10.59_1566_openshift

 Component Previous Current Description 

 Red Hat OpenShift on IBM Cloud N/A N/A N/A
IBM Blockchain Platform CAs are based on the [Hyperledger Fabric CA](https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/), though it is possible to use another CA if it uses a PKI based on x.509 certificates. Because non-Fabric CAs are not configured to create properly formatted MSPs, users who want to use this kind of CA must create the MSP for themselves.

For more information about how certificate authorities are used to establish identity and membership, see [Hyperledger Fabric documentation on identity](https://hyperledger-fabric.readthedocs.io/en/release-2.2/identity/identity.html) and on [membership](https://hyperledger-fabric.readthedocs.io/en/release-2.2/membership/membership.html).





 Ordering services 

Many distributed blockchains, such as Ethereum and Bitcoin, feature systems in which any node can participate in the process where transactions are ordered and bundled into blocks. Because of this fact, these systems rely on probabilistic consensus algorithms that eventually guarantee ledger consistency to a high degree of probability, but are still vulnerable to divergent ledgers (also known as a ledger “fork”), where different participants in the network have a different view of the accepted order of transactions.

Hyperledger Fabric works differently. It features a kind of a node that relies on deterministic consensus algorithms that is called an “ordering node” or an "orderer", that does this transaction ordering. The collection of ordering nodes form the "ordering service".

In addition to promoting finality, separating the endorsement of smart contract execution (which happens at the peers) from ordering gives Fabric advantages in performance and scalability, eliminating bottlenecks that can occur when execution and ordering are performed by the same nodes.

The ordering service performs one other key function: In networks that use a system channel the orderers maintain the "consortium", the list of organizations that can create and join application channels. Because some aspects of the configuration of application channels are inherited by default from the system channel (certain capability levels, for example), it is the job of ordering service admins to establish these defaults.
Save the following example app YAML as a file on your local machine called app.yaml. In this example, the nodeAffinity spec ensures that this pod is only scheduled to a worker node with the specified label.

apiVersion: v1
kind: Pod
metadata:
name: app
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: storage Enter the 'key' of the worker node label created earlier.
operator: In
values:
- local-block Enter the 'value' of the worker label that you created earlier.
containers:
- name: nginx
image: nginx
volumeDevices:
- name: data
devicePath: "/dev/nvme2n1" Enter the path to your local device.
volumes:
- name: data
persistentVolumeClaim:
claimName: local-pvc
Show more
5. Create the app pod in your cluster.

oc create -f app.yaml
6. Log in to your app pod and verify that you can write to your local disk.

kubectl exec <pod_name> -it bash
7. Change directories to the dev folder.

cd dev
8. Run the ls -lR <device-path> command to verify your device details and that your app pod can has read and write permissions to your block device which is indicated by brw in the command output.

ls -lR /dev/nvme2n1

Example output

brw-rw-rw-. 1 root disk 202, 32 Mar 3 21:24 /dev/nvme2n1
9. Optional Run the following commands to write data to your block device.



1. Write "block_data" to the local storage device that you mounted to your app. Replace <device-path> with the path to your storage device.
Component Previous Current Description 

 RHEL 7 Packages N/A N/A Package updates. 
 Red Hat OpenShift on IBM Cloud. 4.8.35 4.8.37 For more information, see the [change log](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-37). 







 Change log for worker node fix pack 4.8.35_1553_openshift, released 11 April 2022 

The following table shows the changes that are in the worker node fix pack 4.8.35_1553_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.8.35_1550_openshift

 Component Previous Current Description 

 RHEL Packages 3.10.0-1160.59.1 3.10.0-1160.62.1 Kernel and package updates for [CVE-2021-45960](https://nvd.nist.gov/vuln/detail/CVE-2021-45960), [CVE-2021-46143](https://nvd.nist.gov/vuln/detail/CVE-2021-46143), [CVE-2022-22822](https://nvd.nist.gov/vuln/detail/CVE-2022-22822), [CVE-2022-22823](https://nvd.nist.gov/vuln/detail/CVE-2022-22823), [CVE-2022-22824](https://nvd.nist.gov/vuln/detail/CVE-2022-22824), [CVE-2022-22825](https://nvd.nist.gov/vuln/detail/CVE-2022-22825), [CVE-2022-
Red Hat OpenShift on IBM Cloud toolkit 4.6.0+20211109 4.6.0+20211201 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20211201). 







 Change log for worker node fix pack 4.6.49_1566_openshift, released 6 December 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.6.49_1566_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.6.49_1564_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.45 3.10.0-1160.49 Updated worker node images and kernel with package updates. Contains fixes for [CVE-2020-36385](https://nvd.nist.gov/vuln/detail/CVE-2020-36385), [CVE-2021-37750](https://nvd.nist.gov/vuln/detail/CVE-2021-37750), [CVE-2021-41617](https://nvd.nist.gov/vuln/detail/CVE-2021-41617), [CVE-2021-20271](https://nvd.nist.gov/vuln/detail/CVE-2021-20271)"{: external}. 







 Change log for worker node fix pack 4.6.49_1564_openshift, released 22 November 2021 

The following table shows the changes that are in the worker node fix pack patch update 4.6.49_1564_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.6.49_1562_openshift

 Component Previous Current Description
* UI
* CLI
* API
* Terraform







 Creating snapshots 

With the UI, CLI, API, or Terraform you can create a snapshot of a Block Storage for VPC volume that is attached to a virtual server instance. You can create a snapshot of a boot or a data volume. If the volume is not attached to a server instance, you can't create a snapshot of it.

Before you take a snapshot, make sure that all cached data is present on disk, especially when you're taking a snapshot of instances with Windows and Linux® operating systems. For example, on Linux® operating systems, run the sync command to force an immediate write of all cached data to disk.



 Creating a snapshot in the UI 

In the console, you can create a snapshot of a Block Storage for VPC volume that is attached to a running virtual server instance.



1. You can access the Block storage snapshot for VPC provisioning screen in the [IBM Cloud® console](https://cloud.ibm.com/login) in multiple ways.



* From the [Block storage snapshots for VPC](https://cloud.ibm.com/vpc-ext/storage/snapshots) list,



1. Go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage snapshots.
2. From the list of snapshots that is initially empty, click Create.



* From the [Block storage volumes for VPC](https://cloud.ibm.com/vpc-ext/storage/storageVolumes) list,



1. Go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. From the list of volumes, locate a boot or data volume that is attached to an instance.
3.
Consenter set 

The ordering service nodes actively participating in the ordering process on a channel. These nodes are also known as "consenters."





 Console 

The name of the user interface in the IBM Blockchain Platform. The console allows users to view, create, and manage their deployments. Because the public and private keys are only stored locally in the browser the console runs on, users maintain total control over their keys.





 Consortium 

The group of non-orderer organizations listed on the orderer system channel. The following lines do not apply to orderers that do not use a system channel: These are the only organizations that can create channels. At channel creation time, all organizations added to the channel must be part of a consortium. However, an organization that is not defined in a consortium may be added to an existing channel. While a blockchain network can have multiple consortia, most blockchain networks have a single consortium.





 CouchDB 

A document store that can be used as the state database of your peers. Using CouchDB allows you to use rich queries and deploy indexes with your smart contract.





 Current state 

The current state of the ledger represents the latest values for all keys that are ever included in its chain transaction log. Because current state represents all latest key values known to the channel, it is sometimes referred to as the world state. Smart contracts execute transaction proposals against current state data. The current state changes every time when the value of a key changes or a new key is added and is critical to a transaction flow because the latest key-value pair must be known before it can be changed. Peers commit the latest values to the current state of the ledger for each valid transaction in a block. The current state is stored the state database associated with a peer.





 Dynamic membership 

A member can be dynamically added to the network by a user with registrar privilege. Members are also assigned roles and attributes, which control their access and authority on the network. Neither roles nor attributes can be assigned dynamically though. Hyperledger Fabric supports the addition or removal of members, peers, and ordering service nodes, without compromising the operations of the overall network. Dynamic membership is critical when business relationships adjust and entities need to be added or removed for various reasons.
RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898). 
 RHEL 8 Packages N/A N/A Worker node package updates for [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898). 
 Red Hat OpenShift on IBM Cloud. 4.10.41 4.10.43 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-43). 
 HAProxy c619f4 508bf6 [CVE-2016-3709](https://nvd.nist.gov/vuln/detail/CVE-2016-3709), [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898), [CVE-2022-1304](https://nvd.nist.gov/vuln/detail/CVE-2022-1304). 







 Change log for worker node fix pack 4.10.41_1546_openshift, released 21 November 2022 

The following table shows the changes that are in the worker node fix pack 4.10.41_1546_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.10.39_1543_openshift

 Component Previous Current Description
Red Hat OpenShift on IBM Cloud toolkit 4.5.0+20210329 4.5.0+20210512 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.5.0+20210512)). 







 Change log for worker node fix pack 4.5.38_1538_openshift, released 10 May 2021 

The following table shows the changes that are in the worker node fix pack 4.5.38_1538_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.5.37_1537_openshift

 Component Previous Current Description 

 Red Hat OpenShift 4.5.37 4.5.38 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.htmlocp-4-5-38).<br><br>Configured worker nodes to integrate with a newer version of the NVIDIA GPU operator. Now when you create an instance of the ClusterPolicy for the GPU operator, you must enter 450.80.02 for the Driver Config version. 
 RHEL 7 Packages 3.10.0-1160.24 3.10.0-1160.25 To increase resiliency, rsyslog no longer keeps old file descriptors. Updated worker node images with kernel and package updates for [CVE-2021-25215](https://nvd.nist.gov/vuln/detail/CVE-2021-25215), [CVE-2020-25692](https://nvd.nist.gov/vuln/detail/CVE-2020-25692), and [CVE-2020-25648](https://nvd.nist.gov/vuln/detail/CVE-2020-25648).
Kubernetes NodeLocal DNS cache 1.16.0 1.17.1 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.17.1). 







 Change log for worker node fix pack 1.20.5_1534, released 29 March 2021 

The following table shows the changes that are in the worker node fix pack 1.20.5_1534. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.20.4_1532

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-136-generic 4.15.0-140-generic Updated worker node images with kernel and package updates for [CVE-2020-27170](https://nvd.nist.gov/vuln/detail/CVE-2020-27170), [CVE-2020-27171](https://nvd.nist.gov/vuln/detail/CVE-2020-27171), [CVE-2021-27363](https://nvd.nist.gov/vuln/detail/CVE-2021-27363), [CVE-2021-27365](https://nvd.nist.gov/vuln/detail/CVE-2021-27365), [CVE-2021-28153](https://nvd.nist.gov/vuln/detail/CVE-2021-28153), and [CVE-2021-3449](https://nvd.nist.gov/vuln/detail/CVE-2021-3449).
* How do I run Red Hat OpenShift Container Platform (OCP) on Power Systems Virtual Servers?

You can find a complete tutorial at the IBM Developer site: [Deploying Red Hat OpenShift Container Platform 4.x on IBM Power Systems Virtual Servers](https://developer.ibm.com/series/deploy-ocp-cloud-paks-power-virtual-server/).
* What is the network latency over Direct Link?

Network latency over Direct link is less than 1 millisecond in every location. To know more about network latency, see [Understanding latency](https://cloud.ibm.com/docs/dl?topic=dl-understanding-latency).
* Are we notified about any planned maintenance activities?

For planned maintenance and disruptive changes, the Power Systems Virtual Server operations team sends you notifications at least 7 days in advance. Watch the Notifications space in the IBM Cloud dashboard for these alerts. You can receive a copy of these notifications directly in your inbox if your email is subscribed for notifications.
* How do I convert existing volumes to replication enabled volumes?

You can retype the volume to toggle the replicationEnable flag of the volume using [Perform an action on a Volume](https://cloud.ibm.com/apidocs/power-cloudpcloud-cloudinstances-volumes-action-post) request. This is possible only when the volume pool of existing volume supports replication.
* How can I check whether volume is already replication enabled?

You need to check the replicationEnabled attribute of the volume. A volume is replicationEnabled when it is true.
* How can I check whether volume is master or auxiliary volume?

Volume is auxiliary when isAuxiliary field of volume is true. When replicationEnabled is true and isAuxiliary is false then volume is a master volume.
* How can I check the serial number of my virtual server instance?

The serial number is available after you deploy your virtual server instance and you can choose to display the serial number system value.

You must pin the IBM i virtual server instances that use the IBM i licenses.
This tutorial focuses on using the High-level Fabric Gateway SDKs.

IBM recommends the High-level Fabric Gateway SDKs which allow client applications to interact with IBM Blockchain Platform networks. These SDKs, available for Node, Java, and Go, allow a client application to invoke smart contracts for the purpose of submitting transactions and evaluating queries. It is recommended that administrative tasks, such as creating channels, deploying smart contracts, are done by using the console, APIs, or Ansible scripts.

The SDKs use the concept of a "Gateway" object to represent the connection of a single identity (user) to a blockchain network. For performance reasons, applications need to keep a gateway object instance in scope for as long as it is required, and can use it to submit multiple transactions across different smart contracts and network channels. If an application needs to handle multiple user identities, then a separate gateway object instance should be maintained for each identity.

Refer to the SDK documentation for each language for details:



* [Java](https://hyperledger.github.io/fabric-gateway-java/release-2.2/)
* [Node](https://hyperledger.github.io/fabric-sdk-node/release-2.2/)
* [Go](https://pkg.go.dev/github.com/hyperledger/fabric-sdk-go/pkg/gateway)



For best practices and examples of how to use the SDKs see the Fabric [Asset Transfer Sample](https://github.com/hyperledger/fabric-samples/tree/master/asset-transfer-basic)

For information about migrating your applications created using the v1.4 SDK to the 2.x SDK, check out [Migrating client applications from v1.4 to v2.0](https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-migration.html).
(https://access.redhat.com/solutions/41899)
* Microsoft® Windows®: [NIC Teaming and ISCSI](https://social.technet.microsoft.com/Forums/en-US/441d2157-119d-4b1e-b40c-1aa3670e44a6/nic-teaming-and-iscsi?forum=winserverhyperv).
* VMware®: [Host requirements for link aggregation](https://kb.vmware.com/s/article/1001938?lang=en_US) or [iSCSI and LAG/LACP](https://core.vmware.com/blog/iscsi-and-laglacp).







 What latency can be expected from the Block Storage for Classic? 

Target latency within the storage is <1 ms. The storage is connected to compute instances on a shared network, so the exact performance latency depends on the network traffic during the operation.





 I ordered a Block Storage for Classic LUN in the wrong data center. Is it possible to move or migrate storage to another data center? 

You need to order new Block Storage for Classic in the correct data center, and then cancel the Block Storage for Classic device that you ordered in the wrong location. When the volume is canceled, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. Billing for the volume stops immediately. When the reclaim period expires, the data is destroyed and the volume is removed from the console, too.





 How can we tell which Block Storage for Classic volumes are encrypted? 

When you look at your list of Block Storage for Classic in the [IBM Cloud® console](https://cloud.ibm.com/login), you can see a lock icon next to the volume name for the LUNs that are encrypted.





 How do we know when we're provisioning Block Storage for Classic in an upgraded data center?