vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg).
4. Click Authorize Host.
5. To see the list of available IP addresses, select IP address as the host type. Then, select the subnet where your host resides.
6. From the filtered list, select one or more IP addresses that can access the volume and click Save.







 SLCLI 

 slcli block subnets-assign -h
Usage: slcli block subnets-assign [OPTIONS] ACCESS_ID
Assign block storage subnets to the given host id.
access_id is the host_id obtained by: slcli block access-list <volume_id>

Options:
--subnet-id INTEGER ID of the subnets to assign; e.g.: --subnet-id 1234
-h, --help Show this message and exit.







 How many volumes can be ordered? 

By default, you can provision a combined total of 700 block and file storage. To increase your volume limit, contact your sales representative. For more information, see [Managing storage limits](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-managingstoragelimits).





 How many Block Storage for Classic volumes can be mounted to a host? 

That depends on what the host operating system can handle, it’s not something that IBM Cloud® limits. Refer to your OS Documentation for limits on the number of volumes that can be mounted.





 Can I attach multiple LUNs with different OS settings? 

No. A host cannot be authorized to access LUNs of differing OS types at the same time. A host can be authorized to access LUNs of a single OS type. If you attempt to authorize a host to access multiple LUNs with different OS types, the operation results in an error.





 Which Windows® version am I to choose for my Block Storage for Classic LUN?
[your local PC]$ ssh-add {id_rsa for slurm 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 Slurm 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 number of worker nodes that are supported for the deployment value worker_node_count is 500 (see [Deployment values](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-deployment-values))). The worker_node_count variable specifies the number of worker nodes that are provisioned at the time that the cluster is created, which will exist throughout the life of the cluster.

When creating or deleting a cluster with many worker nodes, you might encounter VPC resource provisioning or deletion failures. In those cases, running the Schematics apply or destroy operation again might result in the remaining resources being successfully provisioned or deleted. If you continue to see errors, see [Getting help and support](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-getting-help-and-support).





 Does the offering support the Terraform parallelism flag?
Cloud Foundry roles grant access to organizations and spaces within the account. Cloud Foundry roles do not enable user permissions for completing actions within the context of a service across the account.

Cloud Foundry access is assigned by adding a user to an org and space, and then assigning an org role and space role. Depending on the type of role that is assigned, that user can complete specific actions for service instances that are added to a particular space.

Zoom

![Cloud Foundry access](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/CF.svg)

Figure 2. Assigning a user access to a Cloud Foundry org and space

The following roles can be assigned at the organization level:



Table 1. Organization roles and permissions

 Organization role Permissions 

 Manager Organization managers can create, view, edit, or delete spaces within the organization, view the organization's usage and quota, invite users to the organization, manage who has access to the organization and their roles in the organization, and manage custom domains for the organization. 
 Billing manager Billing managers can view runtime and service usage information for the organization on the Usage page. 
 Auditor Organization auditors can view application and service content in the organization. Auditors can also view the users in the organization and their assigned roles, and the quota for the organization. 



The following roles can be assigned at the space level:



Table 2. Space roles and permissions

 Space role Permissions 

 Manager Space managers can add existing users and manage roles within the space. The space manager can also view the number of instances, service bindings, and resource use for each application in the space. 
 Developer Space developers can create, delete, and manage applications and services within the space. Some of the managing tasks include deploying apps, starting or stopping apps, renaming an app, deleting an app, renaming a space, binding or unbinding a service to an application, viewing the number or instances, service bindings, and resource usage for each application in the space.
Cloud Foundry roles grant access to organizations and spaces within the account. Cloud Foundry roles do not enable user permissions for completing actions within the context of a service across the account.

Cloud Foundry access is assigned by adding a user to an org and space, and then assigning an org role and space role. Depending on the type of role that is assigned, that user can complete specific actions for service instances that are added to a particular space.

Zoom

![Cloud Foundry access](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public/includes/account/includes/account/images/CF.svg)

Figure 2. Assigning a user access to a Cloud Foundry org and space

The following roles can be assigned at the organization level:



Table 1. Organization roles and permissions

 Organization role Permissions 

 Manager Organization managers can create, view, edit, or delete spaces within the organization, view the organization's usage and quota, invite users to the organization, manage who has access to the organization and their roles in the organization, and manage custom domains for the organization. 
 Billing manager Billing managers can view runtime and service usage information for the organization on the Usage page. 
 Auditor Organization auditors can view application and service content in the organization. Auditors can also view the users in the organization and their assigned roles, and the quota for the organization. 



The following roles can be assigned at the space level:



Table 2. Space roles and permissions

 Space role Permissions 

 Manager Space managers can add existing users and manage roles within the space. The space manager can also view the number of instances, service bindings, and resource use for each application in the space. 
 Developer Space developers can create, delete, and manage applications and services within the space. Some of the managing tasks include deploying apps, starting or stopping apps, renaming an app, deleting an app, renaming a space, binding or unbinding a service to an application, viewing the number or instances, service bindings, and resource usage for each application in the space.
Forwarded keys are deleted immediately after a session is closed.

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 symphony 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 Symphony 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/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-deployment-values)). The worker_node_min_count variable specifies the number of worker nodes that are provisioned at the time that 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 Symphony Host Factory auto-scaling feature.

When creating or deleting a cluster with many worker nodes, you might encounter VPC resource provisioning or deletion failures. In those cases, running the Schematics apply or destroy operation again might result in the remaining resources being successfully provisioned or deleted.
I create an access group and assign an administrator role on Service A at the account level, and a policy with the viewer role for any resource groups in the account that they need to be able to create instances in. You can do this by selecting Resource group only, then select the resource group, and at least viewer role for that resource group. Then, repeat for each resource group that they need access to.





 A user that requires access to a specific resource 

My account includes a user who needs access to only a specific resource in one service, for example, the ability to write to a bucket, Bucket A, in IBM Cloud Object Storage. This user doesn't need to view the resource groups in my account or access other services or buckets in this instance of Object Storage.

I assign the user a writer role on Bucket A in the specific instance of Object Storage. I can choose to use the IAM UI or the Object Storage UI to assign the role. I use the service-specific UI because I can from a list of resources. The IAM UI doesn't display resources past the service instance level, and I need to manually enter the CRN to assign policy to those resources.







 Next steps 

Now that you know how to set up your resource groups, organize your resources, and create access groups in your account, you can start [inviting users to your account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv) and assigning them access to your access groups. If you already invited users to your account, you can go to your Users page and start to [assign access](https://cloud.ibm.com/docs/account?topic=account-assign-access-resourcesassign-access-resources).

If you decide that your organization wants to manage user access based on your corporate user directory, you can start by [creating trusted profiles](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile).
You might have exceeded your [pull traffic quota limits](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_get), which prevents the Docker image from being fetched.

 How to fix it 

Review your [quota limits and usage](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_get) for storing and pulling images. [Free up used storage and change service plans](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_freeup) or quota limits to stay within given quota limits.





 I tried to compile my app in a single pipeline job, why did it fail? 

You require 4 GB of memory (not file store) to build your app in a single pipeline job.

 What’s happening 

When I attempt to compile my app in a single pipeline job, the build job fails with an unexpected error.

 Why it’s happening 

Your app requires more than 4 GB of memory to compile in a single pipeline job.

 How to fix it 

To build your app in a single pipeline job:



1. Create an [IBM Cloud® Continuous Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers).
2. Configure your build job to use the [private worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-private-workersconfigure_private_worker_integration).







 Why can't the Delivery Pipeline communicate through a firewall? 

Your firewall configuration prevents the Delivery Pipeline from communicating with environments that are behind a firewall.

 What’s happening 

When I attempt to use the Delivery Pipeline, it cannot communicate through my firewall.

 Why it’s happening 

Your firewall must be configured to allow the Delivery Pipeline to communicate with environments that are behind a firewall.

 How to fix it
See [Customizing a cluster](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-cust-cluster).
* Can I stop or shutdown my IBM Analytics Engine clusters to be charged on a per-use basis?

You are charged as long as the cluster is active and not on a per-use basis. For this reason, you should delete the instance after your job has completed and create a new instance before you start another job. To enable creating and deleting clusters as you need them however, means you must separate compute from storage. See [Best practices](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-best-practicesseparate-compute-from-storage).
* Can I scale down nodes in existing IBM Analytics Engine clusters?

No, you can't reduce the number of nodes in existing clusters; you can only add more nodes to those clusters. If you want to scale down, you must delete those clusters and create new ones with the correct number of nodes.
* Do I have root access in IBM Analytics Engine?

No, users do not have sudo or root access to install privileges because IBM Analytics Engine is a Platform as a Service (PaaS) offering.
* Can I install my own Hadoop stack components?

No, you cannot add components that are not supported by IBM Analytics Engine because IBM Analytics Engine is a Platform as a Service (PaaS) offering. For example, you are not permitted to install a new Ambari Hadoop stack component through Ambari or otherwise. However, you can install non-server Hadoop ecosystem components, in other words, anything that can be installed and run in your user space is allowed.
* Which third party packages can I install?

You can only install packages that are available in the CentOS repositories by using the packageadmin tool that comes with IBM Analytics Engine. You do not require sudo or root privileges to install or run any packages from the CentOS repositories.

You should perform all cluster customization by using customization scripts at the time the cluster is started to ensure repeatability and consistency when creating further new clusters.
* Can I monitor the cluster?
You can even remove -A by adding "ForwardAgent yes" to .ssh/config.
* How many worker nodes can I deploy in my Slurm 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 number of worker nodes that are supported for the deployment value worker_node_count is 500 (see [Deployment values](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-deployment-values))). The worker_node_count variable specifies the number of worker nodes that are provisioned at the time that the cluster is created, which will exist throughout the life of the cluster.

When creating or deleting a cluster with many worker nodes, you might encounter VPC resource provisioning or deletion failures. In those cases, running the Schematics apply or destroy operation again might result in the remaining resources being successfully provisioned or deleted. If you continue to see errors, see [Getting help and support](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-getting-help-and-support).
* Does the offering support the Terraform parallelism flag?

The Terraform [parallelism](https://www.terraform.io/docs/cloud/workspaces/variables.htmlparallelism) flag is used to control the number of concurrent operations allowed for Terraform plan, Terraform apply, and Terraform destroy. A larger number can result in faster overall cluster create and destroy times. However, too large a value might result in operation failures. For plan and apply, it's recommended to use values up to 250, and for destroy, it's recommended to use values up to 100.
claimName: block-storage-pvc
Show more
11. Create the pod in your cluster.

oc create -f pod.yaml
12. After the pod is in Running status, get the logs.

oc logs

Example output.

2022-01-21 16:11:00



You successfully created a PV and bound it to a PVC. Then, you deployed and app that uses block storage. Cluster users can now [mount the PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_app_volume_mount) to their deployments and start reading from and writing to the persistent volume.







 Using block storage in a stateful set 

If you have a stateful app such as a database, you can create stateful sets that use block storage to store your app's data. Alternatively, you can use an IBM Cloud database-as-a-service and store your data in the cloud.

What do I need to be aware of when adding block storage to a stateful set?
: To add storage to a stateful set, you specify your storage configuration in the volumeClaimTemplates section of your stateful set YAML. The volumeClaimTemplates is the basis for your PVC and can include the storage class and the size or IOPS of your block storage 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.
RabbitMQ Disk Alarms 

By default, when the RabbitMQ server detects that free disk space has dropped below a certain threshold, it raises a disk alarm. The threshold for Messages for RabbitMQ is 80% of your deployment's disk size. The alarm blocks incoming messages from publishers and prevents messages in memory from being written to disk. The alarm is cluster-wide so if disk space on one node gets too low, the alarm blocks on all nodes. To clear the alarm, either messages that have been written to disk need to be consumed and that space is reclaimed, or scale your deployment to a larger disk size.

More information about memory alarms can be found in the [RabbitMQ documentation](https://www.rabbitmq.com/disk-alarms.html).





 Disk IOPS 

The number of input/output operations per second (IOPS) is limited by the type of storage volume that is being used. Storage volumes for Messages for RabbitMQ deployments are provisioned on [Block Storage Endurance Volumes in the 10 IOPS per GB tier](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingthroughConsoleorderingthroughConsoleEndurance). IOPS limits can affect RabbitMQ message throughput and storage operations. Reaching these limits can cause disk to fall behind on reclaiming space after messages are consumed, leading to disk alarms and publisher throttling until activity slows down. You can increase the number IOPS available to your deployment by increasing disk space.





 Quorum Queues 

High-availability can be managed with [quorum queues](https://www.rabbitmq.com/quorum-queues.html). Using quorum queues impacts performance; it needs more memory and disk space for the WAL that it uses to maintain state for operations. It also needs more disk I/O as it persists all data on disk.
In this case, "ordering" refers to the "order to take snapshots" and not "ordering nodes".

For our example, we use the CLI and order a single snapshot by using 5 GB of space by issuing:

ibmcloud sl file snapshot-order 155617812 -s 5

You might need more or less than 5 GB of space, depending on the size of the pod and the resources that have been used on it. The amount of space that is required depends on the size of your transactions, the quantity of transactions, and how many snapshots (or backups) that you want to keep. To determine how much storage you are using, [monitor](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-monitoring) the disk space that is consumed by your nodes so that you know when to add storage. You can use this data to inform how much storage is being used, and how fast it is growing. Also, if you monitor the size of each snapshot, you can use the snapshot size along with the number of snapshots you want to keep to determine when more snapshot space is required.

Taking a snapshot incurs charges on your account. Press y to accept the charges and order the snapshot.

Alternatively, you can enable snapshots to be taken on a regular schedule for a particular volume. For information on how to set of a snapshot schedule, see [Adding a Snapshot schedule](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingSnapshotsaddscheduleUI).

Again, for our example, we use the CLI to set up a daily snapshot of a CouchDB volume at 3:00 a.m. and retain seven snapshots.

ibmcloud sl file snapshot-enable 155617812 -s DAILY -c 7 -r 3

Which produces a message similar to the following:

OK
DAILY snapshots have been enabled for volume 155617812.

We can now list the snapshot schedule to verify it's in place by issuing:

ibmcloud sl file snapshot-schedule-list 155617812
Its schedule appears Manual.





 Taking a manual Snapshot from the SLCLI 

You can use the following command to create a snapshot from the SLCLI.

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

Options:
-n, --notes TEXT Notes to set on the new snapshot
-h, --help Show this message and exit.





 Listing all Snapshots with Space Used Information and Management functions in the UI 

A list of retained snapshots and space that is used can be seen on the Block Storage for Classic Detail page. Management functions (editing schedules and adding more space) are conducted on the Block Storage for Classic Detail page by using the Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg) menu or links in the various sections on the page. The Snapshot page displays how much capacity the volume has and how much of it is used.

You receive notifications when you reach 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. If you reduce the snapshot data or increase the space, the warning system is reset, and no autodeletion occurs.
* At 90 percent capacity, a second warning is sent when snapshot space usage exceeded 90 percent. 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.