OpenStack Heat and OASIS TOSCA
Open Source and Open Standards working together
Genesis of a partnership…
I recall sitting at a lunch table, over a year ago at the OpenStack Summit in Hong Kong, with many of the Heat core developers discussing their ideas for developing the Heat-native HOT language. They were interested in hearing more about TOSCA since it was an open standard, had an impressive community of support and completed open source implementations; however, to them at that point, it was just a clunky XML standard that did not mesh well with the Heat world.
TOSCA â€śin YAMLâ€ť unveiledâ€¦
I gladly pulled out my laptop and showed them the very first draft of the TOSCA Simple Profile in YAML specification. Immediately, they seemed impressed that TOSCA had evolved so far, so fast towards something that could work hand-in-hand with the HOT language and be Heat developer-friendly. It was apparent that TOSCA could describe application components and relationships above OpenStack using abstractions of the Cloud IaaS resources that Heat was already focused on orchestrating using OpenStack services. In other words, Heat and HOT would take care of understanding how to best orchestrate the OpenStack IaaS resources and TOSCA could worry about everything else. The pieces fell into place, a partnership begun and a roadmap for a TOSCA Heat-Translator open-source implementation of TOSCA YAML was embarked upon.
That brings us to todayâ€¦
The OASIS Topology Orchestration for Cloud Applications (TOSCA) TC is poised to release its final Committee Specification Draft (CSD) towards having the TOSCA Simple Profile in YAML v1.0 specification become an official OASIS standard. It now seems a good time to share how far we have come, share some of the YAML innovations and hint at where TOSCA is going soon. To that end, this blog entry officially â€śkicks offâ€ť what will be the first in a series that TOSCA articles that explore modeling different areas and features of the TOSCA and shows how different types of applications (IaaS, PaaS, etc.) can be easily modeled using other open source technologies.
Some TOSCA topic areas in this series will cover in future blog articles:
Letâ€™s start by describing some of TOSCA Simple Profileâ€™s essential tenants and goalsâ€¦
Keep it simple for application developersâ€¦
Only what the developer needs to modelâ€¦
Composability and reuseâ€¦
TOSCA application templates are Portableâ€¦
Simple transparent packagingâ€¦
Work with DevOpsâ€¦
Agnostic of scripting languagesâ€¦
Capture the expert knowledge of architects, developers and testers
Still working hardâ€¦
I can vouch, first-hand that the TOSCA membership and the Heat-Translator team are really trying to deliver a well-designed yet simple modeling and orchestration standard that developers and companies can rely upon. One that will support them when creating applications for any delivery model (IaaS, PaaS, SaaS), for any provider while supporting the complete choice to usee whatever implementations or languages you want to use or try out (e.g., frameworks, runtimes, scripting, tooling). I hope that by reading upcoming blogs on various aspects of TOSCA, your appreciation for the hard work of its working groups and the TOSCA open source development communities will grow.
Here are some other helpful resources you can use to learn more about TOSCA
A round of thanksâ€¦
This open-open collaboration would not be possible without the support and review of Heat cores including: Steve Baker, Zane Bitter, Steve Hardy, Angus Salkeld and Thomas Spatzier along with the growing Heat-Translator developer community; most notably Sahdev Zala, Ton Ngo, Simeon Monov, Vahid Hashemian, Idan Moyal, Victor Hu, Xie Junan, Feihu Jiang and Srinivas Tadepalli.