[Fiware-opencall-help] FI-WARE Open Call - Technical Query

[Mike Surridge]

Dear FI-WARE,

I am considering making a proposal, and trying to understand what assumptions I can make about other FI-WARE components. I have been studying the Application and Services Ecosystem and Delivery Framework architecture overview at:

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Architecture_of_Applications_and_Services_Ecosystem_and_Delivery_Framework

My query concerns the SLA Monitor component. It appears from the diagram that this component:

- retrieves the SLA Model details from the Repository
- requests relevant monitoring data via the Mediator
- receives monitoring data via the Mediator and from the Composition Execution system

>From the brief introduction, it is clear that the SLA Monitor evaluates the monitoring data with respect to the SLA Model, thus enabling detection of SLA violation and/or SLA satisfaction, etc.

However, it is unclear how other components could access this information. I searched for more information on this in the Wiki but could find nothing.

Can we assume that the SLA Monitor will provide SLA evaluation results to other components, e.g. when SLA terms are violated and/or satisfied? If yes, how will this be done (e.g. query, notification, etc), and is there any specification of what information will be available?

Best Regards,

==
Dr Mike Surridge
Research Director
IT Innovation Centre
Gamma House, Enterprise Road,
Southampton, SO16 7NS, UK

Tel: +44 23 8059 8866

mailto:ms at it-innovation.soton.ac.uk
http://www.it-innovation.soton.ac.uk