This component is required for each cloud region (public cloud, private cloud, or datacenter).
Dedicated Gucamole Setup
This GUA config wizard step is not required if you have set up aserver – A self-signed Guacamole certificate is provided out-of-box for Appliance installations.
AMQP – Configure CCM/CCO Properties for Guacamole Server
Configure the following gua_config_wizard.sh procedure on both the AMQP PRIMARY server and the AMQP SECONDARY server.
Invoke the GUA wizard as a root user (see Virtual Appliance Process > Cloud-Specific Setup Details for a sample setup).
Configure the CCM and CCO (once installed) properties.
Write this down for future reference!
Write down the Field details in a printed version of thesection for later use.
Configure the properties for the CCM and CCO (once installed) VMs:
Wizard Menu Field Possible IP Addresses
CCM_IP or CCM_SA_IP or CCM_LB_IP
CCO_Info CCO Host (once installed) CCO_IP or CCO_LB_IP Security_Info Protocol
The default RDP protocol is TLS (supports Windows 2008 R2, 2012 R2 and 2016).
If you prefer to use older versions of Windows that only support RDP SSL, change the default to RDP from the default TLS.
Config_Certs Certs Zip Path Provide the path for the certs.zip file. The default path is /tmp/certs.zip.
Verify your changes and Exit the GUA configuration wizard.
Select Yes, to restart the AMQP server and corresponding CloudCenter services.
If you are installing the AMQP instance for the first time, then you may need to wait for a few minutes to ensure that all users are listed. You can verify that all users are listed by running the following commands:
Reboot AMQP VM
If you change the AMQP server's host name, the local AMQP database is renamed and you must reboot the AMQP VM.
To reboot the AMQP VM, run the following commands as root:
- If you reboot the VM, be aware of the following details:
You may end up with a new host name and database name after the reboot.
Some clouds set the host name automatically for each new instance or reboot – RabbitMQ uses a preset host name to set the database name.
If a database user exists and a login is not associated, this user may not be able to log into the AMQP server.
Ensure that the required users (cliqr and cliqr_worker) are setup in your database. If you have additional users in your database, they will also be displayed when you run the rabbitmqctl command.
If you do not see these users in your database, run the following commands as root (to recreate the users in the AMQP configuration):
You have successfully configured the AMQP instance! Proceed to thesection.
- No labels