vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Connecting overview 

You can connect command-line interfaces, IBM® or third-party applications and tools, or apps that you create to your Db2 Warehouse on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the prerequisites.



* Collect database details and credentials

To connect to your database, you need database details (such as the host name) and credentials (such as a user ID and password.) You can collect this connection information from the Db2 Warehouse on Cloud web console.
* Verify that a supported driver is installed



* If your application or tool already contains the Db2 v11.1 IBM Data Server Driver Package, then your application or tool is able to connect to your Db2 Warehouse on Cloud database by using that driver.
* Otherwise, install the Db2 driver package, which you can download from the Db2 Warehouse on Cloud web console.



* Configure your environment



* Add entries to the driver configuration file, db2dsdriver.cfg, for your database.
* Secure Sockets Layer (SSL)



Connection details, such as which port to use and the connection string, depend on whether you use SSL connections. Using SSL is strongly recommended because of the stronger security it provides.

To use SSL connections, you need a CA certificate:



* If you use the most recent Db2 Warehouse on Cloud driver package, the certificate file is bundled with the package and used for connections.
* If you use the IBM Data Server Driver Package, you can download the SSL certificate from the Db2 Warehouse on Cloud web console.



* Confirm that ports are available

If your network is behind a firewall, confirm that communications are permitted on port number 50000 for standard protocols or port number 50001 for SSL connections.





 Collecting connection information 



* [Database details and connection credentials](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-db_details_cxn_creds)







 Downloading and installing driver package 



* [Download driver package](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-dr_pkg)
2018.4.1.17, 10.0.1.4, 10.0.3 1.8.7 





 Starting a client session 



1. Log into the DataPower web GUI
2. Navigate to Objects -> Cloud -> Secure Gateway Client or search for Secure Gateway Client
3. Click Add to configure a new client connection
4. Provide a Name, the Gateway ID, and the Security Token (if applicable) and then apply the changes.



Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).
[Removing clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-removeremove)

[Preparing for host maintenance updates](https://cloud.ibm.com/docs/openshift?topic=openshift-host-maintenancehost-maintenance)



* [Identifying your affected workers](https://cloud.ibm.com/docs/openshift?topic=openshift-host-maintenanceworker-maintenance-list)
* [Actions to take before the maintenance period](https://cloud.ibm.com/docs/openshift?topic=openshift-host-maintenanceworker-maintenance-actions)



* [Workers in Classic clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-host-maintenanceworker-maintenance-classic)
* [Workers in VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-host-maintenanceworker-maintenance-vpc)











 Tuning performance 

[Tuning performance](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelkernel)



* [Default worker node settings](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-default)



* [Customizing the operating system](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-default-os)
* [Hardware changes](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-default-hw)



* [Modifying worker node settings to optimize performance](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker)



* [Modifying worker node settings by using the Node Tuning Operator](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-nto)
To set up a secure connection between your cluster and an on-premises network, [configure and deploy the strongSwan IPSec VPN service](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn-setup) directly in a pod in your cluster.

If you plan to use a gateway appliance, set up an IPSec VPN endpoint on a gateway appliance, such as a Virtual Router Appliance (Vyatta). Then, [configure the strongSwan IPSec VPN service](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn-setup) in your cluster to use the VPN endpoint on your gateway. If you don't want to use strongSwan, you can [set up VPN connectivity directly with VRA](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvyatta).

If you plan to connect your cluster to on-premises networks, check out the following helpful information:



* You might have subnet conflicts with the IBM-provided default 172.30.0.0/16 range for pods and 172.21.0.0/16 range for services. You can avoid subnet conflicts when you [create a cluster from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_create) by specifying a custom subnet CIDR for pods in the --pod-subnet option and a custom subnet CIDR for services in the --service-subnet option.
* If your VPN solution preserves the source IP addresses of requests, you can [create custom static routes](https://cloud.ibm.com/docs/openshift?topic=openshift-static-routes) to ensure that your worker nodes can route responses from your cluster back to your on-premises network.
By using a lower-order number, such as 300, you can ensure that this rule is added to the Iptables rule chain before the blocklist policy. Packets from your IP are logged by this policy before they try to match the blocklist policy rule and are denied.

apiVersion: projectcalico.org/v3
kind: GlobalNetworkPolicy
metadata:
name: log-denied-packets
spec:
applyOnForward: true
preDNAT: true
ingress:
- action: Log
destination:
nets:
- <loadbalancer_IP>/32
ports:
- 80
protocol: TCP
source:
nets:
- <client_address>/32
- action: Log
destination:
nets:
- <loadbalancer_IP>/32
ports:
- 80
protocol: UDP
source:
nets:
- <client_address>/32
selector: ibm.role=='worker_public'
order: 300
types:
- Ingress
Show more
2. Apply the policy.



* Linux:

calicoctl apply -f /log-denied-packets.yaml
* Windows and OS X:

calicoctl apply -f /log-denied-packets.yaml --config=<filepath>/calicoctl.cfg



3. Generate log entries by sending requests from your system IP to the NLB IP. These request packets are logged before they are denied.

curl --connect-timeout 10 <loadbalancer_IP>:80
4. Check for log entries that are written to the /var/log/syslog path. The log entry looks similar to the following.
* UI
* API







 Managing the key create and import access policy 

After you set up your IBM Cloud® Hyper Protect Crypto Services instance, you can manage the key create and import access policy by using the Hyper Protect Crypto Services key management service API.

This policy applies only to key management service keys and related operations.



 Understanding the key create and import access settings 

The Key create and import access policy for Hyper Protect Crypto Services instances manage how keys are created and imported into your Hyper Protect Crypto Services instance.

When you enable this policy, Hyper Protect Crypto Services only permits the creation or importation of keys in your Hyper Protect Crypto Services instance that follow the key creation and importation settings that are listed on the key create and import access policy.

Setting and retrieving the key create and import access policy is supported through the API only. To find out more about accessing the Hyper Protect Crypto Services key management service API, check out [Setting up the API](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-kms-api).

Before you enable the key create and import access policy for your Hyper Protect Crypto Services instance, keep in mind the following considerations:



* KeyCreateImportAccess policies do not affect keys that existed before policy creation.

KeyCreateImportAccess policies affect only Hyper Protect Crypto Services requests that are sent after the policy is set. You still have access to all keys that existed in your Hyper Protect Crypto Services instance before the policy is created.
* KeyCreateImportAccess policies can affect your keys across various key actions.

The enforce_token attribute affects imported keys during creation, rotation, and restoration. The create_root_key, import_root_key, create_standard_key, and import_standard_key attributes affect keys only at creation time. All other Hyper Protect Crypto Services actions, such as wrap and unwrap, are not affected and can be invoked on the key as usual.







 Enabling or updating the key create and import access policy for your service instance with the console
By default, GET api/v2/keys returns your first 200 keys, but you can adjust this limit by using the limit parameter at query time. To learn more about limit and offset, see [Retrieving a subset of keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-keys&interface=apiretrieve-subset-keys-api).

Not seeing the full list of keys? You might need to use limit and offset or check with your administrator to ensure you're assigned the correct level access to keys in your instance. To learn more, see [Unable to view or list keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-troubleshootingunable-to-list-keys-api).





 Retrieving a subset of keys 

By specifying the limit and offset parameters at query time, you can retrieve a subset of your keys, starting with the offset value that you specify.

For example, you might have 3000 total keys that are stored in your Key Protect instance, but you want to retrieve keys 200 - 300 when you make a GET /keys request.

You can use the following example request to retrieve a different set of keys.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys?offset=<offset>&limit=<limit>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the limit and offset variables in your request according to the following table.



Table 2. Table 2. Describes usage of the limit and offset variables.

 Variable Description 

 offset The number of keys to skip. For example, if you have 50 keys in your instance, and you want to list keys 26 - 50, use ../keys?offset=25. You can also pair offset with limit to page through your available resources. 
 limit The number of keys to retrieve.
By default, GET api/v2/keys returns your first 200 keys, but you can adjust this limit by using the limit parameter at query time. To learn more about limit and offset, see [Retrieving a subset of keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-keysretrieve-subset-keys-api).

Not seeing the full list of keys? You might need to use limit and offset or check with your administrator to ensure you're assigned the correct level access to keys in your instance. To learn more, see [Unable to view or list keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-troubleshootingunable-to-list-keys-api).





 Retrieving a subset of keys 

By specifying the limit and offset parameters at query time, you can retrieve a subset of your keys, starting with the offset value that you specify.

For example, you might have 3000 total keys that are stored in your Key Protect instance, but you want to retrieve keys 200 - 300 when you make a GET /keys request.

You can use the following example request to retrieve a different set of keys.

$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys?offset=<offset>&limit=<limit>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the limit and offset variables in your request according to the following table.



Table 2. Table 2. Describes usage of the limit and offset variables.

 Variable Description 

 offset The number of keys to skip. For example, if you have 50 keys in your instance, and you want to list keys 26 - 50, use ../keys?offset=25. You can also pair offset with limit to page through your available resources. 
 limit The number of keys to retrieve.
Managing MySQL Connections 

Connections to your IBM Cloud® Databases for MySQL deployment use resources, so it is important to consider how many connections you need when tuning your deployment's performance. MySQL uses a max_connections setting to limit the number of connections (and resources that are used by connections) to prevent runaway connection behavior from overwhelming your deployment's resources.

You can check the value of max_connections with your [admin user](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-user-managementthe-admin-user) and [mysql](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-connecting-mysql).

ibmclouddb=> SHOW max_connections;
max_connections
-----------------
200
(1 row)



 MySQL Connection Limits 

At provision, Databases for MySQL sets the maximum number of connections to your MySQL database to 200. You can raise this value by [Changing the MySQL Configuration](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-changing-configuration).

Leave some connections available, as a number of them are reserved internally to maintain the state and integrity of your database.

Limit the number of simultaneous connections for any nonadmin account. For example, setting max_user_connections=3 restricts the user account to a maximum of three simultaneous connections.

Exceeding the connection limit for your deployment will negatively affect the health of your database and cause it to be unreachable by your applications. After the connection limit is reached, any attempts at starting a new connection result in an error.

FATAL: remaining connection slots are reserved for
non-replication superuser connections

You can access information about connections to your deployment with the admin user, mysql, and SHOW GLOBAL STATUS.

mysql> SHOW GLOBAL STATUS;
: Updated the [maximum number of pods per worker node limitation](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits). For worker nodes that run Kubernetes 1.13.7_1527, 1.14.3_1524, or later and that have more than 11 CPU cores, the worker nodes can support 10 pods per core, up to a limit of 250 pods per worker node.

Version change logs
: Added change logs for [1.14.3_1524](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1143_1524), [1.13.7_1527](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog1137_1527), [1.12.9_1558](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog1129_1558), and [1.11.10_1563](https://cloud.ibm.com/docs/containers?topic=containers-111_changelog11110_1563) worker node patch updates.





 21 June 2019 

Accessing the Kubernetes master through the private cloud service endpoint
: Added steps for [editing the local Kubernetes configuration file](https://cloud.ibm.com/docs/containers?topic=containers-access_clusteraccess_private_se) when both the public and private cloud service endpoints are enabled, but you want to access the Kubernetes master through the private cloud service endpoint only.





 18 June 2019 

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

Ingress ALB change log
* If a connection exposes a route of 0.0.0.0/0, that route is ignored when computing overlapping prefixes.
* Only one report per gateway is available at any time. If you generate a new report, the old report is deleted.
* Older route reports might be inaccurate after you add or remove a connection. As a result, if you update routes within those connections, it is recommended that you generate a new route report.







 Service limits 

Keep in mind the following service limits while using IBM Cloud Transit Gateway.



Table 1. IBM Cloud Transit Gateway service limits

 Service limit Default 

 Number of transit gateways 10 gateways per account, 5 gateways per region 
 Number of connections per transit gateway <br><br> * 10 IBM Cloud VPC connections<br> * 5 IBM Cloud classic connections<br> * 5 IBM Cloud Direct Link connections<br><br><br> 
 Number of prefixes per connection <br><br> * 15 prefixes for VPC connections<br> * 120 prefixes for classic connections<br> * 120 prefixes for GRE connections<br> * 120 prefixes for Direct Link connections<br><br><br> 
 Number of connections with prefix filters 2 connections with prefix filters per gateway 
 Number of prefix filters per connection 10 prefix filters per connection 
 Number of GRE tunnels per transit gateway 12 GRE tunnels per gateway 
 Number of unique base networks targeted by unbound GRE tunnels per transit gateway 5 unique base networks targeted by unbound GRE tunnels per gateway 



You can open an [IBM Support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatarusing-avatar) if you need your service limits expanded.
CDR log event reference 

For cdr_logged events sent by a log webhook, the payload object contains data about a Call Detail Record (CDR) event that was handled by the phone integration. The payload object for a call detail record event contains the following properties:



Properties of the CDR webhook payload object

 Property Type Description 

 primary_phone_number string The phone number that was called. 
 global_session_id string The unique session identifier. 
 failure_occurred boolean Whether a failure occurred during the call. 
 failure_details string Details about any failure that occurred. 
 transfer_occurred boolean Whether an attempt was made to transfer a call. 
 active_calls Number The number of active calls when the call started. 
 x-global-sip-trunk-call-id string The value of the SIP trunk call ID header extracted from the initial SIP INVITE request. The following SIP trunk call ID headers are supported:<br><br><br><br> * X-Twilio-CallSid<br> * X-SID<br> * X-Global-SIP-Trunk-Call-ID<br><br><br> 
 call Object Information about the call. See [call](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-call). 
 session_initiation_protocol Object SIP protocol related details. See [session_initiation_protocol](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-session_initiation_protocol). 
 max_response_milliseconds Object Maximum latency for services used during the call. See [max_response_milliseconds](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-max_response_milliseconds). 
 assistant_interaction_summaries Array Details about the Watson Assistant interactions that took place during the call.
Usage: If you have 100 locks on your secret, and you want to retrieve locks 26 through 50, use ..?offset=25&limit=25.

The minimum value is 0.

--search (string)
: Filter locks that contain the specified string in the field "name".

Usage: If you want to list only the locks that contain the string "text" in the field "name", use ..?search=text.

The maximum length is 64 characters.





 Examples 

ibmcloud secrets-manager secret-version-locks --secret-type=arbitrary --id=exampleString --version-id=exampleString --limit=1 --offset=0 --search=exampleString





 Example output 

Example response for listing the locks that areassociated with a specified secret version.

{
"metadata" : {
"collection_type" : "application/vnd.ibm.secrets-manager.secret.lock+json",
"collection_total" : 2
},
"resources" : [ {
"name" : "lock-1",
"description" : "lock for consumer-1",
"creation_date" : "2020-08-27T14:28:54Z",
"created_by" : "IBM-id-1",
"attributes" : {
"key" : "value"
},
"secret_version_id" : "5bf89b0c-df55-c8d5-7ad6-8816951c6784",
"secret_id" : "cb7a2502-8ede-47d6-b5b6-1b7af6b6f563",
"secret_group_id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"last_update_date" : "2022-04-24T16:50:09.692573+03:00",
"secret_version_alias" : "current"
}, {
"invite_arrival_time": "2021-10-12T20:54:00.565Z",
"setup_milliseconds": 2026,
"headers": {
"call_id": "17465345_115257202@10.90.150.99",
"from_uri": "sip:+18885550456@pstn.twilio.com",
"to_uri": "sip:+18005550123@public.voip.us-south.assistant.test.watson.cloud.ibm.com"
}
},
"max_response_milliseconds": {
"assistant": 339,
"text_to_speech": 535,
"speech_to_text": 0
},
"assistant_interaction_summaries": [
{
"session_id": "7874ec3a-1330-4180-afe1-46bfb220af5b",
"assistant_id": "97f16ba4-ad94-41af-aa6c-33cd56ad5e7e",
"turns":
{
"assistant": {
"log_id": "58bebfd1-0118-419b-a555-b152a1efbbe8",
"response_milliseconds": 339,
"start_timestamp": "2021-10-12T20:54:00.722Z"
},
"request": {
"type": "start"
},
"response":
{
"barge_in_occurred": true,
"streaming_statistics": {
"response_milliseconds": 301,
"start_timestamp": "2021-10-12T20:54:00.722Z",
"stop_timestamp": "2021-10-12T20:54:01.023Z",
* Resolves the following CVEs: [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415)[CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735)[CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861)[CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061)[CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897)[CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)[CVE-2022-417247](https://nvd.nist.gov/vuln/detail/CVE-2022-417247)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.
* Sets the default values for CPU limit & Memory limit to 500m & 500Mi respectively.







 Revision 19, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
* Updates Go to version 1.18.9.
* Resolves the following CVEs: [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415)[CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735)[CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861)[CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061)[CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897)[CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)[CVE-2022-41724](https://nvd.nist.gov/vuln/detail/CVE-2022-41724)
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.
* Sets the default values for CPU limit & Memory limit to 500m & 500Mi respectively.







 Revision 19, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
* Updates Go to version 1.18.9.