In previous part of this vCloud Suite Proof of Concept we have integrated the vCloud Director with the vCloud Automation Center and created blueprints for virtual machines that a customer can request through the Self Service Portal. Now we will take a closer look at the resource request from the Self Service Portal.
- Open the Self Service Portal by typing https://<vCAC_Server>/vCACSelfService address in your internet browser.
- Login with user credentials. I’ve created an admin account for my organization in the Active Directory and assigned the user to the corresponding Provisioning Group in vCAC.
- When logged in, the welcome screen should look similar to the one below.
- Click the New Request button on top of the page. You should see all blueprint available to this particular user.
- Click on the blueprint and a Request vApp wizard window will appear.
- In Step 1 – General Settings, enter the number of machines you want to request, provision information, description and the reason for the request. Click Next.
- In Step 2 – Machine Configuration you have the opportunity to customize the machine (if you are authorized of course). Click Next to continue.
- In Step 3 – Custom Properties, leave the properties as default and click Next.
- Review the request and click Finish to submit it.
- The requested machine will be cloned, deployed and powered on. You can monitor the progress from the My Resources -> My Machines menu on the Self Service Portal. When the virtual machine is deployed, you will see its status as On.
If you get the following error during a new resource request:
Error requesting machine. Transactions with IsolationLevel Snapshot cannot be promoted.
You probably installed the vCAC database with different credentials than the credentials used to run the vCloud Automation Center Service. To fix this, you have to reinstall the vCloud Automation Center Server and make sure when creating the database you use the same credentials for the database as for the vCloud Automation Center Service on your Windows Server. Also, note that the FQDN’s and the database name during the setup of all vCAC components are case sensitive!
If you get the following error during the deployment of the virtual machine:
Error creating user: administrator in organization: <Organization_Name>. Inner Exception: Matching LDAP object for administrator not found
Make sure that your organization in de vCloud Director is configured with LDAP connection and that the user account requesting the resources through Self Service Portal is added as organization administrator.
And so this concludes the vCloud Automation Center in this Proof of Concept series.
Continue to part 21 where we will take a closer look at the vCenter Infrastructure Navigator.
- vCloud Suite POC Part 1: Introduction
- vCloud Suite POC Part 2: Installing vCloud Director Cell
- vCloud Suite POC Part 3: vCloud Director Configuration
- vCloud Suite POC Part 4: Creating a new Provider vDC
- vCloud Suite POC Part 5: Creating new Organization
- vCloud Suite POC Part 6: Add and Publish Catalogs
- vCloud Suite POC Part 7: Create New vApp
- vCloud Suite POC Part 8: Add vCloud Connector
- vCloud Suite POC Part 9: Move VM to the Cloud
- vCloud Suite POC Part 10: Add vCenter Chargeback Manager
- vCloud Suite POC Part 11: Install and Configure vCenter Chargeback Manager
- vCloud Suite POC Part 12: vCenter Chargeback Manager Cost Analysis and Reporting
- vCloud Suite POC Part 13: Add vCenter Operations Manager
- vCloud Suite POC Part 14: Configure vCenter Operations Manager
- vCloud Suite POC Part 15: Create Custom UI in vCenter Operations Manager
- vCloud Suite POC Part 16: Add vCloud Automation Center
- vCloud Suite POC Part 17: Install and Configure vCloud Automation Center
- vCloud Suite POC Part 18: Install and Configure vCAC Self-Service Portal Website
- vCloud Suite POC Part 19: vCloud Director and vCloud Automation Center Integration