2014-07-21 SC minutes

Minutes: TOSCA Interop SC – 21 July 2014

Attendees: Richard Probst, Karsten Beins, Peter Gibbels, Juergen Meynert

Preparing for ODCA Forecast self-service kiosk (conference is 22 September)
3 important deadlines:
-
1 August – provide  1 slide  describing a TOSCA-related product or project
-
22 August – provide  5 to 10 seconds of video  of a TOSCA-related tool (format HD mpeg4)
-
Deadline TBD  – post a  2- to 3-minute video  to YouTube, to be linked to from ODCA kiosk

Richard clarified focus of “interop” showcase is different in 2014 than 2013. Last year, focus was to show portability of TOSCA models between independent implementations, to prove the power of the specification. This year, focus is to  show rapid growth of TOSCA-related ecosystem. This year, no requirement to prove portability and interoperability, merely an opportunity to describe products or projects supporting TOSCA semantics. Last year, portability; this year, ecosystem!

Discussion of importance of OpenStack as one key platform to drive TOSCA adoption. Possible that PaaS work in OpenStack or other community (e.g. CloudFoundry) could create model-based alternatives to TOSCA? Especially since PaaS projects  may not consider infrastructure relevant. But moving existing applications to the cloud must  not  require re-writing them to use a PaaS, so TOSCA is necessary to get critical workloads onto clouds, and divergence of modeling approaches will increase costs to customers and vendors. Conclusion: Urgent need to promulgate TOSCA semantics in PaaS  projects in OpenStack and other communities.

Status of deck for ODCA Forecast kiosk
-
Slides completed and reviewed with TC
-
Voice-over script under development; will present to TC soon
-
Script may drive minor changes to slides
-
Ton Ngo from IBM has volunteered to turn slides into video, and insert 5- to 10-second video clips when ready

Question to pose to ODCA Forecast attendees (and others learning about TOSCA): What can I do now to adopt this technology? What can a tool vendor (producer) do? What can an enterprise architect (consumer) do?

Adoption of TOSCA is easier if earlier in design lifecycle. How do we drive awareness of TOSCA to early-stage designers?