Next Article +

The Right Tools
Will Accelerate You to the Cloud

Make a Plan and Select the Right Tools at Each Stage

Written by Jason Dea

Next you need to understand how efficiently you are using your resources, including processors, memory, disk input and output (I/O) and network I/O. PlateSpin Recon measures capacities and use and generates a number of utilization reports. The Utilization Report, for example, shows you disk usage by server to help you understand which servers are underused and which are at or near capacity. PlateSpin Recon then helps you identify good and bad consolidation candidates with further reports.

Now that you have a good picture of your current situation, you can start planning your consolidation to virtualized machines that run on a smaller number of physical hosts. PlateSpin Recon produces reports that help you determine whether you should scale up, which is to use a small number of powerful servers as virtual hosts, or to scale out, which is a larger number of midrange servers to accomplish the same effect. The reports help you determine which scenario will work best for your organization. (See Figure 2.) The reports include everything from the number of CPUs needed to how much the scenarios would reduce CO2 emissions.

PlateSpin Recon is a very useful tool that you will use in each of the four stages on your migration path to cloud computing to determine where you are and where you should go next. Other Novell products that help you through this stage include PlateSpin Migrate, which we’ll discuss in the next section, and Xen on SUSE Linux Enterprise Server hypervisor.

Stage 2: Strategic Consolidation

In Stage 2 on your path to cloud computing, your organization becomes more comfortable with the concept of virtualization, its use and stability. Your thinking shifts from servers to virtual servers, and you begin to spread production deployments throughout the organization’s functions, including business-critical disaster recovery. You begin the painful transition from server sprawl to virtual server lifecycle management and experimenting with workload migrations.

In concert with PlateSpin Recon, PlateSpin Migrate enables you to move workloads, which include the data, applications and operating systems that would otherwise reside on a physical server, from your physical servers to your virtual environment. PlateSpin Migrate decouples the underlying server hardware and transfers workloads between the physical and virtual environments over a wide area network or the Internet using TCP/IP.

Start with the consolidation scenarios you created in PlateSpin Recon and export the one you have decided to be the best option to PlateSpin Migrate by selecting a PlateSpin Migrate server in PlateSpin Recon and pointing the planned ESX servers in the tool to the real ESX servers. PlateSpin Migrate uses “jobs” to migrate workloads, and PlateSpin Recon populates these jobs automatically.
(See Figure 3.)

Next you will use PlateSpin Migrate to discover your source and target servers, and choose to run the migration wizard, which will walk you through the process of migration from physical servers to a virtual environment.

Stage 3: Process Improvement

Once you’ve reached State 3, you have adopted a virtual environment and mindset, although you likely still have physical servers running for certain applications. You are now focused on using migration tools and on understanding how you can increase utilization rates. You have fully employed disaster recovery for business-critical applications, and you have started dividing between high-priority and-low priority applications. You have moved from just managing data resources to seeking process improvement and discovering new operational efficiencies.

You should regularly use PlateSpin Recon to continue to review and plan for these greater efficiencies. You should also be using PlateSpin Migrate to optimize resource use, and PlateSpin Protect for virtualized disaster recovery.

Stage 4: Pooling and Automation

You have now moved into the realm of cloud computing. You fully trust disaster recovery systems for business-critical applications. You have launched production policies for automation, are pooling resources in an internal cloud environment, and you’re using cloud management capabilities to charge business units for the resources they use. PlateSpin Recon, PlateSpin Migrate and PlateSpin Protect are likely well-worn tools in your IT toolbox.

Novell Cloud Manager helps you apply charges to cloud services used by business units. To set up this charge-back capability, you open Cloud Manager and click on the Business Service option. Cloud Manager then discovers unassigned virtual machines to which you can assign the following: (See Figure 4.)

  • Business service name
  • Business purpose
  • User
  • Service level: Bronze, Silver, Gold or Platinum
  • Number of virtual CPUs, memory, storage size and number of network interface cards
  • Cost to the business unit

Novell Cloud Manger also generates usage, cost and other reports to help you stay on top of your cloud computing environment.

If your organization plans to accelerate to the cloud, it’s time to turn on the fire hose to fill your virtualization pool and turn that box of cloud potential into lower costs, greater flexibility, increased business agility and improved profitability. You should understand the four stages of the Virtualization Maturity Lifecycle that you will advance through on your path to cloud computing, and plan to use the right tools to do the right job at each stage.

Next Article +

Pages: Prev | 1 2 | Next Full Page
Novell Connection Magazine
Special Editions

© 2011 Novell, Inc. All Rights Reserved.