Noobie question... My company has a test instance of VRA up and running using a single default tenant. We're looking at hosting multiple zones with differing security and access requirements which may require creating additional tenants. I'm trying to find the answer to whether blueprints and entitlements can be shared from the default tenant to other tenants. I think the answer is no in VRA 6.x. Does that hold true in VRA 7.x? So far, Google is letting me down. Help!
Looking for comments and relevant links... Thanks in advance.
-G
Quick list of tenanted and non-tentanted entities in vRA 6.2 (will need to update this list for 7.x):
List of all nontenanted entities:
1. Endpoints
2. Computer resources
3. Reservations
4. Managed machines
5. Networking
6. Machine prefixes
7. Build Profiles
8. Data dictionary
List all tenanted entities:
1. Blueprints
2. Business groups
3. Catalog
4. Approvals
5. Branding
6. Tenants Identity Stores
7. Advanced Service Designer
8. Entitlements
So, CloudClient: vRealize Automation 7.2 Information Center
Edit: Also see: vRealize Automation 7.2 Information Center
"Blueprints can be specific to a business group or shared among groups in a tenant, depending on the entitlements that are configured for the published blueprint"
You can use the cloud client to export blueprints from one tenant and immport into another.
vRealize CloudClient 4.1 - VMware {code}
Or: DevOps for IT Managemenent Pack (aka Houdini)
Quick list of tenanted and non-tentanted entities in vRA 6.2 (will need to update this list for 7.x):
List of all nontenanted entities:
1. Endpoints
2. Computer resources
3. Reservations
4. Managed machines
5. Networking
6. Machine prefixes
7. Build Profiles
8. Data dictionary
List all tenanted entities:
1. Blueprints
2. Business groups
3. Catalog
4. Approvals
5. Branding
6. Tenants Identity Stores
7. Advanced Service Designer
8. Entitlements
So, CloudClient: vRealize Automation 7.2 Information Center
Edit: Also see: vRealize Automation 7.2 Information Center
"Blueprints can be specific to a business group or shared among groups in a tenant, depending on the entitlements that are configured for the published blueprint"
Thanks. This is good stuff.