[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: Agenda for Tuesday 11/16/2021 TOSCA Language Ad-Hoc meeting
|
I’m redistributing Peter’s message since he is unable to send to the tosca list directly. From: Bruun, Peter Michael (CMS RnD Orchestration) <peter-michael.bruun@hpe.com>
Hi Tal, Thank you for the great slides today. Let me try to see if I understand you correctly – I probably don’t.
J When we move away from the strict modality of lifecycles involved in topology *creation*, what I see is rather one of the Orchestration *managing* a topology over time. So “TOSCA Orchestration” is not just a question of creating the topology, so that when done, there would be nothing more to do. Instead, each Node and Interface of a node may hold multiple state-dimensions, some of which could be related to creation, others to maintaining other aspects of the infrastructure associated with the node representations. At least that is what I am hearing, when you talk about an on-going relationship between the Executor Context and the Node/Interface scopes, in which Events may keep coming for hours, days, months while the topology
is being *maintained*. Does this capture some of your thinking, or am I misunderstanding you? I mentioned, and you kind of nodded, that we might even consider the possibility that Events may even drive the Resolver to mutate the Representation Graph – or is that out-of-scope? Of course if that can happen,
then it will blur the distinction between what is mutable and immutable. Best regards, Peter P.S. @Chris – I am still unable to send to the TOSCA distribution list – can I ask you to distribute, please? From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of Chris Lauwers
Thanks, |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]