Adding Orchestrator as an infrastructure endpoint

This will add Orchestrator as an additional endpoint into the vRA infrastructure. This will allow you access to plugins that are not part of the endpoints we can configure in the Adding an Orchestrator endpoint recipe in this chapter.

Getting ready

You need an external or internal Orchestrator as well as a user account that has Administrator rights in Orchestrator.

How to do it...

We are now adding Orchestrator as a vRA Infrastructure endpoint:

  1. Log in to vRA with an Infrastructure Admin account.
  2. Go to Infrastructure | Endpoints | Endpoints.
  3. Click on New and select Orchestration | vRealize Orchestrator.
  4. Give the Orchestrator a name.
  5. The Address for the internal Orchestrator is https://[vra FQDN]/vco, and for an external Orchestrator it is https://[vROFQDN]/vco. As vRA uses a proxy, you don't have to specify the port number anymore.
  6. Create Credentials with a user who is a member of the vRO Administrator group.
  7. Add a new property by clicking on New. Enter VMware.VCenterOrchestrator.Priority and set  Value to 1. Click on The green tick button to save this setting.
  8. Click on OK to save the endpoint.

    How to do it...

How it works...

An Orchestrator endpoint lets you create additional customization and lets you use plugins that are not part of the endpoints we configured in the Adding an Orchestrator endpoint recipe in this chapter.

For some features, such as NSX, you may require an Orchestrator Infrastructure endpoint. Also see the recipe NSX integration in Chapter 11, Additional Plugins.

There's more...

You can associate a Blueprint with a given Orchestrator Infrastructure endpoint by adding to the Blueprint the Custom Property VMware.VCenterOrchestrator.EndpointName and, as a value, the endpoint name you specified.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset