Hi Peter,
Please see inline again.
BR/Calin
From:
"Bruun, Peter Michael (CMS RnD Orchestration)" <
peter-michael.bruun@hpe.com>
Date: Thursday, 10 February 2022 at 18:14
To: Calin Curescu <
calin.curescu@ericsson.com>, Chris Lauwers <
lauwers@ubicity.com>, "tosca@lists.oasis-open.org" <
tosca@lists.oasis-open.org>
Subject: RE: [tosca] RE: updated operational model
Hi Calin,
I concur totally with what you propose. I am sure that several of us have actually implemented something like this, and for me it works nicely.
I am, however, noting that some members object strongly to the idea of a dependency graph driving orchestration. Deriving a dependency graph from Relationships is, as far as I am aware, not part
of the our TOSCA standardization. So this would be completely up to the profiles to define.
[CC] I believe that this is the only outstanding feature of TOSCA. The representation graph is the dependency graph in my
opinion. I think that TOSCA 2.0 is freeing the orchestration from the Standard dependencies of TOSCA 1.3, so any set of relationship types in a profile can be used for different dependency graphs which are subsets of the representation graph.
[CC] I also believe that the orchestration should be constructed by following these different relationships/dependencies
subgraphs. This is for me the model driven approach . The beauty is that the orchestration can adapt to any size and form of the representation graph automatically (which can change as a consequence of an update or upgrade).
The ETSI standard does define how a template can refer to a previous/subsequent version of itself, although the way it is done there is perhaps not the best design.
[CC] I think we can solve this with service template versioning in TOSCA directly.
Peter
From: Calin Curescu [mailto:
calin.curescu@ericsson.com]
Sent: 10. februar 2022 17:50
To: Bruun, Peter Michael (CMS RnD Orchestration) <
peter-michael.bruun@hpe.com>; Chris Lauwers <
lauwers@ubicity.com>;
tosca@lists.oasis-open.org Subject: Re: [tosca] RE: updated operational model
Hi Peter,
Some answers/opinions inline