...
| 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.
...
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The topology model includes:
- The concept of a management entity as a type of resource
- The relationship from any resource to the entity or entities that manage it.
The nature of the management is not part of the topology model. This is captured by a separate model (not in scope of topology, and not for review)
Any 'Resource' may be managed for a variety of arbitrary purposes (extendable ENUMlist) by different Management resources.
The management software reference may refer to an internal (to the ONAP deployment) or external Resourceend-point.
The management reference role enables a userof user of the topology to inter work with management software that respects access control (for example TBAC). A ManagementReference ManagementEntity must have at least one ManagementReferenceRole. The MnagementReferenceRole is unique within a ManagmentReference.
...
Grouping: to represent the way topology elements can be grouped in a topology E.g: Geographical area; vendor; ORD;
