[Capi-bof] Cloud Standards Roadmap

Tue Mar 24 06:19:44 CDT 2009

Yes - at least for now.

Trust me, if it is important for this initiative then it will come
back, at the right time.

On Tue, Mar 24, 2009 at 11:06 AM, Paulo Calcada <pcalcada at gmail.com> wrote:
> What you are suggesting is that we could remove GRID from the  Cloud
> Computing diagram, because GRID guys will use Cloud / virtual data centers?
>
> Is not a bad idea :)
>
> Paulo
>
> 2009/3/24 Alexis Richardson <alexis.richardson at gmail.com>
>>
>> IMHO:
>>
>> We should look at what cloud / vitual data center providers are
>> actually DOING and work from there.  People have done good work
>> summarising APIs as a starting point for the next steps.  GRID people
>> will know how to position GRID around this.
>>
>> a
>>
>>
>>
>>
>>
>> On Tue, Mar 24, 2009 at 10:56 AM, Paulo Calcada <pcalcada at gmail.com>
>> wrote:
>> > Yes, definitely, GRID is something that could be "sold" directly to any
>> > of
>> > the upper layers, but that is not a problem, the same is
>> > happening with IaaS, you could use it directly as a service or you could
>> > use
>> > it to provide the supporting layer to and PaaS and the to the SaaS :)
>> >
>> > I come from an Higher education Institution and for me we could
>> > perfectly
>> > use the wikipedia definition:
>> >
>> > "Grid computing (or the use of a computational grid) is the application
>> > of
>> > several computers to a single problem at the same time – usually to a
>> > scientific or technical problem that requires a great number of computer
>> > processing cycles or access to large amounts of data."
>> >
>> > So, GRID, in my prespective is something that we must have inside a
>> > Cloud
>> > Computing diagram, and for me is also clear that we should put here all
>> > the
>> > questions related to the "heavy" computing power.
>> >
>> >
>> > Paulo
>> >
>> > 2009/3/24 Alexis Richardson <alexis.richardson at gmail.com>
>> >>
>> >> GRID is a tricky one.  When it defines an application execution model
>> >> (eg "tasks") it is PaaS.  When it speaks to the management of general
>> >> infra, I think it is IaaS.  And of course, you could have a SaaS
>> >> offering for grid computing.  So IMO, GRID is orthogonal and "a
>> >> technology".
>> >>
>> >> a
>> >>
>> >>
>> >> On Tue, Mar 24, 2009 at 10:42 AM, Paulo Calcada <pcalcada at gmail.com>
>> >> wrote:
>> >> > Hello Sam,
>> >> >
>> >> > I think that it would be very important adding to your "model" a
>> >> > layer
>> >> > dedicated to the Calculus (CPU or computing power) question, such as
>> >> > GRID
>> >> > computing or things like AMD Render Fusion.  I think that both IaaS,
>> >> > PaaS or
>> >> > SaaS are layers well defined, but none of them contains attributes
>> >> > that
>> >> > could be considered useful to the computing or calculus power
>> >> > paradigm.
>> >> >
>> >> > In the follow up of other things that I've presented, and also in the
>> >> > same
>> >> > perspective that others also have done, I could resume my (naive)
>> >> > view
>> >> > or
>> >> > model in the following layered sequence:
>> >> >
>> >> > SaaS - end-users
>> >> > PaaS - developers and entrepreneurs
>> >> > IaaS - IT administrators
>> >> > GRID or other  complex processing solutions that would deploy
>> >> > specific
>> >> > large
>> >> > amount of computing power - scientific or technical advance solutions
>> >> >
>> >> > Paulo
>> >> > www.cloudviews.org
>> >> >
>> >> > 2009/3/24 Sam Johnston <samj at samj.net>
>> >> >>
>> >> >> Morning all,
>> >> >>
>> >> >> I have added the Cloud Standards Roadmap to the Cloud Computing
>> >> >> Community
>> >> >> Wiki. Please review it and let me know if there are any efforts I
>> >> >> have
>> >> >> missed (or better yet, add them to the wiki). We can use this
>> >> >> document
>> >> >> as an
>> >> >> authorative source to track standardisation efforts and hopefully
>> >> >> prevent
>> >> >> duplication/proliferation.
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Sam
>> >> >>
>> >> >> ---------- Forwarded message ----------
>> >> >> From: Sam Johnston <samj at samj.net>
>> >> >> Date: Tue, Mar 24, 2009 at 11:06 AM
>> >> >> Subject: [Sam Johnston] Cloud Standards Roadmap
>> >> >> To: samj at samj.net
>> >> >>
>> >> >> Almost a year ago in "Cloud Standards: not so fast..." I explained
>> >> >> why
>> >> >> standardisation efforts were premature. A lot has happened in the
>> >> >> interim
>> >> >> and it is now time to start intensively developing standards,
>> >> >> ideally
>> >> >> by
>> >> >> deriving the "consensus" of existing implementations.
>> >> >>
>> >> >> To get the ball rolling I've written a Cloud Standards Roadmap which
>> >> >> can
>> >> >> be seen as an authorative source for information spanning the
>> >> >> various
>> >> >> standardisation efforts (including identification of areas where
>> >> >> effort
>> >> >> is
>> >> >> required).
>> >> >>
>> >> >> Currently it looks like this:
>> >> >>
>> >> >> Cloud Standards Roadmap
>> >> >>
>> >> >> The cloud standards roadmap tracks the status of relevant standards
>> >> >> efforts underway by established multi-vendor standards bodies.
>> >> >>
>> >> >> Layer Description Group Project Status Due
>> >> >> Client  ?  ?  ?  ?  ?
>> >> >> Software (SaaS) Operating environment W3C HTML 5 Draft 2008
>> >> >> Event-driven scripting language ECMA ECMAScript Mature 1997
>> >> >> Data-interchange format IETF JSON (RFC4627) Mature 2006
>> >> >> Platform (PaaS) Management API  ?  ?  ?  ?
>> >> >> Infrastructure (IaaS) Management API OGF Cloud Infrastructure API
>> >> >> (CIA)
>> >> >> Formation 2009
>> >> >> Container format for virtual machines DMTF Open Virtualisation
>> >> >> Format
>> >> >> (OVF) Complete 2009
>> >> >> Descriptive language for resources DMTF CIM Mature 1999
>> >> >> Fabric  ?  ?  ?  ?  ?
>> >> >> Other standards efforts
>> >> >>
>> >> >> Cloud Standards Group
>> >> >>
>> >> >> Cloud Computing Reference Model
>> >> >> Cloud Computing Stack
>> >> >> Cloud Platform Reference Architecture
>> >> >>
>> >> >> CCIF UCI - A "singular programmatic point of contact that can
>> >> >> encompass
>> >> >> the entire infrastructure stack as well as emerging cloud centric
>> >> >> technologies all through a unified interface"
>> >> >>
>> >> >> Vendor-owned standards
>> >> >>
>> >> >> Infrastructure
>> >> >>
>> >> >> Amazon EC2 API
>> >> >> AppNexus API
>> >> >> ElasticHosts API
>> >> >> Eucalyptus (which uses the Amazon EC2 API)
>> >> >> FlexiScale API
>> >> >> Globus Numbus (which uses the Amazon EC2 API and WSRF)
>> >> >> GoGrid API
>> >> >> OpenNebula API
>> >> >> SliceHost API
>> >> >> Sun Cloud APIs
>> >> >>
>> >> >> Fabric
>> >> >>
>> >> >> F5 iControl (Networking)
>> >> >>
>> >> >> Other resources
>> >> >>
>> >> >> Apache Tashi
>> >> >> OASIS Reference Model for Service Oriented Architecture
>> >> >>
>> >> >> Please check the Cloud Computing Community Wiki for the latest
>> >> >> version
>> >> >> as
>> >> >> this information will be quickly dated. If you have any updates
>> >> >> please
>> >> >> feel
>> >> >> free to contribute them.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > >
>> >> >
>> >>
>> >>
>> >
>> >
>> > >
>> >
>>
>>
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "Cloud Standards" group.
> To post to this group, send email to cloud-standards at googlegroups.com
> To unsubscribe from this group, send email to
> cloud-standards+unsubscribe at googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/cloud-standards?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>