OCCI Monitoring

Augusto Ciuffoletti

OCCI MonitoringExtending the OCCI API with monitoring capabilities

Augusto Ciuffoletti

Dept. of Computer Science - Univ. of Pisa

April 11, 2013

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiMotivation

I A first step towards SLA

I Give the user an interface to arrange a monitoringinfrastructure

I Useful especially in the case the user is in its turn aservice provider...

I ... or in the case the user wants to ”double check” theprovided service level

I In the former case the user uses the monitoringinfrastructure to ensure quality of service...

I ...and for billing purposes

I Simple and optional, aligned with OCCI

I Two types: the Collector and the Sensor

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;

I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:

I the operational parameters are as many as the types ofresources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:

I the operational parameters are as many as the types ofresources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resource

I deliver such parameters to Target resource

I There are innumerable options for both roles:

I the operational parameters are as many as the types ofresources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:

I the operational parameters are as many as the types ofresources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:

I the operational parameters are as many as the types ofresources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:I the operational parameters are as many as the types of

resources (and more)

I the trasport media are also extremely variable: tcpconnection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:I the operational parameters are as many as the types of

resources (and more)I the trasport media are also extremely variable: tcp

connection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:I the operational parameters are as many as the types of

resources (and more)I the trasport media are also extremely variable: tcp

connection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Collector

I The Collector is a Link, in the OCCI terminology;I It has two distinct roles:

I extract operational parameters from the Source resourceI deliver such parameters to Target resource

I There are innumerable options for both roles:I the operational parameters are as many as the types of

resources (and more)I the trasport media are also extremely variable: tcp

connection, push/pop, database, sms etc.

I The OCCI way: provide plugin extensions

I Plugins are organized into two collections: ToolSet andCollectorSet

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiBasics: the Sensor

I The Sensor is a Resource in the OCCI terminology

I It is specific for monitoring: its role is to process oraggregate the output of one or more Collectors

I Also in this case, the ways to aggregate and processmonitoring data are too many to envision an index

I For instance filtering, interpolation, combination

I For this reason a Sensor can be further specified usingmixins in the AggregatorSet collection

I The Sensor delivers its results to another Resourcethrough a Collector

I The target resource can be, for instance, a ComputeResource that implements a resource managementstrategy

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):

I Metric Attributes: the name corresponds to a measuredmetrics

I Control attributes: how measurements are done

I PublisherSet (Sensor only):

I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):

I Metric Attributes: the name corresponds to a measuredmetrics

I Control attributes: how measurements are done

I PublisherSet (Sensor only):

I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metrics

I Control attributes: how measurements are done

I PublisherSet (Sensor only):

I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):

I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):

I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributes

I Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):

I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):I Input: reference to output Collector attributes

I Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):I Input: reference to output Collector attributesI Control: how the specific aggregation is done

I Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiThe mix-ins: constraints

I The mixins collections are characterized by constrainedattributes

I ToolSet (Collector only):I Metric Attributes: the name corresponds to a measured

metricsI Control attributes: how measurements are done

I PublisherSet (Sensor only):I Input: reference to source Sensor attributesI Control: how measurements are published

I AggregatorSet (Sensor only):I Input: reference to output Collector attributesI Control: how the specific aggregation is doneI Metric: the name corresponds to an aggregated metric

OCCI Monitoring

Augusto CiuffolettiA single stage scenario

I This corresponds to the basic case:

I The collector is characterized with a ToolSet mixin,

I while the sensor has a PublisherSet attribute.

OCCI Monitoring

Augusto CiuffolettiA single stage scenario

I This corresponds to the basic case:

I The collector is characterized with a ToolSet mixin,

I while the sensor has a PublisherSet attribute.

OCCI Monitoring

Augusto CiuffolettiA single stage scenario

I This corresponds to the basic case:

I The collector is characterized with a ToolSet mixin,

I while the sensor has a PublisherSet attribute.

OCCI Monitoring

Augusto CiuffolettiA self-monitoring resource

I This is the simplest case

I The monitored resource has AggregatorSet mixins thatexpose metrics and controls

I e.g.: A Compute Resource with a syslog processor as amixin

OCCI Monitoring

Augusto CiuffolettiA self-monitoring resource

I This is the simplest case

I The monitored resource has AggregatorSet mixins thatexpose metrics and controls

I e.g.: A Compute Resource with a syslog processor as amixin

OCCI Monitoring

Augusto CiuffolettiA self-monitoring resource

I This is the simplest case

I The monitored resource has AggregatorSet mixins thatexpose metrics and controls

I e.g.: A Compute Resource with a syslog processor as amixin

OCCI Monitoring

Augusto CiuffolettiA multi-stage monitoring infrastructure

I An example to show how generic is the model

I Multistage sensors: useful to cross provider boundaries

I Combining measurements: a metric can result fromcombination

OCCI Monitoring

Augusto CiuffolettiA multi-stage monitoring infrastructure

I An example to show how generic is the model

I Multistage sensors: useful to cross provider boundaries

I Combining measurements: a metric can result fromcombination

OCCI Monitoring

Augusto CiuffolettiA multi-stage monitoring infrastructure

I An example to show how generic is the model

I Multistage sensors: useful to cross provider boundaries

I Combining measurements: a metric can result fromcombination

OCCI Monitoring

Augusto CiuffolettiAlso in the document

I Conformance profiles: to accomodate the presence ofproviders that do not implement a monitoring interface

I Security issues

I A detailed example using the http rendering

I ...and several bugs.

OCCI Monitoring

Augusto CiuffolettiAlso in the document

I Conformance profiles: to accomodate the presence ofproviders that do not implement a monitoring interface

I Security issues

I A detailed example using the http rendering

I ...and several bugs.

OCCI Monitoring

Augusto CiuffolettiAlso in the document

I Conformance profiles: to accomodate the presence ofproviders that do not implement a monitoring interface

I Security issues

I A detailed example using the http rendering

I ...and several bugs.

OCCI Monitoring

Augusto CiuffolettiAlso in the document

I Conformance profiles: to accomodate the presence ofproviders that do not implement a monitoring interface

I Security issues

I A detailed example using the http rendering

I ...and several bugs.

OCCI Monitoring

Augusto CiuffolettiAlso in the document

I Conformance profiles: to accomodate the presence ofproviders that do not implement a monitoring interface

I Security issues

I A detailed example using the http rendering

I ...and several bugs.

That’s all...