1. Discussion with OASIS TOSCA
Nigel Davis (Ciena)

2. Agenda Metamodel comparison – update
Aim for formal working together?
Relationship with Kubernetes – discussion
Helm charts…
System design and placement – whiteboard
Pattern libraries
Intertwining of patterns
Realizing the system
Recursive constraints and the spec pattern – whiteboard
Rules for constraint evolution
Allowing any level to drift
“Pruning and refactoring” the model to arrive at the spec
Supporting tools
Expressing constraints

3. All below are modelled in UML in ONF
Controller connects to control port to access properties (i.e. they are simply exposed as are properties through any port OR properties are accessed via a controller that it talks to about the properties.
System Spec
Component Spec?
System Scheme Spec
Component
Ports
A port binds to a port forming an interface. An interface has zero length. An interface can form based upon capability compatibility and policy. The interface has constraints. This may be what is in “relationship type”??
Ports
A component blown open
Anything with ports is a component
Capability to be controlled
A System of components
Purpose capability
Purpose requirement
I believe this is workflow. ONF does not cover workflow
Placement requirement

4. Relationship with Kubernetes
Kubernetes is an Orchestrator
Uses Helm charts for deployment of system

5. System design and placement
Components interconnect to form systems (pattern)
Specifically decorated components interconnect to recursively form specific system patterns (pruned and refactored pattern)
Specific system patterns intertwine to form specific solution architectures (in a guideline library)
Specific solution architectures intertwine to form specific designs (in the service catalogue)
Specific designs need to be stretched across the realization environment (placement)

8. Function
Function
Interfaces
Constraint
Constraints may be shared between interface cases
The component system pattern is sufficient with pointers between the ports to show the binding
Component
Component
Capability
Needs
Grey ports are any function, specializations not considered
Port
Role
Interface is the touching of two facets. A point is the binding of two ports.
Etc
Interface
Binding between compatible ports
(represented by one or two way pointers)

9. Extracting concealed forwarding
Function
Function
Conceptually …
An atomic function is at a single point
Two functions cannot be at the same point
Two adjacent atomic functions touch such that the adjacency is zero length
A complex functions is made by joining multiple atomic functions as a system of adjacent atomic functions
The atomic functions forming a complex function are necessarily spread over a space
Assuming normal space, for any particular complex function, regardless of the choice of specific arrangement of atomic functions some atomic functions that need to be adjacent to form the logic of the system cannot be actually adjacent as they are at a distant and hence must be joined via atomic functions that simply transfer information. This transfer forms a virtual adjacency.
Adjacency between two complex functions can be represented as if a true adjacency, as for atomic functions, however in most cases the adjacency will:
Be achieved via atomic functions that simply transfer
Be spread over spread over space
Will represent multiple parallel/simultaneous semantic interactions
Perfect transfer of information (zero time, infinite capacity) is represented in yellow in the figure as it is the essential property of a forwarding entity
Forwarding is imperfect transfer.
It could be argued that
the transfer function is a little way into the grey function (as shown intentionally)
The transfer function is actually impure and has some aspects of other functions such that it too can be broken open
Function
Function
Transfer
Function
Transfer
Function
Function
Function
Trasnfer
Function
Function
Function
Trasnfer
Function
Trasnfer
Function
e.g. Firewall

10. A system pattern example
Blue lines represent pointers between component ports…
No implication of distance etc. Ports are adjacent.
Function
Function
C.2
B.1
Function
A.1
Function
D.1
Function
C.1
Function
A.2
The actual instantiation may have multiple A.1s in it
The pattern has multiple As in it
I have many connectivity examples of this