vRealize Automation-Tenant Configuration


vRealize Automation can be used to create private cloud or hybrid cloud that can be shared by a number of groups within a company.

vRealize Automation has a concept called Tenants that can be used to provide isolation between independent groups in shared cloud environment, where multiple companies, divisions or independent groups are using a common infrastructure fabric, Tenants are useful for isolating the users, resources and services from one tenant from those of other tenants.

A tenant can be compared to an organizational unit. For private clouds a tenant can be a business unit within enterprise. In hybrid clouds it can be a company that subscribes to cloud services from a service provider.

In Multi-Tenant environment each tenant has unique configuration policies that are specific to that tenant.  Let’s look as some of the attributes that define a tenant.

  • Each tenant has one or more identity stores that are used to authenticate users.  These identity stores can be either Active Directory or any Open LDAP directory service.
  • The management portal can have its own URL.  and the portal can have unique branding specific to that tenant.
  • Tenants can also be divided up into smaller organizations called Business Groups.

vRealize-Automation-Default-Tenant

The default tenant which is created during the vRA deployment is vsphere.local. We can add additional tenants using the system administrator account.

The system administrator can manage system-wide configurations in the default tenant. These configurations include global system defaults for branding and notifications, and monitoring system logs.

Before jumping into tenant configuration lets have a look onto default roles that are available in vRA. vRA offers the below mentioned 3 roles:

System Administrator: This is for performing initial configuration of vRA such as configuring SSO, creating new tenant, setting up AD authentication for default tenant etc.

Infrastructure Administrator: The Infrastructure administrator is responsible for managing endpoints and endpoint credentials, and creating fabric groups.

Tenant Administrator: create custom groups within their own tenant and add both users and groups defined in the identity store to custom groups.

If you want to read more about Roles and permissions I would recommend watching this video

Configure the Identity Stores for the Default Tenant

Each tenant requires at least one identity store. Identity stores can be OpenLDAP or Active Directory. Active Directory in native mode is supported for the default tenant only.

If you have missed earlier posts of this series then I would recommend reading them first before going ahead. You can access the earlier posts from below links:

1: Introduction to vCAC(vRA)

2: Installing and Configuring vRA Identity Appliance

3: Installing and Configuring vRA Appliance

4: Installing and configuring IaaS Components

In this post we will learn how to configure the default tenant.

To start configuring the default tenant open your browser and type URL https://vRA-FQDN/vcac/ and login with user administrator@vsphere.local

After successful login you will be able to see the default tenant (vsphere.local) under Tenants. To add new tenants to your infrastructure you can click on + button.

In this post I am not creating any new tenant and will be only configuring the default tenant. Click on tenant vsphere.local to edit the settings.

ic-1

Go to Identity Stores tab and click on + button

ic-2

1: Enter a name in the Name text box.

2: Select OpenLDAP or Active Directory from the Type drop-down menu. I am using AD in my lab.

3: Enter the URL for the identity store in the URL text box in the format:

ldap://ldap.mycompany.com:389

4: Enter the domain for the identity store in the Domain text box.

5: (Optional) Enter the domain alias in the Domain Alias text box.The alias allows users to log in by using userid@domain-alias rather than userid@identity-store-domain as a user name.

6: Enter the Distinguished Name for the login user in the Login User DN text box.Use the display format of the user name, which can include spaces and is not required to be identical to the user ID.
For example, cn=Demo Admin,ou=demo,dc=dev,dc=mycompany,dc=com.

7: Enter the password for the identity store login user in the Password text box.

8: Enter the group search base Distinguished Name in the Group Search Base DN text box.
For example, ou=demo,dc=dev,dc=mycompany,dc=com.

9: (Optional) Enter the user search base Distinguished Name in the User Search Base DN text box.
For example, ou=demo,dc=dev,dc=mycompany,dc=com.

10: Click Test Connection.

11: Click Add.

ic-3

Click on Administrators tab to add tenant admin and infrastructure admin. Type the name in the search box and it will populate with valid choices.

When complete click Update.

ic-4

ic-5

To test the assigned role , login to your vRA portal using infrastructure admin and tenant admin credentials.

I created vrainf-adm username in my AD for Infrastructure Admin role and vratenant-adm for Tenant Admin role

ic-6

My vrainf-adm is able to login to vRA portal successfully.

ic-7

Now I will test my tenant admin credential.

ic-8

So both my infra-admin and tenant-admin can login to vRA portal.

We are done with configuring default tenant here.

In Next post of this series we will look into:

Creating and Configuring vSphere Endpoints

Creating and Configuring Fabric Groups

Creating Business Groups and Reservations

Creating and Publishing Blueprints

Creating a Service

Creating Entitlements

Deploying a new VM from Self-Service Portal

Share this post on social media if this post is informational to you. Be Sociable 🙂

About Alex Hunt

Hi All I am Manish Kumar Jha aka Alex Hunt. I am currently working in VMware Software India Pvt Ltd as Operations System Engineer (vCloud Air Operations). I have around 5 Years of IT experience and have exposure on VMware vSphere, vCloud Director, RHEL and modern data center technologies like Cisco UCS and Cisco Nexus 1000v and NSX. If you find any post informational to you please press like and share it across social media and leave your comments if you want to discuss further on any post. Disclaimer: All the information on this website is published in good faith and for general information purpose only. I don’t make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this blog is strictly at your own risk. The Views and opinions published on this blog are my own and not the opinions of my employer or any of the vendors of the product discussed.
This entry was posted in Vmware, vRealize Automation and tagged . Bookmark the permalink.

10 Responses to vRealize Automation-Tenant Configuration

  1. Pingback: vRealize Automation- Deploying Virtual Machines from self-Service Portal | Go Virtual.

  2. Pingback: vRealize Automation- Creating Entitlements | Go Virtual.

  3. Pingback: vRealize Automation- Creating a Service | Go Virtual.

  4. Pingback: vRealize Automation-Create and Publish Blueprints | Go Virtual.

  5. Pingback: vRealize Automation-Create Business Group and Reservation | Go Virtual.

  6. Pingback: vRealize Automation-Creating and Configuring Fabric Groups | Go Virtual.

  7. Pingback: vRealize Automation-Configuring vSphere Endpoint | Go Virtual.

  8. Pingback: vRealize Automation- Installing and Configuring IaaS Components | Go Virtual.

  9. Pingback: vRealize Automation- Deploying and Configuring vRealize Automation Appliance | Go Virtual.

  10. Pingback: vRealize Automation- Deploying and Configuring Identity Appliance | Go Virtual.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s