OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

Thanks to everyone for the productive Wednesday meetings. It sounds like we're converging on some high-level concepts:

• We want to create service templates that model the topology of microservices-based services
• We want to create mechanisms for deploying those services on Kubernetes
• In addition, we also want to deploy those services on other platforms (e.g. directly using Docker or using Nomad, Functions as a Service, etc.)

From that discussion, it appears that we may want to define (at least) three separate profiles:

• A  Microservices profile that focuses on service topology
• A Kubernetes profiles that aligns with Kubernetes resources
• A Platform profile that models the infrastructure on which services can be deployed ("orchestrated")

Based on the discussions, I created the following two skeleton profiles:

• A Platform profile (in https://github.com/oasis-open/tosca-community-contributions/tree/master/profiles/community/tosca/platform)
• A Kubernetes profile (in https://github.com/oasis-open/tosca-community-contributions/tree/master/profiles/community/tosca/kubernetes). Note that this profile reflects the "substitution mapping" design approach (https://github.com/oasis-open/tosca-community-contributions/blob/master/profiles/community/tosca/kubernetes/README.md#substitution-mapping-approach). The capability-based approach needs to be fleshed out further.

If you have a chance, please review these profiles so we can have a more in-depth discussion during our next meeting.

Thanks,

Chris