vCloud Director – The Aim and Solution

“A great recipe is something that can be reproduced over and over with minimal effort”

                                                                                                                        Team S&N

The main aim of vTote was to create a dynamic environment for Assurance Testers and Developers.

This environment is able to be kept up to date with current releases and mimics production in every way to the point that one environment in full would be capable of running as production or Disaster Recovery given the correct network segments.

This has been achieved with the implementation of a VMWARE solution called vCloud Director (version 1.5).

Okay so some of this is already here, but are we really using it in production to its full potential.

After fifteen years in the industry I was getting a bit tired of the ho hum of IT. Build Server (vm or physical), Install OS (Linux or MS), Install service (apache, dns, AD, DHCP, etc etc)

Then along comes vcloud director 1 and 1.5… Now I know most people will say Xen has been able to do this and that for a long time. But let me just tell you, a package like this I have never ever seen before, it was a bit of a challenge to initially get the head around the concept.

So for a moment let us assume that you have in your production environment.

Simple Windows Network

 

So in order to build your environement you need to provision up some Windows servers.

So for a moment let us assume that you want to create a three tiered network and populate with three servers.

To paint the picture on how we were to use a combination of VDR and vCloud Director.

We would on a monthly basis to coincide with software release dates take a full production backup using VDR (note that other backups were also being taken on a nightly basis). Once VDR was complete we would restore all production servers as new servers and then convert to templates. We would then place these templates into vCloud director media pool so that our developers / QA and UAT could build up entire environments in private vlans. They could test their code, they could test roll out and functionality on an exact replicate as production.

And behind the scenes it was a relatively easy process to produce a complete wow factor for our staff.

 

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s