vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[New Literal](https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/watson-knowledge-studio/images/new_literal.png) icon on the canvas toolbar. This adds a new literal to the canvas.
2. In the new literal on the canvas, enter the string of text that you want to match. For example, white-tailed deer.







 Creating a regular expression 

To extract information on the basis of the format of text, you must use a regular expression. The syntax for a regular expression is the same as that used to define regular expressions in Java.

To create an extractor that uses a regular expression:



1. From the canvas toolbar, click ![New Regular Expression](https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/watson-knowledge-studio/images/new_extractor_regex.png).
2. Enter a name for the regular expression. You can also add some descriptive information. Note that the information that you enter at the prompt is the name for the expression, not the expression itself.
3. Select the regular expression on the canvas to open the Extractor Properties to the Settings tab. Specify a regular expression. For more information about the syntax, see the [Class Pattern](https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html) Javadocc.
4. Specify options for case sensitivity, token range, and special character handling. If, while designing a regular expression, you see false positives, provide more context by extending the pattern in the regular expression or adding context through a sequence pattern. For example, if your postal code expression matches additional terms, incorporate rules for which letters are permitted in specific positions.





 Regular expression examples 

The following are examples of regular Java expressions that might be used in specific instances.
In this step, you create a Develop and Deploy application to VPC using deployment strategies toolchain. The target virtual machines are configured during the toolchain setup by using your SSH keys. You can change these settings later by updating the Delivery Pipeline configuration. Any code that is merged into the target Git repo branch is automatically built, validated, and deployed into the virtual machines.

To create a Develop and Deploy application to VPC using deployment strategies toolchain, click

[![Create toolchain](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/create_toolchain_button.png)](https://cloud.ibm.com/devops/setup/deploy?repository=https://github.ibm.com/open-toolchain/simple-vsi-toolchain&env_id=ibm:yp:us-south)

Alternatively, from the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps. On the Toolchains page, click Create a Toolchain. On the Create a Toolchain page, click Develop and Deploy application to VPC with multiple deployment strategies.



 Configure the toolchain name and region 

Review the default information for the toolchain settings. The toolchain's name identifies it in IBM Cloud. Make sure that the toolchain's name is unique within your toolchains for the same region and resource group in IBM Cloud.

The toolchain region can differ from the cluster and registry region.

Zoom

!
1 root root 10 Feb 11 03:14 scsi-3600605b00d87b43027b3bc310a64c6c9-part1 -> ../../sdc1
lrwxrwxrwx. 1 root root 10 Feb 11 03:15 scsi-3600605b00d87b43027b3bc310a64c6c9-part2 -> ../../sdc2
7. Repeat the previous steps for each worker node that you want to use for your ODF configuration.



Before you begin, review the [parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-local&interface=uiodf-local-parameter-reference) for the template version that you want to use.





 Creating and assigning a configuration in the console 



1. [From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east.
Create the function that you want to deploy.
2. (optional) If you have more than one file, package the files as a compressed file, otherwise skip this step (see the following examples)
3. (optional) Compile the go/zip file by using the Docker image (docker run -i openwhisk/action-golang-v1.19:nightly -compile ...). This step returns a compressed file that contains the executable file.
4. Create the action by using the ibmcloud cli.



These steps are used in each of the following examples.





 Creating a simple Golang Action 

You can create a simple action in Go by creating a file that contains a Go function.



1. Create the Go file that contains the function. The default entry name is Main. You can change this name to any different public function name (Uppercase first character) if it is specified by using the --main parameter with the ibmcloud fn action create <action_name> <action_file> --main <function_name> command; for example, --main hello if the function is named Hello.

main.go

package main

import "fmt"

// Main is the function implementing the action
func Main(params map[string]interface{}) map[string]interface{} {
// parse the input JSON
name, ok := params["name"].(string)
if !ok {
name = "World"
}
msg := make(map[string]interface{})
msg["body"] = "Hello " + name + "!"
// can optionally log to stdout (or stderr)
fmt.Println("hello Go action")
// return the output JSON
return msg
}
Show more
2. (optional) If you want to pre-compile the function to an executable file that is stored in a compressed format first,
* [Clone repo to local machine](https://cloud.ibm.com/docs/schematics?topic=schematics-edit-blueprintsbp-clone-repo-local)
* [Editing in VSCode](https://cloud.ibm.com/docs/schematics?topic=schematics-edit-blueprintsbp-edit-vscode)



* [Blueprint usage and configuration documentation](https://cloud.ibm.com/docs/schematics?topic=schematics-edit-blueprintsbp-usage-config-doc)
* [Push edited template](https://cloud.ibm.com/docs/schematics?topic=schematics-edit-blueprintsbp-push-template)



* [Next steps](https://cloud.ibm.com/docs/schematics?topic=schematics-edit-blueprintsbp-edit-nextsteps)



[Create a blueprint configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-configcreate-blueprint-config)



* [Creating a blueprint configuration through the CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-configcreate-blueprint-cli)



* [Verifying blueprint config creation](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-configverify-blueprint-create-cli)



* [Creating a blueprint configuration using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-configbp-ui-create)



* [Verifying blueprint config creation using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-configverify-blueprint-create-ui)
"id": "3fad3f2204eb4998c3964d254ffcd771",
"name": "Default"
},
"status": "pending",
"status_reasons": [],
"visibility": "private"
"source_volume": {
"id": "4fec84ef-baf9-405d-bf3b-9d5a60e068f7",
"crn": "crn:[...]",
"href": "",
"name": "ifv-boot-vol"
}
}





 Creating an image from a volume of an existing instance 

You can also create an image from a boot volume that is attached to an existing instance. This procedure:



1. Lists all instances and then, gets the ID of a boot volume that is attached to an available, running instance.
2. Stops the running instance.
3. Creates an image by using the ID of the boot volume image.





 Step 1 - Locating the instance and the boot volume ID 

Make a GET /instances call to list all instances and locate the available, running instance that you need. See the following example:

curl -X GET "$vpc_api_endpoint/v1/instances/version=2021-05-20&generation=2" -H "Authorization: $iam_token"

Make a GET /instances/{id} to view details of a single instance and locate its boot volume ID.

The response shows the ID of the boot volume under volume_attachments:

"volume_attachments": [
{
"device": {
"id": "a8a15363-a6f7-4f01-af60-715e85b28141"
},
You can use the key for encryption or decryption only after it is activated in at least one keystore.
8. Under Summary, view the summary of your key, and then click Create key to confirm.



You have successfully created a managed key.

If you are creating internal KMS keys during the master key rotation, internal KMS keys can still be created successfully. However, an Out of sync flag is displayed next to the key state. For each of these keys, you can sync keys by selecting Show details on the Actions ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg) menu and clicking Sync keys after the master key rotation is completed.





 Creating managed keys with the API 

To create a managed key through the API, follow these steps:



1. [Retrieve your service and authentication credentials to work with keys in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-uko-api).
2. Create a key template by making a POST call to the following endpoint.

https://uko.<region>.hs-crypto.cloud.ibm.com:<port>/api/v4/templates
3. Create a managed key based on the supplied template by making a POST call to the following endpoint.

https://uko.<region>.hs-crypto.cloud.ibm.com:<port>/api/v4/managed_keys

The managed key is to be activated in all keystores in the keystore group that is defined in the key template.

For detailed instructions and code examples about using the API method, check out the [Hyper Protect Crypto Services Unified Key Orchestrator API reference doc](https://cloud.ibm.com/apidocs/ukocreate-managed-key).







 What's next
"name": "test-arbitrary-secret-in-group",
"secret_data": {
"payload": "secret-data"
},
"secret_group_id": "339c026a-ac0f-1ea1-3d43-99adf871b49a",
"secret_type": "arbitrary",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"id": "a7f55e6f-b068-977b-062e-4de644633982"
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}

A request to create IAM credentials in the default secret group returns the following response:

{
"request_id": "3bef24c5-5ab9-72f4-8a1a-dd35a6e7aa15",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"access_groups": [
"AccessGroupId-0529f490-129c-4877-a2a0-b57f50d3e53b"
],
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-16T21:34:51Z",
6. Customize the command based on the settings that you want to use.
7. Run the command to create a configuration.
8. Verify your configuration was created.

ibmcloud sat storage config get --config CONFIG







 Creating a configuration in the API 



1. Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 4.9 configuration.
The passphrase must consist of at least 6 characters. To make sure that a new line is not appended, use echo with -n or cat with EOF. If the path is not specified, you are prompted for the passphrase.

-v, --verbose
: Set to true for verbose output.





 Example output 

$ ibmcloud hpvs registration-key-create abcdefg
Enter password>
Successfully created registration key batch file 'abcdefg_registration-batch.txt' in the current working directory.

Successfully generated registration key with gpg.

Successfully exported the public part of the registration key to 'abcdefg.public' in the current working directory.

Successfully exported the private part of the registration key to 'abcdefg.private' in the current working directory.

To use this registration key to generate a registration definition file run ibmcloud hpvs registration-create --registration-key-public-path abcdefg.public --registration-key-private-path abcdefg.private







 hpvs registration-create 

This command creates a registration definition file that is required to instantiate a Hyper Protect Virtual Server based on an own image. You need to run this command only when you want to use your own image (BYOI).

ibmcloud hpvs registration-create [--repository-name REPO-NAME] [--cr-username USER-NAME --cr-pwd-path FILE-PATH | --no-auth] [--allowed-env-keys ENV-KEYS | --no-env] [--image-key-id IMAGE-KEY-ID] [--fingerprint FINGERPRINT] [--image-key-public-path PUBLIC-KEY] [--registration-key-private-path PRIVATE-KEY-PATH] [--registration-key-public-path PUBLIC-KEY-PATH] [--gpg-passphrase-path PASS-PHRASE] [--cap-add CAPABILITIES] [--isv-secrets ISV-SECRETS | --no-isv-secrets]

If you enter the command without any parameters:

ibmcloud hpvs registration-create
From the More Tools tab within your toolchain, you can choose to use either Object Storage or Artifactory as transient storage to save the build binary files.
2. If your account doesn’t contain any instances of Object Storage, the toolchain creates a new Object Storage instance in the default resource group. Next, the toolchain creates a bucket that uses the same name as the toolchain within the new Object Storage instance.
3. If your account already contains Object Storage instances, the toolchain uses one of those instances to store transient build artifacts.
4. To configure Object Storage or Artifactory details, see the [Configuring advanced user options](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-vsicd-vsi-config-advanced) section.
5. Click Create to create the toolchain.









 Step 2: Explore your new toolchain 

After you create your toolchain, it shows each of the tool integrations that are part of the toolchain in a diagram.



 Explore the pipelines 

You can explore the pipelines to understand the toolchain flow and the different operations that run within each pipeline. For example, to view multiple steps such as cra-discovery-scan and the details for Parameter and Status, click the CI Pipeline tool integration, and then click Succeeded PipelineRuns.

Zoom

![CI PipelineRun details](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ci-pipeline-details-updated.png)

Figure 6. Continuous Integration PipelineRun details





 Explore DevOps Insights 

[DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-di_working) aggregates data from your toolchain so that you can track and improve your end-to-end DevOps processes. View quality metrics, track build and deployment jobs, view policies and more.
The new disk is labeled as hdisk1. Using the lspv command:

 lspv
hdisk0 00f6db0acc7aece5 rootvg active

Using the cfgmr command:

 cfgmr
lspv
hdisk0 00f6db0acc7aece5 rootvg active
hdisk1 none none

5. Create an AIX Volume Group by running the mkvg command. On the helper VM, mksysbvg is the volume group name.

mkvg -fy mksysbvg hdlsk1
0516-1254 mkvg: Changing the PVID in the ODM.
mksysbvg

6. Run the crfs command to create a file system and the mount command to mount it. The following example shows a mounted file system (/mksysb) on the helper VM:

crfs -v jfs2 -a size=18G -m/mksysb -g mksysbvg
File system created successfully.
18873588 kilobytes total on disk space.
New File System size Is 37748736
 mount /mksysb
 df -g /mksysb
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/fslv00 18.00 12.26 32% 6 1% /mksysb




After you complete these steps, you must decide on the best access option. IBM provides several different private access options. Each option allows VM instances with internal IP addresses to reach certain APIs and services.

Log on to the source VM where the source mksysb resides and copy the image to the helper VM after you choose an option. In the following example, the customer is using Secure Copy Protocol (scp) from an on-premises system and copying it into the /mksysb file system of the helper VM:

If you did not decide on a private access option, or chose a different option for your internal IP access, your steps might vary.

Running the cksum command:
For more details on how to configure an alert, see [Creating alerts](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-create_alert_ui).





 Configure a dashboard to monitor archiving 

Complete the following steps to define a dashboard:



1. [Launch the Activity Tracker UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch). The Views section opens.
2. Select the Boards icon ![Boards icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/boards.png).
3. Select New board.

![Create board page](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/boards-1.png)
4. Select Add Graph.
5. Select All lines in the Graph a field section.
6. Select Advance filtering and add the following query:

initiator.id:iam-ServiceId-<GUID> action:cloud-object-storage.object.create target.id:<BUCKET-CRN>

Replace <GUID> with the ID value of the service ID that you copied earlier.

Replace <BUCKET-CRN> with the CRN value of the bucket that you can get from the bucket configuration page.

![Create board page](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/boards-2.png)
7.
24203f96-b134-440e-981a-a24f2d432256 my-root-key





 Example 2 

Create a root key and show the JSON output.

 create a root key
$ ibmcloud kp key create my-root-key --output json

{
"id": "24203f96-b134-440e-981a-a24f2d432256",
"name": "my-root-key",
"type": "application/vnd.ibm.kms.key+json",
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:24203f96-b134-440e-981a-a24f2d432256"
}





 Example 3 

Create a root key from a base64-encoded value.

 create a random, base64-encoded, 32-byte key material
$ KEY_MATERIAL=$(openssl rand -base64 32)

 create a root key from a base64-encoded value
$ ibmcloud kp key create my-base64-root-key -k $KEY_MATERIAL

Creating key: 'my-base64-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
5f9eef2d-53b4-42e8-8b56-c2970255210a my-base64-root-key





 Example 4 

Create a root key using an import token.

 create an import token that expires in 5 minutes and allows 10 retrievals
ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-ontap-san --template-version 22.10 --param "managementLIF=MANAGEMENTLIF" --param "dataLIF=DATALIF" --param "svm=SVM" --param "username=USERNAME" --param "password=PASSWORD" --param "limitVolumeSize=LIMITVOLUMESIZE" --param "limitAggregateUsage=LIMITAGGREGATEUSAGE"
6. Customize the command based on the settings that you want to use.
7. Run the command to create a configuration.
8. Verify your configuration was created.

ibmcloud sat storage config get --config CONFIG







 Creating a configuration in the API 



1. Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 21.04 configuration.
"href": "$vpc_api_endpoint/v1/shares/r134-56f91d4a-2801-470a-b368-176bde64e954/mount_targets/r134-b8573e2c-60ee-4ecc-9eae-c52f890a8195",
"id": "r134-b8573e2c-60ee-4ecc-9eae-c52f890a8195",
"name": "sticky-idealist-spoiled-sloppily",
"resource_type": "share_target"
}
],
"user_tags": [],
"zone": {
"href": "https://us-south-genesis-dal-dev13-etcd.iaasdev.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}





 Creating a file share and mount target by specifying a primary network interface 

New

Make a POST /shares request and create a mount target with a primary network interface. Specify the primary_ip property and optional address subproperty, which reserves the IP address that you indicate. This address must not already be reserved on the subnet.

If you don't specify an address, an available address on the subnet is automatically selected. The default access control mode is security_group, which is displayed in the response.

By default, auto_delete for the primary IP is set to true. When you create a mount target with this option and later delete the target, the primary IP is also deleted. To release the primary IP when the mount target is deleted, set auto_delete to false. This example releases the primary IP.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-11&generation=2&maturity=beta" 
-H "Authorization: $iam_token" 
-d '{
"id": "e6ff7b61-feb4-4c87-94aa-277d6f93e164",
"name": "vpc-name1",
"resource_type": "vpc"
}
}
],
"user_tags": [
"env:test",
"env:prod"
],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}
Show more





 Create a file share and mount target by specifying a subnet 

New

The following examople creates and attaches a [virtual network interface](https://cloud.ibm.com/docs/vpc?topic=vpc-vni-about) to your mount target that identifies the file share with a reserved IP address and applies the rules of the selected Security group. To create the mount target with the network interface, make a POST /shares request and specify a subnet. Specifying the subnet property is required when you're not using the [primary_ip property](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=apifs-create-file-share-pni-api) and specifying addressfor a reserved IP.

In this example, the mount target specifies a subnet ID. When the transit_encryption property set to user_managed, encryption in transit with an instance identity certificate is enabled. The default is none, which disables encryption in transit. The default access control mode is security_group, which is shown in the response.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-05-11&generation=2&maturity=beta" 
-H "Authorization: $iam_token" 
-d '{
"size": 10,