vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Simplified DevOps allows you to move from development to test to production in a single environment by scaling up your Kubernetes resources to add more components.
* Up-to-date Fabric key features. Choose which version of Hyperledger Fabric you want to use when deploying peers or ordering nodes. Leverage the latest features of Hyperledger Fabric v2.2.10:



* [Smart contract lifecycle](https://hyperledger-fabric.readthedocs.io/en/release-2.2/chaincode_lifecycle.html)
* [Raft ordering service](https://hyperledger-fabric.readthedocs.io/en/release-2.2/orderer/ordering_service.htmlraft)
* [Private data collections](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-private-data) that provide increased data privacy by ensuring that ledger data is shared to only authorized peers via the gossip protocol.
* [Fabric Node OUs](https://hyperledger-fabric.readthedocs.io/en/release-2.2/membership/membership.htmlnode-ou-roles-and-msps)
* [Service discovery](https://hyperledger-fabric.readthedocs.io/en/release-2.2/discovery-overview.html), allowing you to dynamically discover and update how your application interacts with your network.
* [Channel access control lists](https://hyperledger-fabric.readthedocs.io/en/release-2.2/access_control.html) that allow you additional control of the governance of your channels and smart contracts.





OPERATE --- Total control of your deployments



* Host or join a network. Deploy peers that are hosted in your cluster to multiple channels on multiple clouds, or invite other organizations to join your consortium or channels while the organizations manage their nodes independently across infrastructures.
* Maintain complete control of your identities. Store and manage the keys that are used to administer your nodes.
About Slurm 

Slurm on IBM Cloud allows you to deploy high-performance computing (HPC) clusters that use the [Slurm Workload Manager](https://github.com/SchedMD/slurm) as HPC scheduling software. This offering uses open source Terraform-based automation to provision and configure IBM Cloud VPC resources that make up the cluster. With simple steps to define configuration properties and use automated deployment, you can build your own HPC cluster in minutes by using your choice of an Intel x86 based [VPC virtual server instance profile type](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=ui) for the worker nodes in the cluster.

Slurm on IBM Cloud supports three interface types for its use: UI, API, and CLI. The UI involves use of [IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started) workspaces. To use the Schematics API and CLI interfaces, the Terraform-based automation code is available in this [public GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-slurm).

The offering enables the initial Slurm-based HPC cluster creation. Any updates that are needed post-deployment regarding Slurm configuration or setup should be performed by using Slurm tools and commands. If you use the Schematics interface to make changes to configuration properties and reapply those changes, you can cause disruptions to the running Slurm cluster. Restoring it back to a working state might not be easy.



  Architecture diagram 

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/b9d02b1a54126fa7ec9db9b74305602ca804fca7/hpc-slurm/images/6547a000-51eb-11ec-9d0c-2f3bcee6ceb8.png)

Figure 1. Architecture diagram of a Slurm cluster on IBM Cloud
FAQs for Citrix Netscaler VPX 

The frequently asked questions in this topic will help you when working with the Citrix Netscaler VPX.



 What is Citrix Netscaler VPX? 

Citrix NetScaler is an application delivery controller that makes applications five times better by accelerating performance, ensuring application availability and protection and substantially lowering operational costs. Choose the best Citrix NetScaler edition that meets your application requirements, and deploy it on the appropriate dedicated system for your performance needs. To learn more about Citrix NetScaler, refer to the [NetScaler page](http://www.citrix.com/products/netscaler-application-delivery-controller/overview.html) on the Citrix website.





 Why is load balancing needed? 

Load balancing traffic has become a key aspect of many customer implementations as it distributes application requests and loads over multiple servers. It also provides a number of benefits to the overall topology including:



* Security. Logical isolation of the application servers is created or traffic requests denied based on IP protocols and port numbers.
* High-availability. Content is replicated to a pool, or group of servers, guaranteeing its availability to hosts.
* Scalability. Additional servers can be added as demand increases, enabling the load balancer to distribute the workload over the additional servers.
* Efficiency. Workloads are dynamically distributed when load balancing is configured. For example, resources like CPUs can be used in a more efficient ways.







 How many load balancing options are available in IBM Cloud? 

For a detailed comparison of the IBM© Load Balancer offerings, refer to [Explore Load Balancers](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-explore).





 Does NetScaler support IPv6? 

Yes. Both IPv6 and IPv4 are supported on the IBM Cloud public network.





 Will the NetScaler load balance traffic on the private network? 

Yes, the NetScaler is the only IBM Cloud load balancing product that extends into the private network.
When a worker node is removed or re-created, a new public and a new private IP address are assigned to the worker node.

NodePorts are ideal for testing public or private access or providing access for only a short amount of time. Note: Because worker nodes in VPC clusters don't have a public IP address, you can access an app through a NodePort only if you are connected to your private VPC network, such as through a VPN connection.

Zoom

![How Kubernetes forwards traffic through a NodePort service](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/nodeport.svg)

How Kubernetes forwards public network traffic through a NodePort service.





 LoadBalancer 

The LoadBalancer service type is implemented differently depending on your cluster's infrastructure provider.



 LoadBalancer services in Classic clusters 

Classic infrastructure

[Network load balancer (NLB)](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer). Every standard cluster is provisioned with four portable public and four portable private IP addresses that you can use to create a layer 4 TCP/UDP network load balancer (NLB) for your app. You can customize your NLB by exposing any port that your app requires. The portable public and private IP addresses that are assigned to the NLB are permanent and don't change when a worker node is re-created in the cluster. You can create a subdomain for your app that registers public NLB IP addresses with a DNS entry. You can also enable health check monitors on the NLB IPs for each subdomain.

Zoom

![LoadBalancer service traffic in Classic clusters](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/containers/images/classic-nlb-sz.svg)
Adding and removing ordering service nodes 

In this tutorial, we'll talk about the process for creating ordering nodes to add to an existing ordering service and to existing channels. This will cover the instructions for adding nodes using the same organization that created the ordering service as well as the steps when using a separate ordering organization that is added as an ordering service admin.

Because ordering nodes that use a system channel can only belong to a single ordering service, if you create an ordering service node from the main Nodes panel, you will not be able to add it to an existing ordering service. If you want to add a node to an existing ordering service, the node must be created specifically for that purpose using the process described below. Also, be aware that adding nodes to an ordering service does not automatically add them to any existing channel. That is a separate process that must take place after the node has been added to the ordering service. For more information, see [Adding and removing ordering service consenters](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenters-add).



 Number of ordering nodes 

While it's technically possible to build a configuration of any number of ordering nodes (no configuration is explicitly restricted), some numbers provide a better balance between cost and performance than others. The reason for this lies in satisfying the needs of high availability (HA) and in understanding the Raft concept of the "quorum", the minimum number of nodes that must be available (out of the total number) for the ordering service to process transactions.

In Raft, a majority of the total number of nodes is needed to form a quorum. In other words, if you have one node, you need that node available to have a quorum, because the majority of one is one. Similarly, if you have two nodes, you will need both available, since the majority of two is two (for this reason, a configuration of two nodes is discouraged; there is no advantage to a two node configuration). In a similar vein, the majority of three is two, the majority of four is three, the majority of five is three, and so on.
Go to My Entitled Software > IBM i evaluation and NLV download.
4. Find the required software that you can download, install, and use. For example:

Web Enablement for i (5722-WE2) - WebSphere Express V8.5.5 Web Enablement for i (5733-WE3) - WebSphere V9







 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.
For more information about namespaces, see [Managing namespaces](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces).



 Step 1: Create the cos-access actioncos-access action 

The cos-access action is a Node.js program that simulates code to access IBM Cloud Object Storage by setting a timeout that resolves after 10 seconds.



1. Go to the [Create page](https://cloud.ibm.com/functions/create) in the Cloud Functions console.
2. Select Action.
3. Create the cos-access action:



1. Name your action cos-access.
2. Click Create Package. Name your package action-tutorial and click Create.
3. Select Node.js 10 for the runtime.
4. Click Create.
5. Paste in the following code example:

/
* main() will be run when you invoke this action
* @param Cloud Functions actions accept a single parameter, which must be a JSON object.
* @return The output of this action, which must be a JSON object.
/
function main(params) {
return new Promise((resolve, reject) => {
// simulate a COS access by resolving after 10s
setTimeout(() => {
console.log('fake COS bucket access done. Resolving Promise...');
resolve({ cos_message: 'SUCCESS'});
}, 10000);
});
}
Show more
6. Click Save.
7. Test your action by clicking Invoke and waiting for the following output to display.

Example output

Results:
{
"cos_message": "SUCCESS"
}

Logs:
[
"2020-04-21T01:51:49.464941Z stdout: fake COS bucket access done. Resolving Promise..."
[Serverless web app and eventing for data retrieval and analytics](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-github-traffic-analytics)Serverless web app and eventing for data retrieval and analytics

In this tutorial, you create an application to automatically collect GitHub traffic statistics for repositories and provide the foundation for traffic analytics. GitHub only provides access to the traffic data for the last 14 days. If you want to analyze statistics over a longer period of time, you need to download and store that data yourself. In this tutorial, you deploy a serverless app in a IBM Cloud Code Engine project. The app manages the metadata for GitHub repositories and provides access to the statistics for data analytics. The traffic data is collected from GitHub either on-demand in the app or when triggered by Code Engine events, e.g., daily. The app discussed in this tutorial implements a multi-tenant-ready solution with the initial set of features supporting a single-tenant mode.

Code Engine Db2 on Cloud

+1

App ID



* 1 hour
* 2023-06-16



[Serverless web application and API with Code Engine](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-webapp)Serverless web application and API with Code Engine

In this tutorial, you will create a serverless web application using a bucket in Object Storage and implementing the application backend using IBM Cloud Code Engine and IBM Cloudant as JSON document database.

Code Engine Cloudant

+1

Object Storage



* 1 hour
* 2023-06-16



[Build a database-driven Slackbot](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-slack-chatbot-database-watson)Build a database-driven Slackbot

In this tutorial, you are going to build a Slackbot which allows to search and create entries in a backend Db2 on Cloud database. The Slackbot is backed by the IBM Watson® Assistant service.
<br> <br>For more information, see [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 



A successful GET api/v2/keys/<keyID_or_alias>/actions/sync request returns an HTTP 204 No Content response, which indicates that the IBM cloud service that is associated with the specified key has been notified.





 Synchronization considerations 

The sync API can only be initialized if it has been longer than an hour since the last notification to the associated cloud services of the key. If you send a request to this API and the key has been synced or a key lifecycle action has been taken within the past hour, the API will return a 409 Conflict response.

You can [view associated resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources) to determine which services are relevant to synchronization.
Calico configuration N/A N/A Updated the calico-node daemon set in the kube-system namespace to set the spec.updateStrategy.rollingUpdate.maxUnavailable parameter to 10% for clusters with more than 50 worker nodes. 
 Cluster health image v1.1.11 v1.1.12 Updated to use Go version 1.15.2. 
 Gateway-enabled cluster controller 1082 1105 Updated to use Go version 1.15.2. 
 IBM Cloud Controller Manager v1.17.12-1 v1.17.13-1 Updated to support the Kubernetes 1.17.13 release. 
 Kubernetes v1.17.12 v1.17.13 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.17.13). 
 Kubernetes NodeLocal DNS cache 1.15.13 1.15.14 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.15.14). 







 Change log for worker node fix pack 1.17.12_1542, released 12 October 2020 

The following table shows the changes that are in the worker node fix pack 1.17.12_1542. 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.17.12_1541

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Updated worker node image with package updates for [CVE-2019-8936](https://nvd.nist.gov/vuln/detail/CVE-2019-8936), [CVE-2020-26137](https://nvd.nist.gov/vuln/detail/CVE-2020-26137), and [CVE-2020-14365](https://nvd.nist.gov/vuln/detail/CVE-2020-14365).
* UI
* CLI
* Terraform







 Mount iSCSI LUN on Red Hat Enterprise Linux 8 

This tutorial guides you through how to mount a IBM Cloud® Block Storage for Classic volume on a server with the Red Hat Enterprise Linux® 8 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 begin, make sure the host that is accessing the Block Storage for Classic volume is authorized correctly.



 Authorizing the host in the UI 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/login). From the menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/icon_hamburger.svg), select Classic Infrastructure!
HA proxy 36b0307 468c09 [CVE-2021-3634](https://nvd.nist.gov/vuln/detail/CVE-2021-3634). 







 Change log for worker node fix pack 1.22.9_1551, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 1.22.9_1551. 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.22.9_1550

 Component Previous Current Description
HA proxy 36b0307 468c09 [CVE-2021-3634](https://nvd.nist.gov/vuln/detail/CVE-2021-3634). 







 Change log for worker node fix pack 1.21.12_1559, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 1.21.12_1559. 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.12_1558

 Component Previous Current Description
HA proxy 36b0307 468c09 [CVE-2021-3634](https://nvd.nist.gov/vuln/detail/CVE-2021-3634). 







 Change log for worker node fix pack 1.23.6_1529, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 1.23.6_1529. 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.23.6_1528

 Component Previous Current Description
HA proxy 36b0307 468c09 [CVE-2021-3634](https://nvd.nist.gov/vuln/detail/CVE-2021-3634). 







 Change log for worker node fix pack 1.20.15_1580, released 09 May 2022 

The following table shows the changes that are in the worker node fix pack 1.20.15_1580. 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.15_1579

 Component Previous Current Description
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 1.22.12_1566, released 16 August 2022 

The following table shows the changes that are in the worker node fix pack 1.22.12_1566. 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.22.12_1565

 Component Previous Current Description
Kubernetes N/A N/A N/A 
 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). 
 CUDA fd4353 0ab756 [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898). 







 Change log for worker node fix pack 1.24.8_1545, released 21 November 2022 

The following table shows the changes that are in the worker node fix pack 1.24.8_1545. 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.24.7_1543

 Component Previous Current Description
Kubernetes N/A N/A N/A 
 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). 
 CUDA fd4353 0ab756 [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898). 







 Change log for worker node fix pack 1.22.16_1579, released 21 November 2022 

The following table shows the changes that are in the worker node fix pack 1.22.16_1579. 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.22.15_1577

 Component Previous Current Description
Kubernetes N/A N/A N/A 
 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). 
 CUDA fd4353 0ab756 [CVE-2022-42898](https://nvd.nist.gov/vuln/detail/CVE-2022-42898). 







 Change log for worker node fix pack 1.25.4_1523, released 21 November 2022 

The following table shows the changes that are in the worker node fix pack 1.25.4_1523. 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.25.3_1521

 Component Previous Current Description