Networking

01:40 PM
Connect Directly
RSS
E-Mail
50%
50%

Private Cloud Automation

It's not easy or inexpensive to implement, but without automation you'll never get self-service or self-healing, or realize maximum ROI. Here's how to get started.

Set Goals

Determine what you want to accomplish with your automation initiative. Do you need self-service machine provisioning? Automated responses to changing infrastructure conditions? How about policy-based virtual machine and application life cycle management?

If the intent is to monitor application performance and spin up additional application servers when demand peaks, the plan is going to be different than if self-service provisioning with departmental chargeback is the primary goal. Formulating a concrete set of objectives is essential to the evaluation phase of your automation project.

Then, since product capabilities vary widely, map that goals list to feature requirements. How easy or difficult it will be to make that match depends on the underlying virtualization and management platforms you're dealing with. A full-featured automation product will need to plug into multiple silos to gather the information it needs to make policy-based automation decisions. This means integrating all relevant server, storage, and network virtualization technologies as well as maintaining accurate licensing and consistent configuration information. Depending on how your network is set up, every one of these resources could be a silo, making integration daunting. Survey respondents with a private cloud strategy underscore that point: 58% say integrating existing IT products with cloud is a major issue.

Because integration can be such a challenge, it's important to delve deep into the compatibility matrix of any prospective product before writing a check. If a vendor provides few hooks, it may be impossible to link policy engines without an absurd investment in labor. How absurd? A 2-to-1 or 3-to-1 investment in expert consulting services or internal staff commitment vs. software costs before the benefits of automation are apparent isn't unheard of.

same as caption

Why? Again, a lack of standards.

That brings us back to goal setting. When it comes time to dig into the details, automation requires that you have a very clear idea of what you want to accomplish so you can create workflows and processes that are repeatable, consistent, trustworthy, and (this is key) reusable. Take incident response: Say an application server has a meltdown that jeopardizes the availability of a key software system. If the application is in a well-constructed app server farm, other servers should continue to meet client demand, but at a higher load with reduced efficiency. If one goal of your automation initiative is a self-healing response to the loss or degradation of an application server, many variables must be considered before an automatic action is taken. We provide examples of goals and their related processes in our full report.

What You Get For The Money

For large enterprises, the cost of these suites can easily reach six figures and climb to $300,000 or more, depending on the level of automation and customization required and the size of the infrastructure. For your licensing investment, you get a task engine that can react to data by triggering workflows and whatever set of common integrations and functionality the vendor bundles; self-service provisioning Web portals, a virtual machine optimization scheduler, or some basic VM power management policies are commonly included.

What you don't get are workflows specific to your network, application portfolio, and business processes. That's why the single most important step is to carefully scope goals and requirements, identify overlap, and conduct a thorough cost-benefit analysis before tackling an automation project.

Still, it's worth getting started. Survey respondents who have private clouds say they've gotten excellent results in terms of reducing operational and capital expenses as well as managing their IT teams' time. Better resource usage overall, life cycle management, and automated provisioning--all very achievable goals--can easily make the effort and expense worthwhile.

What steps has your company taken to build a privat cloud?

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
mjamensky
50%
50%
mjamensky,
User Rank: Apprentice
6/26/2012 | 2:01:50 PM
re: Private Cloud Automation
Without automation youG«÷ll never operationalize a private cloud. Be aware that automation can sometimes be seen as a threat by IT teams, who may perceive it as a job replacement activity. Automation simply frees up extremely busy IT staff, who then get to work on more strategic and technically challenging initiatives that further add value to the organization.

IG«÷ve seen clear operational expenditure (OPEX) results, with one example being the speed with which requests for new services are delivered and fulfilled. The capital expenditure (CAPEX) results can also be significant, and in many cases the day one return on investment (ROI) pays for the cost of the solution. Note that both the OPEX and CAPEX costs, as well as the mentioned G«£absurdG«• investment in consulting services, will vary between organizations and be highly dependent on the selected solution.

- Mark Jamensky, VP Engineering & Operations, Embotics
Cartoon
White Papers
Register for Network Computing Newsletters
Current Issue
2014 Private Cloud Survey
2014 Private Cloud Survey
Respondents are on a roll: 53% brought their private clouds from concept to production in less than one year, and 60% ≠extend their clouds across multiple datacenters. But expertise is scarce, with 51% saying acquiring skilled employees is a roadblock.
Video
Slideshows
Twitter Feed