TOSCA Monitoring Working Group Status Roger Dev August 10, 2015

Monitoring Activation Flow Service Template Virtual Machine (new) Software Component (new) Monitoring Sub-System (MSS) Notify Component State Change: -Create -Modify -Destroy Deliver Metrics (any existing push or pull protocol) Orchestrator Components Created TOSCA specified Outside current charter KEY ? Monitoring Exception

Monitoring Scenario 1 Features FeatureProvided In MS1? Define Key Metrics and GroupsYes Allow for Extended Metric TypesYes Service Template Requires MonitoringYes Specify Metric Types to be monitoredYes Specify Minimum Sample FrequencyYes Actions on thresholds / state changesNo Derived Metrics (Formulas, Aggregations)No

Monitoring Use Cases (I.5) Require Standard Monitoring Require Minimal Monitoring of Select Metrics Require Non-normative Metrics in addition to Standard Monitoring Life-cycle considerations Exception handling considerations

Three aspects of TOSCA Monitoring Define Metrics and Metric Groups as Capabilities Attach Metric Capabilities to normative Node Types Define Monitoring Requirement via Monitoring Policy Definition Directive

Metric Capabilities Strawman – Metrics are organized in a group hierarchy: Availability: – Contactable (Boolean) – General State » Values: Up, Down, Compromised, Unknown – Run Time Compute: – CPU Percent Utilization – CPU 1 Minute average percent utilization – CPU 5 Minute average percent utilization Shorthand Name Metric Type Qualified Name tosca:Metric Type URI tosca.capabilities.Metric

Metric Capabilities Strawman Metric Groups (cont’d) – Memory Memory in Use Memory Available Percent Memory in Use Maximum percent memory in use – Storage Space Available Space Free IO Units In IO Units Out IO Bytes Out IO Bytes In – Network IO Bytes Out Bytes In Units Out Units In Errors

Metric Capabilities Strawman Metric Groups (cont’d) – Threading: Threads in use Maximum Threads in use – Container: Active Child Count Maximum Child Count Failed Child Count – Network Forwarding Queue Depth Maximum Queue Depth Units Forwarded Units Discarded Bytes Forwarded Bytes Discarded – Application: Work units processed 1 Work units in progress 1 Work units processed 2 Work units in progress 2 Errors 1 Errors 2

Attaching Metrics to Normative Node Types tosca.nodes.Compute: derived_from: tosca.nodes.Roottosca.nodes.Root attributes: … requirements: … capabilities: host: type: tosca.capabilities.Containertosca.capabilities.Container valid_source_types: [tosca.nodes.SoftwareComponent]tosca.nodes.SoftwareComponent … metrics: [tosca.capabilities.metric.Availability, tosca.capabilities.metric.Compute, tosca.capabilities.metric.Memory, tosca.capabilities.Storage, tosca.capabilities.metric.Network-IO]

Attaching Metrics to Private Node Types My.Nodes.WidgetShopping: derived_from: tosca.nodes.SoftwareComponent attributes: … requirements: … capabilities: host: type: tosca.capabilities.Containertosca.capabilities.Container … metrics: [tosca.capabilities.metric.Availability, tosca.capabilities.Application, tosca.capabilities.metric.Compute, my.capabilities.metric.WidgetsOrdered, my.capabilities.metric.WidgetsDelivered, … ]

Monitoring Policy If no monitoring policy, then no monitoring Creating an empty policy causes all standard metrics to be collected The set of metrics can be reduced by adding a metrics filter Specify a minimum collection frequency (for all metrics). Otherwise, the system default will be used. (Future) Computations, Thresholds, and Actions can be specified