Cloud Architecture and Architectural Layers
Building a Dev/Test Cloud Using Eucalyptus Reference Architectures
When we talk to IT organizations interested in transforming their data centers into private or hybrid cloud deployment models using open source Eucalyptus software, the question we'll often get is, "How do we get started?" To answer this question, we've published a series of Reference Cloud Architectures which are specific to common use cases in the field. Let's take a look at how the Dev/Test Reference Cloud Architecture and its architectural layers might be used as a framework for building a private or hybrid cloud for app devevelpment and QA purposes.
In many IT organizations, a gap exists between developers and the IT operations team. Developers are looking to create new applications and get them out the door quickly. At the same time, IT operations teams are constantly trying to maintain and control the integrity and balance of IT infrastructure through the use of policies and procedures. Because of this inherent conflict between the speed that developers need and the control that operations requires, there are often delays in provisioning the infrastructure and resources that developers require. This gap often leads to time-to-market delays, lost productivity, and the inability to innovate fast enough.
With our cloud architectures and architectural layers, organizations can deploy an AWS-compatible private or hybrid cloud that provides developers with the same flexibility and agility they've come to expect from the public cloud, while allowing IT operations teams to maintain control and costs. The Eucalyptus cloud architecture provides, as one of the main features of the solution, self-service resource configuration and provisioning, so developers and QA engineers can streamline workflow processes and get their jobs done quickly and efficiently. Developers don't need to submit an IT ticket and wait for weeks or even months to get the resources they need. Developers can quickly provision and configure the compute, storage, and networking resources they need on demand through a self-service web-based user console.
So where does the Reference Cloud Architecture fit in? The Reference Cloud Architecture and architectural layers provide a deployment template for IT operations teams to assist them in setting up and deploying a Eucalyptus private or hybrid cloud. The Reference Cloud Architecture provides the scope of resources they need and the recommended deployment model for the architectural layers specific to their use case (in this case, Dev/Test).
This is important for two reasons: First, it prescribes a bill of materials and guidelines on how to deploy the Eucalyptus cloud architecture on it. Second, the Reference Architecture provides a "recipe" for the bill of materials needed to run the cloud.
In the case of a Dev/Test environment, Infrastructure as a Service (IaaS) provides the automation for provisioning and de-provisioning resources as application and workload demand ebbs and flows. The Reference Architecture provides design choices for the IaaS solution, including physical resources required and a deployment topology.
The Reference Cloud Architecture also outlines technologies commonly deployed with Eucalyptus to provide a complete IaaS solution – such as configuration management, monitoring, and workflow management.
Dev/Test, along with Scalable Web Services, is a great place to get started with Eucalyptus and the Reference Cloud Architecture provides you the tools to get started successfully.