vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The Ed25519 SSH key type can be used only to create instances if the operating system supports this key type. This key type can't be used with Windows or VMware images.

curl -X POST "$vpc_api_endpoint/v1/keys?version=2023-03-30&generation=2" -H "Authorization: Bearer $iam_token" -d '{
"name":"my-key-1",
"public_key":"AAAAB3NzaC1yc2EAAAADAQABAAABAQDDGe50Bxa5T5NDddrrtbx2Y4/VGbiCgXqnBsYToIUKoFSHTQl5IX3PasGnneKanhcLwWz5M5MoCRvhxTp66NKzIfAz7r+FX9rxgR+ZgcM253YAqOVeIpOU408simDZKriTlN8kYsXL7P34tsWuAJf4MgZtJAQxous/2byetpdCv8ddnT4X3ltOg9w+LqSCPYfNivqH00Eh7S1Ldz7I8aw5WOp5a+sQFP/RbwfpwHp+ny7DfeIOokcuI42tJkoBn7UsLTVpCSmXr2EDRlSWe/1M/iHNRBzaT3CK0+SwZWd2AEjePxSnWKNGIEUJDlUYp7hKhiQcgT5ZAnWU121oc5En",
"type":"rsa"
}'





 Updating your SSH key by using the CLI 

You can update an existing key by using the ibmcloud is key-update command. After you update an existing key, the key is renamed immediately. For more information, see [ibmcloud is key-delete](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencekey-delete).
Extract all files from the .zip file. The extracted contents include XMI files (.xmi), the UIMA TypeSystem descriptor file (TypeSystem.xml), and other files.







 What to do next 

You must define a mapping between the UIMA types and Knowledge Studio entity types. You must also create a .zip file that contains all of the files that are required to upload the analyzed data into a Knowledge Studio workspace.







 Mapping UIMA types to entity types 

Before you upload XMI files into a Knowledge Studio workspace, you must define mappings between the UIMA types and Knowledge Studio entity types.



 Before you begin 

The type system in your Knowledge Studio workspace must include the entity types that you want to map the UIMA types to.





 Procedure 

To map UIMA types to Knowledge Studio entity types, follow these steps:



1. Create a file named cas2di.tsv in the folder that contains the UIMA TypeSystem descriptor file, such as exported_typesystem.xml or TypeSystem.xml.
2. Open the cas2di.tsv file with a text editor. Each line in the file specifies a single mapping. The format of the mapping depends on which annotator's annotations you want to map:



* You can create mappings by using the basic format:

UIMA_Type_Name[TAB]WKS_Entity_Type

The following example defines mappings between UIMA types produced by the Named Entity Recognition annotator in Watson Explorer Content Analytics and entity types defined in a Knowledge Studio type system:

com.ibm.langware.Organization ORGANIZATION
com.ibm.langware.Person PERSON
com.ibm.langware.Location LOCATION

Another example defines a mapping between UIMA types produced by custom annotator that was created in Watson Explorer Content Analytics Studio and Knowledge Studio entity types:

com.ibm.Person PERSON
com.ibm.Date DATE
* You can create mappings based on facets that are used in the Pattern Matcher annotator or Dictionary Lookup annotator in Watson Explorer Content Analytics. In text analysis rule files (.pat), the facet is represented as the category attribute.
[Screen capture of creating an entity](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/create-entity.png)
5. For this entity, choose whether you want your assistant to use a dictionary-based or annotation-based approach to find mentions of it, and then follow the appropriate procedure.

For each entity that you create, choose one entity type to use only. As soon as you add an annotation for an entity, the contextual model is initialized and becomes the primary approach for analyzing user input to find mentions of that entity. The context in which the mention is used in the user input takes precedence over any exact matches that might be present. See [Entity evaluation overview](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-described) for more information about how each type is evaluated.



* [Dictionary-based entities](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-create-dictionary-based)
* [Annotation-based entities](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-create-annotation-based)









 Adding dictionary-based entities 

Dictionary-based entites are those for which you define specific terms, synonyms, or patterns. At run time, your assistant finds entity mentions only when a term in the user input exactly matches (or closely matches if fuzzy matching is enabled) the value or one of its synonyms.



1. In the Value name field, type a value. For example, for the @city entity, you might type New York City.

An entity value can be any string up to 64 characters in length.

Important: Don't include sensitive or personal information in entity names or values. The names and values can be exposed in URLs in an app.
2. Add synonyms for the value. For example, you might add NYC and The Big Apple as synonyms for New York City.
ibmcloud atracker target create --name "My target" --type event-streams --target-crn "crn:v1:bluemix:public:messagehub:eu-de:a/11111111111111111111111111111111:22222222-2222-2222-2222-222222222222::" --brokers "broker-1:9093,broker-2:9093" --topic "topic-name" --api-key xxxxx

To see the target definition in a region, see [Getting information about a target using the CLI](https://cloud.ibm.com/docs/atracker?topic=atracker-target_v2_ies&interface=clitarget-get-cli-ies).

When your target is created the target ID is returned. Make note of the target ID. You will need the target ID to configure a rule that routes events to the target in the account.





 Step 4: Next 

Define 1 or more routes in the account. For more information, see [Configuring a route](https://cloud.ibm.com/docs/atracker?topic=atracker-route_v2&interface=cliroute-create-cli).

When you configure a route, you associate a target with a route and define which type of auditing events are routed. The route defines the rules that determine where auditing events are routed in your account. For example, you can define a route that routes auditing events from 2 different regions, and also routes global events.

You can collect [global events](https://cloud.ibm.com/docs/atracker?topic=atracker-event_typesevent_types_global) and [location-based events](https://cloud.ibm.com/docs/atracker?topic=atracker-event_typesevent_types_location).



* Global events report on activity in your account that relate to data and resources that are generally synchronized across all regions.
For more information about each function, see [Artifact creation functions](https://cloud.ibm.com/docs/sql-query?topic=sql-query-artifact).





 stringConditionalExpression 

The three conditional expression functions for string values are TS_EXP_IF_THEN_ELSE(), TS_EXP_IF_THEN(), and TS_EXP_MATCH_CASE().

For more information about each function, see [Artifact creation functions](https://cloud.ibm.com/docs/sql-query?topic=sql-query-artifact).





 identityTimeSeriesExpression 

The identity expression denotes current observation values in time series.







 Operator 

The following types of operators can be used:



* [Unary](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referenceunaryOperator)
* [Arithmetic](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencearithmeticOperator)
* [String](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencestringOperator)
* [Comparison](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencecomparisonOperator)
* [Boolean](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencebooleanOperator)







 Unary operators 



Table 50. Unary operators.

 Operator Operand types Description 

 -A All number types Unary negative operator. The type of the result is the same as the type of A. 
 +A All number types Unary positive operator. The type of the result is the same as the type of A. 
 A All number types Bitwise NOT operator. The type of the result is the same as the type of A. 







 Arithmetic operators 



Table 51. Arithmetic operators.

 Operator Operand types Description
oc create route edge $MYPROJECT-httpsca --service=$MYPROJECT --cert=example.pem --key=example.key --hostname=<www.HOSTNAME> --port=3000

Here, you have used Edge termination. To learn about other secured routes and termination types like passthrough and re-encryption, run oc create route --help command)









 Step 8: Remove resources 



* Delete all resource objects specific to an application:

oc delete all --selector app=$MYPROJECT

To list the application names in the project, run oc get svc | awk '{print $1}'
* Delete the project:

oc delete project $MYPROJECT
* Delete the cluster you created.







 Related content 



* [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-why_openshift)
* [Horizontal Pod Autoscaling](https://docs.openshift.com/container-platform/4.12/nodes/pods/nodes-pods-autoscaling.html)
* [Secured routes](https://docs.openshift.com/container-platform/4.12/networking/routes/secured-routes.html)
Creating plan my-crc-plan1 of backup policy my-backup-policy-v1 under account Test Account as user test.user@ibm.com...
ID r134-f0d881c9-213e-471b-bba7-999ee2eee3ff
Name my-crc-plan1
Active true
Lifecycle state pending
Clone policy Max snapshots Zones
0

Deletion trigger Delete after Delete over count
30 -

Remote Region Policies Region Encryption Key Delete over count
us-east - 10

Attached tags -
Copy tags true
Cron specification 0 0 * * 
Created at 2023-05-05T15:27:01+05:30
Resource type backup_policy_plan

For more information about available command options, see [ibmcloud is backup-policy-plan-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-plan-create).







 Creating backup policies and plans with the API 

You can make calls to the VPC API to create backup policies and plans. A POST /backup_policies request creates a backup policy with tags that you provide to identify Block Storage for VPC volume resources that are to be backed up. The backup policy accepts a backup plan, where you define backup schedules and deletion rules.



 Creating a backup policy and plan with the API 

Make a POST /backup_policies request to create a new backup policy. The match_user_tags property identifies the backup tags on the Block Storage for VPC volume resource and associates it with this plan. In this example, the backup plan is defined as a cron_spec.

curl -X POST "$vpc_api_endpoint/v1/backup_policies?version=2022-04-19&generation=2" -H "Authorization: $iam_token" -d '{
"match_resource_types": [

"volume"
]
],
"match_user_tags": [
"my-daily-backup-policy"
],
You can create subdomains for both public and private VPC load balancers.

ibmcloud oc nlb-dns create vpc-gen2 --cluster CLUSTER (--lb-host VPC_ALB_HOSTNAME | --ip VPC_NLB_IP) [--dns-type public] [--secret-namespace NAMESPACE] [--type (public|private)] [--output json] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--lb-host VPC_ALB_HOSTNAME | --ip VPC_NLB_IP
: For VPC application load balancers, the load balancer hostname. To see load balancer hostnames, run oc get svc -o wide. For VPC network load balancers, the external IP addresses. To specify multiple IP addresses, use multiple --ip options. To see load balancer IP addresses, run oc get svc -o wide.

--dns-type public
: The DNS provider type for the subdomain registration. Currently, only public DNS is supported.

--secret-namespace NAMESPACE
: The Red Hat OpenShift project where you want to create the Kubernetes secret that holds the SSL certificate information for the NLB. If you don't specify a project, the secret is automatically created in the default project.

--type (public|private)
: The VPC load balancer type.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns create vpc-gen2 command 

ibmcloud oc nlb-dns create vpc-gen2 --cluster mycluster --lb-host 1234abcd-us-south.lb.appdomain.cloud --type public
ibmcloud is key-create KEY_NAME (KEY | @KEY_FILE) [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--key-type KEY_TYPE]





 Importing your SSH key by using the API 

To import a new SSH key by using the API, use the [Create a key](https://cloud.ibm.com/apidocs/vpc/latestcreate-key). The file that you import is id_rsa.pub or id_ed25519.pub, which contains your public key. You can't create a brand-new SSH key by using the API. However, you can create a new SSH key by using the UI and from the UI, generate the API code snippet that you need that includes the new SSH key. For more information, see [Creating an SSH key by using the UI](https://cloud.ibm.com/docs/%7Bgenerating-ssh-keys-ui%7D).

For the name property, specify the name of the SSH key. For public_key property, enter in the public key information. For the type property, specify either rsa or ed25519 for the SSH key type.

The Ed25519 SSH key type can be used only to create instances if the operating system supports this key type. This key type can't be used with Windows or VMware images.

curl -X POST "$vpc_api_endpoint/v1/keys?version=2023-03-30&generation=2" -H "Authorization: Bearer $iam_token" -d '{
"name":"my-key-1",
You can create subdomains for both public and private VPC load balancers.

ibmcloud ks nlb-dns create vpc-gen2 --cluster CLUSTER (--lb-host VPC_ALB_HOSTNAME | --ip VPC_NLB_IP) [--dns-type public] [--secret-namespace NAMESPACE] [--type (public|private)] [--output json] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--lb-host VPC_ALB_HOSTNAME | --ip VPC_NLB_IP
: For VPC application load balancers, the load balancer hostname. To see load balancer hostnames, run kubectl get svc -o wide. For VPC network load balancers, the external IP addresses. To specify multiple IP addresses, use multiple --ip options. To see load balancer IP addresses, run kubectl get svc -o wide.

--dns-type public
: The DNS provider type for the subdomain registration. Currently, only public DNS is supported.

--secret-namespace NAMESPACE
: The Kubernetes namespace where you want to create the Kubernetes secret that holds the SSL certificate information for the NLB. If you don't specify a namespace, the secret is automatically created in the default namespace.

--type (public|private)
: The VPC load balancer type.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns create vpc-gen2 command 

ibmcloud ks nlb-dns create vpc-gen2 --cluster mycluster --lb-host 1234abcd-us-south.lb.appdomain.cloud --type public
: Required: The name or ID of the cluster.

--hardware HARDWARE
: Optional: The level of hardware isolation for your worker node. Use dedicated so that available physical resources are dedicated to you only, or shared to allow physical resources to be shared with other IBM customers. The default is shared. For bare metal flavors, specify dedicated.

--flavor FLAVOR
: Choose a machine type, or flavor, for your worker nodes. You can deploy your worker nodes as virtual machines on shared or dedicated hardware, or as physical machines on bare metal. Available physical and virtual machines types vary by the zone in which you deploy the cluster. For more information, see the documentation for the ibmcloud ks flavors (machine-types)[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_machine_types).

--workers NUMBER
: An integer that represents the number of worker nodes to create in the cluster.

--private-vlan PRIVATE_VLAN
: Required: The private VLAN that was specified when the cluster was created. Private VLAN routers always begin with bcr (back-end router) and public VLAN routers always begin with fcr (front-end router). When you create a cluster and specify the public and private VLANs, the number and letter combination after those prefixes must match.

--public-vlan PUBLIC_VLAN
: Optional: The public VLAN that was specified when the cluster was created. If you want your worker nodes to exist on a private VLAN only, don't provide a public VLAN ID. Private VLAN routers always begin with bcr (back-end router) and public VLAN routers always begin with fcr (front-end router). When you create a cluster and specify the public and private VLANs, the number and letter combination after those prefixes must match.
You can use the ibmcloud cbr rule-create[command](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-cli-rule-create-command) to create CBR rules. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/cli?topic=cli-cbr-plugincbr-zones-cli). Note that the service_name for Red Hat OpenShift on IBM Cloud is containers-kubernetes. To find a list of service names, run the ibmcloud cbr service-ref-targets command. To find a list of API types for a service, run the ibmcloud cbr api-types --service-name SERVICE command.



Example command to create a rule that uses the addresses key and the cluster API type and the ipAddress type.

ibmcloud cbr rule-create my-rule-1 --service-name containers-kubernetes --api-type crn:v1:bluemix:public:containers-kubernetes::::api-type:cluster --zone-id ZONE-ID

The following command creates a rule that protects the CLUSTER-ID cluster. Only resources in the NETWORK-ZONE-ID network zone can access the cluster. This rule includes both the cluster and management API types.

ibmcloud cbr rule-create my-rule-2 --service-name containers-kubernetes --service-instance CLUSTER-ID --zone-id NETWORK-ZONE-ID

The following example command creates a rule that allows all private network connections, but allows only resources in the allow-client-ip network zone to connect to the cluster over the public network. For more information about this scenario, see [Setting up context-based restrictions](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorial).
Note: if you do not posses the Manager role on this instance (or an equivalent level of permissions), this field is not visible. 



When you are finished filling out the key's details, click Create key to confirm.

Keys that are created in the service are symmetric 256-bit keys, supported by the AES-CBC-PAD algorithm. For added security, keys are generated by FIPS 140-2 Level 3 certified hardware security modules (HSMs) that are located in secure IBM Cloud data centers.

For more information about creating root keys, check out [Creating root keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys).

For more information about creating standard keys, check out [Creating standard keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-standard-keys).





 Importing your own keys 

You can enable the security benefits of Bring Your Own Key (BYOK) by importing your existing keys to the service. In this example, we'll import a root key.

Complete the following steps to add an existing key.



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/login/).
2. Go to Menu > Resource List to view a list of your resources.
3. From your IBM Cloud resource list, select your provisioned instance of Key Protect.
4. To import a key, click Add and select the Import your own key window.

Specify the key's details:





Table 1. Describes the Import your own key settings.

 Setting Description 

 Key type The [type of key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-envelope-encryptionkey-types) that you would like to manage in Key Protect. Select the Root key button. 
 Name A human-readable alias for easy identification of your key. Length must be within 2 - 90 characters (inclusive).
You can create network zones by using the /v1/zones API. For more information, see the [API docs](https://cloud.ibm.com/apidocs/context-based-restrictionscreate-zone). You can add the containers-kubernetes service to your network zones to allow IBM Cloud Kubernetes Service to access resources and services in your account.

You can include multiple address types in your network zone payload. For more information, see the example payload in the [API docs](https://cloud.ibm.com/apidocs/context-based-restrictionscreate-zone).

Example payload to add IBM Cloud Kubernetes Service to a network zone. The serviceRef attribute for IBM Cloud Kubernetes Service is containers-kubernetes.

{
"name": "Example zone 1",
"description": "",
"addresses": [
{
"type": "serviceRef",
"ref": {
"service_name": "containers-kubernetes",
"account_id": "ACCOUNT-ID"
}
}
]
}

Example payload to add multiple services, IP addresses, and VPCs to a network zone.

{
"name": "zone",
"description": "",
"addresses": [
{
"type": "ipAddress",
"value": "192.168.0.0"
},
{
"type": "vpc",
"value": "crn:v1:bluemix:public:is:us-east:a/CRN"
},
{
"type": "vpc",
"value": "crn:v1:bluemix:public:is:us-south:a/CRN"
},
{
"type": "serviceRef",
"ref": {
"service_name": "cloud-object-storage",
The following list shows supported geospatial functions:



* ST_Distance
* ST_Intersects
* ST_Contains
* ST_Equals
* ST_Crosses
* ST_Touches
* ST_Within
* ST_Overlaps
* ST_EnvelopesIntersect
* ST_IntersectsInterior





 Geospatial data skipping with MinMax indexes 

You can use MinMax indexes on latitude and longitude columns for data skipping. In the following example, the MinMax indexes on the lat and lng columns are used. The following query retrieves all of the points in 1 km around the point POINT(6.433881 43.422323).

SELECT * FROM cos://us-geo/sql/metergen STORED AS PARQUET WHERE
ST_Distance(ST_Point(lng,lat),ST_WKTToSQL('POINT(6.433881 43.422323)')) < 1000.0





 Geospatial data skipping with geospatial indexes 

Geospatial indexes on columns with geometry types can also be used for data skipping. For example, the following statement creates a geospatial index. The hospitals data set is available as a Data Engine sample and contains a geometry type column called “location”. Geometry type columns can be created by using the Geospatial Toolkit.

CREATE METAINDEX
GEOSPATIAL FOR location
ON cos://us-geo/sql/hospitals_geometry.parquet STORED AS parquet

The following example query that uses this index returns the names of those hospitals that are within a radius of 46800 meters of a specified coordinate.

SELECT name
FROM cos://us-geo/sql/hospitals_geometry.parquet STORED AS PARQUET
WHERE ST_Intersects(ST_WKTToSQL(location), ST_Buffer(ST_WKTToSQL('POINT (-74.0 42.0)'), 46800.0))







 Choosing data formats 

You can use data skipping with all of the formats that are supported by Data Engine, except for AVRO.