If all they want is to look at reports, why not just set up an ability to have those reports created on a schedule and either be emailed to the customer or something else? Was there some other reason you needed to provide direct access to vROps?
thanks a lot daphnissov
the thin is they already know that tool and they want to have it in their hands but them the reports are not enough.....
so that means the multi tenant is just a lie from vmware or there are other options
I would take a look at the document below.
vROps is not "strictly" fully multi-tenancy - all tenants connect to the same IP (Although you can NAT to the UI) But there are a few things you can do to get very close to true multi-tenancy
thanks a lot Graham
I was in a meeting and vmware said yes it's multitenant and I was like mmm really anyway my boss bought it (I mean the idea) like a year ago and know I have to implement it
I found that document and I went through pretty fast but I was not sure that's why I asked here
As Graham says, it's really not "multi-tenant" in the sense that other products like vCD or vRA are. You can achieve somewhat similar results as far as RBAC and segregation to only controlled resources, but that depends on how you have your customer environments structured. I have designed and deployed this for a few MSPs and service providers and achieved this result, but those results vary depending on their environment layout. If you needed true multi-tenancy, the only solution is separate vROps instances.