| Gliffy Diagram | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
General discussion items
Top level construct
I am missing a class that can be used by services that need to include flow domains, connectivity and endpoints. I see it as useful and flexible to allow this.
For sure the TAPI model does not deal with services (customer and resource facing) – so I think that we should keep them loosely coupled via this missing class.
So just to play with a name here, lets call it a 'Reosurce'.
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
I'm not trying to describe the service model here, just show how it could relate to the resource side of the house, and why the 'Resource' is an elegant way to hide some of the complexity of what a service is really made up of.
Ownership
The parent page (Abstract Topology Model) describes a requirement for an association of a topology entity to the software that owns it for a given purpose (e.g.: LCM; Configuration)
This is also missing from the proposal. Again just the concept here – of course it needs to have relationships to FlowDomain and Connectivity. These can be managed from multiple perspectives (LCM; Configuration; Assurance; ...) by different products.
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Specific named classes
ManagedFunction
I think this is a type (specialization) of FlowDomain. Basically it is hierarchical in nature, i.e. value defined by an organization or standard that may be realized by virtual machines and or containers. It will contain termination points