Multitenant Use of vRealize Operations as a Service : Designing for vRealize Operations as a Service : 4.1 vRealize Operations Manager Deployment Models : 4.1.2 Dedicated Environment with Tenant Access
   
4.1.2 Dedicated Environment with Tenant Access
This scenario is unrelated to the vRealize Operations Manager multitenant use case that this document is focused on. This scenario is included for comparison reasons.
In this scenario, the service provider operates a vRealize Operations Manager instance per dedicated customer. This is usually done when the customer operates its own cluster and vCenter Server within the service provider environment. Access to this environment is primarily focused on the tenant, but might be open for the service provider as well. An extended scenario might be that the service provider also collects data from the customer operated vCenter Server. This approach is commonly used in managed service environments or dedicated public cloud offerings where the customer rents a dedicated hardware stack.
The advantages are as follows:
Easy to deploy and manage
Sizing is easy because it can be done per tenant/customer
Object policies can be customized to be tenant specific
Disadvantages include the following:
Difficult to get a “big picture” when each customer operates on its own
Currently no data federation available for vRealize Operations
Service provider must monitor a high number of instances
Maintenance (upgrades and so on) requires more resources
Figure 5. Dedicated Environment with Tenant Access