vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Collections 

Collections are a way to group feature flags and properties. These collections can be consumed in your apps with the help of a collection ID and App Configuration SDKs. Every feature must be in a collection, so create your collection first.

By default, Collections displays the list of collections in the current App Configuration service instance along with Name, the Labels associated, the date of creation of the collection, and the collection Content (number of feature flags and number of properties).



  Create a collection 

To create a collection, complete these steps:



1.  From the App Configuration console, click Collections from the navigation menu or from Getting Started > Create a collection.

Zoom

![List of collections](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-collections-default.png)

Figure 1. List of collections in the current App Configuration service instance.
2.  Click Create. The side panel opens with fields for creating a new collection.

Zoom

![Create a collection](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-collections-create.png)

Figure 2. App Configuration service creating a new collection
3.  Provide the collection details:



*  Name - name of the collection.
*  Collection ID - the collection identifier, the value is auto suggested based on the entered collection name. You can modify the same, if needed. Use the Collection ID value as the identifier in your SDK or API code.
*  Tags - specify the tags that need to be associated with the collection, which is optional.
*  Description - add a description of the collection, which is optional.



4.  Click Create.
To use configuration properties:



1. Define the configuration properties to be used by your application. These properties can be implemented as:



* Exported environment variables
* Values stored in a credentials file

The following example shows using environment variables. Each environment variable must be prefixed by IBM_ANALYTICS_ENGINE_API.

export IBM_ANALYTICS_ENGINE_API_URL=<IAE_ENDPOINT_URL>
export IBM_ANALYTICS_ENGINE_API_AUTH_TYPE=iam
export IBM_ANALYTICS_ENGINE_API_APIKEY=<IAM_API_KEY>

IBM_ANALYTICS_ENGINE_API is the default service name for the IBM Analytics Engine API client which means that the SDK will by default look for properties that start with this prefix.



2. Build the service client:

import com.ibm.cloud.iaesdk.ibm_analytics_engine_api.v3.IbmAnalyticsEngineApi;
import com.ibm.cloud.iaesdk.ibm_analytics_engine_api.v3.model.;
import com.ibm.cloud.sdk.core.http.Response;
import com.ibm.cloud.sdk.core.security.;
import java.util.HashMap;

private static IbmAnalyticsEngineApi ibmAnalyticsEngineApiService;

private static String IAM_API_KEY = "{apikey}";
private static String IAE_ENDPOINT_URL = "{url}";
private static String API_AUTH_URL = "{api auth url}";

public static void main(String[] args)
{
HashMap<String, String> config = new HashMap<String, String>();
config.put("APIKEY",IAM_API_KEY );
config.put("AUTH_URL", API_AUTH_URL);

try {
// Create an IAM authenticator.
Authenticator authenticator = IamAuthenticator.fromConfiguration(config);
To attach the block storage device to a non-SDS worker node, you must create a persistent volume (PV) with the IBM Cloud Block Volume Attacher storage class and the details of your block storage device.

The instructions in this topic are available for classic worker nodes only. If you want to attach raw, unformatted block storage to a VPC worker node, see [Adding raw Block Storage for VPC to worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_api_attach).



* Make sure that you [manually](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesmanual_block) added raw, unformatted, and unmounted block storage to your non-SDS worker nodes.
* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* Install the [block storage attacher plug-in](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesblock_storage_attacher).





1. Prepare the PV creation.



* If you used the mkpvyaml container, run the following command.



1. Open the pv-<cluster_name>.yaml file.

nano pv-<cluster_name>.yaml
2. Review the configuration for your PVs.



* If you manually added block storage:**



1. Create a pv.yaml file. The following command creates the file with the nano editor.

nano pv.yaml
2. Add the details of your block storage device to the PV.

apiVersion: v1
kind: PersistentVolume
metadata:
name: <pv_name>
annotations:
ibm.io/iqn: "<IQN_hostname>"
ibm.io/username: "<username>"
ibm.io/password: "<password>"
This runbook uses 'vsanDatastore', 'SDDC-DPortGroup-Mgmt' and 'SDDC-DPortGroup-External'. You need to use your vCenter Server deployment-specific network and storage names in your deployment configurations. For example, you might have datastore such as 'workload_share_YgkI8' (in case IBM Cloud File Storage is used for the datastore) or your private portgoup can be like 'fra04test-fra04-test01-dpg-mgmt'.

You can validate the private and public Distributed PortGroup names and the datastore names for your deployment by using GOVC.

export GOVC_URL='10.208.17.2'
export GOVC_USERNAME='administrator@vsphere.local'
export GOVC_PASSWORD='xxxxx'
export GOVC_INSECURE=1

 Distributed Port Group names
govc ls network | grep -E 'dpg-mgmt|SDDC-DPortGroup-Mgmt' | awk -F / '{print $4}'
govc ls network | grep -E 'dpg-external|SDDC-DPortGroup-External' | awk -F / '{print $4}'

 Datastore names
govc ls datastore | grep -E 'vsan|share' | awk -F / '{print $4}'

Pick your deployment-specific values and use them throughout the runbook.





 Uploading the OVA image to vCenter 

You must upload and import the RHEL ISO and RHEL CoreOS OVA downloads from the previous steps into the vCenter Server instance datastore. You must rename the OVA image to rhcos-latest in order for the image to work with the Terraform templates used later in the build process.

On the jump-server or remote device, by using an editor of your choice, such as Visual Studio Code, copy the following and change for your values. Replace the x in 4.x.3 with the current Red Hat OpenShift version, for example, 4.7.
[get-word](https://cloud.ibm.com/apidocs/text-to-speechget-a-custom-word) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id, word Get a custom word. 
 [list-words](https://cloud.ibm.com/apidocs/text-to-speechlist-custom-words) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customization_id List custom words. 
 [delete-user-data](https://cloud.ibm.com/apidocs/text-to-speechdelete-labeled-data) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customer_id Delete labeled data. 





 Creating a Text to Speech Service instance 

Before you install the package, you must create a Text to Speech Service instance and service credentials.



1. Create a Text to Speech Service instance.
2. When the service instance is created, service credentials are automatically created for you.







 Installing the Text to Speech package 

After you have an Text to Speech Service instance, install the Text to Speech package into your namespace.





 Installing from the Cloud Functions CLI 

Install the Text to Speech package from the CLI. Be sure to [install the Cloud Functions plug-in for the IBM Cloud CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_install) first.

To install the Text to Speech package, run the following commands.



1. Clone the Text to Speech package repo.

git clone https://github.com/watson-developer-cloud/openwhisk-sdk
2. Deploy the package.
To learn how to add an object to your bucket, see [Add some objects to your bucket](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storagegs-add-objects).
3. For each bucket object change, observe new activations for the cosTrigger trigger and cosChange action.
4. Stop polling by pressing ctrl c.
5. You can see the details of an activation by running the activation get command.

ibmcloud fn activation get ACTIVATION_ID
6. If you are unable to observe new activations, verify that the parameter values are correct by running the trigger get command.

ibmcloud fn trigger get cosTrigger



You can see an example activation in the [Data structure of an Object Storage trigger activation](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_ev_data) section.







 Next steps for Object Storage and Cloud Functions 

After you have created a trigger to respond to bucket events and connected it to an action, you can try creating custom actions and sequences.



* You can use the [COS SDK](https://cloud.ibm.com/docs/cloud-object-storage/libraries?topic=cloud-object-storage-sdk-gs) to perform bucket and object-level tasks. The SDK includes code samples in multiple languages.
* You can create your own [actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions) or [web actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions_web) to be executed when the trigger is fired.
To attach the block storage device to a non-SDS worker node, you must create a persistent volume (PV) with the IBM Cloud Block Volume Attacher storage class and the details of your block storage device.

The instructions in this topic are available for classic worker nodes only. If you want to attach raw, unformatted block storage to a VPC worker node, see [Adding raw Block Storage for VPC to worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesvpc_api_attach).



* Make sure that you [manually](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesmanual_block) added raw, unformatted, and unmounted block storage to your non-SDS worker nodes.
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
* Install the [block storage attacher plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-utilitiesblock_storage_attacher).





1. Prepare the PV creation.



* If you used the mkpvyaml container, run the following command.



1. Open the pv-<cluster_name>.yaml file.

nano pv-<cluster_name>.yaml
2. Review the configuration for your PVs.



* If you manually added block storage:**



1. Create a pv.yaml file. The following command creates the file with the nano editor.

nano pv.yaml
2. Add the details of your block storage device to the PV.

apiVersion: v1
kind: PersistentVolume
metadata:
name: <pv_name>
annotations:
ibm.io/iqn: "<IQN_hostname>"
ibm.io/username: "<username>"
ibm.io/password: "<password>"
Upload your ignition file to the IBM Cloud Object Storage bucket that you identified earlier. From your Bucket page in the console, click Add object. Drag your ignition file in the bucket.







 Step 4: Attaching your bare metal host to the location 

Download the ignition file to your bare metal host, then run it to attach the bare metal host to your Satellite location.



1. Run the following command to download the file from your bucket to your host machine. Replace <bucketname> with the name of your IBM Cloud Object Storage bucket, <cos_region> with the region of your bucket (for example, us.east), and <filename> with the name of your ignition file that is in the bucket.

You can run the curl command without creating a local file on the bare metal server to ensure your bare metal server can reach the bucket by removing > ignition.ign from the following example.

curl https://<bucketName>.s3.<cos_region>.cloud-object-storage.appdomain.cloud/<filename> > ignition.ign

For example:

curl https://mybucket.s3.us-east.cloud-object-storage.appdomain.cloud/attachHostmysatloc.ign > ignition.ign
2. Identify the disk that you want to install the CoreOS operating system to. To identify disks, run lsblk

lsblk

The following example is possible output.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 15.5G 0 loop /run/ephemeral
loop1 7:1 0 979.1M 1 loop /sysroot
sda 8:0 0 1.8T 0 disk
sr0 11:0 1 1.1G 0 rom. /run/media/iso

From this output, choose to install on the sda disk.
3. Run the following install command to start the ignition file. Replace <diskName> with the full path of the disk that you retrieved from lsblk and replace <filename> with the name of the file you downloaded from IBM Cloud Object Storage.
Click Add.
5. (Optional): Click Test Connection to verify that the connection succeeded.









 CLPPlus 

Command line processor plus (CLPPlus) is included in the Db2 driver package. CLPPlus provides a command-line interface that you can use to connect to a Db2 on Cloud database. You can use CLPPlus to define, edit, and run statements, scripts, and commands.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).

To use CLPPlus, ensure that a software development kit (SDK) or a Java runtime environment (JRE) for Java Version 1.5.0 or later is installed on your computer and that environment variables are set as follows:



* The JAVA_HOME environment variable is set to the Java installation directory on your computer.
* The PATH environment variable setting includes the bin subdirectory of the Java installation directory on your computer.







 Procedure 



1. In a command shell on Linux operating systems, at the Windows command prompt, or in the DB2 command window on Windows operating systems, run the following commands:

These commands create new entries in the driver configuration file (db2dsdriver.cfg) on your computer and set the connection attributes. You need to do this step only one time.



* For a connection with SSL:

db2cli writecfg add -database BLUDB -host <hostname> -port 50001 -parameter "SecurityTransportMode=SSL"

db2cli writecfg add -dsn <alias> -database BLUDB -host <hostname> -port 50001

where:



* <hostname> is the host name of the server.
* <alias> is an alias that you choose.



* For a connection without SSL:

db2cli writecfg add -database BLUDB -host <hostname> -port 50000
Setting up Terraform for IBM Cloud Monitoring 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud services so that you can rapidly build complex, multitier cloud environments that follow Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the provisioning, update, and deletion of your IBM Cloud Monitoring instances by using HashiCorp Configuration Language (HCL).

Looking for a managed Terraform on IBM Cloud solution? Try out [IBM Cloud® Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform scripting language that you are familiar with, but you don't need to worry about setting up and maintaining the Terraform command line and the IBM Cloud Provider plug-in. Schematics also provides pre-defined Terraform templates that you can install from the IBM Cloud catalog.

Before you begin, ensure that you have the [required access](https://cloud.ibm.com/docs/monitoring?topic=monitoring-iam) to create and work with Monitoring resources.



 Step 1. Install the Terraform CLI 

Complete the following steps to install the Terraform CLI:



1. Create a terraform folder on your local machine, and navigate to your terraform folder.

mkdir terraform && cd terraform
2. Download the Terraform version that you want.

For more information about the IBM Cloud Provider plug-in for Terraform supported versions, see [Installing the Terraform CLI](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cli).

For example, you can download terraform_0.15.5_darwin_amd64.zip for a MacOS.
3. Extract the Terraform zip file and copy the files to your terraform directory.
4. Set the environment PATH variable to your Terraform files.

export PATH=$PATH:<terraform-directory>/terraform
5.
Provisioning an instance by using Terraform 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud services so that you can rapidly build complex, multitier cloud environments that follow Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the provisioning, update, and deletion of your IBM Log Analysis instances by using HashiCorp Configuration Language (HCL).

Looking for a managed Terraform on IBM Cloud solution? Try out [IBM Cloud® Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform scripting language that you are familiar with, but you don't need to worry about setting up and maintaining the Terraform command line and the IBM Cloud Provider plug-in. Schematics also provides pre-defined Terraform templates that you can install from the IBM Cloud catalog.



 Prereqs 



* You must have a paid service plan for the IBM Log Analysis service. [Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
* Ensure that you have the [required access](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-iam) to create and work with Log Analysis resources.







 Step 1. Install the Terraform CLI 

Complete the following steps to install the Terraform CLI:



1. Create a terraform folder on your local machine, and navigate to your terraform folder.

mkdir terraform && cd terraform
2. Download the Terraform version that you want.

For more information about the IBM Cloud Provider plug-in for Terraform supported versions, see [Installing the Terraform CLI](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cli).

For example, you can download terraform_0.15.5_darwin_amd64.zip for a MacOS.
"containers-kubernetes"
]
},
{
"operand": "location",
"operator": "in",
"values":
"us-south",
"eu-de"
]
}
]
}]
Show more

Where:

action
: Action defines whether IBM Cloud® Metrics Routing includes or excludes metrics on the route. Two actions are supported: send and drop. If not specified, the default action is to send the metrics.

send
: Metrics are sent, based on the routing rule, on the defined route.

drop
: Metrics are excluded, based on the routing rule, when metrics are sent on the defined route.

operand
: Operand is the name of the property on which the operator test is run. The following operands are supported: location,service_name,service_instance,resource_type, and resource.

operator
: Two operators are supported: in and is.

in
: The value of the operand property is compared to a list of values.

You can define up to 20 values.

is
: The value of the operand property is compared to a single value.

When using is, only 1 value can be specified.

values
: A string, or an array of strings, to be compared with the operand property to determine whether the metric is routed or not. When the isoperator is used, values must include a single string. When the inoperator is used, values can include multiple strings in an array.

Valid values depend on the operand.

location
: Any location where [IBM Cloud Metrics Routing is available.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions)

service_name
: The CRN service name of an [IBM Cloud service that generates metrics managed through [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud-services-mr)
<-- </section "id="section-list-range-app-examples" "> --><-- </section "id="section-list-range-app" "> --><-- <section "id="section-get-analytics-range-app" "> --> ibmcloud cis range-analytics Get analytics data for range applications (Enterprise plan only). ibmcloud cis range-analytics DNS_DOMAIN_ID --metrics METRICS] --dimensions DIMENSION] --filters FILTERS] --sort SORT] --since SINCE] --until UNTIL]
ibmcloud cis range-analytics DNS_DOMAIN_ID --bytime --time_delta DELTA] --metrics METRICS] --dimensions DIMENSION] --filters FILTERS] --sort SORT] --since SINCE] --until UNTIL] ! !! ! ! ! ! ! ! !
<-- <section "id="section-get-analytics-range-app-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--metrics: One or more metrics to compute. To get all metrics, set metrics to count,bytesIngress,bytesEgress,durationAvg,durationMedian,duration90th,duration99th.--dimension: Can be used to break down the data by given attributes. To get all dimensions, set dimensions to event,appID,coloName,ipVersion. --filters: Used to filter rows by one or more dimensions. Filters can be combined using OR and AND boolean logic. AND takes precedence over OR in all the expressions. The OR operator is defined using a comma (,) or OR keyword surrounded by whitespace. The AND operator is defined using a semicolon (;) or AND keyword surrounded by whitespace. Comparison options are: ==, =, >, <, >=, <=. An example value for filters is: event==connect AND coloName=SFO.--sort: The sort order for the result set.
{
"operand": "location",
"operator": "in",
"values":
"us-south",
"eu-de"
]
}
]
}]
Show more

Where:

action
: Action defines whether IBM Cloud® Metrics Routing includes or excludes metrics on the route. Two actions are supported: send and drop. If not specified, the default action is to send the metrics.

send
: Metrics are sent, based on the routing rule, on the defined route.

drop
: Metrics are excluded, based on the routing rule, when metrics are sent on the defined route.

operand
: Operand is the name of the property on which the operator test is run. The following operands are supported: location,service_name,service_instance,resource_type, and resource.

operator
: Two operators are supported: in and is.

in
: The value of the operand property is compared to a list of values.

You can define up to 20 values.

is
: The value of the operand property is compared to a single value.

When using is, only 1 value can be specified.

values
: A string, or an array of strings, to be compared with the operand property to determine whether the metric is routed or not. When the isoperator is used, values must include a single string. When the inoperator is used, values can include multiple strings in an array.

Valid values depend on the operand.

location
: Any location where [IBM Cloud Metrics Routing is available.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions)

service_name
: The CRN service name of an [IBM Cloud service that generates metrics managed through [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud-services-mr)

service_instance, resource_type, and resource