vania-janet/multiturn-rag-retrieval-data huggingface dataset:
After all the steps are successfully completed, you create the toolchain by clicking Create on the Summary step.

You can always go back to previous steps in the guided installer. The toolchain installer retains all the configuration settings from the successive steps.





 Step 1: Start the CI toolchain setup 

Use one of the following options to access the template for the CI toolchain:



* Click Create toolchain.

[![Create toolchain](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/create_toolchain_button.png)](https://cloud.ibm.com/devops/setup/deploy?repository=https%3A%2F%2Fus-south.git.cloud.ibm.com%2Fopen-toolchain%2Fcompliance-ci-toolchain&env_id=ibm:yp:us-south)
* From the [IBM Cloud console](https://cloud.ibm.com/), click Menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/icons/icon_hamburger.svg) and select DevOps. On the Toolchains page, click Create toolchain. On the Create a Toolchain page, click CI - Develop a secure app with DevSecOps practices.







 Step 2: Set up the CI toolchain name and region 

The Welcome page summarizes the purpose of the toolchain that is created, along with pointers to documentation and related materials. When you are ready to proceed, click Start to begin configuring the toolchain.

Review the default information for the toolchain settings:



1. The toolchain's name identifies it in IBM Cloud.
response = self.service.create_license_entitlement(name=name)
print(response)

createOptions := service.NewCreateLicenseEntitlementOptions()
createOptions.SetName("{name}")
_, response, _ := service.CreateLicenseEntitlement(createOptions)
fmt.Println(response)

name = "{name}";
response = await service.createLicenseEntitlement({ 'name': name } );
console.log(response);

You can unassign a license from the account. Note, however, any IBM Cloud Schematics workspaces in which the license is used will be impacted.
Create a partition 

A partition is a logical and independent space that is associated or attached to the client requesting or creating cryptographic objects in the HSM engine. Each partition has its own data and policies isolated from other partitions. To learn more about partitions, refer to the [Administration Guide (page 211)](https://public.dhe.ibm.com/cloud/bluemix/network/vpx/administration_guide.pdf).

To create a partition, perform the following procedure:



1. Login as the HSM Security Oficer/Administrator using the password specified during [initialization](https://cloud.ibm.com/docs/citrix-netscaler-vpx?topic=citrix-netscaler-vpx-initialize-ibm-hardware-security-module-hsm-):

[jpmongehsm2] lunash:>hsm login

Please enter the HSM Administrators' password:
> 

'hsm login' successful.

Command Result : 0 (Success)
2. Confirm the HSM Admin Login Status is “Logged In”:

[jpmongehsm2] lunash:>hsm show

Appliance Details:
==================
Software Version: 6.2.2-5

HSM Details:
============
HSM Label: jpmonge
Serial : 534071
Firmware: 6.10.9
HSM Model: K6 Base
Authentication Method: Password
HSM Admin login status: Logged In
HSM Admin login attempts left: 3 before HSM zeroization!
RPV Initialized: No
Audit Role Initialized: No
Remote Login Initialized: No
Manually Zeroized: No
[OUTPUT OMITTED]
Show more

The output should show Logged In in the HSM Admin login status. Otherwise, most operations and commands listed in the following sections will fail because they require administrator access.
3. List any existing partitions:
* UI
* API







 Creating managed keys 

You can use Unified Key Orchestrator to create managed keys with the IBM Cloud® console, or programmatically with the Unified Key Orchestrator API.

Before you create a managed key, keep in mind the following considerations:



* For access management, you need to assign a managed key to a vault upon creation.
* A managed key can be assigned to only one vault.
* A managed key can be used for encryption and decryption only after you activate it in at least one keystore.
* You need to select the keystore type when you create a managed key. The keystore type that you select determines where the managed key is to be stored. The keystore type cannot be changed later.
* Assigning a managed key in multiple keystores enables redundancy.
* To protect your privacy, do not store your personal data as metadata for your managed key.





 Creating managed keys with the IBM Cloud console 

To create a managed key by using the console, complete the following steps:



1. [Log in to the Hyper Protect Crypto Services instance](https://cloud.ibm.com/login).
2. Click Managed keys from the navigation to view all the available keys.
3. To create a managed key, click Create key.
4. Under Vault, select a vault for the key for access control, and click Next.

If you want to assign the key to a new vault, click Create vault. For more instructions, see [Creating vaults](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-create-vaults).
5. Under Keystore type, select one of the following keystore types depending on which type of keystore you want to create the key in. And then, click Next.



* AWS Key Management Service: Create a key to be used and stored in an AWS Key Management Service instance.
* Azure Key Vault: Create a key to be used and stored in an Azure Key Vault.
* Google Cloud KMS: Create a key to be used and stored in a Google Cloud KMS keystore.
If you choose to set this option to true, then you must set ibm.io/auto-create-bucket: true and ibm.io/bucket: ""so that your bucket is automatically created with a name with the format tmp-s3fs-xxxx.
* false: When you delete the PVC, the PV is deleted automatically, but your data and the bucket in your IBM Cloud Object Storage service instance remain. To access your data, you must create a new PVC with the name of your existing bucket.



ibm.io/bucket
: In the spec volume claim templates metadata section, set an annotation for the bucket details. Choose between the following options:



* If ibm.io/auto-create-bucket is set to true: Enter the name of the bucket that you want to create in IBM Cloud Object Storage. If in addition ibm.io/auto-delete-bucket is set to true, you must leave this field blank to automatically assign your bucket a name with the format tmp-s3fs-xxxx. The name must be unique in IBM Cloud Object Storage.
* If ibm.io/auto-create-bucket is set to false: Enter the name of the existing bucket that you want to access in the cluster.



ibm.io/secret-name
: In the spec volume claim templates metadata annotations section, enter the name of the secret that holds the IBM Cloud Object Storage credentials that you created earlier. If you add your [IBM Cloud Object Storage credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_install) to the default storage classes, you must not list the secret in the PVC.

kubernetes.io/storage-class
: In the spec volume claim templates metadata annotations section, enter the storage class that you want to use. Choose between the following options:



* If ibm.io/auto-create-bucket: "true": Enter the storage class that you want to use for your new bucket.
* If ibm.io/auto-create-bucket: "false": Enter the storage class that you used to create your existing bucket.
In the [IBM Cloud console ![External link icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/launch-glyph.svg)](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Auto scale > Instance groups.
3. Click New instance group and enter the information in Table 2.
4. If you want to create dynamic scaling policies as part of instance group creation, see [Creating scaling policies](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group&interface=uicreating-scaling-policies). You can also [add policies later](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-instance-groupcreating-target-policies) after you create your instance group.
5. Click Create instance group when the information is complete.





Table 2. Instance group selections

 Field Value 

 Name A name is required for your virtual server instance. 
 Resource group Select a resource group for the instance. 
 Region Select the location where you want your virtual server instance to be created. 
 Placement group Select a placement group for the instance. If you add a placement group, the instance is placed according to the placement group policy. For more information, see [About placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-about-placement-groups-for-vpc). 
 Subnets Select the subnets where you want to create your instance group. To maximize the availability of your applications, select subnets in different zones.
If you delete these configmaps, Code Engine automatically re-creates them.





 Creating configmaps 

Create configmaps with Code Engine.



 Creating a configmap from the console 

Create configmaps with the Code Engine console.

Before you begin, [create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



1. After your project is in Active status, click the name of your project on the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects).
2. From the Overview page, click Secrets and configmaps.
3. From the Secrets and configmaps page, click Create to create your configmap.
4. From the Create config page, complete the following steps.



1. Select the Configmap option.
2. Provide a name; for example, myconfigmap.
3. Click Add key-value pair. Specify one or more key-value pairs for this configmap. For example, specify one key as key1 with the value of value1 and specify another key as key2 with the value of value2. Notice that you can specify values on one or more lines. The name that you choose for your key does not need to be the same as the name of your environment variable.
4. Click Create to create the configmap.



5. Now that your configmap is created from the console, go to the Secrets and configmaps page to view a listing of defined secrets and configmaps.







 Create a configmap with the CLI 

Create configmaps with the Code Engine CLI.

You can populate a configmap in several ways. You can populate it by specifying the key-value pairs directly on the command line, or you can point to a file.

Before you begin
Creation date Set a date range of when the key was created. 
 Keystores The target keystores where the key is activated. 
 Algorithm The encryption algorithm to encrypt data for the key. 
 Length The number of bits that represents the encryption strength of the key. 
 Keystore type The type of keystore where the key is stored. 



You can search for a specific key by using the search bar, or filter keys based on your needs by clicking the Filter icon ![Filter icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/filter.svg) in the Managed keys table. For more information, see [Filtering and searching keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-search-key-list).







 Viewing a list of keys with the API 

To view a list of managed keys 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. View a list of managed keys by making a GET call to the following endpoint.

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

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/ukolist-managed-keys).







 What's next 



* To find out instructions on creating a managed key, check out [Creating managed keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-create-managed-keys).
Created 2023-04-24T18:54:29+05:30
Captured at 2023-04-24T09:48:03+05:30
Tags -
Service Tags -

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





 Creating a snapshot with the API 

You can create a snapshot by using the API.



 Prerequisites for creating a snapshot with the API 

You can create a snapshot by calling the [VPC API](https://cloud.ibm.com/apidocs/vpc). Before you start, gather the following information:



* A unique name for the snapshot.
* The ID of the source volume.
* The resource group ID. You can't change the resource group after the snapshot is created.
* Any tags that you want to attach to the snapshot.







 Creating a snapshot with the API 

To create a snapshot of a boot or data volume, make a POST /snapshots. The following example creates a snapshot of a boot volume by using the volume ID, and specifies user tags that can be associated with a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).

curl -X POST "$vpc_api_endpoint/v1/snapshots?version=2022-12-12&generation=2" -H "Authorization: $iam_token" -d '{
"name": "boot-snapshot-1",
"source_volume": {
"id": "8948ad59-bc0f-7510-812f-5dc64f59fab8"
},
"resource_group": {
"id": "a342dbfb-3ea7-48d1-96e8-2825ec5feab4"
},
"user_tags": [
Two organizations might decide to create a channel only using ordering nodes they own.

In this tutorial, we will create a one node ordering service managed by a single organization. If you want to add additional nodes to this deployment, see [Adding and removing ordering service nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-orderer).





 Creating your ordering service organization CA 

The process for creating a CA for an ordering service is identical to creating it for a peer.



1. Navigate to the Nodes tab and click Add Certificate Authority.
2. In this tutorial, we're creating nodes, as opposed to importing them, so make sure the option to Create a Certificate Authority is selected. Then click Next
3. Give this CA a unique display name, Ordering Service CA. You're free to reuse the CA administrator enroll ID of admin and a secret of adminpw. As this is a different CA, this identity is distinct from the CA admin identity for created for the Org1 CA, even though the ID and secret are identical.
4. The Advanced deployment options are only available in paid clusters and can be safely ignored for purposes of this tutorial. For more information about these options, see the links below.



* [Database and replica sets](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-ha-caibp-console-build-ha-ca-create) (Creating an HA CA) This option is only available on paid clusters.
* [Multizone Kubernetes cluster](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-multi-zone) (Multizone HA) This option is only visible when your cluster is configured with multiple zones.
* [Hardware Security Module (HSM)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm)
For this tutorial, the default settings are sufficient. See [Customizing a CA configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-ca-customization) to learn more about the options that are available.



Task: Creating the peer organization CA



Table 1. Creating the peer organization CA

 Field Display name Enroll ID Secret 

 Create CA Org2 CA admin adminpw 



After you deploy the CA, you will use it when you create your organization MSP, register users, and to create your entry point to a network, the peer.

Advanced users may already have their own CA, and not want to create a new CA in the console. If your existing CA can issue certificates in X.509 format, you can use certificates from your own third-party CA instead of creating new certificates here. The CA should sign using ECDSA and the defaults should be set to use P256 curve. See this topic on [Using certificates from an external CA with your peer or ordering node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-third-party-ca) for more information.





 Associating the CA admin identity 

Each CA is created with a CA admin identity. You can use the admin to register new users with your CA and generate certificates. Before you can use the console to operate your CA, you need to associate the CA admin identity with the CA node itself.

Depending on your cluster type, deployment of the CA can take up to ten minutes. When the CA is first deployed (or when the CA is otherwise unavailable), the box in the tile for the CA will be gray box. When the CA has successfully deployed and is running, this box will be green, indicating that it is "Running" and can be operated from the console. Before proceeding with the steps below, you must wait until the CA status is "Running". If the gray box stops blinking, you can try reloading the page in your browser to refresh the status.
The following table summarizes the options that are used with the fn create command in this example. For more information about the command and its options, see the [ibmcloud ce function create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create) command.



Table 1. Command description

 Option Description 

 --name The name of the function. Use a name that is unique within the project. This value is required.<br><br><br><br> * The name must begin with a lowercase letter.<br> * The name must end with a lowercase alphanumeric character.<br> * The name must be 63 characters or fewer and can contain letters, numbers, and hyphens (-).<br><br><br> 
 --build-source The path to the local source. 
 --runtime The runtime to use for this function. 



3. Use the function get command to display information about your app, including information about the build.

ibmcloud ce function get --name myfun-local

Example output

Getting function 'myfun-local'...
OK

Name: myfun-local
Project Name: sample
Project ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Age: 5m41s
Created: 2023-06-26T16:50:14Z
URL: https://myfun-local.glxo4kabcde.us-south.codeengine.test.appdomain.cloud
Status: Ready

Resources:
CPU: 0.25
Memory: 500M
Max Execution Time: 60 seconds

Build Information:
Build Run Name: myfun-local-run-230123-111011111
Build Type: local
Build Strategy: codebundle-nodejs-18
Timeout: 600
Source: main.js

Build Run Summary: Succeeded
Build Run Status: Succeeded
Creation time The date and time when the virtual data center was created. 
 Status The status of the virtual data center. 



The virtual data center can have different statuses.



Table 3. Status descriptions for virtual data centers

 Status Description 

 Creating The virtual data center is being created. 
 Available The virtual data center is ready to use. 
 Modifying The virtual data center is being modified. 
 Deleting The virtual data center is being deleted. 







 Related links 



* [Resizing-virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_resize)
* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [Deleting VMware Shared virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_deletinginstance)
* [Viewing-virtual data center details](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-details)
* [Accessing the VMware Cloud Director Management console](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_accessing-vcd-console)
* [VMware Cloud Director](https://www.vmware.com/ca/products/cloud-director.html)
In your PVC, set ibm.io/auto-create-bucket: "false" and provide the name of the existing bucket in ibm.io/bucket. 
 bucket auto-create must be enabled when bucket auto-delete is enabled In your PVC, you set ibm.io/auto-delete-bucket: true to automatically delete your data, the bucket, and the PV when you remove the PVC. This option requires ibm.io/auto-create-bucket to be set to true, and ibm.io/bucket to be set to "" at the same time. In your PVC, set ibm.io/auto-create-bucket: true and ibm.io/bucket: "" so that your bucket is automatically created with a name with the format tmp-s3fs-xxxx. 
 bucket can't be set when auto-delete is enabled In your PVC, you set ibm.io/auto-delete-bucket: true to automatically delete your data, the bucket, and the PV when you remove the PVC. This option requires ibm.io/auto-create-bucket to be set to true, and ibm.io/bucket to be set to "" at the same time. In your PVC, set ibm.io/auto-create-bucket: true and ibm.io/bucket: "" so that your bucket is automatically created with a name with the format tmp-s3fs-xxxx. 
 can't create bucket using API key without service-instance-id If you want to use IAM API keys to access your IBM Cloud Object Storage service instance, you must store the API key and the ID of the IBM Cloud Object Storage service instance in a Kubernetes secret. See [Creating a secret for the object storage service credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-cos-understandcreate_cos_secret). 
 object-path “<subdirectory_name>” not found inside bucket <bucket_name> You specified an existing subdirectory in your bucket that you want to mount to your PVC by using the ibm.io/object-path annotation.
The command returns the following output:

name segment_id
India IBMers ibm_employees_01
IBM Employees ibm_employees









 ibmcloud ac segment create 

You can create a segment, by using the command:

ibmcloud ac segment create {--file FILE-PATH | --name NAME [--segment_id SEGMENT_ID] --description DESCRIPTION --tags TAGS --rules RULES}



 Command options 

--name NAME
: Segment name. Required field - input either as a flag or from file.

--segment_id SEGMENT_ID (optional)
: Segment ID. If this value is not provided, name will automatically become the ID. Optional field - input either as a flag or from file.

--description DESCRIPTION
: Description of the segment. Required field - input either as a flag or from file.

--rules RULES
: List of rules that determine whether the entity is part of the segment. Required field - input either as a flag or from file.

--tags TAGS
: Tags associated with the segment. Required field - input either as a flag or from file.

--file FILE
: Input through a file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/cli?topic=cli-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac segment create --name "IBM Employees" --segment_id "ibm_employees" --description "IBM Employees Segment" --tags "ibm" --rules '[{"attribute_name": "email", "operator": "endsWith", "values": "@ibm.com"]}]'



 Output 

The command returns the following output:

name IBM Employees
segment_id ibm_employees
description IBM Employees Segment
created_time 2021-02-02T19:04:22Z
updated_time 2021-02-02T19:04:22Z









 ibmcloud ac segment get