5. Deploying the Client Tenant

You can deploy client tenants using a variant of the master template. This guide uses the following parameters as an example:

  • mode: client
  • key-name: heat-key
  • cidr: 192.168.200.0/24
  • router: 192.168.200.1
  • domain: abc.local
  • domain_netbios_name: abc
  • password: Clientpassw0rd
  • Stack name: client

Other options are as described in Master template parameters.

The templates used require a public SSH key. You can use a key previosly uploaded to the Virtuozzo Hybrid Infrastructure self-service panel or generate a new one, as done in this guide.

Note

In case of issues during the deployment, you can delete the stack with openstack --insecure stack delete provider and try again.

  1. Load client’s OpenStack credentials:

    # source client-openrc.sh
    
  2. Adjust parameters in Tenant-Deploy.yaml. Make sure to change mode to client and cidr to a new subnet, so you can route two private networks.

  3. Repeat steps 2-5 from Deploying the MSP Broker Tenant.

After the tenant is ready, you can assign floating IPs to the VMs to be able to log in to them via RDP.

Now you can log in to the ras-pa-1 VM and deploy the first Parallels RAS Publishing Agent in the client tenant. After this, you can deploy and configure the Parallels RAS tenant according to the Parallels RAS Administrator’s Guide.

Note

To make the DNS service more reliable, you can manually deploy the second AD controller and DNS server in the ras-pa-2 VM. Then you can add the IP Address of the ras-pa-2 VM to the list of DNS servers of your tenant network.