Dispatch /

VCSA’s Assemble!

19 Mar 2014

I have had the pleasure to work with many expansive and unique environments in my career. One of my favorite and the most unique has defined automated PODs of availability throughout multiple data centers and mobile locations.

As the environment has grown, so has the need to segment specific VCSA services like the Syslog Collectors, Dump Collector, Auto Deploy Server, SSO and the Web Client (even the embedded DHCP and TFTP services, where applicable.)

I won't go into the "lump all your services into one big VCSA instance" argument in this post. Suffice it to say that there are use cases where services need to be modular.

Unfortunately, with so many instances of the VCSA deployed throughout the environment, it can become difficult to know which VCSA you’re in as you flip between browser tabs.

Have you ever noticed that the default vCenter Server Summary in the VCSA does not clearly show which system you are logged into? There is no clearly identifiable information other that the URL.

So, this past week we were discussing this issue and decided that it might be nice to consider a slight modification of the VCSA Administration interface to compliment the host alias and the appliance role.

To modify the header and site title of the VCSA when logged into the Administration UI , login into your VCSA as ‘root’ and locate the following file.

/opt/vmware/share/htdocs/service/core/view-deploy.xml

Replace the value in:

<property name="name" value="VMware vCenter Server Appliance"/>

… with your own custom value, such as:

<property name="name" value="'Iron Man' POD - Auto Deploy"/>

If you want to get a little more creative, replace the following file with your own transparent GIF.

/opt/vmware/share/htdocs/service/core/vami-logo.gif

The result is more meaningful and special.


Twitter Facebook