Skip to main content

Hi everyone, 

In our environment, we want everyone (not just members of a specific project) to be able to launch a given blueprint when needed. Right now, blueprints appear to require being tied to a project, which limits visibility and use. Is there a way to make a blueprint globally accessible to all users/groups without restricting it to one project? Or assign the blueprint to multiple projects?

Also, we’d like to enforce category assignment as part of the VM creation process. Ideally, users should be required to select or fill in a category value before deploying a VM. Can this be achieved somehow?

Thanks in advance! 

Hi ​@mariakalendarova 

When you publish a blueprint to the marketplace, you can decide who can launch it.
You have to go to the marketplace manager and there you assign other projects to it.
Projects are logic containers that can hold a list of users/groups and their roles.
Every project you add will get a permission to launch it, depending on the role the user has (minimum role to launch a BP is ‘consumer’).


Don’t forget to enable this toggle button before submitting:

 

As for your second question, in the blueprint, when clicking on the service box, on the VM tab you will find the categories section.

Just tick the “running man” (should turn blue) so it will be available in the BP form.


Then when someone launches the BP it will be shown in the form:

 

Good luck!


@Avico 

 

Thank you very much, you helped me a lot!!


I was happy to help you 😀


Reply