SysD 5.0 review discussion - ServiceRegistry

[borditamas]

The Arrowhead community is admonished to read and review the System Description (SysD) of ServiceRegistry v5.0 draft, available here:

• For easier reading, use the .pdf format.
• To reference exact lines use the .tex format.

Please read the document and share your comments and suggestions within this issue.

Antecedent: #63

[jerkerdelsing]

We need a Monitoring service that should be mandatory for all core microsystems and highly recommended for any application microsystem. Such Monitoring service need to be dynamically extendable with new interfaces while existing interfaces can be taken away. Each action will require a re registration of the Monitoring service to the service registry. Since this will create a number of Monitoring services being registered in each local cloud we need a clear connection to which microsystem own each Monitoring service. Open question on this should be done!

[jerkerdelsing]

Create an OpenAPI spec for a Monitoring service, Jerker