In this recipe, we explore the vRA-integrated Orchestrator. We will have a closer look at what is integrated and how it is working.
You need Java installed to start the Orchestrator Client and access the vRA shell (root access).
I have split this recipe into several small independent sections.
To start the Orchestrator Client, follow these steps:
[IP or FQDN of the vRA appliance]:8281
as Host name and [email protected]
as User name with the corresponding password and click on Login.The Orchestrator Control Center is by default switched off to conserve resources since it is only needed during configuration and to install plugins. To switch it on, you need to login to the vRA and execute the following command:
Service vco-configurator start
Also see the example workflows 13.01.1 Start vRA vRO Control Center
and 13.01.2 Stop vRA vRO Control Center
.
If we decide to use an external Orchestrator, we can give the vRA appliance some resources back by disabling the startup of the Orchestrator Services:
chkconfig vco-server off service vco-server stop chkconfig vco-configurator off service vco-configurator stop
This will stop and disable the services for Orchestrator and the Orchestrator Configurator.
The vRA appliance comes with an installed and configured vRO instance. The integrated instance is pretty well balanced and does everything you need. With vRA7.1, when you add vRA nodes to a cluster, the integrated Orchestrator will also be added as nodes.
The direction for vRA/vRO clusters is definitely towards using the embedded version.
Please also check the Configuring an external Orchestrator in vRA recipe in this chapter for more information on external Orchestrator installations.
The registered Orchestrator administrator group is vcoadmins
, which contains the following user: [email protected]
.
The database that Orchestrator uses is the one vRA uses.
Database |
|
User |
|
Port |
|
vRA 7.x and above dynamically generates and encrypts the vcac
user password upon installation. The following steps will show how to obtain that password, allowing you to connect things such as PGAdmin to the DB:
/etc/vcac/server.xml
file, look for password, for example:password="s2enc~3g5DjU8zn4/0akhnM0uSUheiZZyGagt0dEdjg="
vcac-config prop-util -d --p
"s2enc~3g5DjU8zn4/0akhnM0uSUheiZZyGagt0dEdjg="
psql -U vcac -p 5433 -h localhost -d vcac