by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : July 30, 2013
30 July 30, 2013 FCW.COM There's a crisis brewing in federal virtualization, but it's not what you think. Government's virtualization software isn't failing; it's just failing to see the light of day. Consider these numbers: A shocking nine in 10 government desktop virtualization ini- tiatives never reach production. Worse, in seven out of 10 cases, paper studies topple the project before a pilot can even begin. And we're suffering for it. Skim through any list of topical federal initiatives or executive orders, and you'll nd many --- if not most --- relying heavily on virtu- alization. The greening of IT, telecommuting, cloud adoption, securing data at rest, disaster recovery, big- data analytics and data center consolidation are all virtualization-centric. We know that virtualization is the solution for these criti- cal modernization efforts, just as baseball managers know that good batting wins the game. But in the past 10 years, we've been batting .100, which leads to nervous federal agencies avoiding these efforts altogether. Fortunately, the factors preventing virtualization projects from reaching production are both predictable and solvable --- and ironically, they have little to do with virtualization software. By avoiding the following 10 infrastructure chal- lenges, government agencies can increase their virtualiza- tion batting averages and win the game. 1. Cost. Unnecessary infrastructure costs are the No. 1 killer of virtualization initiatives. As agencies perform initial return-on-investment assessments, the hardware, setup and maintenance costs they consider (which are typically seven to 10 times greater than the cost of soft- ware licenses) can easily capsize the cost/bene t equation. 2. Complexity. Picture yourself in a data center, with multiple components of your virtualization pilot project arriving from different vendors, on different days, with parts missing and a 10-page bill of materials. If it's going to take eight weeks to even test drive the solution, you can pretty much forget about a green light for the project. 3. Power. Excessive power requirements can delay virtu- alization efforts by months while agencies wait for addi- tional power circuit installations for servers, storage-area networks (SANs), controllers, disk shelves and switches. Meanwhile, adding power ies in the face of many current greening and consolidation initiatives. 4. Cooling. Adding cooling is as time-consuming, expensive and ecologically unsound as adding power. 5. Scaling. Agencies are typically given two undesirable alternatives: risk buying the entire infrastructure upfront (ignoring the de nition of "pilot"), or run a pilot on less expensive, non-production infrastructure then rip and replace (to untested production hardware) when the pilot runs out of horsepower. More often than not, they choose neither. 6. Space. In eight of 10 virtualization initiatives, rack space presents a problem --- both in real cost and opportunity cost (i.e., less space for cubicles and of ces). And nothing lls up rack space faster than servers, switches and SANs (all of which are required for high-end virtualization). 7. Weight. Weight isn't always an issue, but when it matters, it matters a lot. First responders and Defense Department Top 10 virtualization killers The data centers that support virtualization can be complex enough to kill many projects, but some smart planning can lead to greater success FirstPer son BY DAVE GWYN
July 15, 2013
August 15, 2013