1. COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Monitoring in TOSCA – Future Use Cases Presenter: Ifat Afek, Alcatel-Lucent September 2015

2. 2 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Monitoring Ad-Hoc Group Status First Minimal Use Case The group has reached a rough consensus about a first minimal use case for monitoring in TOSCA. See https://www.oasis- open.org/apps/org/workgroup/tosca/download.php/56276/Monitoring%20Presentati on%20To%20TC%20--%2020150813.pptxhttps://www.oasis- open.org/apps/org/workgroup/tosca/download.php/56276/Monitoring%20Presentati on%20To%20TC%20--%2020150813.pptx The following areas should be further discussed Complex Metric Types Communication between the orchestrator and the monitoring tool Policies Error handling

3. 3 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Complex Metric Types Current Definitions Normative Metric Types Concrete metrics (CPU/Memory/etc.) and abstract metrics (Availability) Metric definitions on node types Future Definitions Composite Metric Types: ­ Formulas, e.g.: (Space Free / Space Available * 100) ­ Aggregations, e.g.: average Space Free per hour Custom metric types, defined per application Metric Definitions on instances, e.g. different metrics for different Compute instances

4. 4 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Orchestrator and Monitoring Tool Communication Current Definitions None, this issue is not referenced in the first minimal use case Is it part of the group’s charter? Future Definitions Initialization of the communication between the orchestrator and the monitoring tool How does the monitoring tool access the components? Protocol/credentials… Orchestrator notifies the monitoring tool about component creation/deletion/modification/errors Monitoring tool notifies the orchestrator about errors in metrics retrieval

5. 5 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Policies Current Definitions Monitoring policy ­ Required in order to enable monitoring ­ Define what to monitor: only some of the components/metrics ­ Monitoring disposition: required/best effort/none Policies are WIP in TOSCA

6. 6 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Policies Future Definitions Actions on threshold/state change: ­ Notification ­ Auto-scaling ­ Examples: ­ if cpu_utilization > 70% send notification ­ if (cpu_utilization > 80% and num_instances < 3) then scale-out Motivation ­ Policies are defined as a layer on top of the application definition ­ If you deploy applications, you need to monitor them and decide what to do in case there are problems ­ Policies may define abstract actions like “notification”, and each orchestrator may implement it differently (send email, write to log, etc.)

7. 7 COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. Error Handling Current Definitions None Future Definitions The monitoring tool notifies the orchestrator about errors in metrics retrieval Actions if a required metric is missing for a specific component