vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you create an instance template, validation steps are performed that ensure you can use your template to provision a virtual server instance. Need more help? You can always run ibmcloud is help instance-template-create to display help for creating an instance template.







 Creating an instance group 

After you have your instance template in hand, your next step is to create an instance group. Before you can run the instance-group-create command, you must specify a name for the instance group and determine values for the command options, such as what instance template you want to use.

If you want to include a load balancer for your instance group to balance incoming requests across instances and configure specific health checks, you must create the load balancer before you create the instance group. For more information, see



* [About application load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers-about) and [Creating an IBM Cloud Application Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancer).
* [About network load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers) and [Creating an IBM Cloud Network Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer).



For more information about health checks for load balancer pools, see



* [Working with health checks](https://cloud.ibm.com/docs/vpc?topic=vpc-alb-health-checks).
* [Working with health checks](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-health-checks).



Gather the following information.



Table 2. Required instance group details

 Instance group details Description 

 Instance template ID of the instance template that you created in the previous task
It's also possible to assign more easier-to-read names by using "user_friendly_names" or "alias" keywords in multipath.conf. For more information, see the [multipath.conf man page](https://linux.die.net/man/5/multipath.conf).

The volume is now mounted and accessible on the host. You can create a file system next.







 Step 7: Creating a file system (optional) 

Follow these steps to create a file system on the newly mounted volume. A file system is necessary for most applications to use the volume. Use [fdisk for drives that are less than 2 TB](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingRHEL8fdiskrhel) and [parted for a disk bigger than 2 TB](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingRHEL8partedrhel).



 Creating a file system with fdisk 



1. Get the disk name.

fdisk -l | grep /dev/mapper

The disk name that is returned looks similar to /dev/mapper/XXX.
2. Create a partition on the disk.

fdisk /dev/mapper/XXX

The XXX represents the disk name that is returned in Step 1.

Scroll further down for the commands codes that are listed in the fdisk command table.
3. Create a file system on the new partition.

fdisk –l /dev/mapper/XXX



* The new partition is listed with the disk, similar to XXXp1, followed by the size, Type (83), and Linux®.
* Take a note of the partition name, you need it in the next step. (The XXXp1 represents the partition name.)
* Create the file system:

mkfs.ext3 /dev/mapper/XXXp1



4. Create a mount point for the file system, and mount it.
(https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-url)
* [How is resource provisioning performed?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-resource)
* [How do you view the blueprint provisioned resources in your cloud account?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-results)
* [How do you securely pass input variables?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-secure-inputs)
* [Why does the blueprint template, basic example, fail in the apply step?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-basic-example)
* [What is the time taken to create an IBM Kubernetes Service cluster and other resources?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-time)
* [How do you configure the version of Terraform to used?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-tf-version)
* [Is it possible to specify the CLI parameters as a file?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprints-faqfaqs-bp-cli-file)
* [When you create a blueprint config in the us-south target region, why is the blueprint job ID indicating us-east?]
That’s the config block that was created during the create channel flow. On the channel details tab you’ll see nodes and channel members.

To initiate a channel update, click the update button. This will allow you to edit many of the fields you specified when creating the channel, and to perform important tasks like adding channel members. The advanced configuration tab allows you to edit features like capability levels and ordering service consenters that were not edited during channel create. Note that some of these options will require the approval of an ordering service organization.

So now that we have created a channel and joined a peer to it, we can install a smart contract. We can add other members to our channel. We have everything we need to start transacting using the IBM Blockchain platform console. Thank you for watching, and happy block chaining.



 Add the organization to the consortium 

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.

After the Ordering service tile has the green status indicator you can proceed with the following steps. Because you created the ordering service admin using the console, this process is relatively straightforward:



1. Navigate to the Nodes tab.
2. Scroll down to the ordering service you created and click the tile to open it.
3. Under Consortium Members, click Add organization.
4. From the drop-down list, select Org1 MSP, as this is the MSP that represents the peer's organization: Org1.
5. Click Add organization.



When this process is complete, it is possible for Org1 to create or join a channel hosted on your Ordering Service.

In this tutorial, we can easily access the Org1 MSP because both the peer organization and the ordering service organization were created in the same console. In a production scenario, the MSP definitions of other organization would be created by different network operators in their own cluster using their own IBM Blockchain console. In those cases, when the organization wants to join your consortium, the organization MSP definition of the organization will need to be sent to your console in an out of band operation.
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
}
]
}







 hpcs uko vault-create 

Create a vault in the instance with the specified name and description.

ibmcloud hpcs uko vault-create --name NAME [--description DESCRIPTION]



* Command options

--name (string)
: Required. A human-readable name to assign to your vault. To protect your privacy, do not use personal data, such as your name or location. The length must be between 1 and 100 characters. The value must match the regular expression /^[!A-Za-z0-9@$%'_-]!$/.

--description (string)
: Optional. The description of the vault. The length must be between 0 and 200 characters. The value must match the regular expression /(.|\n)/.
* Example

ibmcloud hpcs uko vault-create 
--name='Example Vault' 
--description='The description of the creating vault' 
--output json
* Output

The command returns the output similar to the following example:

ETag
2022-05-20T15:27:01Z
{
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"description": "Test Vault Name description.",
"created_at": "2022-03-09T10:57:43Z",
"updated_at": "2022-03-09T10:57:43Z",
"created_by": "IBMid-1308197YB4",
lvcreate -l ${NFS_sz1} -n ${NFS_lv1} ${NFS_vg}

lvcreate -l ${NFS_sz2} -n ${NFS_lv2} ${NFS_vg}

lvcreate -l ${NFS_sz3} -n ${NFS_lv3} ${NFS_vg}





 Creating the file systems 

On NODE1, create the file systems for NFS exports.

The example uses file system type xfs. Other file system types are possible. Then, the resource definitions need to be changed.

mkfs.xfs /dev/${NFS_vg}/${NFS_lv1}

mkfs.xfs /dev/${NFS_vg}/${NFS_lv2}

mkfs.xfs /dev/${NFS_vg}/${NFS_lv3}





 Creating the mount point for the NFS export 

On both nodes, run the following command.

mkdir -p ${NFS_fs1}





 Making sure that a volume group is not activated on multiple cluster nodes 

Volume groups that are managed by Pacemaker must not activate automatically on startup.

For RHEL 8.5 and later, you can disable autoactivation for a volume group when you create the volume group by specifying the --setautoactivation n flag for the vgcreate command.

On both nodes, edit file /etc/lvm/lvm.conf and modify the auto_activation_volume_list entry to limit autoactivation to specific volume groups.

vi /etc/lvm/lvm.conf

Search for parameter auto_activation_volume_list and add the volume groups, other than the volume group that you defined for the NFS cluster, as entries in that list.

Sample setting of the auto_activation_volume_list entry in /etc/lvm/lvm.conf:

auto_activation_volume_list = [ "rhel_root" ]
$ KEY_MATERIAL=$(openssl rand -base64 32)

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

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





 Example 4 

Create a root key using an import token.

 create an import token that expires in 5 minutes and allows 10 retrievals
$ ibmcloud kp import-token create -e 300 -m 10

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

 extract the nonce that was created by the "kp import-token create" command
$ NONCE=$(ibmcloud kp import-token show | jq -r '.["nonce"]')

 extract the public key that was created by the "kp import-token create" command
$ PUBLIC_KEY=$(ibmcloud kp import-token show | jq -r '.["payload"]')

 encrypt the key material using the public key
$ ibmcloud kp import-token key-encrypt -k $KEY_MATERIAL -p $PUBLIC_KEY

Encrypted Key
qT1pyiS1Sivbmmt4doTtfZC4XuLazk7u ...<redacted>... +a/6EqeAamo/9vo=

 capture the encrypted key material
$ ENCRYPTED_KEY=qT1pyiS1Sivbmmt4doTtfZC4XuLazk7u ...<redacted>... +a/6EqeAamo/9vo=
* [Creating network zones from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcreate-network-zone-console)



* [Creating rules](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcreate-cbr-rule-openshift)



* [Creating rules by using the API](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcreate-cbr-rule-api)
* [Creating rules from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcreate-cbr-rule-cli)
* [Creating rules from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcreate-cbr-rule-console)



* [Limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-cbrcbr-limitations)



[Example context-based restrictions scenarios](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorialcbr-tutorial)



* [Understanding the scenario](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorialcbr-tutorial-scenario)
* [Prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorialcbr-tutorial-prereqs)
* [Creating your network zone](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorialcbr-tutorial-create-zone)
* [Creating your CBR rule](https://cloud.ibm.com/docs/openshift?topic=openshift-cbr-tutorialcbr-tutorial-create-rule)
The following example function create command creates the myfun function, which references code that is located in https://github.com/IBM/CodeEngine. This command automatically builds the code bundle and uploads it to an IBM Cloud® Container Registry namespace in your account. The function references this built code bundle. By specifying the --build-context-dir option, the build uses the source in the helloworld-samples/function-nodejs directory.

ibmcloud ce function create --name myfun --runtime nodejs-18 --build-source https://github.com/IBM/CodeEngine --build-context-dir /helloworld-samples/function-nodejs

Example output

Preparing function 'myfun' for build push...
Creating function 'myfun'...
Submitting build run 'myfun-run-230111-111212718'...
Creating image 'icr.io/ce--abcde-glxo4kabcde/function-myfun:230111-1532-vwo4o'...
Waiting for build run to complete...
Build run status: 'Running'
Build run completed successfully.
Run 'ibmcloud ce buildrun get -n myfun-run-230111-111212718' to check the build run status.
Waiting for function 'myfun' to become ready...
Function 'myfun' is ready.
OK
Run 'ibmcloud ce function get -n myfun' to see more details.

https://myfun.11a66hbi3rhz.us-south.codeengine.appdomain.cloud

Notice the output of the function create command provides information on the progression of the build run before the function is created.

In this example, the built code bundle is uploaded to the ce--abcde-4svg40kna19 namespace in Container Registry.

The following table summarizes the options that are used with the function create command in this example.
If you're unfamiliar with Hyperledger Fabric, which the IBM Blockchain Platform is based on, you might not realize you have to create a Certificate Authority before you create a peer. This is because before we can create a peer, we have to create some identities. These identities allow a network entity, whether it’s an admin or a node, to sign its actions using a certificate. Those certificates are issued by a Certificate Authority, also known as a CA. Therefore, our first step in creating a peer is to create a CA and use it to register identities for the peer admin and for the peer itself. After which we’ll need to create a definition for org1.

To do that, click on Add certificate authority. We’re going to be creating a CA here, not importing one. Then, give this CA a display name. Because it's going to be associated with org1, we'll call it org1 CA. Next we’ll give an enroll ID and secret for the user who will be the admin of the CA itself: admin and adminpw. Note the resource allocation box. If you leave this box deselected, your CA will be deployed with default resources. If you want to know what those resources are, for example to check against the resources available in your cluster, click the box and then next. If you’re comfortable with the default allocation, click next. You’ll be taken to the summary screen which will show the values for the CA you are creating.

If these seem right to you, click Add Certificate Authority. The process of deploying a CA can take a few minutes.

To check on the status of your deployments, make sure to refer to your Kubernetes dashboard. If the box on a node does not turn green, or turns gray at some point, you can check on its status by making sure you’re in the correct resource group and clicking on your deployments. The Kubernetes dashboard is also how you will extend resources in your cluster, as needed. When the CA is ready, you’ll see the gray box turn green, indicating that the CA has been deployed.
[jpmongehsm2] lunash:>partition create -partition partition6

On completion, you will have this number of partitions: 6

-label: Not provided; using name for label.

Please enter a password for the partition:
> 

Please re-enter password to confirm:
> 

Please enter a cloning domain to use when creating this partition:
> 

Please re-enter cloning domain to confirm:
> 

Type 'proceed' to create the initialized partition, or 'quit' to quit now.
> proceed
'partition create' successful.

Command Result : 0 (Success)
Show more

Where the syntax is:

partition create -partition <name-for-new-Partition>
5. Confirm the new partition was created:

[jpmongehsm2] lunash:>partition list

Storage (bytes)	 	----------------------------
Partition Name Objects Total Used Free
===========================================
534071016 partition1 0 207559 0 207559
534071020 partition2 3 207559 3464 204095
534071027 partition3 0 207559 0 207559
534071021 partition4 2 207559 1652 205907
534071030 partition5 10 207559 9400 198159
534071053 partition6 0 207559 0 207559

Command Result : 0 (Success)

The output of the Partition List command now shows six partitions.
* Create application channels

The multiregion ordering service is now configured for HA across regions and is ready for peer organizations to create application channels. If the peers do not reside in any of the consoles that are used in this tutorial, you need to export our five-node ordering service and import it along with the orderer organization MSP into the console where the peer resides. This allows the peer organization admin to create application channels that are based on the ordering service. For instructions on how to create an application channel, see the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-create-channel).
* Multi-organization ordering service

For simplicity, we use a single organization for all five ordering nodes in this tutorial. But it is possible when you build an HA ordering service that multiple organizations will want to contribute their own ordering nodes to the ordering service. In that case, the process is largely the same. The major difference is that each organization that wants to contribute an ordering node needs to have their own CA and own organization MSP definition. The process to add ordering nodes from separate organizations is described in the [Adding and removing ordering service nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-orderer) topic and the resulting architecture in this case would be similar to:

Zoom

![Multiregion multi-organization ordering service](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/mr-ha-os-multiorg.png)

Figure 6. Multiregion, multi-organization ordering service





* Clean up
Want to start fresh? You can remove the following resources that you created as a part of this tutorial:



* From the Nodes tab, open the Multiregion OS CA and click the trash can !
* Pod: When each Certificate Authority, peer, ordering service, or smart contract is deployed, a new Pod is created in a worker node in your cluster. Every time you deploy a smart contract, a new pod is launched for the smart contract.
* App containers: Containers are created inside the pods for each node that is deployed.
* Persistent Storage: Storage for each node is dynamically provisioned from the Kubernetes cluster default storage class every time a node is deployed.



![version 1.4](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/1-4_Pill.png) The following illustration shows how the IBM Blockchain Platform components are deployed to the Kubernetes cluster assuming Hyperledger Fabric v1.4 images are used by the peer.

Zoom

![IBM Blockchain Platform and the Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/IBP-IKS-Diagram-14.svg)

Figure 3: Deploying the IBM Blockchain Platform to a Kubernetes cluster on IBM Cloud.



* Pod: When each Certificate Authority, peer, or ordering service is deployed, a new Pod is created in a worker node in your cluster.
* App containers: Containers are created inside the pods for each node that is deployed.
* Persistent Storage: Storage for each node is dynamically provisioned from the Kubernetes cluster default storage class every time a node is deployed.









 (Optional) Add additional users to the console 

By default, the console uses [IBM Cloud Identity and Access Management (IAM)](https://cloud.ibm.com/docs/account?topic=account-iamoverview) as the IBM Cloud identity service provider. Your IBM Blockchain Platform console is provisioned by configuring the email address of the IBM owner as the Administrator of the console.
* I created a toolchain, why does the Toolchains page show that a Continuous Delivery service is required?

The terms of the plan for the Continuous Delivery service instance that is in the same resource group as the toolchain manages the use of some of the tool integrations (Delivery Pipeline and Git Repos and Issue Tracking) that are contained in the service. The error message indicates that the resource group doesn't contain the required instance of the Continuous Delivery service. For more information about the terms of your plan, see [Plan limitations and usage](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage).
* Can I create a toolchain instance from a template programmatically?

You can directly call the toolchain creation page endpoint to pass all of the parameter values. For more information about these parameters, see [Toolchain Creation Page Parameters](https://github.com/open-toolchain/sdk/wiki/Toolchain-Creation-page-parameters).
* Do I need a separate toolchain instance for each piece of work that my team owns?

You can define multiple pipelines within a single toolchain. However, if these pieces of work are unrelated and only share a definition repo, you can create them in separate toolchains so that you can administer them separately.
* Can I create a toolchain template and then use it to create a toolchain for each piece of work that my team owns?

Creating a custom template is more work, but it ensures that all of your toolchains have the same structure. By using a template, you can quickly add toolchains in the future. If you’re creating only a few toolchains and a standard template exists that is similar to what you need, use that template and customize your toolchains after they are created.
* I created a toolchain template that specified a particular tag and then created toolchains from that template. If I edit my template to change the tag are my toolchains updated with that tag?
* UI
* API







 Creating standard keys 

You can create a standard encryption key with the Key Protect console.

You can create a standard encryption key programmatically with the Key Protect API.



 Creating standard keys in the console 

[After you create an instance of the service](https://cloud.ibm.com/docs/key-protect?topic=key-protect-provision), complete the following steps to create a standard key in the IBM Cloud console.

If you enable [dual authorization settings for your Key Protect instance](https://cloud.ibm.com/docs/key-protect?topic=key-protect-manage-dual-auth), keep in mind that any keys that you add to the service require an authorization from two users to delete keys.



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 create a new key, click Add and leave the Create a key option selected.

Specify the key's details:





Table 1. Descriptions of settings for creating a key.

 Setting Description 

 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. Root keys are selected by default. Select the Standard key button to create a standard key. 
 Key name A human-readable display name for easy identification of your key. Length must be within 2 - 90 characters (inclusive). To protect your privacy, ensure that the key name does not contain personally identifiable information (PII), such as your name or location. Note that key names do not need to be unique. 
 Key alias Optional.