In this multi-part series we will deploy the Identity Appliance, the vCAC Appliance, the Windows IaaS components, ITBM standard, Application Services, and a basic tenant setup.
- Part 1 – Identity Appliance
- Part 2 – vCAC Appliance
- Part 3 – Windows IaaS Install
- Part 4 – Initial Tenant Configuration
- Part 5 – License, Endpoint, Group, Reservation, Blueprint, and Entitlement
- Part 6 – ITBM
- Part 7 – Basic Application Services
Here in Part 6 we will walk through the quick and easy deployment of ITBM. This will be fairly short as the ease in which to deploy and configure ITBM 6.1 Standard is really quite simple and more importantly VERY valuable reporting and cost metering.
Now let’s step through the deployment of the OVF or OVA.
Browse to the location of your OVF or OVA.
Review the EULA and accept.
Name your virtual machine (I choose the fqdn for my deployment). At this point it doesn’t matter just make it something you will know.
Select disk location and type.
Select the network you plan to use for the appliance, realize that vCAC appliance and IaaS will both need to be able to access this location!
Enter the settings for your virtual machine
- Enter and confirm the root password
- Set your local currency
- Select if you wish to enable SSH
- Set your default gateway
- Set your DNS servers
- Set your network IP address
- Set your netmask
Check power on and click finish. This process will take a few moments depending on your storage and network configuration.
Now launch a web browser go to https://fqdn:5480 in my example I used https://itbm-va-ng.biteback.records:5480
Login with root and the password you just defined.
In the System tab go to Time Zone and set it to your local time zone.
In the Admin tab under Time Settings define your ntp servers and save settings. I HIGHLY recommend not using host time because if the host time drifts there’s no warning and it will create issues with the vCAC components.
In the vCloud Automation Center tab you will define
vCAC Hostname -> vcac.fqdn in my example it is vcac-va-ng.biteback.records
Tenant -> vsphere.local (default)
Admin User -> administrator
Check the “Accept …”
It will take a few moments but once complete you will see Registered with vCloud Automation Center server in green.
Now we need to authorize the tenant admin or a user to be a business manager.
Log into your vCAC web interface with an administrative user and go to
Administration tab -> Users
Search for the user (I would use the same user as your tenant and infrastructure admin at this time).
Once you selected the user you can then add the role of Business Management Administrator. Notice you can add read only users.
I have found this authorization can take a few moments and more importantly depending on your browser cache can be serious issue to refreshing the page. I recommend exiting the browser and relogging in.
You should now see a Business Management tab.
Now let’s enter the license key, go to
Administration tab -> Business Management
Expand the Manage Connections.
Add a vCenter connection.
Once complete you will see the vCenter connection made.
Now go to Business Management tab and review the cost collection.
Now we Update Costs by going to
Infrastructure tab -> Compute Resources -> Computer Resources
Start updating costs.
Refresh to see it complete successfully.
Finally go to view the cost associated to a blueprint by going to Catalog tab and start a request. You will see a cost associated to your request.
Now we have completely defined the IaaS in parts 1-5 and added the cost metering with this post. Next in part 7 we will build and configure the final piece of this puzzle with application services.