vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your File Storage for Classic that you want to provision. However, if you want to include labels in your volumeClaimTemplates, Kubernetes does not include these labels when creating the PVC. Instead, you must add the labels directly to your stateful set.

You can't deploy two stateful sets at the same time. If you try to create a stateful set before a different one is fully deployed, then the deployment of your stateful set might lead to unexpected results.

How can I create my stateful set in a specific zone?**
: In a multizone cluster, you can specify the zone and region where you want to create your stateful set in the spec.selector.matchLabels and spec.template.metadata.labels section of your stateful set YAML. Alternatively, you can add those labels to a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagecustom-sc-nfs-creat) and use this storage class in the volumeClaimTemplates section of your stateful set.

Can I delay binding of a PV to my stateful pod until the pod is ready?
: Yes, you can [create a custom storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile-topology) for your PVC that includes the [volumeBindingMode: WaitForFirstConsumer](https://kubernetes.io/docs/concepts/storage/storage-classes/volume-binding-mode) field.

What options do I have to add File Storage for Classic to a stateful set?
: If you want to automatically create your PVC when you create the stateful set, use [dynamic provisioning](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_dynamic_statefulset).
The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your File Storage for Classic that you want to provision. However, if you want to include labels in your volumeClaimTemplates, Kubernetes does not include these labels when creating the PVC. Instead, you must add the labels directly to your stateful set.

You can't deploy two stateful sets at the same time. If you try to create a stateful set before a different one is fully deployed, then the deployment of your stateful set might lead to unexpected results.

How can I create my stateful set in a specific zone?**
: In a multizone cluster, you can specify the zone and region where you want to create your stateful set in the spec.selector.matchLabels and spec.template.metadata.labels section of your stateful set YAML. Alternatively, you can add those labels to a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-file_storagecustom-sc-nfs-creat) and use this storage class in the volumeClaimTemplates section of your stateful set.

Can I delay binding of a PV to my stateful pod until the pod is ready?
: Yes, you can [create a custom storage class](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile-topology) for your PVC that includes the [volumeBindingMode: WaitForFirstConsumer](https://kubernetes.io/docs/concepts/storage/storage-classes/volume-binding-mode) field.

What options do I have to add File Storage for Classic to a stateful set?
: If you want to automatically create your PVC when you create the stateful set, use [dynamic provisioning](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_dynamic_statefulset).
When you set an affinity policy for a new storage volume, the volume is created within the same storage provider as an existing PVM instance or volume. With an anti-affinity policy, the new volume is created in a different storage provider other than the storage provider the existing PVM instance or volume is located in.

The use of volume affinity policy (affinity or anti-affinity) requires the availability of multiple storage providers. You might experience the following errors when you use a volume affinity policy:



* If an additional storage provider is not available to fulfill the requested policy, you might receive an error that indicates the inability to locate a storage provider to create a volume by using the requested volume affinity policy.
* If additional storage providers exist but the storage providers do not have sufficient space to fulfill the requested policy, you might receive an error that indicates the inability to locate a storage provider with enough free capacity to satisfy the requested volume size.



* How to set a PVM instance to allow attaching mixed storage?

You can now attach storage volumes to a PVM instance from different storage tiers and pools, other than the storage pool the PVM instance's root (boot) volume is deployed in. To accomplish this you must modify the PVM instance and set the new PVM instance storagePoolAffinity property to false. The PVM instance storagePoolAffinity property is set to true by default when the PVM instance is deployed and can be changed only by using the modify PVM instance API. For more information about modifying a PVM instance API, see [Modify PVM Instance](https://cloud.ibm.com/apidocs/power-cloudpcloud-pvminstances-put). Attaching mixed storage to a PVM instance has implications on the PVM instance capture, clone, and snapshot features. See [Modify PVM Instance](https://cloud.ibm.com/apidocs/power-cloudpcloud-pvminstances-put) API for more details.
* Does IBM provide maintenance for the AIX, IBM i or Linux operating systems?

No. It is the customer's responsibility to maintain, update, and manage the AIX, IBM i or Linux operating system.
* How does licensing work for the AIX, IBM i, or Linux operating systems?
You can't deploy two stateful sets at the same time. If you try to create a stateful set before a different one is fully deployed, then the deployment of your stateful set might lead to unexpected results.

How can I create my stateful set in a specific zone?
: In a multizone cluster, you can specify the zone and region where you want to create your stateful set in the spec.selector.matchLabels and spec.template.metadata.labels section of your stateful set YAML. Alternatively, you can add those labels to a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_custom_storageclass) and use this storage class in the volumeClaimTemplates section of your stateful set.

Can I delay binding of a PV to my stateful pod until the pod is ready?
: Yes, you can [create a custom storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storagetopology_yaml) for your PVC that includes the [volumeBindingMode: WaitForFirstConsumer](https://kubernetes.io/docs/concepts/storage/storage-classes/volume-binding-mode) field.

What options do I have to add block storage to a stateful set?
: If you want to automatically create your PVC when you create the stateful set, use [dynamic provisioning](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_dynamic_statefulset). You can also choose to [pre-provision your PVCs or use existing PVCs](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_static_statefulset) with your stateful set.



 Creating the PVC by using dynamic provisioning when you create a stateful set 

Use this option if you want to automatically create the PVC when you create the stateful set.
-h, --help Show this message and exit.

If you're using the replication feature, be sure that the schedule you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [Replicating Data](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-replication).





 Deleting a snapshot in the UI 

Snapshots that are no longer needed can be manually removed to free up space for future snapshots. Deletion is done through Storage > Block Storage for Classic.



1. Click your storage volume and click Snapshot to see the list of existing snapshots.
2. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg) next to a particular snapshot and click Delete. Click the confirmation box that warns about possible data loss, then click Delete. This deletion doesn't affect any future or past snapshots on the same schedule as snapshots don't depend on each other.



Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations (oldest first).





 Deleting a snapshot from the SLCLI 

Snapshots that are no longer needed can be manually removed to free up space for future snapshots. You can delete a snapshot from the SLCLI by using the following command.

 slcli block snapshot-delete
Usage: slcli block snapshot-delete [OPTIONS] SNAPSHOT_ID

Options:
-h, --help Show this message and exit.

Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations. The oldest snapshot is deleted first.





 Restoring storage volume to a specific point in time by using a snapshot in the UI
* Can I connect directly through SSH to the bootstrap, compute, or storage nodes from a system external to IBM Cloud?

No, any SSH connection to the bootstrap, compute, or storage nodes is only possible through the bastion node for security reasons. You would use the following command to connect to your bootstrap, compute, or storage nodes (the IP address is specific to your particular node): ssh -J ubuntu@<bastion_IP_address> vpcuser@<IP_address>
* Can I establish an SSH connection between compute and storage nodes?

The compute and storage clusters are created to not have the same passwordless SSH keys. This ensures that there are separate administration domains for the compute and storage clusters; therefore, SSH between nodes from different clusters is not possible.
* Does the Spectrum Scale offering support multiple key_pairs to establish SSH to all of the nodes?

No, the current version of the Spectrum Scale offering supports only a single key_pair that can be provided for access to all of the nodes that are part of the cluster.
* Can I use my own resource group to configure the resources?

Yes, you can provide the resource group of your choice for the deployment of your cluster's VPC resources. Due to the use of trusted profiles in this offering, you must ensure that all of the key_pair values that are specified in the deployment values are created in the same resource group.
* Which operating system versions are supported for the images used for the compute and storage nodes in Spectrum Scale?

With Spectrum Scale, you can use custom or stock images based on RHEL 7.9 or RHEL 8.4. For compute nodes, both RHEL 7.9 or 8.4 can be used. For storage nodes, only RHEL 8.4 is supported.
* Why does Spectrum Scale not allow use of the default value of 0.0.0.0/0 for security group creation?

For security reasons, Spectrum Scale does not allow you to provide a default value that would allow network traffic from any external device.
Or you can delete (and cancel) an in-progress image export job if you have an IAM role that includes the is.image.image.export action.

When you delete an image export job, it is removed only from the export history. The exported image file is not removed from the IBM Cloud Object Storage bucket. You must manage files that are stored in IBM Cloud Object Storage by using the IBM Cloud Object Storage interfaces.

Finally, you can rename an image export job. Renaming the image export job does not change the name of the object that is created in IBM Cloud Object Storage.



 Limits for image export jobs 

The following limits exist for image export jobs:



* Five active export job requests per image
* Ten total export jobs per image
* Twenty active export jobs per account per region







 Viewing custom image export history by using the UI 

To view the export history of a custom image, complete the following steps.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.
2. On the Custom images tab, click the name of a custom image to view details about that image.
3. On the Image details page, click the Export history tab.





 Deleting or canceling an image export job by using the UI 

To delete a completed image export job or cancel (and delete) an in-progress image export job, complete the following steps.



1. On the image details page, click the Export history tab.
2. For the export job that you want to delete or cancel, click the Actions icon !
You can optionally deploy a gateway cluster to host Juniper® vSRX or your own routing or firewall device. The solution can be expanded after the initial deployment by adding more hosts to existing clusters, or by adding new clusters.
3. Your clusters can have multiple datastores. You can use VMware vSAN™ with local SSDs or IBM Cloud File Storage for Classic (NFS), where you can have one or more LUNs with different performance and size characteristics. You can expand the volumes as your needs grow.
4. The automation deploys a vCenter Server appliance on the management or consolidated cluster. Your vCenter Server has an IP address from the IBM Cloud classic infrastructure provided 10/8 address space.
5. The automation deploys three VMware NSX-T™ managers and a cluster is formed which uses NSX-T virtual IP for High Availability. Your NSX-T managers have an IP address from the IBM Cloud classic infrastructure provided 10/8 address space.
6. The automation deploys an Active Directory for authentication and name resolution. You can select between a single Windows virtual server instance in IBM Cloud IaaS hypervisor or two highly available dedicated Windows Server VMs (with bring your own license) on the VMware management cluster.
7. The automation deploys four edge nodes in your deployment and forms two NSX-T edge clusters - Services edge cluster and Workload edge cluster.
8. The gateway cluster is used to host a services Tier 0 Gateway, which provides network connectivity services for your management components.
9. Workload edge cluster hosts workload Tier 0 and Tier 1 Gateways for your workloads. A predefined example overlay network topology with one Tier 1 Gateway is provided by the automation. You can customize it for your own requirements by changing or deleting example segments or by adding new segments.







 VMware vCenter Server clusters 

The vCenter Server deployment might consist of several clusters. The following diagram provides an overview of the key cluster types.

Zoom

!
To resolve this error, create an instance of the Continuous Delivery service in the resource group. For more information about this requirement, see [Plan limitations and usage](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-limitations_usage).





 How do I find my toolchain ID? 

You can find your toolchain ID in the URL of your selected toolchain tool. For more information, see [Identifying your toolchain ID](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-aggregating-multiple-sources).





 Can I manage toolchains by using Terraform? 

You can use Terraform to create, read, update, and delete toolchains and tool integrations. For more information about using Terraform with toolchains, see [Creating a toolchain with Terraform](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains_getting_started&interface=terraformcreating_a_toolchain_terraform), [Deleting a toolchain with Terraform](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains-using&interface=terraformdeleting_a_toolchain_terraform), [Working with tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations&interface=terraform), and the [ibm_cd_toolchain resources documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain).





 Can I manage toolchains by using an API? 

You can use HTTP APIs or selected programming language SDKs to create, read, update, and delete toolchains and tool integrations.
The master key for each Block Storage for VPC volume is encrypted with a unique KMS-generated LUKS passphrase, which is then encrypted by your customer root key (CRK) and stored in the KMS. Passphrases are AES-256 cipher keys, which means that they are 32 bytes long and not limited to printable characters. You can view the cloud resource name (CRN) for the CRK that is used to encrypt a volume. However, the CRK, LUKS passphrase, and the volume's master encryption key are never exposed. For more information about all the keys IBM VPC uses to secure your data, see [IBM's encryption technology - How your data is secured](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutbyok-technologies).





 I use customer-managed encryption for my volumes. What happens when I disable or delete my root key? 

These actions are two separate actions. Disabling a root key in your KMS suspends its encryption and decryption operations, placing the key in a suspended state. Workloads continue to run in virtual server instances and boot volumes remain encrypted. Data volumes remain attached. However, if you power down the VM and then power it back on, any instances with encrypted boot volumes do not start. You can enable a root key in a suspended state and resume normal operations. For more information, see [Disabling root keys](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managingbyok-disable-root-keys).

Deleting a root key has greater consequences. Deleting a root key purges usage of the key for all resources in the VPC. By default, the KMS prevents you from deleting a root key that's actively protecting a resource. However, you can still force the deletion of a root key.
To securely forward private keys to remote nodes, you need to do ssh-add and ssh -A.

[your local PC]$ ssh-add {id_rsa for lsf cluster}
[your local PC] ssh -A -J root@jumpbox_fip root@management_private_ip
...
[root@management] ssh -A worker_private_ip

For Mac OS X, you can persist ssh-add by adding the following configuration to .ssh/config:

Host 
  UseKeychain yes
  AddKeysToAgent yes

You can even remove -A by adding "ForwardAgent yes" to .ssh/config.





 How many worker nodes can I deploy in my Spectrum LSF cluster through this offering? 

Before deploying a cluster, it is important to ensure that the VPC resource quota settings are appropriate for the size of the cluster that you would like to create (see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas)).

The maximum number of worker nodes that are supported for the deployment value worker_node_max_count is 500 (see [Deployment values](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-deployment-values)). The worker_node_min_count variable specifies the number of worker nodes that are provisioned at the time the cluster is created, which will exist throughout the life of the cluster. The delta between those two variables specifies the maximum number of worker nodes that can either be created or destroyed by the LSF resource connector auto scaling feature. In configurations where that delta exceeds 250, it's recommended to take caution if the characteristics of the workload are expected to result in >250 cluster node join or remove operation requests at a single point in time. In those cases, it's recommended to pace the job start and stop requests, if possible. Otherwise, you might see noticeable delays in some subset of the nodes joining or being removed from the cluster.





 Why are there two different resource group parameters that can be specified in the IBM Cloud catalog tile?
Adding and deleting provider virtual data centers 

You can scale an IBM Cloud® for VMware as a Service instance in different ways. Scaling is used to size the instance properly, based on VMware® workload requirements. By creating a provider virtual data center (PVDC), you can increase the size of the VMware as a Service instance.

PVDCs are used within the VMware as a Service instance to form units of the following components, which are fully isolated between PVDCs:



* Compute
* Memory
* Storage



Each PVDC inherits the following policies from the VMware as a Service instance:



* Networking - Networking can be shared between PVDCs.
* User administration - Users and user policies that are configured for the VMware as a Service instance are shared across all PVDCs.
* Catalogs - Catalog images and policies also apply across all PVDCs in the instance.



PVDCs consist of one or more VMware vCenter Server® clusters. A new vCenter Server cluster is created as part of adding a PVDC to the VMware as a Service instance.

You can increase or decrease the capacity of your deployment by adding or deleting PVDCs to and from an instance. You can also expand capacity by adding more clusters to a PVDC.

Typically, the instance is scaled first through host count and storage count management within the cluster. Up to 25 homogeneous hosts are supported in a cluster. After the maximum size of 25 hosts for a cluster is reached, a new cluster is required.

VDCs deployed to a PVDC can use all compute, memory, and storage within the PVDC, including when multiple clusters exist. To get consistent workload performance, it's best if all clusters within the same PVDC use the same host profile type. VMware Cloud Director automatically selects and adjusts the placement of workload VMs across the clusters in the PVDC. Placement is not controlled by users with VMware Cloud Director.

A new PVDC is typically created for the following scenarios:



* Separate and isolate different types of VMware workloads. The previous guidance is to use the same host profile type for all clusters in the same PVDC.
Expanding and contracting capacity for vCenter Server with Hybridity Bundle instances 

You can expand or contract the capacity of your VMware vCenter Server® with Hybridity Bundle instance according to your business needs, by adding or deleting VMware ESXi™ servers.

You can add new ESXi servers to an existing cluster by either selecting an existing configuration or a different configuration than the existing ESXi servers in the cluster. Existing configurations are available when you order your new server. To avoid performance or stability issues, it is recommended that clusters use the same or similar configuration regarding to CPU, RAM, and storage. This functionality is useful for hardware updates within the same cluster. A cluster can have only one type of storage.

You can add new ESXi servers to a cluster while the cluster is in maintenance mode. Additionally, you can simultaneously complete the following operations across multiple clusters:



* Add ESXi servers to a cluster and add ESXi servers to additional clusters.
* Delete ESXi servers from a cluster and delete ESXi servers from additional clusters.
* Add ESXi servers to a cluster and delete ESXi servers from additional clusters.
* Delete ESXi servers from a cluster and add ESXi servers to additional clusters.



Because your initial cluster has vSAN™ storage, adding one or more ESXi servers after deployment can increase the cluster storage capacity.



 Adding ESXi servers to vCenter Server with Hybridity Bundle instances 



 Before you add ESXi servers 



* Whenever possible, add ESXi servers by using the IBM Cloud® for VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the IBM Cloud for VMware Solutions console. Therefore, add ESXi servers to vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the IBM Cloud for VMware Solutions console.
* vSAN storage requires at least 4 ESXi servers.









 Procedure to add ESXi servers 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance for which you want to expand capacity.
3. Click the Infrastructure tab.
4.