vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* From the [Block storage volumes for VPC](https://cloud.ibm.com/vpc-ext/storage/storageVolumes) list,



1. Go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. From the list of volumes, locate a boot or data volume that is attached to an instance.
3. Click the overflow menu (...) and select Create snapshot.



* From the Block storage volume details screen,



1. Go to the volume details page in one of these ways.



* Go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances. Select the instance that contains the volume that you want to make a snapshot of. From the [instance details page](https://cloud.ibm.com/vpc-ext/compute/vs), scroll to the list of attached volumes and click the name of the volume.
* Go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes. From the list of block storage volumes, select the volume that you want to make a snapshot of.



2. On the volume details page, select Create snapshot from the Actions menu.





2. Enter the required information to define your snapshot and select the Block Storage for VPC volume that you want to take a snapshot of.



Table 1. Selections for creating a snapshot

 Field Value 

 Location Specify the region for this snapshot. 
 Name Provide a unique name for the snapshot. The UI verifies the name for proper conventions and identifies duplicate names.
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
All Very High Memory profiles are provisioned with temporary SSD-backed [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) at no additional charge.

Ultra High Memory profiles are available in the US South (Dallas) and EU Germany (Frankfurt) regions. Additional regions will be added.

The following Ultra High Memory profiles are available for x86-64 processors:

Intel x86-64



Table 7. Ultra High Memory profiles options for x86-64 instances
Ultra High Memory profiles options for Intel x86-64 virtual server instances.

 Instance profile vCPU Cores GiB RAM Bandwidth Cap (Gbps) Instance Storage (GB) 

 ux2d-2x56 2 1 56 4 1x60 
 ux2d-4x112 4 2 112 8 1x120 
 ux2d-8x224 8 4 224 16 1x240 
 ux2d-16x448 16 8 448 32 1x480 
 ux2d-36x1008 36 18 1008 64 1x1080 
 ux2d-48x1344 48 24 1344 80 2x720 
 ux2d-72x2016 72 36 2016 80 2x1080 
 ux2d-100x2800 100 50 2800 80 2x1500 
 ux2d-200x5600 200 100 5600 80 2x3000 







 GPU 

The GPU profile family includes both -v100 and -a100 profiles. The GPU profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).



* GPU -v100 profiles include 1 or 2 NVIDIA V100 PCIe 16 GB GPUs. All OS images are supported on these GPU profiles.
* GPU -a100 profile includes 8 NVIDIA A100 NVlink 80 GB GPUs. This GPU profile supports only Linux OS images Ubuntu or RHEL.



The gx2-80x1280x8a100 profile is available for select customers.
Block Storage for VPC driver
: Added steps to install the vpc-block-csi-driver on unmanaged clusters. For more information, see [Setting up Block Storage for VPC for unmanaged clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block-storage-driver-unmanaged).

New! image security add-on
: In clusters that run version 4.5 or later, you can (/docs/openshift?topic=openshift-images#portieris-image-sec)install the container image security enforcement add-onto set up the ([https://github.com/IBM/portieris](https://github.com/IBM/portieris)){: external} Portieris project in your cluster.







 March 2021 



 31 March 2021 

Compliance operator
: Review how you can use the compliance operator from Red Hat with a tailored profile specific to Red Hat OpenShift on IBM Cloud worker nodes.





 30 March 2021 

add-on change logs
: Added version change logs for the [HPCS Router](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) and [Image Key Synchronizer](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog) add-ons.

Master versions
If you want to use an IBM Cloud Object Storage service instance as your default backing store, make sure that you [created the service instance](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpc&interface=uiodf-create-cos), and created the Kubernetes secret in your cluster. When you create the ODF CRD in your cluster, ODF looks for a secret named ibm-cloud-cos-creds to set up the default backing store that uses your Object Storage HMAC credentials.



1. Create a custom resource definition called OcsCluster. Save one of the following custom resource definition files on your local machine and edit it to include the name of the custom storage class that you created earlier as the monStorageClassName and osdStorageClassName parameters. For more information about the OcsCluster parameters, see the [parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpc&interface=uiodf-vpc-param-ref).

Example custom resource definition for installing ODF on all worker nodes on a 4.8 cluster.

apiVersion: ocs.ibm.io/v1
kind: OcsCluster
metadata:
name: ocscluster-vpc Kubernetes resource names can't contain capital letters or special characters. Enter a name for your resource that uses only lowercase letters, numbers, - or .
spec:
osdStorageClassName: <osdStorageClassName> For multizone clusters, specify a storage class with a waitForFirstConsumer volume binding mode
osdSize: <osdSize> The OSD size is the total storage capacity of your OCS storage cluster
numOfOsd: 1
billingType: advanced
ocsUpgrade: false

Example custom resource definition for installing ODF only on specified worker nodes on a 4.8 cluster.

apiVersion: ocs.ibm.io/v1
kind: OcsCluster
metadata:
resources:
requests:
storage: <vpc_block_storage_size>
storageClassName: ""
9. Create your PVC.

oc apply -f pvc.yaml
10. Verify that your PVC is created and bound to the PV that you created earlier. This process can take a few minutes.

oc describe pvc <pvc_name>
11. Create a deployment or a pod that uses your PVC.

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- image: <image_name>
name: <container_name>
volumeMounts:
- name: <volume_name>
mountPath: /<file_path>
volumes:
- name: <volume_name>
persistentVolumeClaim:
claimName: <pvc_name>
nodeSelector:
kubernetes.io/hostname: "<worker_node_primary_IP>"
Show more







 Updating the Block Storage for VPC add-on 

You can update the Block Storage for VPC add-on by disabling and re-enabling the add-on in your cluster. When you disable the add-on, PVC creation and app deployment are not disrupted. Existing volumes and data are not impacted.

Before updating the add-on review the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).



1. Check to see if an update is available. If an update is available, the plug-in version is flagged with an asterisk and the latest version is shown. Note the latest version as this value is used later.
The Memory profile is best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads. The Memory with instance storage profile is best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads.

The Memory with instance storage profile provisions your host with the capability for hosting instances that include [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage). If you provision a dedicated host with a Memory with instance storage profile, any virtual server instances that are provisioned on the dedicated host must also be provisioned with a Memory profile that includes instance storage.

The Memory profile family of dedicate hosts on Intel® x86-64 systems are deployed on either Intel®'s quad processor Xeon® Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or Intel®'s quad processor Gold 6248 Cascase Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.

The following Memory profiles are available for dedicated hosts.

Intel x86-64



Table 4. Intel x86-64 memory profile for dedicated hosts
Dedicated Host Memory profiles options for Intel x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 mx2-host-152x1216 152 76 1216 <br><br> * <br><br><br> 
 mx2d-host-152x1216 152 76 1216 5700 GB 



For supported instance profiles in the Memory family, see [memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesmemory). Instance profiles that are provisioned on a dedicated host in the Memory family must include an mx2 prefix in the instance profile name. Profiles with instance storage include d in the profile name, for example mx2d.

Dedicated hosts have a network performance cap of 80 Gbps. Instances provisioned on the host share bandwidth across the instances.
For more information, see [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) for details.

You must consider the total IOPS required for your installation and the performance characteristics of your database. One option is to colocate multiple directories into a single large volume with high IOPS, versus isolating directories into individual small volumes with an insufficient number of IOPS for the workload characteristics.

For an overview of all available storage profiles, see [VPC Block Storage Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles).

For SAP NetWeaver and SAP AnyDB, a minimum of 5 IOPS/GB is recommended.

Samples of storage configurations that use Intel Virtual Server (Gen2) profiles are available under [Storage design considerations](https://cloud.ibm.com/docs/sap?topic=sap-storage-design-considerations).
Values for creating a mount target.

 Field Value 

 Details 
 Mount target name Specify a mount target name. The name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. You can later edit the name if you want. 
 Zone Zone is inherited from the file share (for example, Dallas 2). 
 VPC Select an available VPC. The list includes only those VPCs with a subnet in the selected zone. 
 Subnet Select a subnet from the list. 
 Reserved IP address Required for the mount target. The IP address cannot be changed afterward. However, you can delete the mount target and create another one with a different IP address. 
 Reserving method You can have the file service select an IP address for you. The reserved IP becomes visible after the mount target is created. Or, specify your own IP. 
 Auto-release Releases the IP address when you delete the mount target. Enabled by default. 
 Security groups The security group for the VPC is selected by default, or select from the list. 
 Encryption in transit Disabled by default, click the toggle to enable. For more information about this feature, see [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit). 



* If you selected VPC as the access mode, provide a name for the mount target and select the VPC where the file share is to be used in.



5. Select the right profile for your workload. The profile that you select determines the input/output performance of a file share. The dp2 profile provides the most flexibility. For more information about file storage IOPS tier and Custom profiles, see [File storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles).
6. Specify the size for the file share.
Go to the [list of Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage&interface=uiviewvols-ui).
2. Click the name of a volume in the list.
3. On the volume details page, click the pencil icon next to the Block Storage for VPC volume name.
4. In the new window, type a tag in the User tags text box.
5. Click Save.









 Applying tags to Block Storage for VPC volumes from the CLI 



 Before you begin 

Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Log in to the IBM Cloud.

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account. If you have access to multiple accounts, select the account that you want to log in as. Respond to any remaining prompts to finish logging in.
2. Select the current generation of VPC.

ibmcloud is target --gen 2







 Applying tags to volumes from the CLI 

Issue the ibmcloud is volume-update VOLUME command with the --tags option to update the user tags of a volume. The volume argument can be defined by either the volume ID or the volume name.

Use the same option to add tags to a volume when you create a volume by using ibmcloud is volume-create.

The following example adds user tags env:test and bkp:test to a volume identified by ID.
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-5iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
When you create a Block Storage for VPC volume in your availability zone, you can use 3 different tiered profiles with predefined IOPS levels and a custom profile with which you can define your own IOPS level based on the volume capacity. All profiles are backed by solid-state drives (SSDs).

For more information, see [Block Storage for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles)







 Block Storage for VPC encryption 

IBM Cloud takes the need for security seriously and understands the importance of being able to encrypt data to keep it safe. When you create a data volume, you can choose to protect your data by using your own root keys, or use the default IBM-managed encryption. Boot volumes that are created during instance provisioning are encrypted with IBM-managed encryption by default. You can edit the boot volume to use your root keys. After you set up encryption for a boot or data volume, you can't change it.

For more information about data encryption, see [About data encryption for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-about).





 Tags for Block Storage for VPC volumes 

Block Storage for VPC is enabled for Global Searching and Tagging (GhoST). You can create and apply [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-user-tags) and [access management tags](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-mgt-tags) to volumes to better control and organize your Block Storage for VPC resources across the VPC.



 User tags for Block Storage for VPC volumes 

User tags are uniquely identified by a Cloud Resource Name (CRN) identifier. When you create a user tag, you provide a unique name within your billing account. You can define user tags in label or key-value format.
$ ibmcloud resource service-instance-create $COS_NAME cloud-object-storage lite global

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=9d4353d8-6b85-4689-90dd-1ccfb4a275ab

 create a Key Management Service (KMS) instance
 "tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1

$ ibmcloud resource service-instance-create $KMS_NAME kms tiered-pricing us-south

 capture the Key Protect (KP) instance id (GUID)
$ KP_INSTANCE_ID=b0d84b32-09d0-4314-8049-da78e3b9ab6f

 create a policy for COS to read KMS; source is COS, target is KMS (Key Protect)
$ ibmcloud iam authorization-policy-create cloud-object-storage kms Reader --source-service-instance-id $COS_INSTANCE_ID --target-service-instance-id $KP_INSTANCE_ID

 capture the COS-to-KMS authorization policy id
$ COS_KMS_AUTHORIZATION=79375168-2d74-49df-98aa-3e727410fa71

 create a KP root key that COS uses to encrypt data
$ ibmcloud kp key create my-cos-key --output json

{
"id": "52a9d772-8982-4620-bfb4-b070dd812a0c",
"name": "my-cos-key",
"type": "application/vnd.ibm.kms.key+json",
"extractable": false,
"state": 1,
"algorithmType": "AES",
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-05-05T20:03:00Z",
"lastUpdateDate": "2020-05-05T20:03:00Z",
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb145:390086ac-76fa-4094-8cf3-c0829bd69526:key:9cca88c9-019e-4f0a-9e76-8e657c6b9720"
}

 delete the key
$ ibmcloud kp key delete 9cca88c9-019e-4f0a-9e76-8e657c6b9720 --output json

{
"id": "9cca88c9-019e-4f0a-9e76-8e657c6b9720"
}





 Example 3 

Delete a root key that is registered with another cloud resource.

 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

 capture the COS instance id (GUID)
$ COS_INSTANCE_ID=9d4353d8-6b85-4689-90dd-1ccfb4a275ab

 create a Key Management Service (KMS) instance
 "tiered-pricing" is the pricing plan and "us-south" is the region
$ KMS_NAME=my-kms-1
A REST API client can help quickly put together both simple and complex HTTP requests.





 Prerequisites 



* IBM Cloud account
* [Cloud Storage resource created](https://cloud.ibm.com/catalog/) (lite plan works fine)
* [IBM Cloud COS CLI installed and configured](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cli)
* [Service Instance ID for your Cloud Storage](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-service-credentialsservice-credentials)
* [IAM (Identity and Access Management) Token](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-service-credentialsservice-credentials)
* [Endpoint for your COS bucket](https://cloud.ibm.com/docs/services/cloud-object-storage/basics?topic=cloud-object-storage-endpoints)





 Create a bucket 



1. Start Postman
2. In the New tab, select PUT.
3. Enter the endpoint in the address bar and add the name for your new bucket. a. Bucket names must be unique across all buckets, so choose something specific.
4. In the Type menu, select Bearer Token.
5. Add the IAM Token in the Token box.
6. Click Preview Request. a. You should see a confirmation message that the headers were added.
7. Click the Header tab where you should see an existing entry for Authorization.
8. Add a key. a. Key: ibm-service-instance-id b. Value: Resource Instance ID for your cloud storage service.
9. Click Send.
10. You'll receive a status 200 OK message.







 Create a text file object 



1. Create a tab by clicking the Plus (+) icon.
Create the [Lithops configuration file](https://github.com/lithops-cloud/lithops/tree/master/configlithops-configuration).
3. Install [Docker (community edition) version](https://docs.docker.com/get-docker/).
4. Log in to Docker.

docker login







 Setting up a storage backend for Lithops 

Select a [supported storage backend](https://github.com/lithops-cloud/lithops/tree/master/configcompute-and-storage-backends); for example, IBM Cloud Object Storage.

To set up IBM Cloud Object Storage,



1. Create an [IBM Cloud Object Storage account](https://www.ibm.com/cloud/object-storage).
2. Create a bucket in the region that you want to use.
3. In the side navigation, click Endpoints to find your API endpoint. You must copy both the public and private endpoints of the region where you created your bucket.
4. Create the credentials to access to your IBM Cloud Object Storage account. Choose one option





 Option 1 (API key) for Lithops 



1. From the IBM Cloud Object Storage navigation, click Service Credentials.
2. Click New credential + and provide a name and select a role.
3. Click Add to generate service credential.
4. Click View credentials and copy the apikey value.
5. Edit your lithops config file and add the following keys.

lithops:
storage_backend: ibm_cos

ibm_cos:
endpoint : <REGION_ENDPOINT>
private_endpoint : <PRIVATE_REGION_ENDPOINT>
api_key : <API_KEY>







 Option 2 (IBM Cloud Object Storage HMAC credentials) for Lithops 



1. From the IBM Cloud Object Storage navigation, click Service Credentials.
2.