Posted by: MelanieYarbrough
Automation, Cloud Computing in 2010, Interop
You’re not going to wake up one morning and discover you’re in the private cloud. Just as there required planning to create your current infrastructure, there are certain steps you need to take before changing it. This year at Interop New York, the focus on the private cloud starts first with virtualization, and the key to getting the most out of virtualization is automation.
This method of managing provisioning and configuration involves codifying something that you’re currently doing manually. This will require different tools and levels of management as your infrastructure evolves.
Automation by Phase
- Server consolidation: Start off simple, utilizing scripts you’ve probably compiled on your own to simplify the manual processes. At this stage, vendor tools will be deployed to share these shortcuts across the enterprise.
- Infrastructure optimization: Support begins to expand beyond single vendors, and capacity management becomes an issue. Automation takes on the responsibility of patching and managing configuration.
- Automation & Orchestration: Another level of maturity in your virtualization strategy means adding provisioning, configuration standardization, compliance, running processes, application deployment, and self-service (or private cloud-like services) to the automated mix.
- Dynamic Data Center: Whether or not this means deploying a private cloud, reaching this level of maturity in your strategy heightens your application portability and calls for SLA-accompanied automation.
Not so fast
Bottom line is, if your application is faulty in the traditional model, it will be faulty in the young and hip model. There are opportunities to ease yourself into the water, however, to make sure that the applications you’re choosing to deploy atop a new infrastructure are the right ones. Rackspace’s recent OpenStack – their open source offering of their very own code – allows you to integrate the code you’d be utilizing in the cloud in your very own infrastructure. Not only can you get comfortable in your comfort zone, running the code in front of the eyes of your own team members before sending your babies out into the cloud, but you can monitor how your applications will run in that environment.
As with all technology that promises to deliver ease-of-use, there are many ways automation can go wrong. Before implementation, ensure each instance has been tested and that there are periodic checks in place once deployed.
Though the conversation at events such as Interop is dominated by cloud, there are specific and real-time practices that you can begin implementing today to prepare yourself for the somewhat cloudy future.