vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Help me decide whether to use a Kubernetes ConfigMap or Secret object for variables](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployvariables).
* For more ways to use configmaps, see the [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/).



apiVersion: apps/v1
kind: Deployment
metadata:
name: wasliberty
spec:
replicas: 3
template:
...
spec:
...
containers:
- name: wasliberty
...
env:
- name: VERSION
valueFrom:
configMapKeyRef:
name: wasliberty
key: VERSION
- name: LANGUAGE
valueFrom:
configMapKeyRef:
name: wasliberty
key: LANGUAGE
...
---

apiVersion: v1
kind: ConfigMap
metadata:
name: wasliberty
labels:
app: wasliberty
data:
VERSION: "1.0"
LANGUAGE: en
Show more





 Secrets for container environment variables 

Secrets provide sensitive configuration information such as passwords for your deployment workloads.

The following example shows how you can reference values from your secret as environment variables in the container spec section of your deployment YAML. You can also mount the secret as a volume. By referencing values from your secret, you can decouple this configuration information from your deployment to keep your containerized app portable.



* [Help me decide whether to use a Kubernetes ConfigMap or Secret object for variables](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployvariables).
Supplemental VRA documentation (archived) 

You can find links here to supplemental documentation for the Vyatta 5600 OS older than 17.2.



 Vyatta Documentation Description 

 [IPsec Site-to-Site VPN Configuration Guide, Addendum 1801](https://public.dhe.ibm.com/cloud/bluemix/network/vra/ipsec_site-to-site-configuration_5600_addendum.pdf) This addendum describes IPsec Virtual Feature Point (VFP) VPN, which was added to site-to-site IPsec VPNs on AT&T products that run on the AT&T Vyatta Network Operating System (referred to as a virtual router, vRouter, or router in the guide) in release 1801. 
 [Brocade Vyatta Network OS Basic System Configuration Guide, 5.2R1](https://public.dhe.ibm.com/cloud/bluemix/network/vra/vyatta-network-os-5.2r1-basic-system.pdf) This guide describes the architecture of the Brocade products that run on the Brocade Vyatta Network OS (referred to as a virtual router, vRouter, or router in the guide). It includes basic system concepts and describes how to use the CLI of the router, perform basic system management and monitoring tasks, manage user accounts, access system logs, and hot-plug interfaces. 
 [Brocade Vyatta Network OS LAN Interfaces Configuration Guide, 5.2R1](https://public.dhe.ibm.com/cloud/bluemix/network/vra/vyatta-network-os-5.2r1-laninterface.pdf) This guide describes how to configure LAN interfaces on Brocade products that run on the Brocade Vyatta Network OS (referred to as a virtual router, vRouter, or router in the guide).
To secure your connection to your IBM® Virtual Servers, a public SSH key can be uploaded to your account, per region. These public keys are deployed to your VSIs to allow access to them.

Before you continue, create an SSH public key that you can upload later to the region of your choice when you are creating the VSI. Follow the steps that are [documented here](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys). Store your public and private key on your client computer - usually, in Linux® environments it is located in the /.ssh folder.

You use security groups to restrict access to and from IP ranges, protocols, and ports. The default security group that is deployed with your sample VPC can suffice. However, you might have to add extra ports for exceptions to the access restrictions, such as the SAP Software Provisioning Manager and for the ports that are being used by your SAP NetWeaver based application.





 Step 2: Creating an IBM Cloud VPC and subnet 

IBM Cloud® compute resources are kept in a global region within a VPC. Use the following steps to create a VPC and its subnet.



1. Log in to the [IBM Cloud console](https://cloud.ibm.com) with your unique credentials.
2. Click Menu icon![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Network > VPCs
3. Click Create.
4. Enter a unique Name for the VPC, for example, sap-test-vpc.
5. Select a Resource group. Use resource groups to organize your account resources for access control and billing purposes. Leave the value default.
6. Optional: Tags. Enter tags to help you organize and find your resources. For example, sap quick guide.
7. Select whether the Default security group allows inbound SSH and ping traffic to VSIs in this VPC. Leave the value default.
8. Optional: Classic access.
Qiskit Runtime workflow migration guide 

This guide describes key patterns of behavior and use cases with code examples to help you migrate code from the legacy qiskit-ibmq-provider package to use the Qiskit Runtime primitives.

To understand how to migrate from the legacy qiskit-ibmq-provider package without using the Qiskit Runtime primitives, see [Migrate your setup from qiskit-ibmq-provider](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-migrate-setup).

The primitives are the recommended tool to write quantum algorithms, as they encapsulate common device queries seen in application packages, and allow for managed performance through the Qiskit Runtime service. However, if your algorithm requires more granular information, such as pre-shot measurements, the primitives might not provide the desired abstraction level. You can refer to the restructured qiskit-ibm-provider package, and its corresponding [migration guide](https://qiskit.org/ecosystem/ibm-provider/tutorials/Migration_Guide_from_qiskit-ibmq-provider.html) for further information on alternatives to the Qiskit Runtime primitives.

The Qiskit Runtime primitives implement the reference Sampler and Estimator interfaces found in [qiskit.primitives](https://qiskit.org/documentation/apidoc/primitives.html). These interfaces let you switch between primitive implementations with minimal code changes. Different primitive implementations can be found in the qiskit, qiskit_aer, and qiskit_ibm_runtime library. Each implementation serves a specific purpose:



* The primitives in qiskit can perform local statevector simulations - useful for quickly prototying algorithms.
* The primitives in qiskit_aer give access to the local Aer simulators for tasks such as noisy simulation.
* The primitives in qiskit_ibm_runtime provide access to cloud simulators and real hardware through the Qiskit Runtime service. They include exclusive features such as built-in circuit optimization and error mitigation support.
4 Minimal business impact: An inquiry or non-technical request. Within 1 business day Monday – Friday business hours 



Response Time Objective describes IBM's goals only and do not represent a guarantee of performance.

Business Hours reflect normal country business hours in your time zone. For example, 8:00 AM to 5:00 PM in North America or 9:00 AM to 6:00 PM in some parts of Asia and Europe, Monday through Friday, excluding weekends and national or statutory holidays.

For further details, please refer to the [IBM Support Guide](https://www.ibm.com/support/pages/node/733923)



 MAS-SaaS Environment Route URLs 

MAS Application Suite Instance:

https://main.home.INSTANCE_NAME.suite.maximo.com/

Admin:

https://maxinst.manage.INSTANCE_NAME.suite.maximo.com/toolsapi

INSTANCE_NAME = Your environment instance identifier found in your Welcome Letter.





 How to Access AWS S3 (Cloud Object Storage) Buckets 



* To access AWS S3 buckets you have to configure Rclone. Rclone is the utility via which you can access AWS S3 COS bucket(s) and upload/download the content.
* To configure Rclone please use steps below. You will need this information while configuring Rclone.
* A separate Rclone config is needed for each bucket as the access credentials for each bucket are unique.
* Some buckets are read-only which means you can only download data from that bucket while some are read/write meaning you can upload and download data.



The below steps can only be performed by the client once they have received their Welcome Letter.



 Rclone Config for COS file Upload and Download - Step-by-Step Guide 





 Pre-requisite Steps: 



1. Installation of Rclone - [https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-rclone](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-rclone)
Qiskit Runtime CLI 

The IBM Cloud® quantum computing command-line interface (CLI) allows you to access IBM Quantum Services via the Qiskit Runtime architecture. You can use IBM Cloud CLI to manage V2 service brokers and templates.



 Prerequisites 



* Ensure that you have a Qiskit Runtime service instance set up by following the instructions in the [Getting started guide](https://cloud.ibm.com/docs/qiskit-runtime?topic=qiskit-runtime-quickstart).
* Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* Install the Quantum Computing CLI by running the following command:

ibmcloud plugin install qiskit-runtime -r <repo_name>



You're notified on the command line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up to date so that you can use the latest commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.

IBM Cloud CLI requires Java&trade 1.8.0. You can download the CLI from IBM Cloud to use on your local system as a complement to the IBM Cloud console.

Make sure you are logged into IBM Cloud under the account where your Qiskit Runtime instance is provisioned by running the ibmcloud login command, as described in the following section.

To point to a specific instance to use with the CLI, you will need to find your CRN, then run the [instance-target](https://cloud.ibm.com/docs/cli?topic=cli-quantum-computing-cliqiskit-runtime-instance-target) command.

To find your CRN, open the IBM Cloud console [Instances page](https://cloud.ibm.com/quantum/instances) and click your instance. In the page that opens, click the icon to copy your CRN. For example:
Qiskit Runtime CLI 

The IBM Cloud® quantum computing command-line interface (CLI) allows you to access IBM Quantum Services via the Qiskit Runtime architecture. You can use IBM Cloud CLI to manage V2 service brokers and templates.



 Prerequisites 



* Ensure that you have a Qiskit Runtime service instance set up by following the instructions in the [Getting started guide](https://cloud.ibm.com/docs/qiskit-runtime?topic=qiskit-runtime-quickstart).
* Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* Install the Quantum Computing CLI by running the following command:

ibmcloud plugin install qiskit-runtime -r <repo_name>



You're notified on the command line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up to date so that you can use the latest commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.

IBM Cloud CLI requires Java&trade 1.8.0. You can download the CLI from IBM Cloud to use on your local system as a complement to the IBM Cloud console.

Make sure you are logged into IBM Cloud under the account where your Qiskit Runtime instance is provisioned by running the ibmcloud login command, as described in the following section.

To point to a specific instance to use with the CLI, you will need to find your CRN, then run the [instance-target](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-quantum-computing-cliqiskit-runtime-instance-target) command.

To find your CRN, open the IBM Cloud console [Instances page](https://cloud.ibm.com/quantum/instances) and click your instance. In the page that opens, click the icon to copy your CRN. For example:
* If you define more than 1 default target, all default targets get a copy of an auditing event that does not have a clearly defined routing rule to indicate where to route events in the account.



Define 1 default target per account to configure where auditing events that are not explicitly managed in the account's routing rules are routed. Consider defining a second default target per account when you want to collect the data in a backup location or account.





 Number and location of targets 

Define the targets where you plan to collect auditing events based on your regulatory and corporate requirements.



* You can have 1 target per region to collect auditing events for that region. Use this option to reduce latency and network connectivity issues.
* You can have 1 target to collect auditing events across the entire account.
* You can define targets within the account or in a different account.



For more information, see [Targets](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resourcesatracker-resources-targets).





 Routing rules in the account 

Define the routing rules that indicate how to route events in your account.



* Routes are global.
* You can define up to 4 routes per account.
* You can define 1 or more routes to configure how auditing events across all regions in your account are collected and stored in 1 or more targets.
* For each route that you define, you can configure 4 rules. These rules are applied top down. When a rule is identified for a region, any follow up rules withing that route definition that apply to that region are not considered.



Decide if you want to drop the collection of auditing events in 1 or more regions. Check any compliance requirements to confirm that you can.



* To drop the collection of auditing events in 1 or more regions, you can configure a route for those regions with no targets defined.



For more information, see [Routes](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resourcesatracker-resources-routes).





 Next
Adding or removing crypto units 

After you provision a Hyper Protect Crypto Services instance, you can request to add or remove crypto units by raising support tickets in the IBM Cloud® Support Center.

To adjust the number of crypto units, complete the following steps.



 Adding crypto units to an existing service instance 



 Step 1: Request to add crypto units 

To add or remove crypto units, you need to first raise a support ticket.



1. In your IBM Cloud dashboard, click the Help icon ![Help icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/help.svg) > Support center from the IBM Cloud console menu bar to enter the Support Center. Click View all in the Recent support cases panel and click Create new case. Or, you can directly go to the [Manage cases page](https://cloud.ibm.com/unifiedsupport/cases) and click Create new case.
2. On the Create a case page displayed, select the offering Hyper Protect Crypto Services, and then specify the following values:



Table 1. Describes the fields that are required to add crypto units

 Field name Action 

 Subject Enter Add crypto units. 
 Description Enter your [service instance ID](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-retrieve-instance-ID), the region that your service instance resides in, and the number of crypto units you want to add. You can have no more than three crypto units for a service instance. 
 Selected resources Select your Hyper Protect Crypto Services service instance. 



3. Check the Email me updates about this issue box, and click Continue to review > Create case.

After the operation is completed successfully, you will get an email notification. You can also check the state in the Support Center by clicking the Help icon !
Securing your data 

To ensure that you can securely manage your data when you use IBM Log Analysis, it is important to know exactly what data is stored and encrypted, and how you can delete any stored personal data.



 How your data is collected in IBM Log Analysis 



 Platform logs 

Log data from IBM Cloud services is collected automatically and available for analysis through the web UI. This data is collected and forwarded to the platform logs instance in the location where the service is available. [Learn more about the services that send logs to the platform service logs instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services).





 Logging agent 

When you configure a logging agent to collect and forward data to an IBM Log Analysis instance, data is automatically collected and available for analysis through the web UI. You can configure the logging agent to connect to the logging instance via the public network and the private network.

By default, you connect to resources in your account over the IBM Cloud public network. To configure an agent to send logs by using a public endpoint, the environment where the agent is running requires internet access to use the public endpoint.

You can enable virtual routing and forwarding (VRF) to move IP routing for your account and all of its resources into a separate routing table. If VRF is enabled, you can then enable IBM Cloud service endpoints to connect directly to resources without using the public network. To configure an agent to send logs by using a private endpoint, you must [enable virtual routing and forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) for your account. Once the account is VRF and service endpoint enabled, the logging agent can be configured to use the private network by using the [Private Endpoint](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api) as the ingestion URL.



* Private endpoints are not accessible from the public internet.
* All traffic is routed to the IBM Cloud private network.









 How your data is stored in IBM Log Analysis
Granting access to keys 

You can enable different levels of access to IBM Cloud® Hyper Protect Crypto Services resources in your IBM Cloud account by creating and modifying IBM Cloud IAM access policies.

As a service administrator or an account owner, determine an [access policy type](https://cloud.ibm.com/docs/account?topic=account-userrolespolicytypes) for users, service IDs, and access groups based on your internal access control requirements. For example, if you want to grant user access to Hyper Protect Crypto Services at the smallest scope available, you can [assign access to a single key](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-grant-access-keysgrant-access-key-level) in an instance.

A good practice is to grant access permissions as you invite new users to your account or service. For example, consider the following guidelines:



* Enable user access to the resources in your account by assigning Cloud Identity and Access Management (IAM) roles. Rather than sharing your admin credentials, create new policies for users who need access to the encryption keys in your account. If you are the admin for your account, you are automatically assigned a Manager policy with access to all resources under the account.
* Grant roles and permissions at the smallest scope needed. For example, if a user needs to access only a high-level view of keys within a specified space, grant the Reader role to the user for that space.
* Regularly audit who can manage access control and delete key resources. Remember that granting a Manager role to a user means that the user can modify service policies for other users, in addition to destroying resources.





 Granting access to all keys in an instance 

You can grant access to keys within a Hyper Protect Crypto Services service instance by using the IBM Cloud console.

Review [roles and permissions](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-access) to learn how IBM Cloud IAM roles map to Hyper Protect Crypto Services actions.

To assign access:



1.
Viewing logs 

After you provision an instance of the IBM Log Analysis service in the IBM Cloud, and configure a logging agent for a log source, you can view, monitor, and manage log data through the IBM Log Analysis Web UI.

When you launch the IBM Log Analysis web UI, log entries are displayed with a predefined format. You can modify in the User Preferences section how the information in each log line is displayed. You can also filter logs and modify search settings, then bookmark the result as a view. You can attach and detach one or more alerts to a view. You can define a custom format for how your lines are shown in the view. You can expand a log line and see the data parsed.

Complete the following steps to view logs:



 Step 1. Grant IAM policies to a user to view logs 

You must grant permissions to users in your account to be able to launch the web UI and view logs.

You must be an administrator of the IBM Log Analysis service, an administrator of the IBM Log Analysis instance, or have account IAM permissions to grant other users policies.

The following table lists the minimum policies that a user must have to be able to launch the IBM Log Analysis Web UI, and view logs:



Table 1. IAM policies

 Service Role Permission granted 

 IBM Log Analysis Platform role: Viewer Allows the user to view the list of service instances in the Observability Logging dashboard. 
 IBM Log Analysis Service role: Reader Allows the user to launch the Web UI and view logs in the Web UI. 



For more information on how to configure these policies for a user, see [Granting permissions to a user to view logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-work_iamuser_logdna).





 Step 2. Navigate to the web UI through the IBM Cloud UI 

To launch the IBM Log Analysis UI through the IBM Cloud UI, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in, the IBM Cloud Dashboard opens.
2. Click the Menu icon !
Registering an Operator 

This tutorial walks you through how to register a Node-RED Operator in IBM Cloud® Partner Center. You can onboard an Operator bundle using a TGZ file or an Operator using a CSV file. By completing this tutorial, you learn how to provide your company details, create a test environment, and set up access for your team to help with the onboarding process.

This tutorial is one of four in a series that demonstrates how to onboard and publish a [sample Node-RED Operator](https://github.com/IBM-Cloud/operator-bundle-sample/releases). It uses a fictitious company that's called Example Corp. As you complete the tutorial, adapt each step to fit your product's needs.



 Before you begin 



1. Verify that you're using a Pay-As-You-Go or Subscription account by going to Manage > Account > Account settings in the IBM Cloud console.
2. Verify that you're assigned the administrator role on all account management services and all IAM-enabled services. For more information, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-services) and [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).







 Step 1: Provide your company name 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > Get started.
2. Enter the name of your company as you want it to be displayed in the catalog, and click Save. For the purpose of this tutorial, enter Example Corp as the company name.







 Step 2: Create your test environment 

You, or a member of your team, uses the test environment to onboard the Operator and validate that it can be deployed to a Red Hat OpenShift cluster.