Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)
Item 2 updated for vRA 7
vCO Endpoints are used by vCAC when vCAC needs to execute vCO workflows. These can be out of the box workflows such as the NSX workflows, or they can be workflows that you created and want vCAC to execute as part of a deployment state transitions such as during building machine, machine provisioned, machine destroyed or various other master workflow states. vCAC cannot execute these workflows without first having a vCO endpoint to which it can query and call to execute. vCAC can pass machine custom properties and other information through to vCO as part of the execution to parameterize the workflows.
Adding a vCO Enpoint
- Navigate to Infrastructure -> Endpoints ->Endpoints and hover over New Endpoint -> Orchestration -> and select vCenter Orchestrator.
- Give the Endpoint a Name, input the vCO url such as(for VRA 6.x https://FQDN:8281/vco) (For VRA 7.0 https://FQDN/vco), then either select or create the credentials. Next create a new custom property with the name VMware.VCenterOrchestrator.Priority and assign a value of 1. This is used in the event that you have more than one vCO server you can control the priority for each to determine which will prioritized for processing requests. Click OK when finished.
- Once created hover over the endpoint and select data collection to perform a data collection.
6 Replies to “vRealize Automation – vCAC 6.1 – Adding a vCO Endpoint”
Have you noticed whether the data collection is actually succeeding? I have two different vCO servers that I’ve added as endpoints and both have the data collection failing with the following error:
“vCenter Orchestrator returned an error: Full authentication is required to access this resource”
The user is a vCO admin. I’ve tried setting up authentication on the vCO configuration side for both LDAP (active directory) as well as SSO and I get the same result. I’m running vCAC 6.1 and the latest vCO 5.5 appliance. Any ideas? Google and VMTN aren’t much help.
And I answered my own question. After reading through your post I realized I wasn’t adding the “/vco” at the end of the URL. I don’t remember having to do this in earlier versions. Thanks for the post!
You are correct in earlier some of the earlier releases you didn’t need the /vco at the end.
When adding the vCO endpoint, can the vCO endpoint be the VIP of clustered vCOs? I haven’t been able to find documentation if this works or if it’s even supported.
Yes it can. Have you seen the Reference Architecture for vCAC?
One tip, when specifying creds, use user@domain format and not domainuser.