Hello,
i have a question about integrating orchestrator Workflows as an XaaS Blueprint.
I have done the following.
1. Add an Orchestrator Endpoint and configure it to use the local (vrealize automation) server with username and password
2. configure an Blueprint to create a snapshot. The create a snapshot should use the default orchestrator workflow to create a snap.
3. add that workflow to the catalog.
But when i try to create a snapshot using the blueprint, i could not browse the vcenter server to create a vm snap. The windows is still empty.
I check the data collection of the orchestrator and it show me that the collection status was succedded.
I also have started the service on the host but the issue is still there.
Thanks
Frank
Ok, so then you haven't actually run it. Change session per user to No using the update workflow. Once done, verify you can list the vCenter inventory in the vRO client.
Why would you want to publish the snapshot action as an XaaS blueprint when this comes out-of-the-box as an action on a deployed machine?
Because not all of my vm´s are deployed with vrealize automation.
And i am testing the functionality and that should work.
Frank
When you create the XaaS blueprint, does the Blueprint Form show the presentation matching the workflow? Do you see nothing?
yes. I also did not see the vcenter there.
Frank
Have you configured vCenter as an endpoint through vRO itself?
yes i do. I am able to create for example a vm from a blueprint that i have created.
With what authentication settings did you add the vCenter endpoint when you ran that workflow? Single session, or per-user session?
I don´t know what you mean. Where can i do a setting like this?
I have created a vcenter endpoint with the default administrator@vsphere.local user and the password.
Also for the orchestrator. the same.
Find you "Add a vCenter Server Instance" workflow token that was successfully ran. Click the Variables tab. Take a screenshot of all the variables in the bottom pane. For example, mine looks like this.
I have just started the workflow. It looks like that
Ok, so then you haven't actually run it. Change session per user to No using the update workflow. Once done, verify you can list the vCenter inventory in the vRO client.
Perfect. Thank!!!!
Frank