Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

You need to prepare some elements outside of vRealize Automation to support VM provisioning. To prepare your environment, do the following:

Creating a Customization Specification in vCenter Server

You need to have a VM template and a customization specification in VMware vCenter Server to be able to create VMs in vSphere using vRealize Automation.
Customization specifications are XML files containing guest operating system settings for virtual machines. Specifications are handy for defining global features in guest operating systems such as the guest OS host’s name, domain name and other settings.
To create a customization specification:

  1. In vCenter, choose vCenter –> Inventory –> Management –> Customization Specifications Manager.
  2. Click New.

  3. Select the Target Virtual Machine OS type.
    The New Customization Specification wizard opens.

  4. In the Name field, enter the name for the new specification.
  5. Click Next.

  6. Select Use the virtual machine name and fill in the Domain Name field for the VM specification at the bottom of the pane. The Use the virtual machine name setting allows the VM to use the same name as for the guest operating system, which makes locating VMs easier for administrative purposes.

  7. Click Next.
  8. Select Area, Location and Hardware Clock Set, and then click Next.
  9. Keep the Typical settings selected by default.
  10. Click Next.
  11. Enter the DNS Search Path (such as testrollout.infobloxIPAMdemo.com), click Add, and then click Next.
  12. Click Finish. The vSphere Client appears, showing your new customization specification in the table.

Ensuring Required Services are Up and Running

Note

Before you proceed, make sure NIOS is operational and all necessary licenses are installed on it.



You can use vRealize Orchestrator embedded to your vRealize Automation or a standalone vRealize Orchestrator. The following instructions apply to the embedded vRealize Orchestrator.
Do the following:

  1. Log in to the vRealize Automation Appliance console as root.
  2. Execute the following command using the command line:
    service vco-configurator start
  3. Enable the vRealize Orchestrator configurator to start on boot up of the vRealize Automation Appliance:
    chkconfig vco-configurator on
  4. In the vRealize Automation Appliance window, click VMware vRealize Appliance management.
  5. Click the Services tab.

  6. Make sure that all services are registered. If some services are not registered, wait for some time and click Refresh to see if the services are registered.

Configuring Authentication Provider

To work properly and manage user permissions, external vRealize Orchestrator requires a method of authentication. If you log in to Orchestrator Control Center for the first time, you have to specify the authentication provider.
To configure the authentication provider:

  1. Log in to Orchestrator Control Center.
  2. On the Configure Authentication Provider page, select an authentication mode:
    — vRealize Automation: Orchestrator is authenticated through the vRealize Automation component registry.
    — vSphere: Orchestrator is authenticated through Platform Services Controller.
  3. In Host address, enter your vRealize Automation or Platform Services Controller host address and click Connect.
  4. Click Accept Certificate.
  5. In User name and Password, enter the credentials of the vRealize Automation or vCenter Single Sign-On administrator account.
  6. In Default tenant, enter the default domain to authenticate a user who logs in without a domain name. The default value is “vsphere.local”.
  7. Click Register.
  8. In Admin group, enter an administrators group and click Search.
  9. Select an administrators group.
  10. Click Save Changes.

You can test the defined authentication provider on the Test Login tab. After you finish configuring the authentication provider, you can proceed to the next steps using the vRO Control Center.

  • No labels