Sample VirtualCenter 2.x Test Plan

Version 1

    Introduction

    This is an operational test plan for verifiying that an installation of VirtualCenter is fit for purpose. 

     

    This document can be treated as both a guide and starting point for developing your own VirtualCenter 2.x testing purposes.

     

    This document is not intended to replace the user guide so it does not provide screen shots on how to do each activity: it's expected that the audience will take this document and create their own level of detail using the available resources like the user guides.

    Intended Audience

    VMware Certified Professionals (VCPs) and Test Analysts/Experts.

    Outline

    The following steps are required:

    1. Fit for purpose specification

    2. VirtualCenter system actions

    3. Accessing VC

    4. Creating Objects

    5. Virtual Machine actions

    6. Optional extensions to this plan

    Author

    Steve Chambers is a Senior Architect at VMware, specialising in Enterprise Virtualization (large scale virtualizaiton of '000s).

    https://www.vmware.com/contact/vmware_logo.gif

    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

     

    Resources

     

    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.

     

    Sample VirtualCenter 2.x Test Plan

    1. Fit for purpose specification

    This section should be customer to specify what should be tested and what results are expected.  The more granularity and detail in this section, the more effort is obviously required but the more professional and perfect the result.

     

    For VirtualCenter 2.x to be fit for purpose, it must pass the following tests:

    1. The VirtualCenter server should be installed, managed and backed up as per standard Windows Server Team SLA.

    2. Check configuration of VirtualCenter against installation documentation and confirm 100% settings.

    3. Windows system administrators should not be able to access the VirtualCenter application.

    4. All of the functions required of VirtualCenter should be proven in our enviroment no matter how basic the function: in the case of features like vMotion, these depend on configurations outside of VirtualCenter so these must be proven.

    5. All of the standard operating procedures executed on VirtualCenter  must be shown to work for a VMware Administrator role, these SOPs apply to VC itself, VMs and Hosts.

    6. In the event of a failure of the VirtualCenter server, the failover procedure should be invoke and VirtualCenter should be available in R2 (second datacenter) within 30 minutes.

    7. Check that the database actions are co-ordinated and working ok (e.g. database backups).

    8. Check that all tests are signed off and verified.

    2. VirtualCenter system actions

    The following actions should be tested.

    1. Power off gracefully using Start -> Shutdown.

    2. Power on after graceful Shutdown.

    3. Check Event Log for <errors>

    4. Power off ungracefully using physical power button.

    5. Power on after ungracefeful Shutdown.

    6. Check Event Log for <errors>

    7. Reboot server from OS.

    8. Check Event Log for <errors>

    9. Stop VirtualCenter service in Services.

    10. Check service has stopped

    11. Start VirtualCenter service in Services.

    12. Check service has started up.

    13. Restart VirtualCenter service in Services.

    14. Check service has restarted.

    15. Check that backup of VirtualCenter server has worked on a schedule.

    16. Recover a test file from backup.

    17. Recover whole VirtualCenter server from backup.

    18. Check that VirtualCenter application monitoring was working during restarts/reboots above.

    19. Run Security procedures / check report against VC server.

    20. Confirm that there are no unnecessary services or files or shares or users on VirtualCenter server (as per documentation).

    3. Accessing VC

    The following items should be tested.  This can be a complex area if you have more complex roles and profiles.  These tests assume that IT Ops are the only ones who can make changes via change process and via the trusted bastions.

    1. Check that VirtualCenter server is only accessible via RDP and that VirtualCenter client can only be run locally on VirtualCenter server - ie. no VC Client on bastion or anywhere else.  Check IPSec rules on VC server as per documentation.

    2. Check that a normal user cannot access VirtualCenter via RDP or via a rogue VC Client, and that users from untrusted networks (non-management) cannot pass any IP traffic (ping, udp, tcp).

    3. Check that Windows Sys Admins can access the VirtualCenter server OS via RDP from bastion host but cannot access VC application via VC client either on bastion host or locally on VC server.

    4. Check that VMware Administrators have only read-only access, as per docs.

    5. Check that IT Ops have full administrator access, as per docs.

    4. Creating Objects

    The following actions should be tested because although they really do "what it says on the tin" (rip-off of a UK advert for fence staining!), the implementation might have had a mistake that affects any operation such as a mis-configuration.

     

    These tests are at the first use of VC - when VC has been used before and VC is populated, these tests may be skipped and signed off as "NOT REQUIRED - UNTESTED" in test documentation.

    1. Create a datacenter

    2. Create a cluster

    3. Add two hosts min.

    4. Create a resource pool

    5. Create a vSwitch

    6. Create a datastore

    7. Configure a role

     

    5. Virtual Machine actions

    The following actions should be possible as a IT Ops role and not VMware administrator (as per docs).  Remove tests / expand as required from this sample.

    1. Provision a virtual machine from scratch following documentation.

    2. Power on virtual machine

    3. Recycle virtual machine (power)

    4. Power off virtual machine

    5. Delete virtual machine

    6. Convert VM to template

    7. Provision VM from template

    8. Provision VM using cloning.

    9. P2V Convert Physical Machine Windows 2003 to Virtual Machine.

    10. P2V Convert Physical Mahcine Windows 2000 to Virtual Machine.

    6.  Optional Extenstions to this plan

    1. VMware Update Manager tests

    2. VMware License Manager tests

    3. VMware Converter tests

    4. Using VMware Support (vm-support, raising a ticket)