These will be placed on the OGF site when possible. Thanks to Alex!

OGF34, Oxford, United Kingdom

Wed, Mar 14 2012, 15:30 BST

Session Leader: Thijs Metsch

Note Taker: Alexander Papaspyrou

Michael Behrens (PaaS, <insert link to preso here>):

spec for PaaS wanted that outlines architecture components
within OCCI: make inventory of PaaS, use case-based approach, requirements
also: contact providers (CloudFoundry, OpenShift)
extend J2EE model to multiple providers of building blocks regarding service delivery
important: design for mobile devices!
re OCCI: should provide the interfacing to the big players
The data layer in PaaS should be location transparent
Need to clear out what the elements in PaaS mean
define the platform first: what are the components, and how do they relate to the infrastructure
platform can be considered as means to provide
every PaaS is different, needing its own description
even application components are somewhat differing from each other
start with extensions like node, key value store: simple things
what about a registry?
does the DRMAA approach fit into the PaaS model
CompatibleOne concept: OCCI usage on multiple levels, in the sense of a SOA
take a look at service management
in fact, everything is there in OCCI
- means for describing services
- as a resource
- in a standardised way
main question is: how to describe the service collection?
what about intercloud?
- brokerage services
- big data access / movement
service registry profile for certain domains
take a look at telco platforms
make a directory of common categories

James Marshal from CompatibleOne volunteers to help with inventory

-- Interlude --

Connect to Inder