Hey all,
this leads back to a discussion I posted couple of months back, but probably did not explain it too well. Well now I have confirmation from VMware that this is actually true.
in Version 6.2 if you create a Blueprint, you had the option to share it (there was a checkbox for it).
In 7.0 this checkbox does not exist anymore and therefore everything is shared within a tenant with no way to 'unshare' it.
typically in 6.2 VRA you would use single tenant for a deployment in a single company. But for 7.0 there is a huge security concern as everything is shared. Therefore I have to create pretty much a tenant per department ... which is cumbersome for users as they all have a different login.
Any BG manager can assign him/herself or anyone in the BG the permission to deploy _any_ Blueprint within this tenant
single machine, multimachine, XaaS, software -- even actions. Finance BG manager can deploy InfoSec machines and Recepotion BG manager can deploy Finance Blueprints ...
Not only that, but if you have 20departments (BGs) and 20 Blueprints each. Each BG manager will have to maintain a service catalog of 400 blueprints. This seems crazy.
The BG managers will be flooded with information/blueprints and actions and services. There is no option to even hide a service from other Business groups. Most BGs only need their own stuff (or only 3-4 shared blueprints). It's very hard to find them in that mess?!
Am I the only one complaining about it? can we restore 6.2 functionality (i need to mark what is shared across the whole tenant?)
Maybe even allow a service split. so a tenant or other architect can specify what services are accessible within the BGs etc. No idea ...
Like I said I'll have to go down the route of creating multiple tenants between different BGs/departments :-(
Kalli
Note: there is no VMware case-ID (AFAIK). however if a VMware employee wants more info I can share the names of VMware engineers that confirmed it.