Monthly Archives: January 2015

vRA 6.2 installation gotchas

Here is a list of the tricks and tips I found deploying vRA 6.2:

  • Java

This one is very nice. Java 1.8 prevent Liquibase from working using SSL (credits). The easiest workaround is to install Java 1.7 instead.
Don’t forget to create the JAVA_HOME environment variable using short names because again vRA installer is not confortable with the quotes in the path.

  • Internet explorer

I was working at a customer where IE is stripped out from Windows (even the explore.exe file is removed). Nevertheless if you don’t disable IESC for admin this will prevent the installer to reach the repository. So disable it (server manager > local server > IE Enhanced Security Configuration).

Setting screen:

  • Simple Install

When you try to deploy a simple install be aware that you cannot control the following elements:
– Installation path of vRA, everything will be deployed in “C:\Program Files (x86)\VMware\vCAC”
– Certifiacte to use, vRA installer will generate a self-signed one. You can then change it after the install following the procedure on page 126 of vrealize automation 62 installation and configuration PDF.

  • Custom install

When you choose the custom install and want to deploy everything on a single machine you must deploy all core components in one pass. I tried to deploy database, model manager data and web site then later Manager and the installer just told me that the vCAC app pool already exist and refused to go further. I had to reinstall everything from scratch including dropping vCAC DB.

Building a lab: from wood to cloud – part 1.

I needed to build a new lab to work on different cloud stacks and as I also love woodworking: I though why not building a custom rack to host my lab. The requirements were quite simple:

  • Host a full VMware stack: vSphere, vRA, vRO, vROM and NSX stack (with all required supporting infrastructure)
  • Host an Openstack instance as well
  • Consume minimal power (even a lab must be energy efficient)
  • Look good
  • Ease maintenance and cabling
  • Portable: I want to be able to move it arround without a forklift
  • Provide a large NAS storage space for various non-lab usage like time machine backups

So with that in mind the first thing was to select the hardware:

Small size and low power consumption leads to two platforms Intel NUC and Apple Mac mini. One of the requirements being looking good: the mac mini was the obvious choice. It is small, power efficient, good looking an easy with ESXi (thanks to William Lam for his numerous and usefull articles on installing ESXi on Mac mini).

But the latest edition of the Mac mini has some limitations:

  • It is non upgradable: RAM is soldered
  • core speed are very low: the entry level nodel runs @ 1.4Ghz

As a consequence it will be quite expensive to get the correct configuration.
So I’ve ordered 3 previous gen MD387LL/A entry level model (on sale @ 499$ each), 3 16Gb upgrade and 3 32Gb SD card (more about those later).

The compute kit

You may ask why the entry level dual core ? the answer is simple, I found that 8Gb of RAM per core is the RAM/core sweet spot. So as the max RAM is 16Gb on those machines, 2 cores is enough and the clock speed is good.

For the storage, I am an NFS fan but I also like VAAI and found that VAAI for NFS is making NFS too complex. So I went with iSCSI storage. I also wanted a large upgradable array. After seeking for the perect array I found that a Synology 1813+ will do the trick:

  • 8 bays upgradable to 18 bays by adding external enclosures
  • 4 Gbe network ports
  • VAAI capable firmware
  • SSD aware, they can be used as read cache or very fast storage.

On the disk side: I had 2x2Tb WD Caviar red, a 512Gb Crucial M500 SSD and another old 2Tb WD caviar green hanging around. I just order 2 extra 3Tb caviar red. The disk configuration will be detailled in a later post.

As NSX is involved the following requirements comes with it, physical switch must support:

  • Jumbo frames: more precisely MTU of at least 1550 for VXLAN
  • 802.1q VLAN
  • IGMP snooping

Again I found that repurposing an old Netgear switch is the most economical option. I had for a long time a Netgear GS108Ev3 which actually meets all the requirements. It even has a nice web admin UI. It only has 8 ports but that will be enough for now.

I am looking for something easy to work with medium mechanical resistance (the lab is not going to be that heavy, neither will it withstand heavy mechanical constraints). So I’ve choose to do it in 1/2 inch particule board (which also happen to be hanging around in the workshop).
Particule board are easy to work and finish. The only drawbacks are:

  • No advanced joinery is possible. i.e. no dovetails
  • It produce nasty particule when cutting or working with a routeur: proper eyes and breathing protection are mandatory, earing protection is always a plus.

Now that everything is chosen. I need to draw my custom enclosure and start working the wood. The next article will cover the building and fitting of the enclosure.