Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Sep 01, 2011
Aeolus is an open source project intended to provide solutions for managing packs of virtual machines across various private and public clouds. The project has been started by Red Hat, but they do not want to own the project, inviting other companies to join forces with them in creating an open cloud management solution.
Aeolus is very similar to what RightScale does, who provides a cloud management console and an unified API that works across Cloud.com, Eucalyptus, and Rackspace, while support for EC2 is to be added in the near future. Aeolus currently runs on a 64-bit machine with Red Hat Enterprise Linux 6.1 or Fedora 14 installed, and can be used to administer virtual images deployed on Amazon Elastic Compute Cloud (EC2), Rackspace Cloud Hosting, Red Hat Enterprise Virtualization (RHEV), VMware vSphere and/or Eucalyptus.
Some have compared Aeolus with OpenStack (Register, ITWorld), but they do not compare with each other. OpenStack is meant to be an open source cloud, like Amazon EC2, and it is used by Rackspace for their Cloud Hosting solution. Aeolus is not a new cloud provider, but a solution for creating machine templates which are then used to create Windows or Linux virtual images that are deployed on the user’s choice of cloud, including on Rackspace. The benefit of such a solution is twofold: offers a single point of managing all cloud deployments and escapes vendor locking by being able to move images around as desired.
Aeolus is made up of several projects: Conductor –managing tool for cloud resources-, Composer –tool for creating images from templates-, Orchestrator –dealing with groups of images-, and HA Manager –providing high availability though isolation, recovery and notification. The source code of the project and its dependencies are hosted on GitHub.
As with other open source projects, its success depends on building a healthy and vibrant community around it. Red Hat has a good reputation with Linux Fedora and JBoss, which might encourage some developers to join the Aeolus project. If others will not participate, it will remain for Red Hat to carry on the efforts by themselves.
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Identity and Access Management for Cloud Apps: A Buyer's Guide
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply