vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud cbr rule-create --description 'Example Rule Description' --service-name kms --context-attributes endpointType=private --zone-id 93de8d3f588ab2c457ff576c364d1145





 Command options 

--description (string)
: The description of the rule.

--context-attributes (string)
: The context-attributes this rule applies to in the form of name=value,name=value,....

--resource-attributes (string)
: The resource-attributes this rule applies to in the form of name=value,name=value,....

--region (string)
: Shorthand for creating IBM Cloud resource attribute region. For supported regions, run ibmcloud regions.

--resource (string)
: Shorthand for creating IBM Cloud resource attribute resource.

--resource-group-id (string)
: Shorthand for creating IBM Cloud resource attribute resourceGroupId.

--resource-type (string)
: Shorthand for creating IBM Cloud resource attribute resourceType.

--service-instance SERVICE_INSTANCE_GUID (string)
: GUID of the service instance. This option is exclusive with the --file option.

--service-name (string)
: Shorthand for creating IBM Cloud resource attribute serviceName.

--zone-id (string)
: Shorthand for adding context attribute networkZoneId to the first context.

--tags (string)
: The access tags of the resource in the form of name:value,name:value,....

--enforcement-mode (string)
: How the rule is enforced. The CLI accepts the values enabled (default), disabled, and report. For more informaiton about enforcement, see [Rule enforcement](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatisrule-enforcement).

--file (string)
: The supplied file is used to create the rule. This flag is unique and cannot be used with other flags.
* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create). For example, create a job that is called myjob that uses the codeengine image. This image is built from codeengine.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine).



Complete the following steps to create and update a Periodic timer (cron) event subscription for a job from the console.



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions.
3. From the Event subscriptions page, click Create to create your subscription.
4. From the Create event subscription page, complete the following steps.



1. For General, provide a name for the Periodic timer subscription, for example, myptimer2. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
2. For Schedule, provide information about the timing of the events. The Periodic timer (cron) event producer uses standard crontab syntax to specify interval details. Choose your interval from the provided patterns or provide your own custom cron expression, such as 0 0 * * , which specifies for the event to occur every day at midnight. For this example, select the schedule pattern for every day, every hour, every minute. Notice that the cron expression is generated for you. The day, hour, and minute patterns and the Cron expression are in Coordinated Universal Time (UTC). If you do not specify a schedule, then this event subscription sends an event every minute.
[Control plane in normal state](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/includes/cloud-databases/includes/cloud-databases/images/cp-normal.png)

Figure 1. Control plane in normal state

Attempting to provision a database instance into a location without a running Control plane (that is, Normal state), causes provisioning to fail.







 Step 4: Provisioning ICD Satellite Deployment 

You can provision your ICD Satellite Deployment by selecting the Satellite location that you created in the Location menu of the provisioning page. For more information, see the relevant [Provisioning documentation](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-provisioning) for your ICD Satellite deployment. After you create a new service instance, this instance will appear in the IBM Cloud Resource List as Provisioned.

When you deploy the first database service instance, a service cluster is automatically deployed into your Satellite location. The deployment of the service cluster can take up to 1 hour.

You can verify in the IBM Cloud UI whether the service cluster is already created:



* From the left Navigation menu, select Satellite, then Locations.
* Select your Satellite location.
* Select Services



After the service cluster is created, you must create a storage assignment manually (see next step)before the database instance will be started. Subsequent database service instances provision more quickly since instances land on the same service cluster.





 Create a Storage Assignment 

When the service cluster is available in your Satellite location, the next step is to create a Satellite storage assignment. Creating the storage assignment allows the service cluster to create volumes on the previously configured storage.

The first database you provision into a location remains "Provision In Progress" until this step is complete.

For more information, see [AWS EBS IBM Cloud Satellite documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-config-storage-ebs).
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervsphere-csi-driver-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervsphere-csi-driver-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driverstorage-vsphere-csi-driver-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driverstorage-vsphere-csi-driver-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driverstorage-vsphere-csi-driver-include-assignment-create-api)
* [Deploying an app that uses VMware](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-driversat-storage-vmware-deploy-app)
* [Removing VMWare storage from your apps](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervmware-csi-rm-apps)
* [Removing the VMware storage configuration from your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervmware-csi-template-rm)



* [Removing the VMWare storage configuration using the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-vsphere-csi-drivervmware-csi-rm-ui)
* [Creating a VPC cluster in the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2clusters_vpcg2_ui)
* [Creating VPC clusters from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2cluster_vpcg2_cli)
* [Example commands to create VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2cluster_create_vpc)
* [Creating a VPC cluster with Terraform](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-vpc-gen2cluster_vpcg2_tf)



[Creating clusters on dedicated hosts for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-create-dedicated-hostscluster-create-dedicated-hosts)

[Creating Satellite clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatellite-clusters)



* [Prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-prereqs)
* [Creating Red Hat OpenShift clusters on Satellite from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-create-console)
* [Creating Red Hat OpenShift clusters on Satellite from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-create-cli)
[Creating a virtual server](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_create_instance.jpg)

Figure 1. Creating a virtual server
4. In section Select a region, you can select the data center in which to create the virtual server instance, or you can accept the preselected default data center.
5. The Service name field offers a name proposal for your virtual server. You can change this name according to your conventions.
6. In the Tags field, you can optionally add tags to organize your resources.
7. Enter your SSH public key into the SSH public key field. For information about SSH keys, see [Generating SSH keys](https://cloud.ibm.com/docs/services/hp-virtual-servers?topic=hp-virtual-servers-generate_ssh). You can enter the public key with or without the comment. The comment is either automatically generated by the SSH key generation command, or you can optionally overwrite it. The auto-generated comment contains person-related information. That's why any comment is removed as the first step during virtual server provisioning.
8. Select one of the available pricing plans. For initial tests, select the Free plan. With this plan, you can have a maximum of two virtual servers at the same time (excluding expired servers). Selecting a different plan leads to fees charged by IBM.

Zoom

![Available pricing plans](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_plans.jpg)

Figure 2. Available pricing plans
9. Click Create to provision a virtual server instance.



The virtual server instance appears in the Resource list.
Before you begin 

Make sure that you set up your [IBM Cloud® CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup) and your [IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-cli).

To create an auto scale instance group by using the CLI, you must complete the following tasks:



1. Make sure that you have the required IBM Cloud Identity and Access Management (IAM) permissions to create instance group resources. For more information, see [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).
2. Create an instance template that is used to provision instances in your group.
3. Create an instance group in a single region that is made up of like virtual server instances.
4. Create an instance group manager so that you can apply your scaling policies.
5. Create scaling policies to dynamically add or remove instances from your group based on the target utilization metrics that you define.







 Creating an instance template 

All resources that are defined in an instance template must all be in the same resource group as the instance group.



 Gathering information to create an instance template 

Ready to create an instance template? Before you can run the ibmcloud is instance-template-create command, you need to know the details about your instance template and command options, such as what profile or image you want to use. Follow these steps to prepare for running the command.

Gather the following required instance template details.



Table 1. Required instance template details

 Instance template details Listing command 

 VPC ibmcloud is vpcs 
 Zone ibmcloud is zones 
 Profile ibmcloud is instance-profiles 
 Subnet ibmcloud is subnets 
 Image ibmcloud is images 



Use the following commands to determine the required information for creating a new instance template.



1.
r134-89ec781c-9630-4f76-b9c4-a7d204828d61 my-key rsa 4096 gtnf+pdX2PYI9Ofq.. Default

If you do not have an SSH key available, you can create an SSH key by using the [ibmcloud is key-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencekey-create) command. For more information, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).
9. List all the available placement groups that you can associate with your instance.

ibmcloud is placement-groups

For this example, you see a response that is similar to the following output.

ID Name State Strategy Resource Group
c5f1f366-b92a-4080-991a-aa5c2e33d96b placement-group-region-us-south stable power_spread Default







 Creating an instance by using the CLI 

Use the following information to create an instance with the CLI.





 Provision from a stock or custom image 

After you know the needed values, use them to run the ibmcloud is instance-create command. You also need to specify a unique name for the instance.

Use the following steps to create a basic virtual server instance from a stock image by using the CLI. By default, a boot volume is attached to the instance when the instance is created. For most virtual server instances, the default boot volume size is 100 GB. The default boot volume size for a z/OS virtual server instance is 250 GB.



1. Create an instance by using the following command.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET --image IMAGE --keys KEYS
console.log(Bucket: ${bucketName} created!);
logDone();
}))
.catch(logError);
}

// Create new text file
function createTextFile(bucketName, itemName, fileText) {
console.log(Creating new item: ${itemName});
return cos.putObject({
Bucket: bucketName,
Key: itemName,
Body: fileText
}).promise()
.then(() => {
console.log(Item: ${itemName} created!);
logDone();
})
.catch(logError);
}

// Delete item
function deleteItem(bucketName, itemName) {
console.log(Deleting item: ${itemName});
return cos.deleteObject({
Bucket: bucketName,
Key: itemName
}).promise()
.then(() =>{
console.log(Item: ${itemName} deleted!);
logDone();
})
.catch(logError);
}

// Delete bucket
function deleteBucket(bucketName) {
console.log(Deleting bucket: ${bucketName});
return cos.deleteBucket({
Bucket: bucketName
}).promise()
.then(() => {
console.log(Bucket: ${bucketName} deleted!);
logDone();
})
.catch(logError);
}

// Multi part upload
function multiPartUpload(bucketName, itemName, filePath) {
var uploadID = null;

if (!fs.existsSync(filePath)) {
logError(new Error(The file '${filePath}' does not exist or is not accessible.));
* To create an environment, see [Create an environment](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-environmentsac-create-environment).
* To create a feature flag, see [Create a feature flag](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flagsac-create-feature-flag).
* To create a property, see [Create a property](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-propertiesac-create-properties).







 Step 4: Integrate App Configuration service SDK 

App Configuration provides SDKs to integrate with your application. For more information about SDK installation and technical concepts, see [Integrating SDKs](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-sdks).





 Step 5: Create segments 

Segments helps you to quickly turn features on or off for selective audience. Use segments to target feature flags for A/B testing and beta launches.

To create a segment, see [Create a segment](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-segmentsac-create-segment)





 Next steps 



* [How to target Feature flags to Segments](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flagstargeting-segment-with-feature-flag)
* [How to target Properties to Segments](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-propertiestargeting-segment-with-properties)
* [Enable feature flag](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-feature-flagsenabling-feature-flag) (ON/OFF).
* The volume must be in the region where you want to create the custom image.
* The volume must be a primary boot volume with 100 GB capacity. Data volumes are not supported.
* The volume must be attached to an instance. Unattached boot volumes are not supported.
* The instance must be in an available state.
* The available, running instance must be stopped before you create the custom image. Creating an image from a running instance is not allowed.









 Options for creating an image from a volume 

You can create a custom image from a boot volume in several ways.



* In the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimage-from-volume-vpc-ui), you can create a custom image from any of the following places.



* The Custom images for VPC page,
* The list of instances on the Virtual server instances for VPC page,
* The Instance details page,
* The list of volumes on Block storage volumes for VPC page.
* The Volume details page.



* In the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimage-from-volume-vpc-api), you can create a custom image at the same time as you create a new instance, or you can create an image from an existing instance. With the regional API, you create an image by making a POST /images call and passing the boot volume ID.
* From the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimage-from-volume-vpc-cli), you can create a custom image at the same time as you create a new instance, or you can create an image from an existing instance. Issue the ibmcloud is image-create command and specify the boot volume's ID.







 Image from volume encryption 

When you create an image from a volume, you have the following encryption choices.



* If you want to create an instance and boot volume with default IBM-managed encryption, then the image from that boot volume inherits the IBM-managed encryption.
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 Org1 CA admin adminpw 



After you deploy the CA, you need to associate an admin identity. This will allow you to operate your CA and use it to create your organization MSP, register users, and your 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 external CA instead of creating a new CA 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 node is created with a CA admin identity. You use the admin identity 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 status indicator box in the CA tile is a flashing gray box. When the CA is successfully deployed and is running, this box is 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.
"keyVersion": { "id": "2cbea94c-6070-4a24-b0f8-7a56e4d7cb6f", "creationDate": "2020-06-15T16:05:53Z"
}
}
]





 Example 2 

This example shows the full lifecycle of two cloud resources (Cloud Object Storage and Key Protect - from creating Key Protect instances and creating a policy between them to deleting the instances.

A summary of the steps is:



 Step Where Description 

 1 CLI Create cloud object storage (COS) and Key Protect (KP) instances 
 2 CLI Create a policy for COS to access KP encryption keys 
 3 CLI Create a KP root key that COS uses to encrypt data 
 4 Console UI Create a COS bucket and specify KP encryption; this is done in the console user interface (UI) because there is no API or CLI support at this time 
 5 CLI View the KP registration 
 6 CLI Upload and download an object to verify COS and KP works together 
 7 CLI Delete the COS bucket and the KP root key 
 8 CLI Delete the authorization policy between COS and KP 
 9 CLI Delete the COS and KP instances 



These commands show COS and Key Protect service plans. The ibmcloud resource service-instance-create command requires a service plan name and a location, which is in the catalog.

 show the catalog offerings for cloud object storage (COS) and Key Protect
$ ibmcloud catalog service cloud-object-storage

$ ibmcloud catalog service kms

The example covers multiple steps and should be performed in consultation with the summary provided.

 create a Cloud Object Storage (COS) instance
 "lite" is the pricing plan and "global" is the region
$ COS_NAME=my-cos-1

$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

Creating service instance my-cos-1 in resource group Default of account <account name> as <email address>...
OK
New instance Create a virtual server instance on this dedicated host. 
 Disable placement Temporarily prevent new virtual server instances from being provisioned on this host. No instances can be created on the host until placement is enabled again. You must disable placement before you can delete a dedicated host. 
 Enable placement Indicate that new virtual server instances can be provisioned on this host. If placement has been disabled, it must be enabled before instances can be created on the host. 
 Delete If you no longer need the dedicated host, you can delete it to permanently remove it from your account. Before you can delete the dedicated host, you must first delete any virtual server instances on the host. (Click the name of the dedicated host to access the Host detail page which displays instances on the host.) Then, you must disable the placement of any new virtual server instances on the dedicated host. This prevents any new instances from being created before you can delete the dedicated host. If the dedicated host is in a failed state, you can proceed directly with the delete action. 







 Viewing dedicated host details 

You can view details about a dedicated host, such as the dedicated group that it's a part of, the ID of the host, the profile used to create it, and the remaining vCPU and memory on the host.

To view details about a dedicated host, complete the following step:



* On the Dedicated hosts tab of the Dedicated hosts for VPC page, click the name of the dedicated host about which you want to view details.







 Managing dedicated groups 

When you have a dedicated group created, you can create new dedicated hosts within the group. You can also create new virtual server instances on the hosts in the the group. If you no longer need a dedicated group, you can delete it.

To complete management tasks on your dedicated groups, complete the following steps.



1. In the [IBM Cloud console](https://cloud.ibm.com/vpc-ext), go to Menu icon !