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.
GCN : August 2014
67 their migration to a private cloud following a half-dozen steps: 1 | Begin by addressing the thorny budget issues. Given today's funding realities, many CIOs likely won't have ready access to the hundreds of thousands or millions of dollars needed to fund a full cloud implementation from scratch. But an incremental approach is to pay for the cloud a piece at a time. Start by focusing on a current pain point, such as the time and resources being devoted to patch management or provisioning new resources. "For example, make a small investment that enables the organization to automate the delivery of applications to reduce costs related to staff time," McDermott suggests. 2 | Invest in tools that give the organization the ability to provision VMs on top of the existing IT infrastructure. at will take out additional costs that CIOs can use to buy an integrated "cloud-in-a- box" platform of computing, storage and networking components. "You can start provisioning resources onto that platform to begin the physical-to-virtual migration of servers," McDermott says. " en start systematically shutting down physical hardware over time. In this way, you make private cloud investments in manageable chunks --- $200,000 to $400,000 at a time over two years --- so the program is essentially paying for itself. At each step along the way, you'll be able to see value of the investments, which is a less risky approach than spending $2 million up front." 3 | Evaluate the current IT environment. It's critical to have a sound inventory so that the IT team can determine if core areas, such as the internal network infrastructure, need a refresh to accommodate new ways of delivering services. 4 | Virtualize wherever possible. e widespread server virtualization efforts that have taken place over the past few years have helped many IT shops reduce physical hardware requirements, increase utilization rates and alleviate power demands. Now, organizations are looking beyond consolidation to the next big wave of virtualization, which spans servers, storage systems and networks. Along with reduced hardware footprints and cost savings in energy and other areas, widespread virtualization addresses the security concerns that come about when a number of users share resources in a private cloud implementation. But security concerns may be lessened with the advent of software-defined data centers, which comprehensively apply virtualization to computing, networking and storage resources. 5 | Determine which applications are right for running in a private cloud. Not every application will likely be right for cloud migration. e IT team will need to evaluate and prioritize the applications in use. 6 | Implement technologies for automated provisioning and orchestration. Clearly, these tools offer key management advantages for the IT team, particularly when paired with a portal that lets users serve themselves based on defined use policies. "Once you create the catalog and tie it to a library of standard hardware images, end users can make requests for new services," McDermott says. " e orchestration platform then steps in to automate and build out the services." With an incremental approach, IT managers can launch dynamically provisioned services to users from a private cloud --- and, most important, avoid large up- front capital investments. "ORGANIZATIONS HAVE THE ABILITY TO MICRO SEGMENT THEIR NETWORKS VIA SOFTWARE TO ASSURE THAT WORKLOADS ARE ISOLATED FROM ONE ANOTHER." -Edward Newman, senior director of cloud and IT transformation, EMC Global Services