vania-janet/multiturn-rag-retrieval-data huggingface dataset:
XenServer pooling 

XenServer pooling can be thought of as up to 16 servers that work as a cluster. This cluster not only allows for shared resources but allows for live migration of virtual machines that use XenMotion. One server acts as the "controller node", while the rest of them are workers. Opening any of the servers in the pool through XenCenter opens the management information for the entire pool. When a node joins the pool, its management password is changed to match the management password of the controller node. When you remove a node from the pool, the password is stays the same as the management password of the controller node.

All systems in the node must be from the same processor family, as in Intel or AMD. Ideally, hardware must be identical for pooling to be successful. Compatibility issues aren't entirely true with heterogeneous CPU pooling. You need to perform compatibility tests for yourself to see whether your hardware is compatible. For more information, see [Understanding heterogeneous CPU pooling ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://support.citrix.com/article/CTX127059).

You have two methods for creating a XenServer pool. One is through the XenCenter console by using the "New Pool" option. Follow the simple step-by-step on-screen instructions to create and add systems to the pool. The other method is by using the command line. On the new worker node, the following command can be executed:

xe pool-join controller-address= controller-username= controller-password=

Note: The management IP address is the 10.x.x.x IP address of the server if you used the default installation.

When you work with bonded networks, a newly joined worker can have its interfaces that are attached to the incorrect bonded networks. To correct this issue, destroy the bonds on the worker from the command line and re-create the bonds with the proper PIFs and networks.

You have two methods of ejecting a worker node from the pool.
Specify the HCX network connection by selecting one of the following options. If any of the management or service mesh target clusters are deployed with private network only, the only networking option that you can choose is private.



* Public network - HCX creates an encrypted connection between sites over the public network. License registration and metering are completed over the public network.
* Private network - HCX creates an encrypted connection between sites over the private network. License registration and metering are completed over a private network through HTTP proxy.



3. If private network connection is selected, proxy information is displayed. Otherwise, a proxy option is not available. Complete the following fields:



* Proxy IP address - The IPv4 address of the proxy server.
* Proxy port number - The proxy server port. The port number is typically 8080 or 3128.
* Proxy user name (Optional) - The username if proxy authentication is required.
* Proxy password (Optional) - The password if proxy authentication is required.
* Reenter proxy password (Optional) - Reenter the password for proxy authentication validation.



4. Specify the Public endpoint certificate type. If you select CA Certificate, configure the following settings:



* Certificate contents - Enter the contents of the CA certificate.
* Private key - Enter the private key of the CA certificate.
* Password (Optional) - Enter the password for the private key, if it is encrypted.
* Reenter password (Optional) - Enter the password for the private key again.
* Hostname (Optional) - The hostname to be mapped to the common name (CN) of the CA certificate. HCX requires that the format of the CA certificate must be accepted by NSX Edge. For more information about NSX Edge certificate formats, see [Importing SSL Certificates](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.3/com.vmware.nsx.admin.doc/GUID-19D3A4FD-DF17-43A3-9343-25EE28273BC6.html).
To find the path to the messageHubFeed trigger, run ibmcloud fn package list | grep <binding>, where <binding> is the name of your package binding.





 Creating a trigger for an Event Streams package outside IBM Cloud 

If you want to set up your Event Streams outside of IBM Cloud, you must manually create a package binding for your Event Streams service. You need the Event Streams service credentials and connection information.



1. Create a package binding that is configured for your Event Streams service.

ibmcloud fn package bind /whisk.system/messaging myMessageHub -p kafka_brokers_sasl "
["broker-1-9eyy8dkv3rrj0wdn.kafka.svc01.us-south.eventstreams.cloud.ibm.com:9093", "broker-1-9eyy8dkv3rrj0wdn.kafka.svc02.us-south.eventstreams.cloud.ibm.com:9093", "broker-1-9eyy8dkv3rrj0wdn.kafka.svc03.us-south.eventstreams.cloud.ibm.com:9093"]" -p user <your Event Streams user> -p password <your Event Streams password> -p kafka_admin_url https://9eyy8dkv3rrj0wdn.svc01.us-south.eventstreams.cloud.ibm.com
2. Now you can create a trigger by using your new package that is fired when new messages are posted to your Event Streams topic.

ibmcloud fn trigger create MyMessageHubTrigger -f myMessageHub/messageHubFeed -p topic mytopic -p isJSONData true







 Listening for messages 

After a trigger is created, the system monitors the specified topic in your messaging service. When new messages are posted, the trigger is fired.

The payload of that trigger contains a messages field, which is an array of messages that are posted from the last time the trigger is fired. Each message object in the array contains the following fields:
* <host> is the cluster_kube_apiserver_host, for example https://api.green.coc-ibm.com:6443.
* <port> is the cluster_kube_apiserver_port.
* To find the <host> and <port> variables, run this command: kubectl get configmap -n kube-public -o yaml.
* <openshift_user> is the OpenShift admin user.
* <openshift-token> is the token that you obtain by running this command oc whoami -t or login to the OpenShift console and click the user's Copy Login Command.
* <admin-pass> is the password that you want to set for Ansible Tower admin user.
* <my-secret> is the secret that you want to set. It can be a base64 encoded string.
* <pg_username> is the username for postgresql.
* <pg_password> is the password for postgresql.
* <rabbitmq_pass> is the password for Rabbit MQ.
* <rabbiterlangapwd> is the Rabbit MQ erlang cookie.



11. Log in to Ansible Tower and import the license from the temporary-tower-license.txt downloaded in Before you begin section. The first time you log in to Ansible Tower, the license screen is automatically displayed:

http://<ansible-tower-host>

Run this command to locate the value:

oc get route -n ansible-tower

{: codeblock} The default admin-username is admin and password is the password you set for the admin_password parameter during installation, in the setup_openshift.sh command.







 Integrate Ansible Tower with IBM Cloud Pak for Multicloud Management 

Enable navigation to Red Hat Ansible Tower within the IBM Cloud Pak console.

Complete the following steps on a Linux system. These steps enable navigation to Ansible from the IBM Cloud Pak console:



1. Obtain the menu customization script, automation-navigation-updates.sh. See Before you begin.
It's a good idea to use an [API key](https://cloud.ibm.com/apidocs/cloudantintroduction) for continuous replications. The advantage is that if your primary account details change, for example after a password reset, your replications can continue unchanged.

API keys aren't tied to a single account. This means that a single API key can be created, then granted suitable database permissions for both accounts.

For example, the following command requests an API key for the account myaccount-dc1:

curl -XPOST "https://myaccount-dc1.cloudant.com/_api/v2/api_keys" -u myaccount-dc1

A successful response is similar to the following abbreviated example:

{
"password": "YPN...Tfi",
"ok": true,
"key": "ble...igl"
}

Take careful note of the password. It isn't possible to retrieve the password later.





 Step 3. Grant access permission 

Give the API Key [permission](https://cloud.ibm.com/apidocs/cloudantgetsecurity) to read and to write on both databases.

If you also need to replicate indexes, assign admin permissions.

Use the IBM Cloudant Dashboard, or see the [authorization](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountauthorization) information for details of how to grant permissions programmatically.





 Step 4. Set up replications 

Replications in IBM Cloudant are always uni-directional: from one database to another database. To replicate both ways between two databases, two replications are required, one for each direction.
You can notify a user when their password is updated. The notification can be helpful if they did not request that their password be changed. They can take the proper steps to resecure their account.



1. Go to the Cloud Directory > Email templates > Password change tab of the service dashboard.
2. Set Password changed email to Enabled.
3. Customize the content of your message. You can add parameters and insert images by using the UI. To change the [language](https://cloud.ibm.com/docs/appid?topic=appid-cd-typescd-languages) of the message, you can use [the APIs](https://us-south.appid.cloud.ibm.com/swagger-ui//Management%20API%20-%20Config/mgmt.updateLocalization) to set the language. However, you are responsible for the content and conversion of the message. Check out the following table to see the different parameters that you can use in your message. If a user does not supply the information that is pulled by the parameter, it appears blank.



Table 4. Parameters that you can use in messages that are related to changing a password

 Parameter Description 

 %{passwordChangeInfo.time} Displays the time at which a new password went into effect. 
 %{passwordChangeInfo.ipAddress} Displays the IP address from which the password change was requested. 



You can also use the message parameters that are listed in the [Welcome message](https://cloud.ibm.com/docs/appid?topic=appid-cd-typescd-messages-welcome) section.
4. Click Save.









 Supported languages 

You can use [the language management APIs](https://us-south.appid.cloud.ibm.com/swagger-ui//Management%20API%20-%20Config/mgmt.updateLocalization) to set the language in which your user communication can be written. However, only English is available out of the box. You are responsible for the conversion of the messages.
Connecting with rabbitmqadmin 

The rabbitmqadmin connection information is in the "cli" section of your [connection strings](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-connection-strings). The table contains a breakdown for reference.



Table 1. rabbitmqadmin/cli connection information

 Field Name Index Description 

 Bin The recommended binary to create a connection; in this case it is rabbitmqadmin. 
 Composed A formatted command to establish a connection to your deployment. The command combines the Bin executable, Environment variable settings, and uses Arguments 
 Environment A list of keys or values you set as environment variables. 
 Arguments 0... The information that is passed as arguments to the command shown in the Bin field. 
 Certificate Base64 A self-signed certificate that is used to confirm that an application is connecting to the appropriate server. It is base64 encoded. 
 Certificate Name The allocated name for the self-signed certificate. 
 Type The type of package that uses this connection information; in this case cli. 





* 0... indicates that there might be one or more of these entries in an array.



The example command lists all the exchanges in your RabbitMQ.

rabbitmqadmin --username=admin --password=$PASSWORD --ssl --ssl-ca-cert-file=0b22f14b-7ba2-11e8-b8e9-568642342d40 --host=1a619c43-6415-4abb-8df0-0c7b1b3a3001.8f7bfd8f3faa4218aec56e069eb46187.databases.appdomain.cloud --port=31797 list exchanges



* rabbitmqadmin - The command itself.
* --username and --password - Authentication for the user that you are using to connect.
* --ssl - ensures that the connection is TLS/SSL secured.
* UI
* CLI
* API







 Setting the Admin Password 



 Setting the Admin Password in the UI 

The IBM Cloud® Databases for Redis service is provisioned with authentication enabled, and comes with an admin user.

If you are using Redis 5.x and below, the admin user is the only user for your deployment. Redis didn't have support for multiple users until version 6.x.

You have to set the admin password before you can use it to connect. To set the password through the IBM Cloud dashboard, select Manage from the service dashboard to open the management panel for your service. Open the Settings tab, and use the Change Database Admin Password panel to set a new admin password.

![The Change Database Admin Password Panel in Settings](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/images/settings-admin-password.png){: caption="Figure 1. The Change Database Admin Password Panel in Settings" caption-side="bottom"}





 Setting the admin password with the CLI 

Use the cdb user-password command from the IBM Cloud CLI cloud databases plugin to set the admin password with the command line.

For example, to set the admin password for a deployment named "example-deployment", use the following command.

ibmcloud cdb user-password example-deployment admin <newpassword>





 Setting the admin password via the API 

The Foundation Endpoint that is shown on the Overview panel of your service provides the base URL to access this deployment through the API. Use it with the /deployments/{id}/users/{username} endpoint to set the admin password.

curl -X PATCH 'https://api.
It is expected - proceed by sending the form.







 Adding a vSphere backup job 



1. On the navigation, click Computers. The computers page shows the registered computers and environments.
2. Click Jobs.
3. In the Select job Task menu, click Create New VMware® vCenter Job.
4. Specify the following information.



* In the Name field, type a name for the backup job.
* In the Description field, optionally type a description for the backup job.
* In the Destination list, select the vault where you want to save the backup data.
* In the Password and Confirm Password fields, type an encryption password. You can also type a password hint in the Password Hint field.



A vault appears in the list only if it is assigned to the user, or if the user added it to the computer’s Vault Settings. For new backup jobs, the encryption method is AES 256 bit. Existing jobs can have other encryption methods.
5. In the Include in Backup field, take one or more of the following steps until the Backup Set field shows the VMs that you want to include in the backup job.



* To add specific VMs to the backup job, select each VM, and then click Include.
* To exclude specific VMs from the backup job, select each VM, and then click Exclude.
* To add VMs to the backup job by name, check the virtual machines box, and then click Include.
* To remove an inclusion or exclusion record from the Backup Set box, click Delete next to the record.



6. Click Apply Now to consolidate and simplify records in the Backup Set box, if changes need to be applied.
7. Click Create Job.







 Setting up a schedule 

After the backup job is created, you can add one or more schedules for running the job automatically.



1. When you click Create Job, the Schedule window appears and gives you an option to create a custom schedule for the backup job.

By default Daily retention is selected for the job. Retention and Job schedule can be changed in this window, and multiple Retention schemes can also be assigned to the backup job.
2.
Other algorithms can be found [here](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q120800_.html)
* <SUBJECT_DN> - this is the 'Subject DN' in the file default_cert.txt, created at the last step of 'Select a certificate'
* Note. The single quotes around the Subject DN are required







4. Exit runmqsc, by typing:



* END





![Image showing the commands entered to command line to set policy](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_ams_set_policy.png)





 Test the queue now that queue manager AMS is enabled 



1. Inside the app terminal
2. Run amqsputc to put a message on the default queue



* amqsputc DEV.QUEUE.1



3. The terminal will prompt you for a Password



* This is your <APP_API_KEY> = 'apiKey' in the file apiKey.json



4. Terminal will now be waiting for input. Enter a message



* Hit Enter key twice to exit from amqsputc



5. Run amqsgetc against the alias queue to get the messages from the default queue



* amqsgetc DEV.ALIAS.QUEUE.1
* DEV.ALIAS.QUEUE.1 is our name for the alias queue



6. The terminal will prompt you for a Password



* This is your <APP_API_KEY> = 'apiKey' in the file apiKey.json



7. Terminal will now output the encrypted messages from the default queue



!
vmware.directorsite.create An event is generated when a VMware Cloud Director site is created. 
 vmware.directorsite.delete An event is generated when a VMware Cloud Director site is deleted. 
 vmware.directorsite-pvdc.create An event is generated when a VMware Cloud Director site provider virtual data center (PVDC) is created. 
 vmware.directorsite-pvdc.delete An event is generated when a VMware Cloud Director site PVDC is deleted. 
 vmware.directorsite-cluster.create An event is generated when a VMware Cloud Director site cluster is created. 
 vmware.directorsite-cluster.delete An event is generated when a VMware Cloud Director site cluster is deleted. 
 vmware.directorsite-host.add An event is generated when a host is added to a VMware Cloud Director site. 
 vmware.directorsite-host.remove An event is generated when a host is removed from a VMware Cloud Director site. 
 vmware.directorsite-nfs-storage.add An event is generated when NFS storage is added to a VMware Cloud Director site. 
 vmware.directorsite-nfs-storage.remove An event is generated when NFS storage is removed from a VMware Cloud Director site. 
 vmware.directorsite.password-reset An event is generated when the user password for a VMware Cloud Director site is reset. 
 vmware.directorsite-iam.config An event is generated when the OIDC (OpenID Connect) for a VMware Cloud Director site is configured. 
 vmware.directorsite-iam.read An event is generated when the OIDC for a VMware Cloud Director site is checked. Monitoring is not enabled yet. 







 Viewing events 

VMware as a Service events are global events. For more information, see [Monitoring global and location-based events](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-monitor_eventsmon_def_event_type).

IBM Cloud Activity Tracker can have only one instance per location.
Initialize IBM Hardware Security Module (HSM) 

Most configurations of the HSM for your Citrix Netscaler VPX require initialization of the HSM device. Without this, only certain show commands can be executed.

To initialize your device, follow these steps:



1.  Connect using SSH into the IBM© Hardware Security Module device with the credentials listed in the Control Portal under Devices > Device List > Expand HSM name.

Alternatively, you can use public key authentication. For more information review the [Appliance Administration Guide (page 38)](https://public.dhe.ibm.com/cloud/bluemix/network/vpx/appliance_administration_guide.pdf).

SSH access is generally enabled and allowed by default. If you have issues connecting with SSH, check your infrastructure routing and security.
2.  Execute the hsm init command:

[jpmongehsm2] lunash:>hsm init -l jpmonge

Please enter a password for the HSM Administrator:
> 

Please re-enter password to confirm:
> 

Please enter a cloning domain to use for initializing this HSM:
> 

Please re-enter cloning domain to confirm:
> 

CAUTION:  Are you sure you wish to initialize this HSM?

Type 'proceed' to initialize the HSM, or 'quit'
to quit now.
> proceed
'hsm init' successful.

Command Result : 0 (Success)
Show more

Where the syntax used is: hsm init -l <hsmlabel>



The -l parameter or label is a parameter used to assign an identifier to the HSM, and can be any meaningful text or description related to the business, administrator, or the role it fulfills. The HSM administrator password will be the designated password for the HSM Security Officer (SO), and is essentially a profile required to create and configure crypto objects, as well as make changes to the HSM environment.

Lastly, the cloning domain is a shared identifier that allows objects to be formed among a group of HSMs. This is typically used for backup and/or HA.

Refer to the [LunaSH Command Reference Guide](https://public.dhe.ibm.com/cloud/bluemix/network/vpx/lunash_command_reference_guide.pdf) for all available commands supported in the HSM CLI.
3000406 - Check whether Virtual Private Cloud (VPC) has no rules in the default security group
3000407 - Check whether Virtual Private Cloud (VPC) is configured with at least TLS v1.2 for all inbound traffic through a load balancer
3000408 - Check whether Flow Logs for VPC are enabled
3000410 - Check whether Virtual Private Cloud (VPC) security groups have no inbound ports open to the internet (0.0.0.0/0)
3000411 - Check whether Virtual Private Cloud (VPC) security groups have no outbound ports open to the internet (0.0.0.0/0)
3000412 - Check whether all virtual server instances have at least one Virtual Private Cloud (VPC) security group attached
3000413 - Check whether all network interfaces of a virtual server instance have at least one Virtual Private Cloud (VPC) security group attached
3000419 - Check whether VPN for VPC has Internet Key Exchange (IKE) policy encryption that is not set to ""triple_des""
3000420 - Check whether VPN for VPC has Internet Key Exchange (IKE) policy authentication that is set to minimum ""sha256""
3000421 - Check whether VPN for VPC has a Diffie-Hellman group set to at least group 
3000422 - Check whether VPN for VPC has IPsec policy encryption that is not set to ""triple_des""
3000423 - Check whether VPN for VPC has IPsec policy authentication that is set to minimum ""sha256""
3000424 - Check whether VPN for VPC has an IPsec policy that does not have Perfect Forward Secrecy (PFS) disabled
3000425 - Check whether VPN for VPC authentication is configured with a strong pre-shared key with at least 24 alphanumeric characters
3000426 - Check whether VPN for VPC has a Dead Peer Detection policy that is set to ""restart""
3000427 - Check whether Application Load Balancer for VPC has public access disabled
3000428 - Check whether Application Load Balancer for VPC is configured with multiple members in the pool