vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Document classifier](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-doc-classifier) 





 Grouping facets 

To organize your facets, you can group them in folders.

Grouping facets does not combine the data from the facets. It merely makes the facets easier to find because they are organized in named folders.

To associate facets such that you can combine data from multiple facets, the facets must have a facet and subfacet relationship. Such hierarchical relationships must be defined at the time that the facet enrichment or annotation is created and applied to the collection.

To group facets, complete the following steps:



1. From the initial search page, submit a search.
2. From the Facet analysis pane, click the Edit icon.

Zoom

![Facet analysis pane edit icon](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/cm-facet-edit.png)

Figure 1. Facet analysis pane edit icon
3. Name the group, and then select the facets that you want to group together.

Zoom

![Facet grouping dialog](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/cm-facet-group.png)

Figure 2. Facet grouping dialog
4. Click Apply.
5. The facets that you grouped are now available from a folder with the group name.

Zoom

!
* [Understanding the impact of a master outage](https://cloud.ibm.com/docs/containers?topic=containers-debug_masterreview-master-outage)



[Cluster states](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-states-reference)



* [Aborted](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-aborted)
* [Critical](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-critical)
* [Create failed](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-create-failed)
* [Delete failed](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-delete-failed)
* [Deleted](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-deleted)
* [Deleting](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-deleting)
* [Deploy failed](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-deploy-failed)
* [Deploying](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-deploying)
* [Normal](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-normal)
* [Pending](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-pending)
Adding clusters to vCenter Server instances 

You can add clusters to VMware vCenter Server® instances to expand the compute and storage capacity. Within a cluster, you can manage VMware ESXi™ servers for better resource allocation and high availability.

Adding clusters to vCenter Server instances with VMware vSphere® 6.5 or 6.7 is not supported.



 Before you add clusters to vCenter Server instances 



* Whenever possible, add clusters by using the IBM Cloud® for VMware Solutions console and not the VMware vSphere® Web Client. Changes that you make on the vSphere Web Client are not synchronized with the VMware Solutions console. If you want to add clusters to vCenter Server instances by using the vSphere Web Client, do so only for on-premises clusters or clusters that you don't manage in the VMware Solutions console.
* The number of clusters, hosts, and virtual machines (VMs) determines the maximum number of clusters that you can add. You must remain within the VMware® sizing guidelines and limits for your deployment. For more information, see [VMware configuration maximums](https://configmax.vmware.com/home).
* You can add a cluster while another cluster is being created or deleted.







 Cluster type 

Select the cluster type: Workload cluster or Gateway cluster.





 System settings for workload clusters 

When you add a workload cluster to a vCenter Server instance, you must specify the following settings.



 Cluster name 

The cluster name is set to vcs-xx by default, where xx represents two randomly generated alphabetic characters.

You can also specify a new cluster name that meets the following requirements:



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* The cluster name must start with a lowercase alphabetic character.
* The cluster name must end with a lowercase alphabetic or numeric character.
* The maximum length of the cluster name is 30 characters.
* The cluster name must be unique within the vCenter Server instance.







 Licensing settings 

Review the following information and specify the licensing setting for the VMware vSphere component in the cluster:
* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_solution_model)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_migrate_results)



* [Research nonprofit securely hosts sensitive data while it grows research with partners](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_research)



* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_research_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_research_solution)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_healthuc_research_results)





[Retail use cases for IBM Cloud](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_retailcs_uc_retail)



* [Brick-and-mortar retailer shares data, by using APIs with global business partners to drive omnichannel sales](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_retailuc_data-share)



* [Context](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_retailuc_data-share_context)
* [Solution](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_retailuc_data-share_solution)
* [Results](https://cloud.ibm.com/docs/containers?topic=containers-cs_uc_retailuc_data-share_results)
You can also delete a cluster while another cluster is being created or deleted.
* Ensure that all nodes in a cluster are powered on and operational before you delete the cluster.
* When you delete a cluster, all VMs (virtual machines) from the cluster are also deleted and they can't be recovered. If you want to keep the VMs, migrate them to other clusters.









 Procedure to delete clusters from vCenter Server with Hybridity Bundle instances 



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 that you want to delete clusters from.

Ensure that the instance status is Available. Otherwise, you cannot delete clusters from the instance.
3. Click the Infrastructure tab. In the CLUSTERS table, locate the cluster that you want to delete and click the Delete icon in the Actions column.







 Related links 



* [Viewing vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_viewinginstances)
* [Expanding and contracting capacity for vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_addingremovingservers)
-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--nlb-subdomain SUBDOMAIN
: The subdomain to regenerate the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns secret regenerate command 

ibmcloud ks nlb-dns secret regenerate --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud







 Experimental: ibmcloud ks nlb-dns secret rm 

Virtual Private Cloud

Classic infrastructure

Delete a secret from an NLB subdomain and prevent future renewal of the certificate.

You might delete the secret for an NLB subdomain if you no longer use the subdomain, or if the owner of the secret leaves your organization.

ibmcloud ks nlb-dns secret rm --cluster CLUSTER --nlb-subdomain SUBDOMAIN [-f] [--output json] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--nlb-subdomain SUBDOMAIN
: The subdomain to delete the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.





 Example nlb-dns secret rm command
-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--nlb-subdomain SUBDOMAIN
: The subdomain to regenerate the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns secret regenerate command 

ibmcloud ks nlb-dns secret regenerate --cluster mycluster --nlb-subdomain mycluster-a1b2cdef345678g9hi012j3kl4567890-0001.us-south.containers.appdomain.cloud







 Experimental: ibmcloud ks nlb-dns secret rm 

Virtual Private Cloud

Classic infrastructure

Delete a secret from an NLB subdomain and prevent future renewal of the certificate.

You might delete the secret for an NLB subdomain if you no longer use the subdomain, or if the owner of the secret leaves your organization.

ibmcloud ks nlb-dns secret rm --cluster CLUSTER --nlb-subdomain SUBDOMAIN [-f] [--output json] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--nlb-subdomain SUBDOMAIN
: The subdomain to delete the secret for. To list subdomains, run ibmcloud ks nlb-dns ls --cluster CLUSTER.

-f
: Optional: Force the command to run with no user prompts.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example nlb-dns secret rm command
The name of the storage configuration that you want to assign to your cluster group. To list Satellite storage configurations, run ibmcloud sat storage config ls.

--cluster CLUSTER_ID
: The ID of a Satellite cluster. To list Satellite clusters, run ibmcloud oc cluster ls --provider satellite. To assign the storage configuration to multiple clusters at once, create a cluster group or run this command with this option multiple times. If you do not include this option, you must specify the --group or the --service-cluster-id option.

--group GROUP
: The ID of the cluster group. To list Satellite cluster groups, run ibmcloud sat group ls. To assign the storage configuration to multiple cluster groups at the same time, repeat this option. If you do not include this option, you must specify the --cluster or the --service-cluster-id option.

--service-cluster-id CLUSTER_ID
: The ID of a Satellite-enabled IBM Cloud service cluster. To find the cluster ID, run ibmcloud sat service ls --location <location>. If you do not include this option, you must specify the --cluster or the --group option.

--name NAME
: Optional. Enter a name for your storage assignment.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat storage assignment create --group staging --config file100 --name file100-staging







 ibmcloud sat storage assignment get 

Get the details of a Satellite storage assignment.

ibmcloud sat storage assignment get --assignment ASSIGNMENT



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--assignment ASSIGNMENT
: Required. The name of the storage assignment. To list Satellite storage configurations, run ibmcloud sat storage assignment ls.

--output json
The following command creates a rule that protects the CLUSTER-ID cluster. Only resources in the NETWORK-ZONE-ID network zone can access the cluster. This rule includes both the cluster and management API types.

ibmcloud cbr rule-create my-rule-2 --service-name secrets-manager --service-instance CLUSTER-ID --zone-id NETWORK-ZONE-ID







 Next steps 

You must follow the creation or modification of zones or rules with adequate testing to ensure access and availability.

Users who attempt to access your resources outside of the defined zones receive HTTP error 401 when the appropriate rules are not established.
List the name of your ODF cluster.

oc get ocscluster

Example output:

NAME AGE
ocscluster-vpc 71d
2. Describe the storage cluster and review the Events section of the output for any error messages.

oc describe ocscluster <ocscluster-name>
3. List the pods in the kube-system namespace and verify that they are Running.

oc get pods -n kube-system
4. Describe the ibm-ocs-operator-controller-manager pod and review the Events section in the output for any error messages.

oc describe pod <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system
5. Review the logs of the ibm-ocs-operator-controller-manager.

oc logs <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system
6. Describe NooBaa and review the Events section of the output for any error messages.

oc describe noobaa -n openshift-storage
* [About high availability](https://cloud.ibm.com/docs/containers?topic=containers-haha-about)
* [Overview of potential points of failure in IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-hafault_domains)







 API reference 

[IBM Cloud Kubernetes Service API](https://containers.cloud.ibm.com/global/swagger-global-api//)

[IBM Cloud Kubernetes Service API JSON](https://containers.cloud.ibm.com/global/swagger-global-api/swagger.json)

[IBM Cloud Container Registry API](https://cloud.ibm.com/apidocs/container-registry)

[IBM Cloud Vulnerability Advisor API](https://cloud.ibm.com/apidocs/container-registry/va)

[Community Kubernetes API](https://kubernetes.io/docs/reference/)





 CLI plug-in reference 

[IBM Cloud Kubernetes Service CLI Map](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map)



* [ibmcloud ks cluster](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map_cluster)
* [ibmcloud ks worker](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map_worker)
* [ibmcloud ks worker-pool](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map_worker-pool)
* [ibmcloud ks zone](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map_zone)
* [ibmcloud ks ingress](https://cloud.ibm.com/docs/containers?topic=containers-icks_mapicks_map_ingress)
Use these commands to register clusters for use with [Satellite configurations](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig). You can use configurations to consistently deploy and update apps across clusters.



 ibmcloud sat cluster get 

Get the details of a cluster that is registered with the Satellite Config component.

ibmcloud sat cluster get --cluster CLUSTER [-q] [--output JSON]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Cluster resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--cluster, -c CLUSTER
: Required. The name or ID of the cluster. To list registered clusters, run ibmcloud sat cluster ls.

--output JSON
: Optional. Displays the command output in JSON format.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat cluster get -c mycluster







 ibmcloud sat cluster ls 

View a list of clusters that are registered with the Satellite Config component. You can use Satellite configurations to consistently deploy and update apps to these clusters.

ibmcloud sat cluster ls [--filter FILTER] [--limit NUMBER] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Cluster resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--filter FILTER
: Optional. Filter results by a cluster property. Currently, the only supported cluster property is the cluster ID.

--limit NUMBER
: Optional. Limit the number of clusters that are returned. The default value is 50.

-q
: Optional.
If the issue persists when creating additional clusters, open an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).





 Delete failed 

Review the following description of the Delete failed cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The Kubernetes master or at least one worker node can't be deleted. List worker nodes by running ibmcloud ks worker ls --cluster <cluster_name_or_ID>. If worker nodes are listed, see [Unable to create or delete worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errors). If no workers are listed, open an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).





 Deleted 

Review the following description of the Deleted cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The cluster is deleted but not yet removed from your dashboard. If your cluster is stuck in this state for a long time, open an [IBM Cloud support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).





 Deleting 

Review the following description of the Deleting cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The cluster is being deleted and cluster infrastructure is being dismantled. You can't access the cluster.





 Deploy failed 

Review the following description of the Deploy failed cluster state. To view the state of your cluster, run ibmcloud ks cluster get --cluster <cluster_name_or_ID>.

The deployment of the Kubernetes master can't be completed. You can't resolve this state.
* [ibmcloud sat cluster get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-get)
* [ibmcloud sat cluster ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-ls)
* [ibmcloud sat cluster register](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-register)
* [ibmcloud sat cluster unregister](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-unregister)



* [Cluster group commands](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-commands)



* [ibmcloud sat group attach](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-attach)
* [ibmcloud sat group create](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-create)
* [ibmcloud sat group detach](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-detach)
* [ibmcloud sat group get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-get)
* [ibmcloud sat group ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-ls)
* [ibmcloud sat group rm](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecluster-group-rm)
Setting up multi-cluster and job forwarding using Spectrum LSF 

The following example is a guide on how to set up the multi-cluster and job forwarding using Spectrum LSF. This example explains common situations where a cluster is on-premises and another is in the cloud.

This example assumes that the on-premises cluster labeled with "OnPremiseCluster" uses a subnet 192.168.0.0/24 and its management host uses 192.168.0.4 (on-premise-management). The cloud cluster labeled with "HPCCluster" uses a subnet 10.244.128.0/24 and its management host uses 10.244.128.37 (icgen2host-10-244-128-37). Both of the configuration directories are in /opt/ibm/lsf/conf, but you can change the directory depending on your cluster configuration.



1. The following is an example of the /etc/hosts file for the cloud cluster. You need to make sure that the host names for the LSF management hosts are DNS-resolveable.

...
10.244.128.61 icgen2host-10-244-128-61
10.244.128.62 icgen2host-10-244-128-62
10.244.128.63 icgen2host-10-244-128-63

192.168.0.4 on-premise-management added

For the on-premises /etc/hosts file, make sure to add the information about the management host in the cloud cluster:

10.244.128.37 icgen2host-10-244-128-37 added
2. Both clusters need to recognize each other, so you need to modify /opt/ibm/lsf/conf/lsf.shared. This configuration file should be identical in both clusters.

...
Begin Cluster
ClusterName Servers Keyword modified
HPCCluster (icgen2host-10-244-128-37) modified
OnPremiseCluster (on-premise-management) modified
End Cluster
...
3.
Viewing clusters for Cyber Recovery instances 

You can view the summary and detailed information of the clusters that are provisioned in Cyber Recovery instances.



 Procedure to view clusters for Cyber Recovery instances 



1. From the IBM Cloud® for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click an instance to view the clusters in it.
3. Click the Infrastructure tab. In the Clusters table, view the summary about the clusters:



* Cluster name: The name and type of the cluster.
* Cluster type: The type of cluster. Types include witness, consolidated, workload, and edge services.
* ESXi servers: The number of VMware ESXi™ servers in the cluster.
* Storage: The type of storage that the cluster uses.
* Data center location: The IBM Cloud data center where the cluster is hosted.
* Pod: The pod where the cluster is deployed.
* Networking: Whether Public and private network or Private network only.
* Uplink speed: Whether 10 Gb or 25 Gb.
* Status: The status of the cluster. The status can have one of the following values:



* Initializing: The cluster is being created and configured.
* Modifying: The cluster is being modified.
* Available: The cluster is ready to use.
* Deleting: The cluster is being deleted.
* Deleted: The cluster is deleted.



* Actions: Click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) to delete the cluster.



4. Click a cluster name to view the ESXi server, storage, and network interface details.



ESXi server details

Additional ESXi server details

Storage details



Table 1. ESXi server details

 Item Description 

 Name The name of the ESXi server is in the following format: <host_prefix><n>.<root_domain>, where n is the sequence of the ESXi server.