SovLabs Support Portal will be moving soon!

SovLabs Support

Submit a Ticket My Tickets
Welcome
Login

How To - Configure multiple tenants on a single vRA - vRO utilizing SovLabs modules

Overview

You may be in a position where you have a single vRA/vRO deployment but have a need to have multiple tenants.  In this how to we will cover how to enable the SovLabs catalog items for additional tenants beyond the first one you have installed and licensed against.

NOTE:  This process does not require a second license key from SovLabs. Please see FAQ section at the bottom of this document for further information on licensing errors

Considerations

  • Have licensed the SovLabs modules against a vRA tenant already
  • Have installed the SovLabs modules against a vRA tenant already
  • Have configured subsequent Tenants in vRA
  • Have followed the  Pre Requisite guides for the second Tenant (see Additional Info at the bottom of this page)
    • Follow steps on configuring your vRA tenant Steps 1.0 → 1.5
    • Follow steps on configuring vRO hosts Steps 2.3 → 2.4


Procedure

This configuration is a two part update, the first time you run the configuration you are performing a full configuration and the second run you perform the update.  The first run will create the services for the subsequent tenant whilst the second run will publish the updates for the catalog items into the subsequent tenant.

First Run : Full configuration

  1. From within vRO, browse to SovLabs (1) → Configuration (2) → SovLabs Configuration (3)


  2. Right click the SovLabs configuration and select Start workflow


  3. Place a check to accept the term of the license agreement (1) and click Next (2)


  4. Select the new vRA tenant (1), Select the correct business group (2), Select Yes to create the vRA Catalog Service (3), Enter the security group for this tenant (4) and click on Next (5)


  5. Select No to upgrade SovLabs vRA content (1) and click next (2)


  6. Place a check in Yes to install or update SovLabs worflow subscriptions (1) and click Submit (2)


  7. Confirm that the SovLabs Configuration runs successfully on the subsequent tenant.  In this run you will see Create or Update SovLabs LifeCycle Stubs AND Create Service and Entitlement.


  8. If you are in a clustered environment, I would recommend waiting for configurations to sync prior to continuing to the next step.



Second Run : Upgrade configuration

  1. From within vRO, browse to SovLabs (1) → Configuration (2) → SovLabs Configuration (3)


  2. Right click the SovLabs configuration and select Start workflow


  3. Place a check to accept the term of the license agreement (1) and click Next (2)


  4. Select the new vRA tenant from the first run (1), Select the correct business group from the first run (2), Select No to create the vRA Catalog Service (3), Enter the security group for this tenant (4) and click on Next (5)


  5. Place a check in Upgrade Existing SovLabs vRA content (1), Place a check in Update F5 RESTipe (2) and click on Next (3)


  6. Place a check in Yes to install or update SovLabs worflow subscriptions (1) and click Submit (2)


  7. Confirm that the SovLabs Configuration runs successfully on the subsequent tenant. In this run, you should only see Create or Update SovLabs LifeCycle Stubs


  8. If you are in a clustered environment, I would recommend waiting for configurations to sync before continuing

    NOTE: Please check your vRA environment. It is recommended that you restart your environment after this process.

Confirm SovLabs catalog items are visible in subsequent tenant

  1. Log into the subsequent vRA tenant and click on Catalog (If not already there)


  2. Do a search for SovLabs (1). This will display all modules you are licensed for in this tenant (2)



Additional information

Getting Started with SovLabs : http://docs.sovlabs.com/latest/vRA/7.6/getting-started/
SovLabs Module Upgrade : http://docs.sovlabs.com/latest/vmware-vra7x-plugin/getting-started/sovlabs-plugin/upgrade/

F.A.Q

Q: When I try to log into my new vRA tenant it won't authenticate the local account I created.

A: In some instances we have seen issues when creating a new tenant and the local account you create for initial access has the same name and details as an existing or the vsphere.local tenant. 
For example:  In your vsphere.local tenant you have and account named admin_user (admin_user@vsphere.local).  
You go ahead and create a new tenant and you create a local account named admin_user (admin_user@vsphere.local) and grant it the appropriate rights to configure this new tenant.
When you go to log into your tenant.  It fails to authenticate.

This issue is very infrequent however thought we should document a work around just incase though it is not related to SovLabs. To work around this, you need to make the local account name unique across all tenants and authentication will subsequently work. 

Q: When I run the licensing catalog item in my new tenant, I receive an error stating "Error: license already installed.".

A: As part of the document you do not need to run the licensing module. If in your new/subsequent tenant you only see the licensing catalog item, you may have missed the second step which is to run the SovLabs Configuration in update mode.  This will then publish all the modules you are licensed for.


Q: How do I upgrade the SovLabs module if I am running multiple Tenant?

A:  The upgrade process is exactly the same as if this was a single tenant (Please see additional information to link on SovLabs module upgrade process).   Once you have performed the upgrade against your primary tenant, you will need to repeat step 3.1 - Configure the SovLabs plugin on each tenant you have configured for use with the SovLabs Module

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.