The ceilometer.pipeline Module

class ceilometer.pipeline.EventPipeline(source, sink)

Bases: ceilometer.pipeline.Pipeline

Represents a pipeline for Events.

publish_data(ctxt, events)

support_event(event_type)

class ceilometer.pipeline.EventPipelineEndpoint(context, pipeline)

Bases: ceilometer.pipeline.PipelineEndpoint

sample(messages)

class ceilometer.pipeline.EventPipelineTransportManager

Bases: ceilometer.pipeline._PipelineTransportManager

static serializer(data)

class ceilometer.pipeline.EventSink(cfg, transformer_manager)

Bases: ceilometer.pipeline.Sink

flush(ctxt)

Flush data after all events have been injected to pipeline.

publish_events(ctxt, events)

class ceilometer.pipeline.EventSource(cfg)

Bases: ceilometer.pipeline.Source

Represents a source of events.

In effect it is a set of notification handlers capturing events for a set of matching notifications.

support_event(event_name)

class ceilometer.pipeline.Pipeline(source, sink)

Bases: object

Represents a coupling between a sink and a corresponding source.

flush(ctxt)

publish_data(ctxt, data)

Publish data from pipeline.

class ceilometer.pipeline.PipelineEndpoint(context, pipeline)

Bases: object

sample(messages)

exception ceilometer.pipeline.PipelineException(message, pipeline_cfg)

Bases: exceptions.Exception

class ceilometer.pipeline.PipelineManager(cfg, transformer_manager, p_type={'source': <class 'ceilometer.pipeline.SampleSource'>, 'pipeline': <class 'ceilometer.pipeline.SamplePipeline'>, 'sink': <class 'ceilometer.pipeline.SampleSink'>})

Bases: object

Pipeline Manager

Pipeline manager sets up pipelines according to config file

Usually only one pipeline manager exists in the system.

publisher(context)

Build a new Publisher for these manager pipelines.

Parameters:context – The context.

class ceilometer.pipeline.PollingManager(cfg)

Bases: object

Polling Manager

Polling manager sets up polling according to config file.

class ceilometer.pipeline.PublishContext(context, pipelines=None)

Bases: object

add_pipelines(pipelines)

class ceilometer.pipeline.SamplePipeline(source, sink)

Bases: ceilometer.pipeline.Pipeline

Represents a pipeline for Samples.

get_interval()

publish_data(ctxt, samples)

support_meter(meter_name)

class ceilometer.pipeline.SamplePipelineEndpoint(context, pipeline)

Bases: ceilometer.pipeline.PipelineEndpoint

sample(messages)

class ceilometer.pipeline.SamplePipelineTransportManager

Bases: ceilometer.pipeline._PipelineTransportManager

static serializer(data)

class ceilometer.pipeline.SampleSink(cfg, transformer_manager)

Bases: ceilometer.pipeline.Sink

flush(ctxt)

Flush data after all samples have been injected to pipeline.

publish_samples(ctxt, samples)

class ceilometer.pipeline.SampleSource(cfg)

Bases: ceilometer.pipeline.Source

Represents a source of samples.

In effect it is a set of pollsters and/or notification handlers emitting samples for a set of matching meters. Each source encapsulates meter name matching, polling interval determination, optional resource enumeration or discovery, and mapping to one or more sinks for publication.

get_interval()

support_meter(meter_name)

class ceilometer.pipeline.Sink(cfg, transformer_manager)

Bases: object

Represents a sink for the transformation and publication of data.

Each sink config is concerned only with the transformation rules and publication conduits for data.

In effect, a sink describes a chain of handlers. The chain starts with zero or more transformers and ends with one or more publishers.

The first transformer in the chain is passed data from the corresponding source, takes some action such as deriving rate of change, performing unit conversion, or aggregating, before passing the modified data to next step.

The subsequent transformers, if any, handle the data similarly.

At the end of the chain, publishers publish the data. The exact publishing method depends on publisher type, for example, pushing into data storage via the message bus providing guaranteed delivery, or for loss-tolerant data UDP may be used.

If no transformers are included in the chain, the publishers are passed data directly from the sink which are published unchanged.

class ceilometer.pipeline.Source(cfg)

Bases: object

Represents a source of samples or events.

check_sinks(sinks)

check_source_filtering(data, d_type)

Source data rules checking

• At least one meaningful datapoint exist
• Included type and excluded type can’t co-exist on the same pipeline
• Included type meter and wildcard can’t co-exist at same pipeline

static is_supported(dataset, data_name)