vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can resize the memory and core count beyond the 8x and 1/8x boundaries when the VM is shut down. The following table shows an example of recalculated values:

When VM is active

When VM is shut down



Table 1. Resizing VM core count and memory when the VM is active

 Specified value when the VM instance was provisioned Minimum resize value (must be greater than or equal to 0.25 cores, 2 GB memory) Maximum resize value 

 4 core and 8 GB memory 0.5 cores and 2 GB memory 32 cores and 64 GB memory 



If you want to resize an existing VM that was created before 15 December 2020 to 8x ratio of core count and memory, you must first shut down the VM, resize the VM, and then activate the VM. You must resize the VM at least once when the VM is shut down to enable 8x ratio. Simply shutting down and activating the VM does not enable the 8x ratio of core count and memory.







 Managing your storage volumes 

Learn how to add new storage volumes and modify existing ones. You can now attach storage volumes to a VM instance from different storage tiers and pools, other than the storage pool the VM instance's root (boot) volume is deployed in. To accomplish this you must modify the VM instance and set the new VM instance storagePoolAffinity property to false. You can now attach mixed storage to a VM instance. For more information, see [How to set a VM instance to allow attaching mixed storage?](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqsmixed_storage).

You can create a storage volume by specifying any name of your choice. If you want to reuse the storage volume name, you must delete the existing storage volume with the same name. After you delete the original volume, allow one hour before creating a new volume with the same name.



 Adding and managing storage volumes 

If you want to attach or detach a volume, complete the following steps:



1.
You can upgrade or downgrade disk storage for any virtual server by updating your storage options in the First Disk through Fifth Disk fields in the Configuration screen of the device you want to update. For more information, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-servers).
* How many hourly virtual servers can I start?

The number of instances that you can run depends on the maturity level of your account. By default, an account older than 45 days has a limit of 20 instances that can run on public virtual servers, dedicated virtual servers, and bare metal servers, at any time. A newer account has a smaller limit. If you would like to increase your limit, contact support about what you are doing and how many concurrent instances you might need.
* How am I billed for bandwidth for my hourly virtual servers?

Hourly virtual billing is broken down for inbound and outbound traffic. All inbound traffic to your virtual server is free of charge. Outbound traffic is metered and charged per GB, with totals assessed at the end of your billing period.
* What happens to my data when my portable storage is deleted?

Virtual server instance SAN is similar to file storage. Virtual server instance disks are just files on an NFS share that Xen presents to the instance as a block device, that is, a hard disk drive. When you delete an instance SAN disk, you delete the file, after which undelete is not possible. Any pointers to the data on that volume are removed, and the data becomes inaccessible. If the physical storage is reprovisioned to another account, a new set of pointers is assigned. A new account can't access any data that was on the physical storage. The new set of pointers shows all 0's. When new data is written to the volume or LUN, any inaccessible data that still exists is overwritten.
* Can I use a Red Hat Cloud Access subscription to create a virtual server?

Yes. When you import an image, you can specify that you provide the operating system license.
Like with reaching 75 percent capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
* At 95 percent capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95 percent. Snapshots continue to be deleted each time usage exceeds 95 percent until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset, and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.



By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time from the CLI.

If snapshot space usage increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if usage jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%.





 Listing all Snapshots with Space Used Information and Management functions from the SLCLI 

You can accomplish this task from the SLCLI by using the following command.

 slcli file snapshot-list --help
Usage: slcli file snapshot-list [OPTIONS] VOLUME_ID

Options:
--sortby TEXT Column to sort by
--columns TEXT Columns to display. Options: id, name, created, size_bytes
-h, --help Show this message and exit.

Notifications are sent when you reach three different space thresholds – 75 percent, 90 percent, and 95 percent.



* At 75 percent capacity, a warning is sent that snapshot space usage exceeded 75 percent. To remediate, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule.
Setting a quota on a bucket 

A hard quota sets a maximum amount of storage (in bytes) available for a bucket. Once reached, the limit prevents adding any additional objects to the bucket until existing objects are moved or deleted to free up space, or the quota is raised.

This feature is not currently supported in Object Storage for Satellite. [Learn more.](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cos-satellite)

There are two types of usage quota: a "hard" quota described above, and a "soft" quota that alerts a user that usage has crossed a threshold, but does not prevent any further object writes. To configure a soft quota, make use of [IBM Cloud Monitoring](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-mm-cos-integration) to set [usage alerts](https://docs.sysdig.com/en/event-alerts.html).



 Using the console 

You can use the console to add a hard quota to a bucket during creation, or an existing bucket.



 Creating a new bucket with a quota 



1. After navigating to your object storage instance, click on Create bucket.
2. Under Advanced configurations, look for Quota enforcement and toggle the selector to Enabled.
3. Now raise or lower the value and choose the appropriate storage unit. Then, click Save.
4. Continue configuring any other rules, setting, or policies on the new bucket.







 Adding a quota to an existing bucket 

First, make sure that you have a bucket. If not, follow the [getting started tutorial](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) to become familiar with the console.



1. Navigate to a bucket, so that you are looking at a list of objects. Select Configuration from the navigational menu.
2. Under Advanced configurations, look for Quota enforcement and toggle the selector to Enabled.
Make sure to choose your storage configuration carefully to have enough capacity to store your data. After you provision a specific type of storage by using a storage class, you can't change the type or retention policy for the storage device. However, you can [change the size and the IOPS](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_change_storage_configuration) if you want to increase your storage capacity and performance. To change the type and retention policy for your storage, you must create a new storage instance and copy the data from the old storage instance to your new one.



1. List available storage classes in IBM Cloud® Kubernetes Service.

kubectl get storageclasses | grep block

Example output

ibmc-block-bronze ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-custom ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-gold ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-retain-bronze ibm.io/ibmc-block Retain Immediate true 148m
ibmc-block-retain-custom ibm.io/ibmc-block Retain Immediate true 148m
ibmc-block-retain-gold ibm.io/ibmc-block Retain Immediate true 148m
ibmc-block-retain-silver ibm.io/ibmc-block Retain Immediate true 148m
ibmc-block-silver ibm.io/ibmc-block Delete Immediate true 148m
2. Review the configuration of a storage class.

kubectl describe storageclass STORAGECLASS

For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storageclass_reference). If you don't find what you are looking for, consider creating your own customized storage class. To get started, check out the [customized storage class samples](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass).
3.
Like with reaching 75 percent capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
* At 95 percent capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95 percent. Snapshots continue to be deleted each time usage exceeds 95 percent until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.



By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time from the CLI.

If snapshot space utilization increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if utilization jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%.





 Listing all Snapshots with Space Used Information and Management functions from the SLCLI 

You can accomplish this task from the SLCLI by using the following command.

 slcli block snapshot-list --help
Usage: slcli block snapshot-list [OPTIONS] VOLUME_ID

Options:
--sortby TEXT Column to sort by
--columns TEXT Columns to display. Options: id, name, created, size_bytes
-h, --help Show this message and exit.

Notifications are sent when you reach three different space thresholds – 75 percent, 90 percent, and 95 percent.



* At 75 percent capacity, a warning is sent that snapshot space usage exceeded 75 percent. To remediate, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule.
* [Adding Block Storage for Classic to apps](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageadd_block).
* [Storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_storageclass_reference).
* [Customizing storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_custom_storageclass).







 Deciding on the block storage configuration 

Red Hat OpenShift on IBM Cloud provides pre-defined storage classes for block storage that you can use to provision block storage with a specific configuration.

Every storage class specifies the type of block storage that you provision, including available size, IOPS, file system, and the retention policy.

Make sure to choose your storage configuration carefully to have enough capacity to store your data. After you provision a specific type of storage by using a storage class, you can't change the type or retention policy for the storage device. However, you can [change the size and the IOPS](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_change_storage_configuration) if you want to increase your storage capacity and performance. To change the type and retention policy for your storage, you must create a new storage instance and copy the data from the old storage instance to your new one.



1. List available storage classes in IBM Cloud® Kubernetes Service.

oc get storageclasses | grep block

Example output

ibmc-block-bronze ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-custom ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-gold ibm.io/ibmc-block Delete Immediate true 148m
ibmc-block-retain-bronze ibm.io/ibmc-block Retain Immediate true 148m
ibmc-block-retain-custom ibm.io/ibmc-block Retain Immediate true 148m
* UI
* CLI
* API
* Terraform







 Managing backup policies 

Manage backup policies and their associated plans that were created for your Block Storage for VPC volumes. Delete policies and plans that you no longer need. Update the policy and plan. Audit your policies by integrating Activity Tracker events. Check the status of your backup policies.



 Backup policy deletion overview 

When you delete a backup policy, you also delete the plan that is associated with it. You can also delete plans within a policy.

When you delete a backup policy, any backups that were scheduled to be created based on the tags that were defined in the policy are no longer to be taken.





 Managing backup policies in the UI 

Delete a backup policy, rename a policy, and edit user tags in the UI.



 Renaming a backup policy in the UI 

You can rename a policy from the list of backup policies or from the backup policies details page.



* From the list of backup policies, click the overflow menu (ellipsis) and select Rename.
* From the policy details page, click the pencil icon next to the policy name.







 Editing tags for target resources in the UI 

From the Backup policy details page, you can edit the tags for your Block Storage for VPC volumes target resources.



1. Go to the [details page for a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policies&interface=uibackup-view-policy).
2. For Tags for target resources, click the pencil icon.
3. In the new window, enter a user tag name. For existing Block Storage for VPC volumes with user tags, enter the tag name exactly as it appears in the volume. You can also add user tag here and then go back and add it to a volume. You need only one tag for a volume to create a backup.
4. Click Next.
5. Review the information on the next window. If you're satisfied, check the disclaimer and click Save changes.







 Editing or deleting a backup plan in the UI
For more information about creating and by using custom domains, see [Managing your domains](https://cloud.ibm.com/docs/apps?topic=apps-update-domain).
* To manage the allocated quota for an org, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) for the respective org, and select Quotas.

From here, you can view the quota details for the number of apps, amount of memory, number of services, and plan details. The quota represents the resource limits for the org, which is assigned when the organization is created. The resources that are available to an org vary depending on whether you have a free account or a billable account. Any application or service that is included in a space within the org contributes to the usage of the allocated quota.

To change the quota that is allocated to an org, you must create a support case. For more information, see [Working with support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).

To view the quota details at the space level for each location, click the Actions icon ![Action icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) for the respective org, and select Quotas. Then, expand each row accordingly.







 Updating orgs and spaces by using the CLI 



 Renaming orgs 



1. Log in, and select the account.

ibmcloud login
2.
To set a limit on how much storage is available for the bucket, set the --set quotaLimit=trueVPC clusters only: To enable authorized IPs on VPC, set the --set bucketAccessPolicy=true option.



If you don't set the --set quotaLimit=true option during installation, you can't set quotas for your PVCs.

Example helm ibmc install commands for OS X and Linux

helm ibmc install ibm-object-storage-plugin ibm-helm/ibm-object-storage-plugin --set license=true [--set quotaLimit=true/false] [--set bucketAccessPolicy=false] [--set allowCrossNsSecret=true/false]

quotaLimit
: A quota limit sets the maximum amount of storage (in bytes) available for a bucket. If you set this option to true, then when you create PVCs, the quota on buckets created by those PVCs is equal to the PVC size.

allowCrossNsSecret
: By default, the plug-in searches for the Kubernetes secret in namespaces other than the PVC namespace. If you set this option to false the plug-in searches for the Kubernetes secret in only the PVC namespace.

Example helm install command for Windows.

helm install ibm-object-storage-plugin ./ibm-object-storage-plugin --set dcname="${DC_NAME}" --set provider="${CLUSTER_PROVIDER}" --set workerOS="${WORKER_OS}" --region="${REGION} --set platform="${PLATFORM}" --set license=true [--set bucketAccessPolicy=false]

DC_NAME
: The cluster data center. To retrieve the data center, run kubectl get cm cluster-info -n kube-system -o jsonpath="{.data.cluster-config.json}{'n'}". Store the data center value in an environment variable by running SET DC_NAME=<datacenter>.
For a tutorial on how to do this, see Changing the size and IOPS of your existing storage device on your [Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_change_storage_configuration) or [OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_change_storage_configuration) cluster.

Note that you do not need to adjust the CPU, memory, or storage for your smart contract pods. These pods will automatically use as many resources as they need to function efficiently. In cases where your smart contracts are struggling because of insufficient resources, you will have to address this at the cluster level.



 Monitoring file storage 

If you are using Classic infrastructure, to view your consumption of file storage, navigate to your Kubernetes cluster on IBM Cloud. Click on the menu icon ![action menu](https://cloud.ibm.com/docs-content/v1/content/icons/overflow-menu.svg). Then click Classic infrastructure > Storage > File Storage. This will display the capacity and usage for each persistent volume claim (PVC). This usage can be mapped to your IBM Blockchain Platform nodes by clicking on the cell in the Notes column.

You will see something that looks like this:

PVC {"plugin":"ibm-file-plugin-77497497cc-5qm58","region":"us-south","cluster":"05ccfca248dc4c389978d074524e0a8e","type":"Endurance","ns":"n4c817f","pvc":"n4c817forg1ca-fabric-ca-pvc","pv":"pvc-63074ac8-8b9b-11e9-88db-222bd59fb4bc","storageclass":"default","reclaim":"Delete"}

To see the same information from the command line, log in to your cluster and enter this command:
How do I fix it? 

To see the new expanded LUN size, you need to rescan and reconfigure your existing Block Storage for Classic disk on the server. See the following examples. For more information, see your operating system Documentation.



 Windows® 2016 



1. Go to Server Manager > Tools > Computer Management > Disk Management.
2. Click Action > Refresh.
3. Click Action > Rescan Disks. This process can take up to 5 minutes or more to finish. The additional capacity displays as a deallocated partition on the existing Disk.
4. Partition the deallocated space as you want. For more information, see [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).







 Linux 



1. Log out of each multipath session of the block storage device that you expanded.

 iscsiadm --mode node --portal <Target IP> --logout
2. Log in again.

 iscsiadm --mode node --portal <Target IP> --login
3. Rescan the iscsi sessions.

 iscsiadm -m session --rescan
4. List the new size by using fdisk -l to confirm that the storage was expanded.
5. Reload multipath device map.

 multipath -r <WWID>

 multipath -r 3600a09803830477039244e6b4a396b30
reload: 3600a09803830477039244e6b4a396b30 undef NETAPP ,LUN C-Mode
size=30G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=undef
|-+- policy='round-robin 0' prio=50 status=undef
| - 2:0:0:3 sda 8:0 active ready running
You can also use the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=cliexpand-existing-boot-vol-cli) or the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=apiexpand-existing-boot-vol-api).





 How many volumes can I provision on my account? 

You can provision up to 300 Block Storage for VPC volumes per account in a region. You can request your quota to be increased by opening a [support case](https://cloud.ibm.com/unifiedsupport/cases/form) and specifying the region where you need more volumes. For more information about preparing a support case when you're ordering Block Storage for VPC volumes or requesting an increase to your volume or capacity limits, see [Managing volume count and capacity limits](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-storage-limit).





 Can I set up shared storage in a multizone cluster? 

In the IBM Cloud®, storage options are limited to an availability zone. Do not try to manage shared storage across multiple zones.

Instead, use an IBM Cloud® classic service option outside a VPC such as IBM Cloud® Object Storage or IBM® Cloudant® for IBM Cloud® if you must share your data across multiple zones and regions.





 I have volumes on the Classic infrastructure. Can I port them to the VPC? 

No. The VPC provides access to new availability zones in multi-zone regions. Compute, network, and storage resources are designed to function in the VPC.





 What is image from volume and how does it relate to Block Storage for VPC volumes? 

With the image from volume feature, you can create a custom image directly from a Block Storage for VPC boot volume. Then, you can use the custom image to provision other virtual server instances.