Hi, Thanks to all of you for helping the last weeks and months preparing the sessions we just had at the OGF 42 event in London. Also many thanks to those who attended in person. Again: it is the community who uses, lives and defines the standard :-) Here are some rough meeting notes I took over the course of the OGF event. Excuses for the bit longer list - we had a total of 4 sessions with plenty of discussions. Many thanks again, -Thijs, Andy * Roadmap ** Plan to release update of the documents asap ** Ideally finish drafts next month - public comment later this year ** Note: Backward compatibility is key and must! * Introducing the errata of the Core spec. ** Walked through the updates made to the core specification ** Topics to be addressed: *** Required and Mutability members of 'Attribute' should be 1 *** Type of the Attributes should be Object, Hash, List * Introducing the errata of the Infrastructure spec. ** Topics to be addressed: *** Move over ssh key & user_data mixins into Master branch *** Add all error states to the enum of possible states. *** Update the usage of related according to core specification * Introducing the new ToC of the HTTP protocol spec ** Discussion of a new ToC was conducted and agreed upon. - to be circulated soon... ** Topics to be addressed: *** Allow 202 return code upon creation? *** pagination support *** Writeup import and export functionalities on collections to allow for interop between e.g. CIMI/TOSCA/OVF/... with OCCI *** Queries/Filters on the QI *** Queries/Filters on collections * Demo of visualizing OCCI entities and their relationships using D3 ** Gregory demoed the visualizations of any kind of OCCI entities relationship using D3 visual library. * Discussion of JSON rendering ** Topics to be addressed: *** Links of an entity should be fully rendered not a list of URIs *** TBC: addition of a pattern member to the attribute? * Introducing the SLA draft ** Topics to be addressed: *** State models require update with respect to actions available *** Name clashes for the attribute names in the terms needs to resolved *** Make note in spec: If one service term is violated the agreement is violated * Introducing the Platform draft ** Topics to be addressed: *** Add a set of generic mixins for e.g. databases - maybe take look at Bluemix for input help. * Introducing the Billing draft ** Needs to be written up as a spec. * Introducing Inter-PaaS ** TBC * OCCI Monitoring demo ** Augusto introduced his demo implementation of a Monitoring framework using OCCI ** It became clear sth like notification links can be useful - some writeup is under way... * erOCCI implementation/ OCCIware consortium updates ** Jean introduced the OCCIware consortium ** Gave a brief update on the erOCCI implementation * rOCCI discussions ** Boris quickly gave an overview of the rOCCI framework from client to server side. And noted the usage in EGI alongside the parts the rOCCI server can speak too (ONE, EC2, ...) * OCCI/DRMAA v2 bindings ** Meeting took place Wednesday ** Peter walked through the OCCI DRMAA draft specification and cleaned-up minor details ** Biggest change: *Sessions will be managed via HTTP not explicitly through OCCI entities. ** Started dummy implementation to validate the concepts. Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052