vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Your daemon set, secret, and the Monitoring agent are still deployed to your cluster and you must manually remove them. Because the ConfigMap is removed, metrics are no longer sent to your IBM Cloud Monitoring service instance. Independent of how you created the configuration, existing metrics are still available in IBM Cloud Monitoring until your selected retention period ends.

ibmcloud ob monitoring config delete --cluster CLUSTER --instance MONITORING_INSTANCE

Minimum required permissions:



* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Cloud Monitoring



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to delete an existing Monitoring configuration. To retrieve the cluster name or ID, run ibmcloud ks cluster ls. This value is required.

--instance MONITORING_INSTANCE
: The ID or name of the IBM Cloud Monitoring service instance that you used in your monitoring configuration. To retrieve the service instance name, run ibmcloud resource service-instances. This value is required.

Example command

ibmcloud ob monitoring config delete --cluster mycluster --instance mymonitoringinstance





 ibmcloud ob monitoring config list 

Virtual Private Cloud

Classic infrastructure

List all Monitoring configurations that were created for your cluster with the IBM Cloud Kubernetes Service observability plug-in.

To list monitoring configurations that you manually set up without using the IBM Cloud Kubernetes Service observability plug-in, you must first make this configuration available to the plug-in by using the [ibmcloud ob monitoring agent discover](https://cloud.ibm.com/docs/containers?topic=containers-observability_climonitoring_agent_discover) command.

ibmcloud ob monitoring config list --cluster CLUSTER

Minimum required permissions:



* Viewer platform access role and Reader service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Cloud Monitoring



Command options:

--cluster CLUSTER
* [Create a PVM Instance snapshot](https://cloud.ibm.com/apidocs/power-cloudpcloud-pvminstances-snapshots-post)



CLIs to create snapshot and clone



* [Create a snapshot](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referencecreate-snapshot)
* [Create a volume clone for specific volumes](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referencecreate-volume-clone)







 Are there any initial snapshot requirement in terms of storage? 

None. The storage is allocated on demand.





 Does the snapshot and volume clone supports any safeguard policy? 

None. Power Systems Virtual Server does not (currently) provide any options to safeguarded copy (such as cyber protection).





 Can you tell me more about the backup process using the PowerHA Toolkit for IBM i? 

The PowerHA Toolkit for IBM i provides the 5250 user interfaces and automation to use them for backups. In a nutshell, it does the following:



* Automates the memory flush
* Create the volumes-clone
* Attach the clones to a host
* Start the host
* kicki-off the backups
* Move the BRMS data back to the production VM before shutting down the backup VM
* Remove the cloned volumes.



It also allows you to quickly create an intermediate snap-shot then a volumes-clone before entering the long-running volume detach or attach phase. You have the ability to pause the process immediately before attaching volumes.





 How do you set up private networks between Intel® Virtual Servers (x86) and Power Systems Virtual Servers?
Get started with the Sampler primitive 

Use the examples in this topic to learn how to set up and use the Sampler primitive program.



 Overview 

With the Sampler primitive you can more accurately contextualize counts. It takes a circuit as input and generates quasiprobabilities. This enables you to more efficiently evaluate the possibility of multiple relevant data points in the context of destructive interference.

If you are using the Standard plan, running Sampler incurs a cost. See [Manage costs](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-cost) for cost information.





 Prepare the environment 



1. Follow the steps in the [getting started guide](https://cloud.ibm.com/docs/quantum-computing?topic=quantum-computing-get-started) to get your Quantum Service instance ready to use.
2. You need at least one circuit to submit to the program. Our examples all have circuits in them, but if you want to submit your own circuit, you can use Qiskit to create one. To learn how to create circuits by using Qiskit, see the [Circuit basics tutorial](https://qiskit.org/documentation/tutorials/circuits/01_circuit_basics.html).







 Single experiment example 

from qiskit.circuit.random import random_circuit
from qiskit_ibm_runtime import QiskitRuntimeService, Sampler

service = QiskitRuntimeService()

 Run on a simulator
backend = service.get_backend("ibmq_qasm_simulator")
 Use the following line if you want to run on a system instead of a simulator:
 backend = service.least_busy(simulator=False)

circuit = random_circuit(2, 2, seed=1234)
circuit.measure_all()

sampler = Sampler(backend)
job = sampler.run(circuit)
result = job.result()

print(circuit)
print(f" > Quasiprobability distribution: {result.quasi_dists}")
Running Hyper-V in an active directory environment 

Use the following steps to run Hyper-V in an active directory environment



 Before you begin 

Before you begin running Hyper-V in an active directory environment, you need to make sure that the following ations are complete.



* A supported 64-bit Windows server that runs Hyper-V (Full or Core installation of the OS).
* A global group on the domain that is used to manage Hyper-V.
* Domain Admin access to enable changes on the Hyper-V server from the computer that you are working from.







 Configuring a Hyper-V server 

Use the following steps to configure a Hyper-V server.



1. Open a management connect to the Hyper-V server.
2. Add Hyper-V group to the Distributed COM Users group.
3. Add Hyper-V group to the CIMV2 and Virtualization namespaces.
4. Add Hyper-V group to the Authorization store for Hyper-V on the Hyper-V server.
5. Provide the Hyper-V group permissions to the Hyper-V Directory on the Hyper-V server.







 Setting up a remote management connection 

Use the following steps to set up a remote management connection.



1. Make sure you are logged in to a computer on the domain that has Domain Admin privileges.
2. Go to Control panel > Administrative Tools > Computer Management.
3. In the Action menu, select Connect to another computer.
4. Enter the server name or IP and click OK.







 Adding Distributed COM Users group to a Hyper-V server 

Use the following steps to add Distributed COM Users group to the Hyper-V server.



1. Go to System Tools > Local Users and Groups > Groups > Distributed COM Users > Add to Group.
2. Click Add and enter the group name for the Hyper-V group and click OK.







 Granting remote access to the server for CIMV2 and Virtualization namespaces 

You can update the permissions for Remote access to the server for Virtualization and CIMV2.



1. From the Computer Management window, select Service and Applications > WMI Control.
To remove monitoring configurations that you manually set up without using the Red Hat OpenShift on IBM Cloud observability plug-in, you must first make this configuration available to the plug-in by using the ibmcloud ob monitoring agent discover [command](https://cloud.ibm.com/docs/openshift?topic=openshift-observability_climonitoring_agent_discover).

When you delete the monitoring configuration, the components that are deleted depend on how you created the monitoring configuration. For monitoring configurations that were created with the ibmcloud ob monitoring config create command, the daemon set for the Monitoring agent, the ConfigMap, and secret are removed from your cluster, and metrics are no longer sent to your IBM Cloud Monitoring service instance. Monitoring configurations that you manually created and made visible to the plug-in by using the ibmcloud ob monitoring agent discover command, only the ConfigMap is removed. Your daemon set, secret, and the Monitoring agent are still deployed to your cluster and you must manually remove them. Because the ConfigMap is removed, metrics are no longer sent to your IBM Cloud Monitoring service instance. Independent of how you created the configuration, existing metrics are still available in IBM Cloud Monitoring until your selected retention period ends.

ibmcloud ob monitoring config delete --cluster CLUSTER --instance MONITORING_INSTANCE

Minimum required permissions:



* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Cloud Monitoring



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to delete an existing Monitoring configuration. To retrieve the cluster name or ID, run ibmcloud oc cluster ls. This value is required.

--instance MONITORING_INSTANCE
: The ID or name of the IBM Cloud Monitoring service instance that you used in your monitoring configuration. To retrieve the service instance name, run ibmcloud resource service-instances. This value is required.

Example command

ibmcloud ob monitoring config delete --cluster mycluster --instance mymonitoringinstance
To remove logging configurations that you manually set up without using the Red Hat OpenShift on IBM Cloud observability plug-in, you must first make this configuration available to the plug-in by using the ibmcloud ob logging agent discover[command](https://cloud.ibm.com/docs/openshift?topic=openshift-observability_clilogging_agent_discover).

When you delete the logging configuration, the components that are deleted depend on how you created the logging configuration. For logging configurations that were created with the ibmcloud ob logging config create command, the daemon set for the Log Analysis agent, the ConfigMap, and secret are removed from your cluster, and pod logs are no longer sent to your IBM Log Analysis service instance. Logging configurations that you manually created and made visible to the plug-in by using the ibmcloud ob logging agent discover command, only the ConfigMap is removed. Your daemon set, secret, and the Log Analysis agent are still deployed to your cluster and you must manually remove them. Because the ConfigMap is removed, pod logs are no longer sent to your IBM Log Analysis service instance. Independent of how you created the configuration, existing log data is still available in IBM Log Analysis until your selected retention period ends.

ibmcloud ob logging config delete --cluster CLUSTER --instance LOGGING_INSTANCE

Minimum required permissions:



* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Log Analysis



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to delete an existing Log Analysis configurations. To retrieve the cluster name or ID, run ibmcloud oc clusters. This value is required.

--instance LOGGING_INSTANCE
: The ID or name of the IBM Log Analysis service instance that you used in your logging configuration. To retrieve the service instance name, run ibmcloud resource service-instances. This value is required.

Example command

ibmcloud ob logging config delete --cluster mycluster --instance mylogginginstance
To remove logging configurations that you manually set up without using the IBM Cloud Kubernetes Service observability plug-in, you must first make this configuration available to the plug-in by using the ibmcloud ob logging agent discover[command](https://cloud.ibm.com/docs/containers?topic=containers-observability_clilogging_agent_discover).

When you delete the logging configuration, the components that are deleted depend on how you created the logging configuration. For logging configurations that were created with the ibmcloud ob logging config create command, the daemon set for the Log Analysis agent, the ConfigMap, and secret are removed from your cluster, and pod logs are no longer sent to your IBM Log Analysis service instance. Logging configurations that you manually created and made visible to the plug-in by using the ibmcloud ob logging agent discover command, only the ConfigMap is removed. Your daemon set, secret, and the Log Analysis agent are still deployed to your cluster and you must manually remove them. Because the ConfigMap is removed, pod logs are no longer sent to your IBM Log Analysis service instance. Independent of how you created the configuration, existing log data is still available in IBM Log Analysis until your selected retention period ends.

ibmcloud ob logging config delete --cluster CLUSTER --instance LOGGING_INSTANCE

Minimum required permissions:



* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Log Analysis



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to delete an existing Log Analysis configurations. To retrieve the cluster name or ID, run ibmcloud ks clusters. This value is required.

--instance LOGGING_INSTANCE
: The ID or name of the IBM Log Analysis service instance that you used in your logging configuration. To retrieve the service instance name, run ibmcloud resource service-instances. This value is required.

Example command

ibmcloud ob logging config delete --cluster mycluster --instance mylogginginstance
Distributing your workload across three zones ensures high availability for your app in case a zone becomes unavailable. You must have your worker nodes spread evenly across all three availability zones to meet the [IBM Cloud service level agreement (SLA)](https://cloud.ibm.com/docs/overview?topic=overview-slas) for HA configuration. This setup also makes your cluster more cost-efficient. Why is that, you ask? Here is an example.

Let's say you need a worker node with six cores to handle the workload for your app. To make your cluster more available, you have the following options:



* Duplicate your resources in another zone: This option leaves you with two worker nodes, each with six cores in each zone for a total of 12 cores.
* Distribute resources across three zones: With this option, you deploy two cores per zone, which leaves you with a total capacity of six cores. To handle your workload, two zones must be up at a time. If one zone is unavailable, the other zone can fully handle your workload. If two zones are unavailable, the two remaining cores are up to handle your parts of your workload, and you could temporarily add another worker node to that zone.







 How is my Red Hat OpenShift on IBM Cloud master set up? 

When you create a cluster in a multizone location, a highly available master is automatically deployed and three replicas are spread across the zones of the metro. For example, if the cluster is in dal10, dal12, or dal13 zones, the replicas of the master are spread across each zone in the Dallas multizone metro.





 Do I have to do anything so that the master can communicate with the workers across zones? 

If you created a VPC multizone cluster, the subnets in each zone are automatically set up with Access Control Lists (ACLs) that allow communication between the master and the worker nodes across zones.
1. Generate a license file in /etc/rackware by running the following command:

rwadm relicense
2. You need to purchase the license from RackWare by emailing the generated license file to [licensing@rackwareinc.com](mailto:licensing@rackwareinc.com) or [sales@rackwareinc.com](mailto:sales@rackwareinc.com).
3. After you receive a valid license, download the license file and place it in /etc/rackware. Restart the services to apply the license by running the following command:

rwadm restart
4. Verify the license by running the following command:

rw rmm show







 Step 3: (Optional) Transit Gateway for private connectivity 

The IBM Cloud Transit Gateway provides connectivity between VMware IBM Cloud classic and your VPC infrastructure.

When you connect the two entities, be aware that the VMware classic infrastructure is on the 10.0.0.0 network and thus the VPC network needs to reside on a different network. Otherwise, the network overlaps and there is a communication connectivity issue.



1. Order IBM Cloud Transit Gateway

a. Use local routing option
2. Add connections

a. Classic infrastructure

b. VPC



* Select region









 Step 4: Set up and provision VPC and virtual server instance 

The RMM solution handles only the OS, application, and data movement. It does not to set up a VPC target side; you need to handle this. You will first need to set up the VPC infrastructure. At a bare minimum, you need to set up a VPC, subnets, and the corresponding instances that you are planning to migrate. The new target virtual server instance profile (vCPU and vMemory) does not need to match the source. However, as for the storage, it needs to be the same or greater in size. This guide does not go through all of the details for setting up the VPC infrastructure.
source-address Network-A;
destination-address any;
application any;
}
then {
permit;
}
}
Show more





 Performance consideration 

In order to achieve the best IPSEC VPN performance, use AES-GCM as the encryption algorithm for both IKE and IPSEC proposals.

For example:

set security ike proposal IKE-PROP encryption-algorithm aes-128-gcm
set security ipsec proposal IPSEC-PROP encryption-algorithm aes-128-gcm

With AES-GCM as the encryption algorithm, you don't need to specify the authentication algorithm in the same proposal. AES-GCM provides both encryption and authentication.





 Additional VPN configurations 

To configure IPSec VPN, site to site, remote access VPN, and other features, refer to this [configuration guide](https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/security/security-vpn-ipsec.pdf) from Juniper.

For an example of how to configure a route-based site to site IPSec VPN, refer to this [configuration guide](https://www.juniper.net/documentation/en_US/junos/topics/example/ipsec-route-based-vpn-configuring.html) from Juniper.
If you assigned only service access roles to users, the users must be given the cluster master URL to open the Red Hat OpenShift web console from their browser at https://<master_URL>/console instead of the IBM Cloud console. Otherwise, [give the users the platform Viewer role](https://cloud.ibm.com/docs/openshift?topic=openshift-usersadd_users_cli_platform).





 Overview of RBAC 

In Kubernetes, role-based access control (RBAC) is a way of securing the resources inside your cluster. RBAC roles determine the Kubernetes actions that users can perform on those resources, such as Kubernetes pods, namespaces, or services. Example actions that are permitted by RBAC roles are creating objects such as pods or reading pod logs.

You can assign RBAC roles through the following methods.

By using IBM Cloud IAM
: You can use IAM to automatically create and manage RBAC in your cluster, by assigning [service access roles](https://cloud.ibm.com/docs/openshift?topic=openshift-access-overviewservice-roles-ov) to users. Every user who is assigned a service access role is automatically assigned a corresponding RBAC cluster role. This RBAC cluster role is applied either in a specific namespace or in all namespaces, depending on whether you scope the policy to a namespace. Change that you make to the user in IAM, such as updating or removing the service access policy, are automatically synchronized to the RBAC in your cluster. The synchronization of service roles to RBAC might take a couple minutes, depending on the number of users and namespaces in your cluster.

Managing your own RBAC
: See [Assigning RBAC permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-access-overviewrole-binding).





 Overview of classic infrastructure 

Classic infrastructure roles enable access to your classic IBM Cloud infrastructure resources.

Set up a user with Super User infrastructure role, and store this user's infrastructure credentials in an API key.
You must provision the virtual server instance with the same [network details](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-post-provisioning-cvadview-network-details) as the other service components that are attached to the resource location.





 Step 3. Establish network connectivity for Active Directory Topology 



 IBM Cloud 

If you chose IBM Cloud Active Directory topology and are using the Active Directory in IBM Cloud as your only domain controller, no further network configuration is required. The Cloud Connectors are joined to the Active Directory server domain and are configured to communicate with Citrix Cloud. You might have to create users with the necessary privileges. You can also create bulk users in Active Directory. For more information, see this step-by-step guide on how to [Create bulk users in Active Directory](https://activedirectorypro.com/create-bulk-users-active-directory/).





 Extended (Multisite) 



1. With an Extended (Multisite) setup, you must establish network connectivity between IBM Cloud and your on-premises location.

You can set up network connectivity by using any of the gateway appliances available in IBM Cloud. For more information, see the About section in the [Gateway Appliance IBM Cloud catalog page](https://cloud.ibm.com/gen1/infrastructure/provision/gateway).

You must set up another Gateway appliance on-premises too. Configure both the appliances and establish network connectivity between the two sites.

When you order a gateway appliance from IBM Cloud, the data center and backend VLAN must correspond to the same data center and VLAN where your other services are provisioned. See [View network details](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-post-provisioning-cvadview-network-details).
2. Install the domain controller in IBM Cloud

A Windows virtual server instance is provisioned in the same VLAN and network as your other servers. Complete the following steps to install the domain controller and join the secondary controller:



1.