vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-config-create-api)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filestorage-local-volume-file-include-assignment-create-console)
* [Creating an assignment in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filestorage-local-volume-file-include-assignment-create-cli)
* [Creating a storage assignment in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filestorage-local-volume-file-include-assignment-create-api)
* [Deploying an app that uses your local file storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filedeploy-app-local-file)
* [Removing the local file storage configuration from your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filesat-storage-remove-local-file-config)



* [Remove the local file storage configuration from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filesat-storage-rm-local-file-ui)
* [Remove the local file storage configuration from the command line](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filerm-local-file-temp-cli)
A builder builds the house from well-defined components using the blueprint for guidance.

It builds on the Schematics Workspace support for Infrastructure as Code (IaC) and Hashicorp Terraform. See [Working with blueprints](https://cloud.ibm.com/docs/schematics?topic=schematics-work-with-blueprints) for details of how to use blueprints and Terraform to create large-scale environments. When using the service, Schematics users create a [blueprint](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb1) to deploy and manage the cloud resources that are specified by a [blueprint template](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb2).



 Blueprint 

A blueprint is the resource in Schematics a user works with to manage the group of modular environments and cloud resources created from a [blueprint template](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb2) and config. The blueprint resource in Schematics records the details of the template and the specific [configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb3) details. All operations against the deployed cloud resources and modules are performed using the blueprint resource or ID.

The blueprint (resource) maintains the record of operations run, job status, the cloud resources deployed, and the [blueprint template](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb2). It defines the infrastructure architecture and the unique input values that are used to configure the environment.

A blueprint is created with a [blueprint configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-termsbpb3).
First, create a root key from a [base64 value](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-key-create-example-3) or an [imported token](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-key-create-example-4).

 create a random, base64-encoded, 32-byte key material
$ 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
* [Creating a virtual server instance with the CLI - provision with a stock or custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cliinstance-create-from-image-cli)
* [Creating a virtual server instance with the API - provision with a stock or custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=apicreate-instance-stock-custom-image-api)
* [Creating an instance using Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=terraformcreate-instance-using-terraform)
Click Vaults from the navigation to view all the available vaults.
3. To create a vault, click Create vault.
4. Enter a name in Vault name. Optionally, you can add an extended description to your vault in the Description section.

The vault name must be of 1 to 100 characters in length. The characters can be letters (case-sensitive), digits (0-9), or symbols (#@!$%\’_-).
5. Click Create vault to confirm.



You have successfully created a vault.





 Creating vaults through the API 

To create a vault through the API, follow these steps:



1. [Retrieve your service and authentication credentials to work with vaults in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-uko-api).
2. Create a vault by making a POST call to the following endpoint.

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

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/ukocreate-vault).







 What's next 



* To find out instructions on editing a vault, check out [Editing vault details](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-edit-vaults).
* To find out how to delete a vault, check out [Deleting vaults](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-vaults).
* To find out how to grant access to vaults, see [Granting access to vaults](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-grant-access-vaults).
mklabel gpt
* Parted can be used to create primary and logical disk partitions, the steps that are involved are the same. To create a partition, parted uses mkpart. You can give it other parameters like primary or logical depending on the partition type that you want to create. The listed units default to megabytes (MB). To create a 10-GB partition, you start from 1 and end at 10000. You can also change the sizing units to terabytes by entering unit TB if you want to.

mkpart
* Exit parted with quit.

quit



3. Create a file system on the new partition.

mkfs.ext3 /dev/mapper/XXXp1

It's important to select the right disk and partition when you run this command. Verify the result by printing the partition table. Under file system column, you can see ext3.
4. Create a mount point for the file system and mount it.



* Create a partition name PerfDisk or where you want to mount the file system.



mkdir /PerfDisk



* Mount the storage with the partition name.



mount /dev/mapper/XXXp1 /PerfDisk



* Check that you see your new file system listed.



df -h
5. Add the new file system to the system's /etc/fstab file to enable automatic mounting on boot.



* Append the following line to the end of /etc/fstab (by using the partition name from Step 3).



/dev/mapper/XXXp1 /PerfDisk ext3 defaults,_netdev 0 1
Because this tutorial presumes that a user is adding a node to a channel that was created as part of the [Build a network tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network), the channel the Ordering Service_2 node is being added to, channel1, does not yet have the newly created ordering service organization, Ordering Service2 MSP, as one of the administrators of the channel. While a new ordering node can be added to a channel even if the organization that owns the node is not an administrator of the ordering service, it is a best practice to add the organization that owns the node when you add the node.

Because you are editing a part of the channel configuration that is governed by ordering service organization admins, you will be asked to send the channel configuration update to an ordering service organization admin to be signed as part of the configuration update process. This organization can be any of the organizations that is an admin of the ordering service, not just one of the organizations that owns one of the consenters that is already in the channel. In this tutorial, that means selecting Ordering Service MSP. Do not select Ordering Service2 MSP here as it is being added as part of this channel configuration update.





 Add Ordering Service2 MSP to channel1 

To add an ordering service organization to an application channel, navigate to the channel and click the Settings button. First, specify which peer organization and which peer organization admin is making the update request. If the application channel was created before the ordering organization was added to the system channel, click Ordering service administrator and add Ordering Service2 MSP as an administrator.

If your console is at a build before 2.1.3-104, you will not see this option. To see the version of your build, click on the support icon in the upper right hand corner (it resembles a question mark). The version will be listed below IBM Blockchain Platform version on the upper left.

After the organization has been added, we can add the consenter.

It is possible to add a node to the consenter and add the MSP of the organization that owns the node as part of the same channel configuration update.





 Add the node to the application channel
* UI
* CLI
* API







 Creating a VPN server 

Create a VPN server to allow clients from the internet to connect to the VPC network while maintaining secure connectivity.

You can create a VPN server by using the UI, CLI, or API.



 Before you begin 

Before you provision a VPN server, complete the following prerequisites in the following order:



1. Review [Planning considerations for VPN servers](https://cloud.ibm.com/docs/vpc?topic=vpc-client-to-site-vpn-planning).
2. Decide which VPN client authentication that you want to use: certificate-based, user ID and passcode, or both. For more information, see [Setting up client-to-site authentication](https://cloud.ibm.com/docs/vpc?topic=vpc-client-to-site-authentication).
3. For user ID and passcode authentication only, [create an IAM access group and grant users the role to connect to the VPN server](https://cloud.ibm.com/docs/vpc?topic=vpc-create-iam-access-group).
4. [Create a certificate manager instance and import certificates](https://cloud.ibm.com/docs/vpc?topic=vpc-client-to-site-authenticationcreating-cert-manager-instance-import).
5. For server authentication only, [create IAM service-to-service authorization](https://cloud.ibm.com/docs/vpc?topic=vpc-client-to-site-authenticationcreating-iam-service-to-service).
6. Depending on the deployment mode that you selected for your VPN server, do one of the following:



* For a High Availability (HA) VPN server, create a VPC and two subnets in two different zones. The VPN server resides in the two subnets.
* For a stand-alone VPN server, create a VPC and one subnet in one zone.
encrypted: <true_or_false>
resourceGroup: "<resource_group>"
data
encryptionKey: <encryption_key>

name
: Enter a name for your Kubernetes secret.

namespace
: Enter the namespace where you want to create your secret. To reference the secret in your PVC, the PVC must be created in the same namespace.

iops
: In the string data section, enter the range of IOPS that you want to allow for your Block Storage for Classic instance. The range that you enter must match the Block Storage for VPC tier that you plan to use.

zone
: In the string data section, enter the VPC zone where you want to create the Block Storage for Classic instance. Make sure that you use a zone that your worker nodes are connected to. To list VPC zones that your worker nodes use, run ibmcloud ks cluster get --cluster <cluster_name_or_ID> and look at the Worker Zones field in your CLI output. If you don't specify a zone, one of the worker node zones is automatically selected for your Block Storage for Classic instance.

tags
: In the string data section, enter a comma-separated list of tags to use when the PVC is created. Tags can help you find your storage instance after it is created.

resourceGroup
: In the string data section, enter the resource group that you want your Block Storage for Classic instance to get access to. If you don't enter a resource group, the instance is automatically authorized to access resources of the resource group that your cluster belongs to.

encrypted
: In the string data section, enter true to create a secret that sets up encryption for Block Storage for Classic volumes. If you set this option to true, you must provide the root key CRN of your Key Protect service instance that you want to use in parameters.encryptionKey. For more information about encrypting your data, see [Setting up encryption](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-block-encryption) for your Block Storage for VPC.

encryptionKey
The admin team will be responsible for creating the IAM resources. The instructions below use the ibmcloud iam api-key-create command to create an API key for the admin. The api key will be used by terraform to perform tasks on your behalf.

The api keys are the same as a passwords to your account. Keep the api keys safe.



1. Initialize and verify the basename shell variable. Verify it matches the basename in the terraform.tfvars file:

eval $(grep basename terraform.tfvars | sed -e 's/ //g' -e 's/.//')
echo basename=$basename
2. Change directory, generate and source your personal API key in local.env. When Terraform is invoked it will become you. Terraform will be the administrator:

cd admin
echo export TF_VAR_ibmcloud_api_key=$(ibmcloud iam api-key-create $basename-admin --output json | jq .apikey) > local.env
cat local.env
source local.env
3. Apply of the main.tf Terraform configuration file creates the following resources:



* Resource groups for each team
* Access groups for each team and a service ID in each access group
* Access group policies for the resource groups
* Access group policies for the resources



terraform init
terraform apply
4. Verify some of the resources were created:

ibmcloud resource groups | grep $basename

ibmcloud iam access-groups | grep $basename

ibmcloud iam service-ids | grep $basename

ibmcloud iam access-group-policies $basename-network

Output will resemble something like this:

$ ibmcloud resource groups | grep $basename
widget0-application2 36b06a303f224f28ad42aebbb491cc44 false ACTIVE
[MAS-MS-Register-Request-Approved](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-Register-Request-Approved.png)

Figure 13. MAS-Dedicated Request Approved

If you need support, see the next section How to Create a Case







 How to Create a Case 

This section describes how to create a case for Maximo Application Suite Dedicated (MAS-Dedicated)



1. Access the IBM Support Community:

[https://www.ibm.com/mysupport](https://www.ibm.com/mysupport)
2. Click the Open a case button on top right of page.
3. Sign in with valid IBMid:

Please note: If you do not have an IBMid, or your IBMid has not been registered with a valid product and customer account, go to the following link(s):

[How to Create An IBMid](https://cloud.ibm.com/docs/mas-mshow-to-create-an-ibmid)

[Register for Maximo Application Suite Support](https://cloud.ibm.com/docs/mas-mshow-to-register-for-mas-support)
4. On the following page, populate all required (*) fields ensuring Maximo Application Suite on Cloud is selected for Product and click on the Submit Case button
5. Case Creation will be confirmed and case number referenced:

Note: Cases are (9) digit numbers preceded with “TS”

You will also receive an email confirming the Case #
6. Click Back to all cases (in the upper left hand corner) or go to [https://www.ibm.com/mysupport/s/my-cases](https://www.ibm.com/mysupport/s/my-cases) to see a full list of your cases.







 How to set password and login to MAS
If you want to pre-provision the PVC for your stateful set before you create the stateful set, follow steps 1-3 in [Adding block storage to apps](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block) to create a PVC for each stateful set replica. Make sure that you create your PVC with a name that follows the following format: <volume_name>-<statefulset_name>-<replica_number>.

volume_name
: Use the name that you want to specify in the spec.volumeClaimTemplates.metadata.name section of your stateful set, such as nginxvol.

statefulset_name
: Use the name that you want to specify in the metadata.name section of your stateful set, such as nginx_statefulset.

replica_number
: Enter the number of your replica, starting with 0.

For example, if you must create three stateful set replicas, create three PVCs with the following names: nginxvol-nginx_statefulset-0, nginxvol-nginx_statefulset-1, and nginxvol-nginx_statefulset-2.

Looking to create a PVC and PV for an existing storage device? Create your PVC and PV by using [static provisioning](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting_block).
2. Follow the steps in [Dynamic provisioning: Creating the PVC when you create a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_dynamic_statefulset) to create your stateful set. The name of your PVC follows the format <volume_name>-<statefulset_name>-<replica_number>. Make sure to use the following values from your PVC name in the stateful set specification: spec.volumeClaimTemplates.metadata.name : Enter the <volume_name> of your PVC name.

metadata.name
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-groupcreating-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.
Because the console uses peers to gather information about the channels that the peers belong to, unless an organization has joined a peer to a channel, it cannot interact with the channel.

When you have created your CAs, identities, MSPs, ordering service, a peer, have added your peer organization to the consortium, and have imported the MSPs of any organizations who will be joined to this channel, navigate to the Channels tab in the left navigation. This is where channel creation and management are handled.

When you first navigate to this tab, it will be empty except for the Create channel and Join channel buttons. This is because you haven't created a channel and joined a peer to it yet.

Creating the channel

Perform the following steps from your console:



1. Navigate to the Channels tab.
2. Click Create channel. The create channel panel will open. From here, you will perform all of the steps to create your channel.
3. On the Prerequisites panel, you can decide whether or not you want to specify any Advanced channel configuration options. See [Advanced options](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-available-parameters-advanced) to learn more. For the purposes of this tutorial, we'll assume you don't want to specify any advanced channel configuration options, so click Next.
4. On the Channel details page, give you channel a name and specify the ordering service the channel will be hosted on. In this tutorial, our channel is called channel2 while the ordering service is called Ordering Service.
5. On the Organizations page, select the organizations who will be part of this channel. Since we have two organizations, select and add Org1 MSP (org1msp) and then Org2 MSP (org2msp). After clicking Add, you can assign an organization a role on the channel. Because each channel must have at least one operator, make both organizations Operator.
6. Next, choose a Update policy for the channel. This is the policy that will dictate how many organizations will have to approve updates to the channel configuration.
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. [Key aliases](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-key-alias) are ways to describe a key that allow them to be identified and grouped beyond the limits of a display name. Keys can have up to five aliases. 
 Key ring Optional. [Key rings](https://cloud.ibm.com/docs/key-protect?topic=key-protect-grouping-keys) are groupings of keys that allow those groupings to be managed independently as needed. Every key must be a part of a key ring. If no key ring is selected, keys are placed in the default key ring. Note that to place the key you're creating in a key ring, you must have the Manager role over that key ring. For more information about roles, check out [Managing user access](https://cloud.ibm.com/docs/key-protect?topic=key-protect-manage-access). 



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

If you know which key ring you want a key to be placed in, and you are a Manager of that key ring, you can also navigate to the Key rings panel, select ⋯ and click Add key to key ring. This will open the same panel you see by clicking Add on the Keys page with the Key rings variable filled in with the name of the key ring.





 Creating standard keys with the API 

Create a standard key by making a POST call to the following endpoint.

https://<region>.kms.cloud.ibm.com/api/v2/keys



1.