vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-c002.us-east.satellite.appdomain.cloud 169.62.196.20 None created ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-c002 default
ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-c003.us-east.satellite.appdomain.cloud 169.62.196.23 None created ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-c003 default
ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-ce00.us-east.satellite.appdomain.cloud ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-c000.us-east.satellite.appdomain.cloud None created ne1d37313068166254bcb-edfc0a8ba65085c5081eced6816c5b9c-ce00 default
9. To continue to use the location for production workloads, repeat these steps to attach more hosts to the location control plane in multiples of 3, such as 6, 9, or 12 hosts. For more information, see [Adding capacity to your Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizingcontrol-plane-attach-capacity).









 Creating a cluster, API key, and cluster roles 

After setting up the location and the control plane, create cluster and an API key.



 Creating a Satellite cluster 



1.
* [ibmcloud oc cluster pull-secret apply](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_pull_secret_apply)
* [ibmcloud oc cluster rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_rm)
* [ibmcloud oc cluster service bind](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_service_bind)
* [ibmcloud oc cluster service ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_services)
* [ibmcloud oc cluster service unbind](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_service_unbind)
* [ibmcloud oc cluster subnet add](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_add)
* [ibmcloud oc cluster subnet create](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_create)
* [ibmcloud oc cluster subnet detach](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_detach)
* [Deprecated: ibmcloud oc cluster user-subnet add](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_user_subnet_add)
When you initiate cluster management actions, such as running ibmcloud oc commands, basic information about the cluster such as name, ID, user, the command is routed through a regional endpoint and the global endpoint.





 Resources in a multizone cluster 

In a multizone cluster, your cluster's resources are spread across multiple zones for higher availability.

Worker nodes are spread across multiple zones in the metro location to provide more availability for your cluster. The Kubernetes master replicas are also spread across zones. When you initiate local container orchestration actions, such as oc commands, the information is exchanged between your master and worker nodes through the global endpoint.

Other cluster resources, such as storage, networking, compute, or apps running in pods, vary in how they deploy to the zones in your multizone cluster. For more information, review these topics:



* Setting up [file storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageadd_file) and [block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageadd_block) in multizone clusters, or [choosing a multizone persistent storage solution](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).
* [Enabling public or private access to an app by using a network load balancer (NLB) service in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancermulti_zone_config).
* [Managing network traffic by using Ingress](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about).
* [Increasing the availability of your app](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_apps).
We can use the IAM wildcarding features [Assigning access by using wildcard policies](https://cloud.ibm.com/docs/account?topic=account-wildcard) to simplify the access policies that control access to the mirrored resources.

If you are new to IAM access policies, see [What is IBM Cloud Identity and Access Management?](https://cloud.ibm.com/docs/account?topic=account-iamoverview) and [Managing access to your Event Streams resources](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-security) for more details.

Define the following IAM access policies on both clusters, where <ALIAS> is the alias for the other cluster. For example, on cluster B, the resource ID is A.checkpoints.internal.



Table 2. Access policies

 Resource type Resource ID Role 

 cluster Reader 
 group <RESOURCE_NAME>.* As required by the application 
 topic <RESOURCE_NAME>.* As required by the application 
 txnid <RESOURCE_NAME>.* As required by the application 
 topic (specific to the checkpoint topic) .checkpoints.internal Reader 



Grant fine-grained access policies to individual applications. For example, for applications simply consuming grant only Reader access.

For mirroring user controls, you must have the following permissions on the target cluster.



Table 3. Target cluster permissions

 Resource type Resource ID Role 

 cluster Manager 







 Considerations when you share clusters between multiple entities 

When multiple entities, such as different business units, are sharing an instance and require isolation from each other, follow naming guidelines to simplify the management and operation of mirrored clusters.

Name Kafka resources by using the following template: <ENTITY_PREFIX><SEPARATOR><NAME>

Where:



* <ENTITY_PREFIX> is the prefix for the entity that uses this topic.
* <SEPARATOR> is an optional character that is used to easily separate the entities and resource names.
* <NAME> is the name of the Kafka resource.
To continue to use the location for production workloads, repeat these steps to attach more hosts to the location control plane in multiples of 3, such as 6, 9, or 12 hosts. For more information, see [Adding capacity to your Satellite location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizingcontrol-plane-attach-capacity).









 Creating a cluster, API key, and cluster roles 

After setting up the location and the control plane, create cluster and an API key.



 Creating a Satellite cluster 



1. From the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), click Create.
2. In the Infrastructure section, select Satellite.
3. In the OCP entitlement section, specify an existing OCP entitlement for the worker nodes in this cluster by providing your [Red Hat® account pull secret](https://console.redhat.com/openshift/install/pull-secret) as a file or in raw JSON format. The cluster also uses this pull secret to download Red Hat OpenShift images from your own Red Hat account.
4. In the Location section, select the Satellite location where you want to create the cluster. Make sure that the location that you select is in a Normal state.
5. In the Operating System section, select the operating system of the hosts that you want to use in the default worker pool of your cluster. In locations that are Red Hat CoreOS enabled, you can use either your RHCOS or RHEL hosts. In RHCOS enabled locations, when you want to add worker pools to your cluster, you can use RHCOS or RHEL hosts. Make sure to attach hosts with the operating system that you want to use to your location before assigning them to a worker pool.
6. In the Worker pools section, configure the details for your default worker pool.



1. Select the Satellite zones that Satellite uses to evenly assign hosts across zones that represent zones in your underlying infrastructure provider. Generally, create your worker pool across 3 zones for high availability.
Each IBM Cloud Satellite location is connected by using IBM Cloud Satellite Link, which provides the connection to the IBM Cloud® control plane. It provides audit, packet capture, and visibility to the security team, while a configuration utility provides a global view of applications and services. IBM Cloud Satellite Link provides a simple way to manage the connection between IBM Cloud and the Satellite location with visibility into all the traffic that goes back and forth with control of the endpoints on both sides of the link.

Users can have groups of Red Hat® OpenShift® clusters in a [Satellite cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig). You can use [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-cluster-config) to deploy the application into a [Satellite cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

Follow a two-step process to enable your Red Hat® OpenShift® clusters to leverage Satellite Config to perform simultaneous deployments.



1. [Create a cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigsetup-clusters-satconfig-groups), which is a logical grouping of clusters that run on a Satellite location.
2. [Attach a cluster to a cluster group](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigsetup-clusters-satconfig-access), which grants Satellite Config access to manage the resources within the cluster.



As an advanced configuration, you can also deploy the application to the compute infrastructure in your on-premises data center or other cloud providers by using [IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-started).



1.
vi /etc/lvm/lvm.conf

Search for parameter auto_activation_volume_list and add the volume groups, other than the volume group that you defined for the NFS cluster, as entries in that list.

Sample setting of the auto_activation_volume_list entry in /etc/lvm/lvm.conf:

auto_activation_volume_list = [ "rhel_root" ]

Rebuild the initramfs boot image to make sure that the boot image does not activate a volume group that is controlled by the cluster.

On both nodes, run the following command.

dracut -H -f /boot/initramfs-$(uname -r).img $(uname -r)

Reboot both nodes.









 Installing and setting up the RHEL HA Add-On cluster 

Use the following instructions to perform the initial cluster configuration.



* Install and set up the RHEL HA Add-On cluster according to [Implementing RHEL HA Add-On cluster on Power Systems Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel).
* Configure and test fencing as described in [Create the fencing device](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhelha-rhel-create-fencing-device).



Sample output of the cluster status at this stage.

 pcs status
Cluster name: SAP_NFS
Cluster Summary:
* Stack: corosync
* Current DC: cl-nfs-1 (version 2.0.5-9.el8_4.5-ba59be7122) - partition with quorum
* Last updated: Fri Mar 10 10:35:42 2023
* Last change: Fri Mar 10 09:52:08 2023 by root via cibadmin on cl-nfs-1
* 2 nodes configured
* 1 resource instance configured

Node List:
* Online: [ cl-nfs-1 cl-nfs-2 ]

Full List of Resources:
* res_fence_ibm_powervs
: To prevent any interruption of service, [redeploy your cluster workloads](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appcopy_apps_cluster) to a [supported data center](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-mz) and remove your MEX01 clusters by 31 October 2022. Clusters remaining in these data centers after 31 October 2022 will be removed. You cannot create clusters in this location after 07 May 2022. For more information about data center closures and recommended data centers, see [Data center consolidations](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).

Red Hat OpenShift on IBM Cloud default version update.
: [4.9](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) is now the default version.

CLI change log update
: The [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog) is updated for version 1.0.394.





 6 April 2022 

Master fix pack update

: Red Hat OpenShift on IBM Cloud [4.9.25_1534_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49) and [4.8.35_1552_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48)







 March 2022 



 30 March 2022 

Cluster autoscaler add-on
: Version [1.1.0_475](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog) is available.
Authorization policy 18cfc980-4458-4313-972e-93f312cdcd81 is deleted successfully

 view the authorization policy (it should no longer exist)
$ ibmcloud iam authorization-policies

Getting authorization policies under account ea998d3389c3473aa0987652b46fb146 as <email address>...
OK
No policy found

 delete the KMS instance
$ ibmcloud resource service-instance-delete $KMS_NAME --force

Deleting service instance my-kms-1 in resource group Default under account <account name> as <email address>...
OK
Service instance my-kms-1 with ID crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:b3933ab0-d579-46fc-8ed5-351aea657b9a:: is deleted successfully

 delete the COS instance
$ ibmcloud resource service-instance-delete $COS_NAME --force

Deleting service instance my-cos-1 in resource group Default under account <account name> as <email address>...
OK
Service instance my-cos-1 with ID crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:: is deleted successfully

 view resources (COS and KMS should no longer exist)
$ ibmcloud resource service-instances

Retrieving instances with type service_instance in resource group Default in all locations under account <account name> as <email address>...
OK
No service instance found.
Authorization policy 18cfc980-4458-4313-972e-93f312cdcd81 is deleted successfully

 view the authorization policy (it should no longer exist)
$ ibmcloud iam authorization-policies

Getting authorization policies under account ea998d3389c3473aa0987652b46fb146 as <email address>...
OK
No policy found

 delete the KMS instance
$ ibmcloud resource service-instance-delete $KMS_NAME --force

Deleting service instance my-kms-1 in resource group Default under account <account name> as <email address>...
OK
Service instance my-kms-1 with ID crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:b3933ab0-d579-46fc-8ed5-351aea657b9a:: is deleted successfully

 delete the COS instance
$ ibmcloud resource service-instance-delete $COS_NAME --force

Deleting service instance my-cos-1 in resource group Default under account <account name> as <email address>...
OK
Service instance my-cos-1 with ID crn:v1:bluemix:public:cloud-object-storage:global:a/ea998d3389c3473aa0987652b46fb146:4b636e74-f3ca-40bb-80b8-3bd21801ccb8:: is deleted successfully

 view resources (COS and KMS should no longer exist)
$ ibmcloud resource service-instances

Retrieving instances with type service_instance in resource group Default in all locations under account <account name> as <email address>...
OK
No service instance found.





 Example 3
ID: crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:ea557753-a15b-4570-a9a3-1efefbd2d382::
GUID: ea557753-a15b-4570-a9a3-1efefbd2d382
Location: us-south
State: active
Type: service_instance
Sub Type: kms
Allow Cleanup: false
Locked: false
Created at: 2020-05-31T15:04:50Z
Updated at: 2020-05-31T15:04:50Z
Last Operation:
Status create succeeded
Message Completed create instance operation

 list the service instances
$ ibmcloud resource service-instances
Retrieving instances with type service_instance in resource group Default in all locations under account <account name> as <email address>...
OK
Name Location State Type
<instance_name> us-south active service_instance

 delete the public service instance
$ ibmcloud resource service-instance-delete <instance_name>
Deleting service instance <instance_name> in resource group Default under account <account name> as <email address>...
Really delete the service instance <instance_name> with ID crn:v1:bluemix:public:kms:us-south:a/ea988d3289c24739a0977651b46fb145:ea557753-a15b-4570-a9a3-1efefbd2d382::? [y/N] > y
OK
* On the card for the vm-centos8-01 virtual machine, click on Details
* Scroll down to Guest OS Customization and expand the section. Capture the password for the instance.
* Back at the Virtual Machines page, click on Actions and then Launch Web Console.
* Login to the instance using the user root and the password captured above. You will be required to change the password. Change it to a password of your choice and proceed to login.









 Step 5: Remove resources 



1. Navigate to [Schematics](https://cloud.ibm.com/schematics/workspaces) workspaces and select your workspace.
2. Click on the Actions... drop down and click Destroy resources to clean up all the resources that were provisioned via Schematics.
3. Click on the Actions... drop down and click Delete workspace to delete the workspace.
4. Navigate to the [IBM Cloud for VMware Solutions Resources](https://cloud.ibm.com/infrastructure/vmware-solutions/console/instances).
5. Delete the vmware-tutorial instance listed under the VMware Solutions Shared section.







 Expand the tutorial 

Want to add to or change this tutorial? Here are some ideas:



* Create a fork of the vmware-solutions-shared repository and modify it to include additional virtual machines and create a new Schematics workspace to use it.
* Add to the template to configure the virtual machine for secure SSH.







 Related content 



* [IBM Cloud for VMware Solutions docs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Schematics docs](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started)
* [IBM Cloud for VMware Solutions](https://www.ibm.com/cloud/vmware)
If the delete operation failed from the console or you want to use command-line, you can use the oc command-line interface to complete the steps to uninstall. When you use the command-line, you need to remove the resources on your OpenShift Container Platform cluster that are associated with the IBM Cloud Pak for Multicloud Management.

If you do not have the OpenShift CLI installed, download and install the CLI from the Red Hat Customer Portal.

When you are running the commands to remove the associated resources, use the project that you selected during the installation of your OpenShift Container Platform cluster. Replace the <project_name> parameter in the following commands with your project name.



1. Delete the resources for the custom resource definition (CRD):

oc -n <project_name> delete IBMServicesPlatform default
2. Delete the deployment:

oc -n <project_name> delete deployment ibmservices-operator
3. Delete the custom resource definition:

oc -n <project_name> delete CustomResourceDefinition IbmServicesPlatforms.operator.ibm.com
4. Delete the ClusterRoleBinding:

oc -n <project_name> delete clusterrolebinding ibmservices-operator
5. Delete the pull secret:

oc -n <project_name> delete secret ibmplatform-image-pull-secret
6. Delete the admin-credential:

oc -n <project_name> delete secret admin-credential
7. Delete configmap cloudpak-foundation:

oc -n kube-system delete configmap cloudpak-foundation
8. Verify that the Cloud Pack is uninstalled.

Access the OpenShift web console and verify that the components that are related to the IBM Cloud Pak for Multicloud Management, such as any related pods, are no longer installed.
Select Delete the persistent storage used by the cluster and enter the name of the cluster to confirm.
4. Click on Delete









 Related content 



* [Understanding Red Hat OpenShift Service Mesh](https://docs.openshift.com/container-platform/4.12/service_mesh/v2x/ossm-architecture.html)
* [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift)
* [Comparing Service Mesh and Istio](https://docs.openshift.com/container-platform/4.12/service_mesh/v2x/ossm-architecture.html) - [Exposing apps with routes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes)
* [Istio Observability](https://istio.io/docs/concepts/observability/)
1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click the Cloud director sites tab, then click an instance name.
3. Click the Add-on services tab.
4. Click the vertical overflow menu in the Veeam Backup and Replication panel and click Delete.
5. In the Delete add-on service window, review the considerations, and enter Veeam Backup and Replication to confirm that you want to delete all Veeam backup services from your instance. Click Delete.







 Related links 



* [Ordering VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering)
* [Viewing VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
* [Managing Veeam for VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-veeam)
* [Veeam website](https://www.veeam.com/)
* [Veeam Help Center](https://www.veeam.com/documentation-guides-datasheets.html)
6. Acknowledge that cancellation might cause data loss in the future by checking the box. Then, select Cancel IBM Cloud Backup for Classic.







 Cancel the service with Terraform 

Use the terraform destroy command to conveniently destroy a remote object such as an instance of IBM Cloud Backup for Classic. The following example deletes the vault that is defined by its ID.

terraform destroy --target ibm_storage_evault.example.id

For more information, see [terraform destroy](https://developer.hashicorp.com/terraform/cli/commands/destroy).





 Uninstall the Backup Agent from your server 



 Removing the Backup Agent from a Windows® Server 



1. Establish a remote desktop session to your server.
2. Go to Start, and click Control Panel.
3. Select Programs and Features.
4. Right-click the EVault Software Agent and confirm the removal by clicking uninstall.
5. In the dialog box that appears, click Yes.
6. Select Total uninstall and confirm by clicking Next >.
7. Restart your server at your earliest convenience to ensure that the software is removed completely.







 Removing the Backup Agent from a Linux® Server 



1. Establish a Secure Shell connection (SSH) to your server.
2. From the command line, issue the following command.

/opt/BUAgent/uninstall.sh
3. When prompted by the following question, press Y, then press Enter.

VVAgent is still running. Do you wish to stop it? ([Y]/n)
4. At the next prompt, press Y. Then, press Enter again.

This will remove jobs, settings, etc. (y/[N])
5. Restart your server at your earliest convenience to ensure that the software is removed completely.