UPDATE: Dec 9 2014 – vCAC is renamed to vRealize Automation (vRA). vRA 6.2 is dropping today and the pre-req script is posted here.
UPDATE: Dec 16 2014 – Doh!! I was multitasking too much when i posted that last update. The pre-req script wasn’t the point of this original post, but is still useful none the less. To recap – the pre-req script is to ease setting up a vRA IAAS machine. The template prep script is to ease setting up a linux template to be used _WITH_ vRA.
A great tool that flew under my radar in the most recent 6.1 release for
AppD….er…Application Services and vCAC proper… is a script that does all the steps to prepare a linux template for you for both agents. If you are at all familiar with this process, you’ll find it to be a huuuuuuuge time saver.
If you look at the documentation it’s quite cumbersome and full of potenial human error points. This script will check all dependencies, install them where it can, and either prompt for the appropriate server names or accept inline input.
First pull the script off the AppD server and make it executable.
chmod 744 preparevCACTemplate.sh
How to use it – Interactive
If you wanted to just dive in run it for interactive mode:
I update templates quite often in the lab environments I work in, so I like keeping a quick reference in a note that I can quickly cut & paste from. Now that this script accepts inline inputs I could gain an extra sysadmin merit badge and just drop it into a shell script in a common place across all templates and just manually run that. Easy Peasy.
So here’s the help page:
Here’s what I would run which tells it the three server names, not to install java, not to check ssl certs, a timeout of 300 secs and not to prompt to confirm:
./preparevCACTemplate.sh -i iaas.mydomain.com -a appd.mydomain.com -c vcac.mydomain.com -s false -t 300 -j false -n
echo "" > /etc/udev/rules.d/70-persistent-net.rules
The last line is a handy step that prevents centOS templates to increment the nic# when cloning. There could be a better way but it works.
… it does it’s thing…..and finishes with:
Now you’re ready to shut it down, take a snapshot, start data collection, and update your blueprint!