vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* instance-memory



* For more information, see:



* [Creating virtual server instances by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) or [Creating virtual server instances by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli).
* [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=ui).
* [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance&interface=ui).











 Create or delete a dedicated host 

Creating or deleting a dedicated host generates a metric for the 'instance-vcpu' resource.



* instance-vcpu



* For more information, see [Creating dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances&interface=ui) and [Managing dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-dedicated-hosts-groups&interface=ui).









 Create or delete a file share 

Creating or deleting a file share generates a metric for the 'share' resource.



* share



* For more information, see:



* [Creating file shares and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=ui).
* [Delete a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uidelete-file-share-ui)
To create an enterprise, you must be the account owner or have the Administrator role on the Billing account management service.

Creating an enterprise from an account and importing existing accounts cannot be undone. This tutorial is provided as an example of the steps you can follow to set up an enterprise by department, but you should carefully plan your enterprise structure around your organization's needs.





 Step 1: Create the enterprise 

Enterprises are created from an existing Subscription account. When you create the enterprise, the account is added to the enterprise hierarchy. Billing transitions to being managed by the enterprise, but its users and resources remain the same and are completely unaffected. For a complete description of account impacts, see [Creating an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-create-enterprise).



1. In the IBM Cloud® console, go to Manage > Enterprise, and click Create.
2. Enter the name of your company, such as Example Corp, to identify your enterprise.
3. Enter your company's domain, such as examplecorp.com.
4. Review the information about the impact to your account, and select I understand the impact to my account. Then, click Create. The account is now permanently part of the enterprise and can't be removed.



After your enterprise is created, you are directed to the enterprise dashboard. From here, you can view the enterprise details, accounts, users, and billing information. Go to the Accounts page to view your enterprise structure, where you see the following accounts:



* An enterprise account with the same name as your enterprise. This account is used for enterprise management.
* The account that you created the enterprise from. Users can continue working with resources in the account unaffected.







 Step 2: Create an enterprise structure with account groups 

Use account groups to [organize related accounts](https://cloud.ibm.com/docs/account?topic=account-enterprise-organize). The second and third tier of the Example Corp. enterprise hierarchy contain the Marketing, Development, Sales, Design, and Engineering account groups. Complete the following steps to create the account groups:



1.
See [Customizing an ordering service configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-orderer-create-json) to learn more about the options that are available.





 Task: Create an ordering service 



Table 13. Create an ordering service

 Display name MSP ID Enroll ID Secret 

 Create ordering service Ordering Service osmsp 
 CA Ordering Service CA 
 Ordering Service Identity OS1 OS1pw 
 Administrator certificate Ordering Service MSP 
 Associate identity Ordering Service MSP Admin 



After the ordering service has been created, you are able to see it on the Nodes panel.









 Step three: Join the consortium hosted by the ordering service 

If your cluster does not use a system channel, skip this step. To verify if a cluster uses a system channel, click the cluster tile and check the Orderer Type.

As we noted earlier, a peer organization must be known to the ordering service before it can create a channel or be joined to a channel when the channel is created. This act of being "known" to the ordering service is also known as "joining the consortium", the list of organizations known to the ordering service. This is because channels are, at a technical level, messaging paths between peers through the ordering service. Just as a peer can be joined to multiple channels without information passing from one channel to another, so too can an ordering service have multiple channels running through it without exposing data to organizations on other channels.

Because only ordering service admins can add peer organizations to the consortium, you will either need to be the ordering service admin or send MSP information to the ordering service admin.

Watch the following video to learn how to add a peer organization to the consortium, create the channel, and join a peer to the channel. For video tutorials on how how to create a peer and an ordering service, see [video series](https://developer.ibm.com/series/ibm-blockchain-platform-console-video-series/):

Video transcript

Hello again, and welcome to this demonstration of how to create a channel using the IBM Blockchain Platform console.
[Two worker nodes](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/autoscaling.png)

Five worker nodes added
5. The difference of nodes that were created by the auto scaling function are destroyed automatically after 10 minutes of not being used.







 Step 7: Customize your HPC cluster for your workloads 

You have two options to add software packages in the cluster for your workload. You can install the additional software in the NFS shared file system (for example, /home/lsfadmin/shared from the LSF management host), which is visible to all compute nodes. The files that you add to the NSF shared file system are stored in the block storage that is attached to the storage node. The data is lost when the entire HPC cluster is being destroyed. Remember to save the data that you want to keep before you destroy the cluster.

The other option is to build your own custom image on top of the default image used by the HPC cluster solution. The creation of the custom image must be prepared before you create an HPC cluster. When a new custom image is created in VPC, a name is associated with this image. You need to use this name in the image_name parameter. For more information, see [Extend base image and create a new custom image](https://github.ibm.com/hybrid-cloud-infrastructure-research/tracker/wiki/Extend-base-image-and-create-a-new-custom-image).





 Step 8: (Optional) Set up hybrid connectivity 

If you want to set up a hybrid connectivity environment by using VPN, see the instructions [Installing a VPN to an HPC cluster](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-install-vpn-hpc-cluster).
* UI
* CLI
* API







 Creating an image from a volume 

Use the UI, CLI, or API to create an image from a volume that is attached to an available virtual server instance as the primary boot volume or as a secondary boot volume.



 Scenarios for creating an image from a volume 

You can create an image from a volume in several ways.



* Select an instance and create an image from that instance's boot volume. The new image inherits the boot volume encryption (customer-managed or IBM-managed).
* Select an instance, create an image from that instance's boot volume, and specify different encryption. For example, if the instance's boot volume was encrypted with IBM-managed encryption, you can select customer-managed encryption for the new image.
* Create an image from a boot volume in the list of block storage volumes. The volume must be a boot volume that is attached to a virtual server instance.



Depending on the size of the image that you're creating, the job might take from 5 minutes to 1.5 hours. You can cancel a job that's taking too long to queue. For more information, see [Performance considerations](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageifv-performance).





 Creating an image from a volume in the UI 

Use the UI to create an image from a volume that is attached to an available virtual server instance as the primary boot volume or as a secondary boot volume.



 Choosing the source for your custom image 

Use the UI to import your custom image by choosing to create and import an image from a volume.



1. In [IBM Cloud console](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 > Compute > Images.
2. On the Custom images tab, click Create.
Creating actions 

Create an IBM Cloud® Functions action, which is a top-level function that returns a JSON object. You can combine actions into a package to simplify the management of your actions.

Before you begin

To create an action, your source code must meet certain requirements. For example, if you want to create an action from code that is contained in multiple files, package your code as a single .zip file before you create the action.

See [Preparing apps for actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prep) for details about the requirements for packaging code for each runtime.



 Creating actions from the CLI 



1. Create an action by running the [ibmcloud fn action create](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_action_create) command.

ibmcloud fn action create <action_name> <file> --kind <runtime>

Example

ibmcloud fn action create hello hello.js --kind nodejs:10

Example output

ok: created action hello
2. Verify that the action is in your actions list.

ibmcloud fn action list

Example output

actions
hello private



Tips:



* To save on cost, you can set limits.



* To set a limit for memory usage, include --memory <value> with your create command, where the value is in megabytes.
* To set a timeout, include --timeout <value> with your create command, where the value is in milliseconds.



* If you packaged your code as a Docker image, include --docker <docker_hub_username>/<docker_hub_image>:<tag> with your create command instead of the local path to your app and the --kind flag. Manage your images well by not using the latest tag whenever possible. When the latest tag is used, the image with that tag is used, which might not always be the most recently created image.
$ 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
e55f86ab-6984-4594-ad23-3024f6440a58 my-base64-root-key

 create a new key material
$ NEW_KEY_MATERIAL=$(openssl rand -base64 32)

 rotate the key
$ ibmcloud kp key rotate e55f86ab-6984-4594-ad23-3024f6440a58 -k $NEW_KEY_MATERIAL

Rotating root key...
OK

 the key was created from a key material, NOT providing a new key material will fail
$ ibmcloud kp key rotate e55f86ab-6984-4594-ad23-3024f6440a58

Rotating root key...
FAILED





 Example 3 

This examples shows how to...



1. Create a root key
2. Create a data encryption key (DEK), this is the plaintext
3. Wrap the DEK with the root key, this creates a ciphertext
4. Rotate the root key
5. Unwrap the ciphertext to reveal the original DEK (plaintext) and a new ciphertext (the new ciphertext is the plaintext wrapped with the new rotated root key)
6. Unwrap the new ciphertext to reveal the original DEK (plaintext)



 create a root key
$ KEY_ID=$(ibmcloud kp key create my-root-key --output json | jq -r '.["id"]')

$ echo $KEY_ID
qT1pyiS1Sivbmmt4doTtfZC4XuLazk7u ...<redacted>... +a/6EqeAamo/9vo=

 capture the encrypted key material
$ ENCRYPTED_KEY=qT1pyiS1Sivbmmt4doTtfZC4XuLazk7u ...<redacted>... +a/6EqeAamo/9vo=

 encrypt the nonce
$ ibmcloud kp import-token nonce-encrypt -k $KEY_MATERIAL -n $NONCE

Encrypted Nonce IV
fR8uRvbrKIm9y/LCq9p6pwFBXbF864q/bw5meQ== efQgA8xBeyuBy39D

 capture the encrypted nonce and the initialization vector (IV)
$ ENCRYPTED_NONCE=fR8uRvbrKIm9y/LCq9p6pwFBXbF864q/bw5meQ==
$ IV=efQgA8xBeyuBy39D

 create a root key using an import token, provide an encrypted key, nonce, and initialization vector (IV)
$ ibmcloud kp key create my-imported-root-key -k $ENCRYPTED_KEY -n $ENCRYPTED_NONCE -v $IV

Creating key: 'my-imported-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
4241a9b3-0ee0-4cfd-b0f3-fd80505fb675 my-imported-root-key





 Example 5 

Create a standard key.

 create a standard key
$ ibmcloud kp key create my-standard-key -s
You can also choose to manually create two partitions in a volume, create a random value as the third seed, wrap it, and store it in the metadata partition:



1. Create two partitions on the block device using the linux command parted.



* 1st partition is labeled as metadata and is of length 100 MiB (note that the metadata partition is reserved for internal metadata only and not to be accessed by a workload). Create a file system (ext4) before using the partition. Create a file by the name keyfile.
* 2nd partition is labeled as data and fills up the full disk space.



2. Use the Hyper Protect Crypto Services KMS API [Wrap a key](https://cloud.ibm.com/apidocs/hs-cryptowrapkey) to generate a random plain text that is rooted in an HSM and wrap it without passing the value.
3. Copy the ciphertext returned from the response object to keyfile with linux commands.
4. Prepare the contract with the KMS information and create a Hyper Protect Virtual Server instance with the manually partitioned volume that contains a wrapped seed.



When the instance is running, the key daemon periodically contacts the Hyper Protect Crypto Services instance. The same timeout kmsTimeout applies. If the Hyper Protect Crypto Services instance cannot be reached, the state of the CRK is not Active, or the access parameters (kms details) no longer match, the daemon will trigger a reboot.

Check logs in Log Analysis if your instance shuts down.







 Working with customer-managed keys for Hyper Protect Virtual Servers for VPC 



 Rotating the root key 

If the CRK is rotated [manually](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-rotate-keys&interface=ui) or automatically based on a [key rotation policy](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-rotation-policy&interface=ui), the key daemon detects the key rotation and rewraps the seed.





 Changing to a different Hyper Protect Crypto Service instance or root key
* UI
* CLI
* API
* Terraform







 Creating a Continuous Delivery service instance 

You must have an IBM Cloud® Continuous Delivery service instance before you can create and use toolchains that contain certain tool integrations. For more information about this limitation, see [Scope of a service instance](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usageservice_scope).

After you create a Continuous Delivery service instance, you can [create continuous delivery toolchains](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started).

You can have one active instance of Continuous Delivery only in a region and resource group. For information about deleting an existing service instance, see [Deleting a Continuous Delivery service instance](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-delete_cd_service).



 Creating a Continuous Delivery service instance by using the console 



1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2. From the IBM Cloud console, click Catalog and select Services.
3. Select the Developer Tools category.
4. Click the Continuous Delivery tile.
5. Select the region that you want to create the Continuous Delivery service in.
6. Choose a Lite or Professional pricing plan. Lite plans offer the full capabilities of Continuous Delivery to small teams at no cost, with usage limits. If you create a Lite-plan instance, it is automatically deleted 30 days after creation. For more information about Continuous Delivery service plans, see [Plan limitations and usage](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage).
7. In the Configure your resource section, specify a name for the Continuous Delivery instance that you are creating.
8. Select the resource group where you want to create the Continuous Delivery service instance.
* For more information about creating a volume during instance provisioning, see [Create and attach a Block Storage for VPC volume when you create an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi).
* For more information about creating a Block Storage for VPC encrypted by your own encryption keys, see [Creating Block Storage for VPC volumes with customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption).



For more information about creating and managing instances in the VPC, see [About virtual server instances for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers).

Block Storage for VPC provides features that are unique to the VPC and are not compatible with the classic infrastructure storage. If you're interested in IBM Cloud® Block Storage for Classic on the classic infrastructure, see [IBM Cloud® Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-getting-started).
For more information, see [Adding the node to the ordering system channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenter-system-channel).
3. [Add the node to any application channels](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenters-add) where you want it to become a consenter.



If you have already created an ordering service, you can reuse the CA, MSP, node identity, and admin identity you created as part of that process when creating the new node and can skip down to the [Create the node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-add-orderer-create-node) section below. If you are creating the node using either a separate console and separate organization (or both), proceed to [Create the node using a separate org and console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-add-orderer-create).



 Create the CA and organization for the new node 

If an organization other than the organization that created the ordering service wishes to create a new node, they will need to complete several steps. For the purpose of this tutorial, it is assumed that a user has followed the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network) in their console and has created a peer, ordering service, and an application channel. Subsequent to this, a separate user, with a separate console, wishes to add a node to that ordering service, which is called Ordering Service.
Creating a workspace 

The first step in building a custom model is to create a workspace.



 About this task 

For each model that you want to build and use, you create a single workspace that contains the artifacts and resources needed to build the model. You then train the model to produce a custom model that can be deployed to an external service for use.

Before creating a workspace, answer these questions:



* What type of model do you want to create?



* Machine learning model: Uses statistical approach to finding entities and relationships in documents. This type of model can adapt as the amount of data grows.
* Rule-based model: Uses a declarative approach to finding entities in documents. This type of model is more predictable, and is easier to comprehend and maintain. However, it does not learn from new data. It can only find patterns it has been taught to look for.
* Advanced Rules model: offers deeper customization for text analysis than rule-based models. See [Creating an advanced rules model](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-create-advanced-rules-model) for instructions.



You can also create one workspace that contains both one rule-based model and one machine learning model.
* What services will use the model?

See [Watson services integration](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_overview_fullwks_watsoninteg) for information about the other Watson services that custom models can be used with.







 Procedure 

To create a workspace, complete the following steps:



1. Log in as a Knowledge Studio administrator, and click Create Workspace.

People with the project manager role can perform almost all tasks except creating a workspace. An administrator must create the workspace initially and assign project managers to it.
2. Give the workspace a name. Choose a short name that reflects your domain content or the purpose of the model. If you need to, you can change the workspace name later.
3. Identify the language of the documents in your workspace.
Create an instance by using the following command.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET --boot-volume VOLUME_ID --keys KEYS --volume-attach VOLUME_ATTACH_JSON

For example, if you create an instance that is called my-instance in us-south-1 and use the bx2-2x8 profile and an existing boot volume, your instance-create command looks similar to the following example.

ibmcloud is instance-create my-instance r134-35b9cf35-616e-462e-a145-cf8db4062fcf us-south-1 bx2-2x8 0726-198db988-3b9b-4cfa-9dec-0206420d37d0 --boot-volume r006-feec3e99-995e-4e8f-896b-48b42c7d05a7 --keys r134-89ec781c-9630-4f76-b9c4-a7d204828d61 --volume-attach @/Users/myname/myvolume-attachment_create.json

For an example volume attachment JSON file, see [Create a volume attachment JSON](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage&interface=clivolume_attachment_json). You can also include [user tags for the volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=clicreate-instance-vol-cli) in the volume attachment.

Information about the network interfaces that are created for the new instance aren't returned after the instance is created. You can view the information by using the ibmcloud is instance INSTANCE command as described in the next step.

The status displays pending until the instance is created.