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 Srini Penchikala on Aug 12, 2008
In this interview Jerry Cuomo, an IBM Fellow and the Chief Technology Officer of WebSphere Division, talks with Floyd Marinescu on Virtualization, Cloud Computing, and WebSphere Virtual Enterprise (VE) product.
Jerry talked about what IBM is doing with WebSphere Virtual Enterprise to help virtualize middleware and application stack. Responding to a question about the conceptual framework for thinking about Virtualization, Jerry explained Virtualization concepts he calls Atomic and Molecular Virtualization.
I have been talking internally (at IBM) about things that I call "Atomic Virtualization" and "Molecular Virtualization". These are techniques for virtualizing servers, so atomic virtualization is about virtualizing a single server. It is about freeze drying the server, freeze drying the configuration and information that is used to pre-install and configure that server so that it can be hot deployed. That's interesting but that's a starting point, where it really starts to get cool is when you can create collections of these things, so that's what I call molecular virtualization. This actually allows you to freeze dry actual server topology, a group of servers. So you have your servers as your atoms and the bonds and links between those atoms, are your configurations, your best practices, that create actually a collection of your virtual servers, again, a virtual molecule. Now, again we build up on this by deploying that molecule to a virtual cluster and this becomes the first entry into clouds.
Speaking of how Software As a Service (SaaS) fits into Cloud Computing space, he said:
I absolutely think it fits in. I talk about this progression of virtualization kind of thinking about machine virtualization, server virtualization; I talked about atoms and molecules. There is an actual progression when you start to look at the platform itself. So virtualizing the platform, instead of going up to your cloud and saying: "Cloud, I need a machine to run this type of workload, I need this much CPU and I need this much memory", what you do when you talk to your cloud as a platform as a service you say "Cloud, I need some support to run my commerce application, I want to install a catalog of products". So you are not asking for servers, you are actually asking for it to do a job for you. So, take my application, here it is, here is how I want it to run, I may give you some operational policies, like response time goals, throughput goals. I may give you some business priorities, this application is more important than that application from a business prospective, I may give you some health policies, but I want the platform to manage it.
Jerry discussed the new features in the next release of WebSphere Application Server (Version 7) and its support for Virtualization.
In our next release of WebSphere version 7, we will have a virtual appliance option for you to order WebSphere. So absolutely this is becoming a way of doing business. Hardening the environment right down to embedding the Operating System as an embedded system. When you use your router at home it probably has a built-in operating system, it probably has some built-in storage, it probably has some middleware in there. But you don't know, you just use it for the function. So you see that as a reasonable model going forward. We also think it is interesting once we have these virtual appliances to create dispensers, things that allow you to take the virtual appliance, deploy it, manage it, meter it, monitor it, and again this is where some of our WebSphere Virtual Enterprise technologies are going to come into play to act as the dispenser of these virtual appliances.
Here is the interview (29:36 minutes).
Srini Penchikala currently works as Security Architect and has 17 yrs of experience in software product management.
Introducing SQLFire: a memory-optimized, high performance SQL database
The WebSphere Liberty Profile for Developers: An Introduction
Troubleshoot Java/.NET performance while getting full visibility in production
Introduction to WebSphere Liberty Profile
Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
An Unified Approach to Performance Management and Cost Management for Cloud
www.jinspired.com/products/jxinsight/meteringth...
A working application of metering the cloud in practice:
ABC for Cloud Computing
williamlouth.wordpress.com/2009/01/27/abc-for-c...
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.
2 comments
Watch Thread Reply