[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tosca] Groups - TOSCA Imperative Workflows supporting custom workflow language uploaded
ÂÂÂÂÂÂÂÂÂ Iâm not sure I agree that âBring Your Own Orchestratorâ is really the main promise of TOSCA. In fact, I firmly believe that TOSCA very much wants to be a full orchestration language that allows for ânativeâ TOSCA orchestration (itâs actually in the name J ). The main promise of TOSCA is that itâs technology and platform-independent, which (in theory) allows for portable service templates.
ÂÂÂÂÂÂÂÂÂ That doesnât mean that in practice TOSCA should be used for all (or even most) orchestration tasks. Because of its technology and platform-independent approach, TOSCA is in fact perfectly positioned to act as an âumbrellaâ orchestrator that uses what I call a âdecompose and delegateâ approach: decompose high-level service descriptors into smaller components, where each of these components could be orchestrator by their own (presumable domain-specific) orchestrators. For example, it would be perfectly natural to âdelegateâ orchestration of parts of a TOSCA service to Kubernetes or to use Ansible for other components.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]