vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Log in to IBM Cloud by using the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).

ibmcloud login

If the login fails, run the ibmcloud login --sso command to try again. The --sso parameter is required when you log in with a federated ID. If you use this option, go to the link that is listed in the CLI output to generate a one-time passcode.
2. Optional. List all of the toolchains in the targeted account, region, and resource group to identify the instance that you want to delete.

ibmcloud dev toolchains
3. Delete a toolchain by running the [ibmcloud dev toolchain-delete](https://cloud.ibm.com/docs/ContinuousDelivery?topic=cli-idt-clitoolchain-delete) command.

ibmcloud dev toolchain-delete TOOLCHAIN-NAME



The following table lists and describes each of the variables that are used in the previous steps.



Table 1. Variables for deleting the toolchain from the CLI

 Variable Description 

 TOOLCHAIN_NAME The name of the toolchain that you want to delete. 







 Deleting a toolchain with the API 



1. [Obtain an IAM bearer token](https://cloud.ibm.com/apidocs/toolchainauthentication). Alternatively, if you are using an SDK, [obtain an IAM API key](https://cloud.ibm.com/iam/apikeys) and set the client options by using environment variables.

export CD_TOOLCHAIN_AUTH_TYPE=iam && export CD_TOOLCHAIN_APIKEY={iam_api_key} && export CD_TOOLCHAIN_URL={base_url}
2. Delete the toolchain that you want to remove.



* Curl
* Java
* Node
* Python
* Go
: Easily manage worker nodes of the same flavor (CPU, memory, virtual or physical) with worker pools.
: Guard against zone failure by spreading nodes evenly across select multizones and by using anti-affinity pod deployments for your apps.
: Decrease your costs by using multizone clusters instead of duplicating the resources in a separate cluster.
: Benefit from automatic load balancing across apps with the multizone load balancer (MZLB) that is set up automatically for you in each zone of the cluster.

Highly available masters
: Reduce cluster downtime such as during master updates with highly available masters that are provisioned automatically when you create a cluster.
: Spread your masters across zones in a [multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersmz-clusters) to protect your cluster from zonal failures.

Image security compliance with Vulnerability Advisor
: Set up your own repo in our secured Docker private image registry where images are stored and shared by all users in the organization.
: Benefit from automatic scanning of images in your private IBM Cloud registry.
: Review recommendations specific to the operating system used in the image to fix potential vulnerabilities.

Continuous monitoring of the cluster health
: Use the cluster dashboard to quickly see and manage the health of your cluster, worker nodes, and container deployments.
: Find detailed consumption metrics by using IBM Cloud® Monitoring and quickly expand your cluster to meet work loads.
: Review logging information by using IBM® Log Analysis to see detailed cluster activities.

Secure exposure of apps to the public
: Choose between a public IP address, an IBM provided route, or your own custom domain to access services in your cluster from the internet.

IBM Cloud service integration
: Add extra capabilities to your app through the integration of IBM Cloud services, such as Watson APIs, Blockchain, data services, or Internet of Things.





 Comparison between Red Hat OpenShift and community Kubernetes clusters 

Both Red Hat OpenShift on IBM Cloud and IBM Cloud Kubernetes Service clusters are production-ready container platforms that are tailored for enterprise workloads. The following table compares and contrasts some common characteristics that can help you choose which container platform is best for your use case.
* RHEL8.4 for SAP NetWeaver (RHEL8-SP4-SAP-NETWEAVER)
* RHEL 8.4 general purpose (RHEL8-SP4)
* RHEL 8.6 general purpose (RHEL8-SP6)
* RHEL8.6 for SAP HANA (RHEL8-SP6-SAP )
* RHEL8.4 for SAP NetWeaver (RHEL8-SP6-SAP-NETWEAVER)



To view the certification details in the Red Hat catalog, see [IBM Power System E980 (9080-M9S)](https://catalog.redhat.com/cloud/instance-types/detail/5636281) and [IBM Power System S922 (9009-22A)](https://catalog.redhat.com/cloud/instance-types/detail/5636201).

If you do not choose to use the full Linux subscription for Power Systems Virtual Server you must obtain the subscription directly from the vendor and bring your image. After you deploy your Linux VM, you must log in to the VM and register it with the Linux vendor’s satellite server. To reach the Linux vendor satellite servers (where you can register and obtain packages and fixes), you must attach a public network to your VM.

When you create an OVA image, ensure that the image includes the correct version of RHEL image with cloud-init version from March 2021, or later. If you are using an earlier RHEL image, download the appropriate cloud-init and configure it as in the steps that are documented at [Installing and configuring cloud-init on Linux](https://www.ibm.com/support/knowledgecenter/en/SSXK2N_1.4.4/com.ibm.powervc.standard.help.doc/powervc_install_cloudinit_hmc.html).

You can use the [pvsadm tool](https://github.com/ppc64le-cloud/pvsadmreadme) to convert the RHEL 8.3 Qcow2 images to OVA image.
During your investigation phase, you might also want to review the available infrastructure [deployable architectures](https://cloud.ibm.com/catalogreferencearchitecture) in the catalog. IBM Cloud has created automation for the deployment of common architectural patterns that combine one or more cloud resources and designed for easy scalability and modularity. You can review the components of the architecture and the level of compliance each deployable architecture meets by reviewing the details directly in the catalog detail pages, and you can customize these architectures to meet your exact needs.

Zoom

![IBM Cloud catalog showing deployable architecture tiles](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/images/catalog.svg)

Figure 2. IBM Cloud catalog showing deployable architecture tiles





 Deploying your infrastructure and applications 

Now that you've evaluated what is available to you on IBM Cloud and you know what needs to be customized or what can be used as is, it's time to start working! The engineers on your teams can start by getting your infrastructure and application workloads ready to deploy.

Your team can use [projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-config-project) to help organize your enterprise deployments and ensure that commit checks, vulnerability scans, and cost estimations are completed as deployable architectures are configured. Within the context of a project, you can easily deploy infrastructure resources from approved, compliant IBM Cloud or private catalog offerings by using a deployable architecture. By using a predefined deployable architecture, you can be sure that you are meeting the compliance standards that the architecture is associated with. Or, you can onboard your own and specify the controls within Security and Compliance Center that your architecture is compliant with.

Before you deploy an architecture, a validation check is run on your configuration for both compliance and risk so that you can address any issues that are found.
During the sign-in flow, App ID validates the URIs before clients are allowed to participate in the authorization workflow, which helps to prevent phishing attacks and grant code leakage. By registering your URI, you're telling App ID that the URI is trusted and it's OK to redirect your users.



1. Click Manage Authentications > Authentication Settings.
2. In the Add web redirect URI field, type the URI. Each URI must begin with http:// or https:// and must include the full path, including any query parameters for the redirect to be successful.
3. Click the + symbol in the Add web redirect URIs box.
4. Repeat steps one through three until all possible URIs are added to your list.







 Step 2: Obtain your credentials 

You can obtain your credentials in one of two ways.



* By navigating to the Applications tab of the App ID dashboard. If you don't already have one, you can click Add application to create a new one.
* By making a POST request to the [/management/v4/<tenantID>/applications endpoint](https://us-south.appid.cloud.ibm.com/swagger-ui/!/Applications/registerApplication).

Request format:

 {: codeblock}
curl -X POST https://us-south.appid.cloud.ibm.com/management/v4/39a37f57-a227-4bfe-a044-93b6e6060b61/applications/ 
-H 'Content-Type: application/json' 
-H 'Authorization: Bearer <IAMToken>' 
-d '{"name": "ApplicationName"}'

Example response:

 {: screen}
{
  "clientId": "xxxxx-34a4-4c5e-b34d-d12cc811c86d",
  "tenantId": "xxxxx-9b1f-433e-9d46-0a5521f2b1c4",
* In the System Addons section, under CDP Addon, select any additional Veeam options to add. Keep in mind that if you select Veeam Backup and Replication 9.5 Update 3, you are required to select at least one option in the CDP Addon list.







 Ordering Veeam on an existing server 

You can add Veeam to an existing server with the [OS reload](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-reloading-the-os) procedure. The server must be running a Windows OS and it must be set up for monthly billing.

To add Veeam, use the following steps.



1. In the System Addons section, under OS-Specific Addons, click the Veeam tab and select one of the Veeam options.
2. In the System Addons section, under CDP Addon, select any additional Veeam options to add. If you select Veeam Backup and Replication 9.5 Update 3, you are required to select at least one option in the CDP Addon list.







 Deploying Veeam Backup and Replication 

A trial version of Veeam Backup and Replication Version 8 is used in the example.



 Prerequisites 

Before you proceed with deployment, verify that the following prerequisites are satisfied:



* Have an existing AltaVault appliance that is configured for use with IBM Cloud Object Storage and Veeam Backup and Replication.
* Obtain a copy of Veeam Backup and Replication for VMware environments, which is a single executable file. Contact your Veeam representative for a copy or download a [30-day trial version](http://www.veeam.com/vm-backup-recovery-replication-software.html).
* Obtain a license file to use with Veeam Backup and Replication. In most cases, this file is emailed to the email address that is used to download Veeam Backup and Replication. If you did not receive this file, contact your Veeam representative. \n The license file is used to activate all of the Veeam Backup and Replication functions.
In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesrequirements) for all installed deployments, your Box data source must meet the following requirement:



* You must obtain any required service licenses for the data source that you want to connect to. For more information about licenses, contact the system administrator of the data source.







 Prerequisite steps 

If you want to enable document-level security, you must take some steps to set it up. For more information, see [About document-level security](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesconfiguredls).

You must create a custom application in Box before you can connect to Box from Discovery. Anyone can create the custom app, but only a Box administrator can authorize it.

To create a custom application, complete the following steps:



1. Make sure you have a [Box account](https://www.box.com/). During this process, you get the configuration file and the client ID.
2. Next, create a custom app that uses Server Authentication with JWT as its authentication method.

For detailed steps, see [Setup with JWT](https://developer.box.com/guides/authentication/jwt/jwt-setup/) in the Box Developer Documentation.

Follow these guidelines when you create the app:



1. During the setup procedure, choose to use the Server Authentication with JWT method to verify application identity with a key pair.
2. Choose the appropriate access level for the Box content that you want to crawl:



* Box files that are shared with managed users: App access plus Enterprise access
* Box files which are shared with the service account: App access only
* Box files which are shared with the service account and its app users: App access only



Support for configuring the Box level access with App access only was added with the 4.6 release.
3. Configure the access level by following the appropriate steps for your app access level type:



* App access plus Enterprise access
As team members join a project, they need an integrated set of tools that span development, deployment, and production operations. IBM's Open Toolchain architecture enables a team to rapidly provision best-in-class DevSecOps tools from IBM, open source, and others. Integrations between these tools are configured automatically. Toolchains are a first class concept on the platform, so Developers can quickly organize everything that they need in one place, and evolve the toolchain over time. IBM provides [toolchain templates](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_about) and [Terraform resources and examples](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-terraform-setup) that support Garage Method best practices, which you can customize to promote proven toolchain patterns across your enterprise. IBM also provides [HTTP APIs and programming language SDKs](https://cloud.ibm.com/apidocs/toolchain) for you or for applications that you write to assemble and work with toolchains at a fine grained level.

IBM Cloud® Continuous Delivery provides a core set of tools for any DevSecOps toolchain: Git Repos and Issue Tracking and Delivery Pipeline. Git Repos and Issue Tracking is based on the GitLab Community Edition, and offers planning boards and source code collaboration through merge requests. The Delivery Pipeline orchestrates build, test, and deployment jobs across multiple environments as changes progress from the Developer to production. Applications can be deployed in minutes to a Kubernetes cluster on IBM Cloud, to either public or private clouds.

Open toolchain integrates more tools around Continuous Delivery such as IBM Cloud® Event Notifications, Slack, Atlassian JIRA, Sonatype Nexus, JFrog Artifactory, Sauce Labs, PagerDuty, and IBM Vulnerability Advisor. You can also substitute other tools for the Continuous Delivery capabilities, including GitHub and Jenkins. Developers can also use their favorite IDEs and editors, such as Visual Studio Code, Eclipse, and more.
Configuration and settings for attached storage 

This design supports the attachment of shared storage with NFS v3 only. NFS v4 and v4.1 aren't supported.

The attached storage for this design is limited to the IBM Cloud® storage available in the same IBM Cloud data center as the vCenter Server solution. Additionally, all virtual disks that are stored to the datastore are thin-provisioned by default.

The architecture specifies that NFS v3 datastores are attached by using the DNS name from IBM Cloud storage to connect to the share. The NFS share is attached to all hosts in the vCenter Server cluster and placed into a datastore cluster with storage DRS enabled.



 vSphere Storage Distributed Resource Scheduler (Storage DRS) 

Use Storage DRS to manage the aggregated resources of a datastore cluster. When Storage DRS is enabled, it provides recommendations for virtual machine (VM) disk placement and migration to balance space and I/O resources across the datastores in the datastore cluster.

The following features are available when storage DRS is turned on:



* Space load balancing among datastores within a datastore cluster
* I/O load balancing among datastores within a datastore cluster
* Initial place for virtual disks based on space and I/O workload



In this design, Storage DRS is enabled with the automation level set to Fully Automated. As a result, files are migrated automatically to optimize resource usage on the data cluster. Since the cluster is fully automated, all other Storage DRS options are set to Use cluster settings.





 Storage DRS runtime settings for NFS v3 

The aggressiveness of Storage DRS is determined by specifying thresholds for space that is used and I/O latency. Storage DRS collects resource usage information for the datastores in a datastore cluster. vCenter Server uses this information to generate recommendations for placement of virtual disks on datastores.

When low aggressiveness level is set for a datastore cluster, Storage DRS recommends Storage vMotion migrations only when necessary. For example, if I/O load, space usage, or their imbalance is high, Storage DRS recommends a migration.
* [Security Bulletin: A vulnerability in PostgreSQL JDBC Driver (PgJDBC) affects IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data (CVE-2022-21724)](https://www.ibm.com/support/pages/node/6575507)
* [Security Bulletin: A vulnerability in GNU Tar affects IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data (CVE-2019-9923)](https://www.ibm.com/support/pages/node/6575509)
* [Security Bulletin: A vulnerability in logback-classic affects IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data (CVE-2021-42550)](https://www.ibm.com/support/pages/node/6575511)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a stack-based buffer overflow in GNU C Library (CVE-2022-23218)](https://www.ibm.com/support/pages/node/6578617)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to stack-based buffer overflow in GNU C Library (CVE-2022-23219)](https://www.ibm.com/support/pages/node/6578619)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a buffer overflow and underflow in GNU C Library (CVE-2021-3999)](https://www.ibm.com/support/pages/node/6578621)







 8 April 2022 (Version 4.0.7) 

Support for sounds-like is now documented for custom models based on next-generation models
: For custom language models that are based on next-generation models, support is now documented for sounds-like specifications for custom words. Support for sounds-likes has been available since late 2021.

Differences exist between the use of the sounds_like field for custom models that are based on next-generation and previous-generation models.
- destination:
host: reviews
subset: v3
EOF
Show more

In Istio VirtualService rules, there can be only one rule for each service and therefore when defining multiple [HTTPRoute](https://istio.io/latest/docs/reference/config/networking/virtual-service/HTTPRoute) blocks, the order in which they are defined in the yaml matters. Hence, the original VirtualService rule is modified rather than creating a new rule. With the modified rule, incoming requests originating from Firefox browsers will go to the v2 version(Black stars) of bookinfo. All other requests fall-through to the next block, which routes all traffic to the v3(Red Stars) version of bookinfo.







 Canary deployment 

In Canary Deployments, newer versions of services are incrementally rolled out to users to minimize the risk and impact of any bugs introduced by the newer version. To begin incrementally routing traffic to the newer version of the bookinfo service, modify the original VirtualService rule:



1. Run the below command to send 80% of traffic to v1,

oc replace -f https://raw.githubusercontent.com/Maistra/istio/maistra-2.2/samples/bookinfo/networking/virtual-service-reviews-80-20.yaml

In the modified rule, the routed traffic is split between two different subsets of the reviews microservice. In this manner, traffic to the modernized version 2 of reviews is controlled on a percentage basis to limit the impact of any unforeseen bugs. This rule can be modified over time until eventually all traffic is directed to the newer version of the service.
2. View the bookinfo application again in your browser tab. Ensure that you are using a hard refresh (command + Shift + R on Mac or Ctrl + F5 on windows) to remove any browser caching. You should notice that the bookinfo application should swap between V1 or V2 at about the weight you specified.
3. To route all traffic to reviews v3,
View the BookInfo web page in a browser.

Mac OS or Linux

open http://$GATEWAY_URL/productpage

Windows

start http://$GATEWAY_URL/productpage
5. Try refreshing the page several times. Different versions of the reviews section round-robin through no stars (v1 of reviews), black stars (v2), and red stars (v3).



For more information about how routing works in Istio, see [Understanding what happened](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_bookinfo_understanding).





 Step 3: Simulate a phased rollout of BookInfo 

To simulate a release of an app, you can perform a phased rollout v3 of the reviews microservice of BookInfo.

After you finish testing your app and are ready to start directing live traffic to it, you can perform rollouts gradually through Istio. For example, you can first release v3 to 10% of the users, then to 20% of users, and so on.



1. Configure a virtual service to distribute 0% of traffic to v1, 90% of traffic to v2, and 10% of traffic to v3 of reviews.

apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
name: reviews
spec:
hosts:
- reviews
http:
- route:
- destination:
host: reviews
subset: v1
weight: 0
- destination:
host: reviews
subset: v2
weight: 90
- destination:
host: reviews
subset: v3
weight: 10
Show more

kubectl apply -f <filename>.yaml
2. View the BookInfo web page in a browser by running open http://$GATEWAY_URL/productpage on Mac OS or Linux or by running start http://$GATEWAY_URL/productpage on Windows.
3. Try refreshing the page several times.
Setting up a VPN client 

In this tutorial, you learn how to set up your VPN client and connect to the VPN server.



 Before you begin 

Obtain the following information from your VPN server administrator:



* Client profile file (<vpn_server>.ovpn)
* The type of authentication that was configured for the VPN server

Choices are client certificate, user ID and passcode, or both. If client certificate-based authentication was implemented, make sure that you also received the client certificate.
* If the VPN server certificate was ordered from a public Certificate Authority (CA), make sure that you have the CA certificate number.







 Step 1: Install a VPN client 

First, you must download and install an OpenVPN client. The following client software versions are supported.



* For macOS Catalina and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-macos), OpenVPN Connect v2, and Tunnelblick 3.8.4
* Windows 8 and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-windows), OpenVPN Connect v2
* RHEL 7.x and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-linux), OpenVPN Connect v2, and OpenVPN command-line client (version 2.4.4 and later)
* Ubuntu 18.04 and later: [OpenVPN Connect v3](https://openvpn.net/vpn-client/tab-linux), OpenVPN Connect v2, and OpenVPN command-line client (version 2.4.10 and later)



You can choose other OpenVPN-2.4-compatible client software. However, software that is not listed is not guaranteed to work.





 Step 2: Set up client authentication 

Your VPN server administrator can choose to set up a client certificate, a user ID and passcode, or both types of authentication.