Test laboratories: we know we need them. But releasing it from the ground can be an insurmountable task! So to help you roll up your sleeves and get started, here is a summary of how we set up test labs for our customers, plus some practical ideas to help you get the most out of your test lab once it's up and running!
Hardware: In previous years, getting approval to set up a testing environment was very difficult because of the number of devices and hardware classes needed. Because hardware has improved and virtualization technology has moved forward, we can now build test labs using a single workstation!
When I created a test lab for customers involved in developing application objects, both traditional and virtual, I recommended that, if possible, they dedicate machines to the task. For customers who are testing servers, new applications, or new operating systems, setting up virtual machines on their personal workstations is a good choice (especially if they have a laptop). They can then work in the testing environment whenever they have time. Whatever it is, here are a few recommendations:
* Make sure the hardware is relatively new. Even though it's tempting to redirect an older machine, you will quickly become frustrated if you don't have enough RAM or disk space.
* Insert as much RAM as possible into the machine. Most testing can be done on a machine with 4G RAM. However, keep in mind that to test products like ZCM, you might need more. My special test machine has 8G RAM, 1TB hard drive, and runs Windows XP 64 bit.
* Buy an inexpensive external drive. This is great for moving, sharing and storing your virtual machine library. You can also use it for backup. Make sure you back up this environment regularly, for obvious reasons!
Software: There are many free products out there to use when creating virtual machines. Of course, some are better than others. Although it's tempting to use free products, you might quickly become frustrated with their limitations. Paid products have features such as unlimited snapshots and cloning. Be sure to check the software license details when making a clone to ensure that you are compliant.
Using a Virtual Machine: Here are just a few of the many ways you can use your virtual test lab!
* Application Development: First, create a Windows Application Development virtual machine that only contains a basic OS with patches and whatever application development tools are needed, and take snapshots. Then, for each application that you develop, return to the original snapshot, develop the application and take a new snapshot. This creates a snapshot library that you can restore when patching or adjusting settings for a given application.
* Application Testing: You can also create a second VM with only a basic OS, patch, antivirus, Novell client, ZEN agent, etc., to test the application. Be sure to take a basic snapshot so you can idexx indonesia return to it after each test. (You don't need to save a snapshot of the application test: just a base.) Whether you are developing a virtualized application or MSI with AdminStudio, this environment will serve you well.
* Pre-migration testing: Set up one or more servers to emulate a production environment. Again, take a snapshot before making changes. Then test the migration you plan, such as updating GroupWise, migrating to OES Linux, etc. By saving a basic virtual machine library, the sky is the limit on the type of testing you can do.
* Teaching, Training, and Demo: Save a virtual machine library on an external drive. This gives you a great way to organize classes quickly or provide product demos for your staff or end users. For example, you can do lunch and learn to show your user community GroupWise tips and tricks, improve your technology at ZCM, or present new software to management to show off its capabilities.
Virtualization software has become a must-have tool in our consulting practice. Hopefully the ideas presented above will give you the boost you need to get started!
Komentar
Posting Komentar