You can simplify the deployment of individual components by defining installation variables or by creating a registry file on your vCloud Availability Installer Appliance.
About this task
Both ways to deploy and configure vCloud Availability for vCloud Director are displayed for your reference. The installation using variables is presented in the left column of the table in each step, containing standard installation and configuration commands. The installation with simple commands, using a vCloud Availability Installer Appliance registry file, is presented in the right column of the table in each step.
- Create protected password files on your vCloud Availability Installer Appliance.
OS credentials are stored in text files in ~/.ssh directory for all appliances. The files are only accessible to the system root user for security purposes. You provide the path to the respective password file during installation and configuration steps.Note:
The appliances-root-password is the root password that is set for the vCloud Availability for vCloud Director appliances that you create during installation procedures. The following example uses the same root password for all vCloud Availability for vCloud Director appliances. You can set different passwords for all appliances, by creating a dedicated password file in the ~/.ssh directory. Provide the path to the correct password file in the respective installation and configuration step.
Command Using Registry
# mkdir ~/.ssh # chmod 0700 ~/.ssh # echo 'appliances-root-password' > ~/.ssh/.root # echo 'vcd-password' > ~/.ssh/.vcd # echo 'sso-password' > ~/.ssh/.sso # echo 'management-vsphere-password' > ~/.ssh/.vsphere.mgmt # find ~/.ssh -type f -name '.*' -print0 | xargs -0 chmod 0600
# mkdir ~/.ssh # chmod 0700 ~/.ssh # echo 'appliances-root-password' > ~/.ssh/.root # find ~/.ssh -type f -name '.*' -print0 | xargs -0 chmod 0600
- Define installation variables.
In the current example, the deployment environment consists of one management vSphere and two resource vSphere sites.
The management vSphere details refer to the path of the environment managed by the service providers that is not available to tenant users. The resource vSphere details relate to the path of the environment that tenants use.
The resource vSphere sites are part of the same SSO domain to which the vCloud Director host is federated.
The management vSphere hosts the vSphere Replication Cloud Service and the vCloud Availability for vCloud Director Portal.
A resource vSphere hosts the vSphere Replication Manager and the vSphere Replication Server.
For test and development environments, if you use docker to manage your Cassandra and RabbitMQ hosts, the commands in the current example place the docker host in the management vSphere environment.
If necessary, you can host all the components in the management vSphere.
The VSPHERE_PLACEMENT_LOCATOR value contains the target data center name, the tag host, the name of the target cluster, and the IP address or the fully qualified domain name (FQDN) of the target ESXi host. The VSPHERE_PLACEMENT_LOCATOR value depends on the topology of your vSphere environment. Following are examples for valid VSPHERE_PLACEMENT_LOCATOR values.
If the target ESXi host is not part of a cluster, skip the cluster-name element, as shown in the following examples.
The VSPHERE_PLACEMENT_DATASTORE value is the datastore name as it is displayed in the vSphere Web Client.
For more information about the VSPHERE_PLACEMENT_LOCATOR and VSPHERE_PLACEMENT_DATASTORE values, see Specifying the Inventory Path for a Cluster, Host, or Resource Pool in the OVF Tool User's Guide.Important:
The Variables listed in the table are used as an example. Update values to match your environment.
Define Installation Variables
Create Registry File
# export MGMT_VSPHERE_ADDRESS=mgmt-vsphere-address # export MGMT_VSPHERE_USER=mgmt-vsphere-admin-user # export MGMT_VSPHERE_LOCATOR='mgmt-locator' # export MGMT_VSPHERE_DATASTORE='mgmt-datastore' # export MGMT_VSPHERE_NETWORK='mgmt-network' # export VSPHERE01_ADDRESS=vsphere-01-address # export VSPHERE01_PLACEMENT_LOCATOR=vsphere-01-locator # export VSPHERE01_PLACEMENT_DATASTORE=vsphere-01-datastore # export VSPHERE01_PLACEMENT_NETWORK=vsphere-01-network # export VSPHERE02_ADDRESS=vsphere-02-address # export VSPHERE02_PLACEMENT_LOCATOR=vsphere-02-locator # export VSPHERE02_PLACEMENT_DATASTORE=vsphere-02-datastore # export VSPHERE02_PLACEMENT_NETWORK=vsphere-02-network # export VCD_ADDRESS=vcd-01-address # export VCD_USER=root@system # export SSO_USERemail@example.com
Create a ~/.vcav/registry file to hold installation variables. Update the values to match your environment.
vsphere mgmt-vsphere-name address mgmt-vsphere-address api-port 443 api-user admin-user api-password admin-user-password placement-locator mgmt-locator placement-datastore mgmt-datastore placement-network mgmt-network vsphere vsphere-01-name address vsphere-01-address api-port 443 api-user vsphere-01-admin-user api-password vsphere-01-admin-password placement-locator vsphere-01-locator placement-datastore vsphere-01-datastore placement-network vsphere-01-network vsphere vsphere-02-name address vsphere-02-address api-port 443 api-user vsphere-02-admin-user api-password admin-user-password placement-locator vsphere-02-locator placement-datastore vsphere-02-datastore placement-network vsphere-02-network VCD vcd-01-name address vcd-01-address api-port 443 api-user root@System api-password vcd-root-password sso-user firstname.lastname@example.org sso-password sso-password
Update the file permissions
# chmod 0600 ~/.vcav/registry