Cloud Template Sharing

[jinhoe]

How to config a shared cloud template that deploy a vm in a network based on user's assigned project?

Example:

• User 1 has access to Project A
• User 2 has access to Project B
• User 3 has access to Project A & B

When user deploy the template, I want:

• User 1 deploy to Project A network (without additional input)
• User 2 deploy to Project B network (without additional input)
• User 3 having an option to select Project A or B network

I know this can be done by creating 3 templates separately, but that will be hard to manage at scale. Any advice?

[mannharry]

Since you want to deploy to project specific , I don't see option to , however you can share same cloud template among other project .

Regards

Harry

[jinhoe]

@mannharry thanks for your reply. I am using a shared template.

What about user 3? Since user 3 was assigned to Project A & B. When using the shared template, which network will the VM be deployed to?

I can create a dropdown menu in cloud template for the user 3 to select network A or B, but this dropdown will also appear for user 1 & 2 since they share the same template. It does not make sense for user 1 & 2 to see the dropdown menu.

Is there a way I can configure to allow such scenario or the only way is the have separate cloud template? Which means user 3 will see 2 "deploy vm" template (for project A & B).

[gregd90]

Hi there,

This is a policy driven placement model question. You can achieve this by using constraint tags on your Cloud Template, and capability tags on your networks. There are two ways you could address this:

1. Setup. Tag your networks with a capability tags, based on the project, e.g. project:project01 project:project02. 

2. Have an action running on your Service Broker custom form, that dynamically generates a value for a network constraint tag, based on the requestors Project, .e.g. project01, project02. Translate the input parameter to a network constraint tag on your Cloud Template.

3. Alternatively, use a Project network constraint tag, which forces all requests through that Project to use one or more tags. So e.g. all requests from Project01 will be be constrained to project:project01 and only resolve to networks matching this constraint.

Hope that helps.

Regards,

Greg D

[bdamian · Accepted solution]

What you want can be done with a mix of:

• Cloud Template
• Custom Property
• vRealize Orchestrator Actions
• Custom Forms

But, is really worth it?

In this post (spanish) I show how to select networks based on a custom property in each project. Add an Action to select a default network and an option in the custom form to hide the drop down if only one network is present and you have it.

https://tecnologiaimasd.blogspot.com/2022/08/vra8-definir-redes-disponibles-por.html

[jinhoe]

@gregd90 

Thanks, I think dynamically form might be the way.

[jinhoe]

@bdamian Thanks, I think you have the exact solution that I need! The blog is good, I can understand after using google page translate. Can't wait to test it out!