Archive for January, 2014

A vCloud Automation Technical White Paper

Posted: January 7, 2014 in vCAC
A vCloud Automation Technical White Paper

By Neeshan Peters

1. Introduction

The purpose of the white paper is to illustrate the benefits of vCloud Automation Center version 6.0 in a dispersed enterprise environment. Helping to resolve such issues as IP address management VM sprawl, labeling, descriptions, and control of overprovision.

2. Trends

Today’s virtualization technology gives us the ability to rapidly provision VM’s, and networks. The problem comes when you have more than two or three people that have the ability to provision VM’s and networks. It gets even worse the larger the IT department is and doubles in fault if the department is dispersed geographically.

Industry challenges

Complexity increasing

Long project lifecycles

Application definition

VM isolation

VM tracking

VM sprawl

Need to coordinate virtual enterprises

3. Problem

When a VM is created we find it hard for the creator to place notes on the VM for things like, the VM owner & the purpose of the machine. They may build the machine with way to much resource such as too much CPU, memory or disk space. Maybe they are building the machine on the wrong resources all together. This is where vCAC comes in.

Conventional management methods not up to the challenge

They is no product right now that will make these items a requirement and also is customizable to any environment.

4. Solution

vCloud Automation Center can resolve these issues and more. It is capable of being installed and running within a day to address these challenges. It gives you Ip address management, required fields and automatically making notes on the VM of who created it. Controls that make sure no user may over provision a machine without your consent via workflows.

This new generation of management systems can meet the challenge
  • Resource Reservations
    Resources can be pre allocated for a particular group’s usage assuring that they will be available when needed. However, they can also be reallocated if necessary to meet changing business needs.
  • Service Level Resource Thresholds
    vCloud Automation Center’s policies govern how compute resources are allocated to assure optimal performance for the task that needs to be performed. Optional approvals are available for requests, which exceed standard service levels.
  • Service Tiers
    Resources can be pooled within various service tiers (e.g. gold, silver, bronze). The combination of service level resource thresholds and service tier policies assure that resource consumers receive the “right size” compute or application service at the “right service level” for the task that need to perform.
  • Service Approvals
    vCloud Automation Center can be configured to facilitate automation of an approvals process. Where approvals are necessary, vCloud Automation Center can integrate with Active Directory and configured for alternate approvers to ensure that change management and business requirements are met.
  • Service Entitlements
    Each service created in vCloud Automation Center can be designed with entitlements to ensure that each user, or group, has access to the services they have been preauthorized to consume. – See more at:
5. Benefits

There are just too many benefits to place into this white paper but here are a few that may be of interest;

Reduce unauthorized and over-provisioning of machines

Reuse resources automatically

Recycle inactive and abandoned machines

Build with the same speed or faster as being at the vCenter console

Control IP address management

Provision new networks with a VM

Integrate with hybrid services

Manage and see the cost of services and VM’s


Better visibility into you infrastructure and the cost of running it. You will be able to know everything that goes on when you need to know and answer the tough questions when the arise.

7. Conclusion

As you can see vCloud Automation Center has the capability to resolve all of the problem specified and more. This is just the tip of the proverbially iceberg. You will be better able to manage you environment proactively rather than reactively in a world where being reactive is too late.

Additional information

For more information, visit the vCloud Automation Center product page


White Papers

Posted: January 7, 2014 in vCAC

A list of White papers that i will be writing.

vCAC 6.0 vCloud Automation Center White Paper

VMware Stencils

Posted: January 7, 2014 in Tools
VMware Stencils

VMware vSphere Visio Stencils

Presentation Pack

Veeam Stencils

VCE Vblock Visio Stencils



vCenter Tools

Posted: January 7, 2014 in Tools
vCenter Tools

vSphere Plugin Wizard 2.0

sshAutoConnect vCenter Plug-in

Auto Deploy GUI

vCloud Connector

VMware vCenter Support Assistant


vCenter Converter

vSphere Management Assistant


VMware Support Toolbar

VMware SiteSurvey

CPU Identification Utility

VMware Studio

VMware vCenter Update Manager 4.1 Sizing Estimator

VMware Compliance Checker for vSphere

VMware vCenter Orchestrator Appliance


VMware Posters


vCAC 6 AD Forest Problem

Posted: January 3, 2014 in vCAC
AD Login Problem

It seems I have hit my first major problem with vCAC 6. After doing a few test runs and other scenarios it looks like I have found the problem.

I have a multitiered domain, a forest. The main domain the users of vCAC will use is just under the main/root domain, we will call root level 1. So that means we are using the domain on level 2. Now what happens is I am only able to use AD accounts that I configure for vCAC that are on level 2 (identity source points to level 2) and do not belong to any AD groups of level 1 or 3. What happens if the account belongs to any group that is outside of level 2, is after a log on attempt, the progress bar on the log on page will stop and nothing will happen.

I found  the problem by looking at the “vmware-sts-idmd” log. It will say that the log on was successful however there was an error calling for an ldap search of a group the account is in, in domain level 1 or 3. In the log will be an ldap referral error code 10.

Error received by LDAP client: com.vmware.identity.interop.ldap.LinuxLdapClientLibrary, error code: 10

Exception when calling ldap_search_s: base=CN=ROL_3Par_User,OU=AdminRoleGroups,OU=Admin,DC=DOMAIN,DC=com, scope=0, filter=(objectClass=group), attrs=[Ljava.lang.String;@20bea718, attrsonly=0

I have tried using the global catalog port 3268 instead of 389. I thought this would work but it seems that the ldap client cannot bind on this port. I have also tried using just the root domain as the identity source with no luck.

So I am still working on this. Any help would be welcomed.