|By Reuven Cohen||
|August 25, 2008 04:00 AM EDT||
Reuven Cohen's "ElasticVapor" Blog
Over the last few weeks I've been engaged in several conversations about the need for a common, interoperable and open set of cloud computing standards. During these conversations a recurring theme has started to emerge. A need for cloud interoperability or the ability for diverse cloud systems and organizations to work together in a common way.
In my discussion yesterday with Rich Wolski of the Eucalyptus project he described the need for a "CloudVirt" API similar to that of the Libvirt project for virtualization. For those of you that don't know about libvirt, it's an open source toolkit which enables a common API interaction with the virtualization capabilities of recent versions of Linux (and other OSes).
I would like to take this opportunity to share my ideas as well as get some feedback on some of the key points I see for the creation of common cloud computing reference API or standard.
* Cloud Resource Description
The ability to describe resources is (in my opinion) the most important aspect of any standardization effort. One potential avenue might be to use the Resource Description Framework proposed by the W3C. The Resource Description Framework (RDF) is a family of specifications, originally designed as a metadata data model, which has come to be used as a general method of modeling information through a variety of syntax formats. The RDF metadata model is based upon the idea of making statements about Web resources (or Cloud Resources) in the form of subject-predicate-object expressions, called triples in RDF lingo. This standardized approach could be modified as a primary mechanism for describing cloud resources both locally and remotely.
* Cloud Federation (Cloud 2 Cloud)
The holy grail of cloud computing may very well be the ability to seamlessly bridge both private clouds (datacenters) and remote cloud resources such as EC2 in a secure and efficient manor. To accomplish this a federation standard must be enabled. One of the biggest hurdles to over come in federation is the lack of clear definition to what federation is.
So let me take a stab at defining it.
Cloud federation manages consistency and access controls when two or more independent geographically distinct clouds share either authentication, files, computing resources, command and control or access to storage resources. Cloud federations can be classified into three categories: peer-to-peer, replication, and hierarchical. Peer 2 peer seems to be the most logical first step in creating a federation spec. Protocols like XMPP, P4P and Virtual Distributed Ethernet may make for good starting points.
* Distributed Network Management
The need for a distributed and optimized virtual network is an important aspect in any multi-cloud deployment. One potential direction could be to explore the use of VPN or VDE technologies. My preference would be to use VDE, (Virtual Distributed Ethernet). A quick refresher, a VPN is a way to connect one or more remote computers to a protected network, generally tunnelling the traffic through another network. VDE implements a virtual ethernet in all its aspects, virtual switches, virtual cables. A VDE can also be used to create a VPN.
VDE interconnects real computers running (through a tap interface), virtual machines as well as the other networking interfaces through a common open framework. VDE supports heterogeneous virtual machines running on different hosting computers and could be the ideal starting point. Network shaping and optimization may also play an important role in the ability to bridge two or cloud resources.
Some network optimization aspects may include;
- Compression - Relies on data patterns that can be represented more efficiently.
- Caching/Proxy - Relies on human behavior , accessing the same data over and over.
- Protocol Spoofing - Bundles multiple requests from chatty applications into one.
- Application Shaping - Controls data usage based on spotting specific patterns in the data and allowing or disallowing specific traffic.
- Equalizing - Makes assumptions on what needs immediate priority based on the data usage.
- Connection Limits - Prevents access gridlock in routers and access points due to denial of service or peer to peer.
- Simple Rate Limits - Prevents one user from getting more than a fixed amount of data.
* Memory Management
When looking at the creation of compute cloud memory tends to be a major factor in the performance of a given virtual environment, whether a virtual machine or some other application component. Cloud memory management will need to involve ways to allocate portions of virtual memory to programs at their request, and freeing it for reuse when no longer needed. This is particularly important in "platform as a service" cloud deployments.
Several key memory management aspects may include;
- Provide memory space to enable several processes to be executed at the same time
- Provide a satisfactory level of performance for the system users
- Protect each program's resources
- Share (if desired) memory space between processes
- Make the addressing of memory space as transparent as possible for the programmer.
* Distributed Storage
I've been working on creating a cloud abstraction layer called "cloud raid" as part of our ElasticDrive platform and have been looking at different approaches for our implementation. My initial idea is to connect multiple remote cloud storage services (S3, Nirvanix, CloudFS) for a variety of purposes. During my research the XAM specification began to look like the most suitable candidate. XAM addresses storage interoperability, information assurance (security), storage transparency, long-term records retention and automation for Information Lifecycle Management (ILM)-based practices.
XAM looks to solve key cloud storage problem spots including;
- Interoperability: Applications can work with any XAM conformant storage system; information can be migrated and shared
- Compliance: Integrated record retention and disposition metadata
- ILM Practices: Framework for classification, policy, and implementation
- Migration: Ability to automate migration process to maintain long-term readability
- Discovery: Application-independent structured discovery avoids application obsolescence
Potential Future Additions to the API
The virtualization of I/O resources is a critical part of enabling a set of emerging cloud deployment models. In large scale cloud deployments a recurring issue has the ability to effectively management I/o resources whether on a machine level or network. One of the problems a lot of users are encountering is that of the "nasty neighbor" or a user who has taken all available system I/o resources.
A common I/o API for sharing, security, performance, and scalability will need to be addressed to help resolve these issues. I've been speaking with several hardware vendors on how we might be able to address this problem. This will most like have to be done at a later point after a first draft has been released.
* Monitoring and System Metrics
One of the best aspects of using cloud technology is the ability to scale applications in tandem to the underlying infrastructure and the demands placed on it. Rather then just scaling on system load, users should have the ability to selectively scale on other metrics such as response time, network throughput or other metrics made available. Having a uniform way to interact with system metrics will enable cloud providers and consumers a common way to scale applications.
Security & Auditability.
In my conversations with several wall street CIO's the questions of both security and cloud transparency with regards to external audits has come up frequently.
My list of requirements is by no means a complete list. Cloud computing encompasses a wide variety of technologies, architectures and deployment models. What I am attempting to do is address the initial pain points whether you are deploying a cloud or just using it. A lot of what I've outlined may be better suited to a reference implementation than a standard, but none the less I thought I'd put these out ideas out for discussion.
-- Update --
Looks like I've forgotten an obvious yet important aspect to my cloud standards. Authentication. Maybe something like OAuth or OpenID could form the basis for this as well. I'll need to do some more thinking on this one.
|MiamiWebDesigner 08/25/08 06:25:14 AM EDT|
Kudos to the Cloud Crowd for Re-Inventing the Wheel!
One thing 30 years in the IT industry has taught me is that the more things change, the more they stay the same. Another is that the only memory we seem to access is short-term. Yet another is that techno-marketeers rely on that, so they can put labels like "revolutionary" and "innovative" on platforms, products and services that are mere re-inventions of the wheel ... and often poor copies at that.
A good example is all the buzz about "Cloud Computing" in general and "SaaS" (software as a service) in particular:
Both terms are bogus. The only true cloud computing takes place in aircraft. What they're actually referring to by "the cloud" is a large-scale and often remotely located and managed computing platform. We have had those since the dawn of electronic IT. IBM calls them "mainframes":
The only innovation offered by today's cloud crowd is actually more of a speculation, i.e. that server farms can deliver the same solid performance as Big Iron. And even that's not original. Anyone remember Datapoint's ARCnet, or DEC's VAXclusters? Whatever happened to those guys, anyway...?
And as for SaaS, selling the sizzle while keeping the steak is a marketing ploy most rightfully accredited to society's oldest profession. Its first application in IT was (and for many still is) known as the "service bureau". And I don't mean the contemporary service bureau (mis)conception labelled "Service 2.0" by a Wikipedia contributor whose historical perspective is apparently constrained to four years:
Instead, I mean the computer service bureau industry that spawned ADAPSO (the Association of Data Processing Service Organizations) in 1960, and whose chronology comprises a notable portion of the IEEE's "Annals of the History of Computing":
So ... for any of you slide rule-toting, pocket-protected keypunch-card cowboys who may be just coming out of a 40-year coma, let me give you a quick IT update:
1. "Mainframe" is now "Cloud" (with concomitant ethereal substance).
2. "Terminal" is now "Web Browser" (with much cooler games, and infinitely more distractions).
3. "Service Bureau" is now "SaaS" (but app upgrades are just as painful, and custom mods equally elusive).
4. Most IT buzzwords boil down to techno-hyped BS (just as they always have).
Bruce Arnold, Web Design Miami Florida
Feb. 7, 2016 07:00 AM EST Reads: 101
Feb. 6, 2016 03:30 PM EST Reads: 709
Feb. 6, 2016 03:15 PM EST Reads: 328
Feb. 6, 2016 02:30 PM EST Reads: 355
Feb. 6, 2016 01:30 PM EST Reads: 345
Feb. 6, 2016 01:00 PM EST Reads: 541
Feb. 6, 2016 11:00 AM EST Reads: 121
Feb. 6, 2016 11:00 AM EST
Feb. 6, 2016 09:00 AM EST
Feb. 6, 2016 05:00 AM EST Reads: 332
Feb. 5, 2016 09:00 PM EST Reads: 775
Feb. 2, 2016 02:00 PM EST Reads: 406
Feb. 2, 2016 04:30 AM EST Reads: 839
Feb. 1, 2016 05:00 AM EST Reads: 923
Jan. 31, 2016 09:00 PM EST Reads: 718
Jan. 31, 2016 07:15 PM EST Reads: 1,135
Jan. 31, 2016 10:00 AM EST Reads: 1,201
Jan. 31, 2016 10:00 AM EST Reads: 798
Jan. 30, 2016 07:45 PM EST Reads: 775
Jan. 30, 2016 03:45 PM EST Reads: 1,259