vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Red Hat OpenShift on IBM Cloud toolkit 4.8.0+20220412 4.8.0+20220509 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20220509). 







 Change log for worker node fix pack 4.8.39_1557_openshift, released 23 May 2022 

The following table shows the changes that are in the worker node fix pack 4.8.39_1557_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.39_1556_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.62.1 3.10.0-1160.66.1 Worker node kernel & package updates for [CVE-2018-25032](https://nvd.nist.gov/vuln/detail/CVE-2018-25032), [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271), [CVE-2022-0492](https://nvd.nist.gov/vuln/detail/CVE-2022-0492). 
 HA proxy 36b0307 468c09 [CVE-2021-3634](https://nvd.nist.gov/vuln/detail/CVE-2021-3634). 







 Change log for worker node fix pack 4.8.39_1556_openshift, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 4.8.39_1556_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.37_1555_openshift
Red Hat OpenShift on IBM Cloud toolkit 4.8.0+20220712 4.8.0+20220816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20220816). 







 Change log for worker node fix pack 4.8.47_1570_openshift, released 29 August 2022 

The following table shows the changes that are in the worker node fix pack 4.8.47_1570_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.47_1568_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-2526](https://nvd.nist.gov/vuln/detail/CVE-2022-2526). 
 Red Hat OpenShift on IBM Cloud. N/A N/A N/A 
 HAProxy 6514a2 c1634f [CVE-2022-32206](https://nvd.nist.gov/vuln/detail/CVE-2022-32206), [CVE-2022-32208](https://nvd.nist.gov/vuln/detail/CVE-2022-32208) 







 Change log for worker node fix pack 4.8.47_1568_openshift, released 16 August 2022 

The following table shows the changes that are in the worker node fix pack 4.8.47_1568_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.46_1567_openshift

 Component Previous Current Description
--wait WAIT
: Wait and track the progress of the Schematics workspace job. If true, installation waits. If false, the software installs immediately. Default is true.

--workspace-name NAME (optional)
: Provide a workspace name. Default is OfferingName-Date.

--workspace-tags TAGS (optional)
: Provide a comma-separated list of tags.

--workspace-tf-version VERSION (optional)
: Provide a workspace terraform version.

--workspace-region REGION (optional)
: Provide a workspace region.

--workspace-rg-id ID (optional)
: Provide a workspace resource group ID.

--schematics-delete VALUE (optional)
: Provide this flag to delete the Schematics workspace after validation and installation.







 ibmcloud catalog utility netrc 

Run the following command to create a .netrc file, generate the machine name in your .netrc file, or update the credential in your .netrc file. A .netrc file stores the required login information that is needed to use Terraform modules from the IBM Cloud catalog.

By running this command, you configure a .netrc file for the machine name cm.globalcatalog.cloud.ibm.com with iamtoken as the username and your IAM token as the password.

You need version 1.2.7 or higher of the catalogs management CLI plug-in to run the .netrc command.

ibmcloud catalog utility netrc





 ibmcloud catalog utility update-module-references 

Run the following command to check your working directory's Terraform modules for updates from the catalog and update the source attribute to the latest version. The README.md is also updated.

ibmcloud catalog utility update-module-references





 ibmcloud catalog offering unpublish account 

Run the following command to unpublish a product from your account. After the product is unpublished, users in your account cannot create an instance of the product.

ibmcloud catalog offering unpublish account [--catalog CATALOG]



 Command options
For the purposes of this overview, we focus just on certificate authorities (CAs), orderers, peers, smart contracts, and applications. As you can see from the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network), this sequence is not arbitrary; it reflects the proper order in which components in a network based on Fabric are deployed.



 Peers 

At a conceptual level, a blockchain network is comprised mainly of organizations (as organizations decide on how a network is structured, as well as owning nodes and managing identities). At a physical level, however, a blockchain network is comprised primarily of peer nodes that are owned and administered by organizations. Peers are the fundamental elements of the network because they host ledgers and smart contracts (which are contained in [chaincode](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/chaincodenamespace.html)), and are therefore where transactions are executed and validated.

More accurately, the peer hosts instances of the ledger, and instances of smart contracts. Because smart contracts and ledgers are used to encapsulate the shared processes and shared information in a network, these aspects of a peer make them a good starting point to understand what a Fabric network does.

To learn more about peers specifically, check out [Peers](https://hyperledger-fabric.readthedocs.io/en/release-2.2/peers/peers.html) from the Fabric community documentation.

The IBM Blockchain Platform console allows you to create peers, join them to channels, create anchor peers, install smart contracts, and seamlessly upgrade your peers.





 Certificate Authorities (CAs) 

You can think of a blockchain network as a series of managed interactions between nodes to serve a defined business use case. For these interactions to be verifiable (to ensure, in other words, who is who) requires identities and a system of permissions that can be checked during each interaction. You can think of the kind of identity that is needed as being similar to a credit card in that it identifies someone within a particular context.
What is network segmentation and how can I set it up for a Classic cluster? 

Network segmentation describes the approach to divide a network into multiple subnetworks. You can group apps and related data to be accessed by a specific group in your organization. Apps that run in one subnetwork can't see or access apps in another subnetwork. Network segmentation also limits the access that is provided to an insider or third-party software and can limit the range of malicious activities.

Red Hat OpenShift on IBM Cloud provides IBM Cloud VLANs that ensure quality network performance and network isolation for worker nodes. A VLAN configures a group of worker nodes and pods as if they were attached to the same physical wire. VLANs are dedicated to your IBM Cloud account and not shared across IBM customers. In classic clusters, if you have multiple VLANs for your cluster, multiple subnets on the same VLAN, or a multizone classic cluster, you must enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so your worker nodes can communicate with each other on the private network. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning). To perform this action, you need the Network > Manage Network VLAN Spanning[infrastructure permission](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_access), or you can request the account owner to enable it.
An addressing method that is used to enable one IP address to communicate with several other IP addresses, such as those on a private subnet, by means of a lookup table. Network address translation has two main types: 1-to-1 and many-to-1.





 Network File System (NFS) 

A protocol that allows a computer to access files over a network as if they were on its local disks.





 NFS 

See [Network File System](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2031282).





 NLP 

See [natural language processing](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2031058).





 node 



* A member of a cluster that runs as a container or virtual machine on shared hardware.
* A physical component of the blockchain network infrastructure, namely a peer, Certificate Authority (CA), or ordering node.









 O 



 OAuth 

An HTTP-based authorization protocol that gives applications scoped access to a protected resource on behalf of the resource owner, by creating an approval interaction between the resource owner, client, and resource server.





 OCI container image 

A container image that is compliant with the OCI Image Format Specification





 on-prem 

See [on-premises](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4561212).





 on-premises (on-prem) 

Pertaining to software that is installed and run on the local computers of a user or organization.





 ontology 

An explicit formal specification of the representation of the objects, concepts, and other entities that can exist in some area of interest and the relationships among them.





 orderer node 

See [ordering node](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9884023).





 ordering node 

A node that collects transactions from network members, orders the transactions and bundles them into blocks.





 ordering service 

A service that provides a shared communication channel to clients and peers for the broadcast of messages that contain transactions.





 org
* UI
* CLI
* Terraform







 Mount iSCSI LUN on Ubuntu 20 

This tutorial guides you through how to mount a IBM Cloud® Block Storage for Classic volume on a server with the Ubuntu 20.04 Server Edition operating system. Complete the following steps to connect a Linux®-based IBM Cloud® Compute instance to a multipath input/output (MPIO) iSCSI storage volume. You're going to create two connections from one network interface of your host to two target IP addresses of the storage array.

If multiple hosts mount the same Block Storage for Classic volume without being cooperatively managed, your data is at risk for corruption. Volume corruption can occur if changes are made to the volume by multiple hosts at the same time. You need a cluster-aware, shared-disk file system to prevent data loss such as Microsoft® Cluster Shared Volumes (CSV), Red Hat Global File System (GFS2), VMware® VMFS, and others. For more information, see your host's OS Documentation.

It's best to run storage traffic on a VLAN, which bypasses the firewall. Running storage traffic through software firewalls increases latency and adversely affects storage performance. For more information about routing storage traffic to its own VLAN interface, see the [FAQs](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqshowtoisolatedstorage).

Before you start configuring iSCSI, make sure to have the network interfaces correctly set and configured in order for the open-iscsi package to work correctly, especially during startup time. In Ubuntu 20.04 LTS, the default network configuration tool is [netplan.io](https://netplan.readthedocs.io/en/latest/examples/). For more information about how the ISCSI service works on the Ubuntu OS, see [iSCSI Initiator (or Client)](https://ubuntu.com/server/docs/service-iscsi) Documentation.
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.9.51 4.9.52 For more information, see the [change log](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-52). 
 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.9.51_1566_openshift, released 21 November 2022 

The following table shows the changes that are in the worker node fix pack 4.9.51_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.9.51_1563_openshift

 Component Previous Current Description
- Isolating networking workloads to edge nodes in classic gateway-enabled clusters - Flow of traffic to apps when using an [NLB 1.0](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer-about), an [NLB 2.0](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer-about), or Ingress ALBs.
: Ready to get started? [Create a standard classic cluster with a gateway in the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-classic&interface=ui).

Version change logs
: Patch updates are available for Kubernetes [1.15.4_1518](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog1154_1518), [1.14.7_1534](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1147_1534), [1.13.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11311_1537), and [1.12.10_1568](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog11210_1568_worker).







 September 2019 



 27 September 2019 

IBM Cloud Object Storage supported in VPC clusters
: You can now provision IBM Cloud Object Storage for your apps that run in a VPC cluster. For more information, see [Setting up IBM Cloud Object Storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-cos-understand).





 24 September 2019 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 0.4.31](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog).

Ingress ALB change log
Updated image for [CVE-2021-22946](https://nvd.nist.gov/vuln/detail/CVE-2021-22946). 
 Konnectivity agent v0.0.24_262_iks v0.0.24_268_iks Update to use Go version 1.16.9. 
 Konnectivity server v0.0.24_262_iks v0.0.24_268_iks Update to use Go version 1.16.9. 
 Kubernetes v1.21.5 v1.21.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.21.6). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1547 1590 Updated to use Go version 1.16.9. 







 Change log for worker node fix pack 1.21.5_1538, released 10 November 2021 

The following table shows the changes that are in the worker node fix pack patch update 1.21.5_1538. 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.21.5_1537

 Component Previous Current Description
Fixed a bug in VPC load balancer creation when the cluster, VPC, or subnet are in a different resource group. 
 IBM Cloud File Storage for Classic monitor 379 384 Updated to use Go version 1.15.5 and to run as a non-root user. Updated image to implement additional IBM security controls. 
 IBM Cloud File Storage for Classic plug-in 379 384 Updated to use Go version 1.15.5 and to run with a least privileged security context. Updated image to implement additional IBM security controls. 
 IBM Cloud RBAC Operator 197bc70 c148a8a Updated to use Go version 1.15.6 and updated image to implement additional IBM security controls. 
 Key management service (KMS) provider v2.0.5 v2.0.7 Updated image to implement additional IBM security controls. 
 Kubernetes v1.18.12 v1.18.13 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.13). 
 Kubernetes NodeLocal DNS cache N/A N/A Updated the NodeLocal DNS cache configuration to support [customizing the node-local-dns config map](https://cloud.ibm.com/docs/containers?topic=containers-cluster_dnsdns_nodelocal_customize). 
 Load balancer and load balancer monitor for IBM Cloud Provider 208 1004 Updated Alpine base image to version 3.12 and to use Go version 1.15.5. Updated image for [CVE-2020-8037](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8037) and [CVE-2020-28928](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28928). Updated image to implement additional IBM security controls. 
 Operator Lifecycle Manager N/A N/A Updated to run as a non-root user.
* Use IBM® Secure Gateway for IBM Cloud® to maintain secure connections to existing on-premises databases.







 Step 2: Use secure and performance driven compute 



* ML apps that require higher-performing compute are hosted on Red Hat OpenShift on IBM Cloud on Bare Metal. This ML cluster is centralized, so each regional cluster doesn't have the expense of bare metal workers; Kubernetes deployments are easier too.
* Vulnerability Advisor provides image, policy, container, and packaging scanning vulnerability scanning.







 Step 3: Ensure global availability 



* After Developers build and test the apps in their Development and Test clusters, they use the IBM CI/CD toolchains to deploy apps into clusters across the globe.
* Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workload within each geographic region, including self-healing and load balancing.
* With the toolchains and Helm deployment tools, the apps are also deployed to clusters across the globe, so workloads and data meet regional regulations.







 Step 4: Data sharing 



* IBM Cloudant is a modern NoSQL database suitable a range of data-driven use cases from key-value to complex document-oriented data storage and query.
* To minimize queries to the regional databases, IBM Cloudant is used to cache the user's session data across apps.
* This choice improves the front-end app usability and performance across apps on Red Hat OpenShift on IBM Cloud.
* While worker apps in Red Hat OpenShift on IBM Cloud analyze on-premises data and store results in IBM Cloudant, IBM Cloud® Functions reacts to changes and automatically sanitizes data on the incoming feeds of data.
* Similarly, notifications of research breakthroughs in one region can be triggered through data uploads so that all researchers can take advantage of new data.









 Results 



* Microservices greatly reduce time to delivery for patches, bug fixes, and new features. Initial development is fast, and updates are frequent.
* Researchers have access to clinical data and can share clinical data, while they comply with local regulations.
* Patients who participate in disease research feel confident that their data is secure and making a difference, when it is shared with large research teams.
App Configuration server SDK for Node 

App Configuration service provides SDK to integrate with your Node.js microservice or application.

Version v0.4.0 has changes to the return value of getCurrentValue method. Hence, if you are already using a version lesser than v0.4.0, read the [migration guide](https://github.ibm.com/devx-app-services/appconfiguration-node-sdk/blob/development/docs/v0.3-v0.4.md) before you upgrade the SDK to latest.



 Integrating server SDK for Node 

App Configuration service provides SDK to integrate with your Node.js microservice or application. You can evaluate the values of your feature flag and property by integrating the App Configuration SDK.



1. Install the SDK. Use the following code from the npm registry.

npm install ibm-appconfiguration-node-sdk@latest
2. In your Node.js microservice, include the SDK module with:

const {
AppConfiguration
} = require('ibm-appconfiguration-node-sdk');
3. Initialize the sdk to connect with your App Configuration service instance.

const region = AppConfiguration.REGION_US_SOUTH;;
const guid = '<guid>';
const apikey = '<apikey>';

const collectionId = '<collectionId>';
const environmentId = '<environmentId>';

const appConfigClient = AppConfiguration.getInstance();
appConfigClient.init(region, guid, apikey)
appConfigClient.setContext(collectionId, environmentId)

Where:



* region: Region name where the App Configuration service instance is created.
Red Hat OpenShift on IBM Cloud toolkit 4.6.0+20220712 4.6.0+20220816 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.6.0+20220816). 







 Change log for worker node fix pack 4.6.60_1596_openshift, released 29 August 2022 

The following table shows the changes that are in the worker node fix pack 4.6.60_1596_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.60_1594_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A Worker node package updates for [CVE-2022-2526](https://nvd.nist.gov/vuln/detail/CVE-2022-2526). 
 Red Hat OpenShift on IBM Cloud. N/A N/A N/A 
 HAPROXY 6514a2 c1634f [CVE-2022-32206](https://nvd.nist.gov/vuln/detail/CVE-2022-32206), [CVE-2022-32208](https://nvd.nist.gov/vuln/detail/CVE-2022-32208) 







 Change log for worker node fix pack 4.6.60_1594_openshift, released 16 August 2022 

The following table shows the changes that are in the worker node fix pack 4.6.60_1594_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.60_1593_openshift

 Component Previous Current Description