Introduction

What are the key activities across the whole deployment of a VI3 solution?

The VI3.Blueprint Project has been devised by the community to bring together the collective experience into one place to provide guidance through the whole deployment process, from VI3 Business Case through to day-to-day VI3 Operations.

To go straight into the list of project documents, see VI3.Blueprint Directory.

If you want to get involved with the project, then check out How to get involved with the VI3.Blueprint project.

This project is underway and is targeted for completion at the end of March 09.

Intended Audience

VMware Certified Professionals (VCP) and VMware Architects (VCDX), and the broad cast of virtualization advocates and IT professionals who make these projects successful.

Outline

The activities in a deployment are grouped by stages, though the stages do overlap to some degree and are not completely linear.

1. Initiating

2. Designing

3. Implementing

4. Operating

There are many methodologies and frameworks available to manage a VI3 deployment, whether it's VMware PSO's Assess/Plan/Build/Manage, ITIL v3 or your own home grown one This is not Yet Another Frameowrk (YAF), instead it is a simple blueprint / list of the most common activities used in the many times I've seen these projects completed successfully. The idea is to provide a thorough high-level view backed up by detailed individual documents. So for example, the Consolidation Pipeline activity will have a VIOPS document providing the detail and you can link to it easily from here.

The rough timeline for executing this blueprint is 180 days: at the end of that 180 days you could have a working VI3 cluster that is well managed and is being fed by a healthy pipeline of P2V candidates. You could do it faster with less activities, or longer with more - it all depends on what your situation demands, but this list is pretty typical of large enterprise organizations.

What's in the VI3.Blueprint?

The best place to start is the VI3.Blueprint Directory.

The directory gives you an index of all the documents and their current status as the project is developing:

• Specification - the specification for the document is being worked on

• Writing - the specification is complete, and now the document is being written.

• Review - the document has been written and published, and is now being reviewed and updated

• Complete - the main Reviewing has been completed, but feedback is still welcome.

How you can help

All VIOPS documents are collaborative and improved by peer review and feeding back comments into document improvements. You will see documents grow and take shape in front of your eyes. Please act upon any thoughts you have such as:

• Is there something missing or incorrect in this document? Post a comment at the bottom of this document

• Do you have additional information or related material to share? start a discussion thread about this document

• Keep informed! Subscribe to the Strategy Blog

Your participation goes a long way to improving this kind of content for the benefit of everyone; there have been some fantastic feedback from users to authors on this site.

We are seeking reviewers, researchers and co-authors for this work. There are 60 points to write up, research and review. Get your name in lights; earn rewards!

Private message or email Steve Chambers

Disclaimer

You use this proven practice at your discretion. VMware and the author do not guarantee any results from the use of this proven practice. This proven practice is provided on an as-is basis and is for demonstration purposes only. |