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.
This document provides an index to the tasks and documents for the project.
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.
Initiating
Designing
Implementing
Operating
VI3.Blueprint Directory
|
|
|---|
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.
The different Task Status's reflect the tasks in the VI3.Blueprint, and can be:
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.
Stage 1: Initiating
|
|---|
The Initiating stage secures the support, funding and authority to proceed with the VI3 solution.
ID | Status | Document | Description |
|---|---|---|---|
Initiate.1 | Review | Using the VMware TCO/ROI Online Calculator to create your own financial justification for VI3 | |
Initiate.2 | Review | Key document to securing management support and funding | |
Initiate.3 | Review | Limited test environment to prove basic concepts for VI3 | |
Initiate.4 | Review | Securing the authority to proceed to Designing |
The output of this stage is the authority to proceed with a signed off VI3 Project Charter.
Stage 2: Designing
|
|---|
The Designing stage uncovers the detailed requirements and formulates the design decisions through workshops that bring together other subject matter experts with the VI3 experts.
ID | Status | Document | Description |
|---|---|---|---|
Design.1 | Writing | Schedule of activities and resources required for the Designing stage | |
Design.2 | Writing | List of all the requirements across technical and service considerations | |
Design.3 | Writing | Forecasting VI3 consumption through P2V and Containment | |
Design.4 | Writing | Planning the formal and informal education for the project and beyond | |
Design.5 | VI3 Design Workshop | Bringing together VCP/VCDX and other Architect/Designers | |
Design.6 | Writing | Bringing together VCP/VCDX and Network Experts (CCNA/CCIE) | |
Design.7 | Writing | Bringing together VCP/VCDX and Storage Experts | |
Design.8 | VI3 Migration Workshop | Planning the migration process and tools | |
Design.9 | Writing | Detailing technical design decisions, assumptions and constraints. Input to Implementing. | |
Design.10 | VI3 Introduction Workshop | VMware Infrastructure 101 for all comers | |
Design.11 | VI3 Security Workshop | Bringing together VCP/VCDX and IT Security Professionals (CISSP) | |
Design.12 | VI3 BCDR Workshop | Bringing together VCP/VCDX and Business Continuity Professionals | |
Design.13 | VI3 Release Workshop | Bringing together VCP/VCDX, Server, OS, App and Systems Management | |
Design.14 | VI3 Configuration Management Workshop | Bringing together VCP/VCDX and Systems Management | |
Design.15 | VI3 Change Management Workshop | Bringing together VCP/VCDX and Change Management | |
Design.16 | VI3 Chargeback Workshop | Bringing together VCP/VCDX and Finance | |
Design.17 | VI3 SLM Workshop | Bringing together VCP/VCDX and Service Management | |
Design.18 | VI3 Capacity Management Workshop | Bringing together VCP/VCDX and Capacity Management | |
Design.19 | VI3 Operations Workshop | Bringing together VCP/VCDX and IT Operations | |
Design.20 | VI3 Incident and Problem Management Workshop | How to do fault isolation and root cause analysis | |
Design.21 | Writing | Bringing together VCP/VCDX, IT Operations and Systems Management | |
Design.22 | VI3 Service Design Document | Detailing service design decisions, assumptions and constraints. Input to Implementing stage. |
The output of this stage is two approved design documents (Technical and Service) to begin the Implementation.
Stage 3: Implementing
|
|---|
The Implementing stage takes the Technical and Service designs and bakes them into hard, unambiguous architecture documents and build guides and creates the solution by building the VI3 cluster and integrating it with the other IT processes.
Tasks TBD.
Stage 4: Operating
|
|---|
The Operating stage takes an operationally accepted VI3 solution and manages it from day-to-day.
Tasks TBD.
Resources
AuthorsRoll Up! Roll Up! 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
Steve Chambers, Senior Architect at VMware
VMware (NYSE: VMW) is the global leader in virtualization solutions from the desktop to the datacenter. Customers of all sizes rely on VMware to reduce capital and operating expenses, ensure business continuity, strengthen security and go green. With 2008 revenues of $1.9 billion, more than 130,000 customers and more than 22,000 partners, VMware is one of the fastest-growing public software companies. Headquartered in Palo Alto, California, VMware is majority-owned by EMC Corporation (NYSE: EMC). For more information, visit www.vmware.com. |
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. |
There are no comments on this document