OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [tosca] Introducing Turandot: A TOSCA orchestrator for Kubernetes


Sure!

On Wed, Apr 22, 2020 at 5:16 PM Paul L. <paul.lipton@live.com> wrote:

Hi Tal,

Â

Thanks for sharing. Iâve asked Chris to brief us on his new TOSCA orchestrator at tomorrowâs TC meeting, after a walkthrough of the new CSD01 candidate. Would you be interested in doing the same for Turandot at our May 12th TC meeting?

Â

Thanks again,

Paul

Â

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Tal Liron
Sent: Wednesday, April 22, 2020 6:02 PM
To: tosca@lists.oasis-open.org
Subject: [tosca] Introducing Turandot: A TOSCA orchestrator for Kubernetes

Â

This one has been a long time coming!

Â

The Puccini project is intentionally designed to purely address the issue of TOSCA and not have any opinion about orchestration. The approach there is "BYOO": Bring Your Own Orchestrator.

Â

Well, now it's time to bring one in!

Â

The Turandot orchestrator is, at its essence, Puccini running as a Kubernetes operator. Using either a built-in inventory, or a robust external inventory product, one can register CSARs as annotated service templates, and then instantiate them into Kubernetes resources.

Â

Included is a TOCA profile for Kubernetes, which very closely matches the Kubernetes specs themselves with some TOSCA quality-of-life details added on top. KubeVirt is given the same treatment, and indeed one can use it to run full-blown virtual machines within Kubernetes. Multus is also supported for advanced networking via Kubernetes CNI.

Â

TOSCA policies govern workload composition via TOSCA substitution mapping. Multi-cluster workloads are handled by "delegates" -- Turandot can install itself on a another cluster, send the service templates there, and let the remote Turandot operator manage its Kubernetes resources.

Â

Included is a complex multi-cluster MANO example, which showcases an abstract network service that uses provisioning policies to substitute the network functions for VNFs, CNFs, and even an out-of-cluster PNF. The data plane is itself a node template that can be substituted for various technologies.

Â

As of now, Turandot is not quite ready for everyone to use. Documentation is lacking, and there need to be many more (and simpler) examples. However, it can be demoed. :) If there's interest, I would be more than happy to show it in action in an upcoming TOSCA TC meeting.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]