I've done that for some clients and I must to say that is not quite easy.
This is one of my vRO Workflow:
There are workflows in the plugin to create the Machine Prefix, the Business Group and the Entitlements (in my workflow, the "Create Client Entitlements" is a bigger workflow with all the calls). But sadly, to create the Reservation I've used direct API calls. Although complicated, it is very well explained in the "vrealize-automation-73-programming-guide.pdf" document.
I hope this leads you in the right direction.
Thx bdamian for your feedback !
Thats is one of mutiple question : It's more efficient to create a reservation with API calls or with a workflow ?
Actually we try to create a reservation with a workflow.
This Workflow works :
BUT we still have a lot of attributes to put in place dynamically.
The selection of :
- vCenter environments for example: We have 4 vCenter with clusters that have identical names on the 4 vCenter.
In short, the journey is still very long and we don't know if it is better to work with a Workflow than an API call.
- Ressource Pool
Have a nice week-end
I've started to use the API because in vRA6 there was no workflow to create reservations. The workflows always end in API calls so I imagine that it's no big difference. The only thing that matters is to do the things in the way you need to do it.
we just see these two post :
they speak about a vCO plug-in "Reservation Manager" created by "Flow Grab".
The web Site "Flow Grab" is down.
- Do you know if it's possible to find an other location to download this plug-in : Reservation Manager ?
- Has anyone ever tested this plugin ?
Thx for your feedback.