event_pipeline allows non-unique source names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
Undecided
|
Rohit Jaiswal |
Bug Description
event_pipeline.
---
sources:
- name: snapshot_source
events:
- "snapshot.
- "snapshot.
- "snapshot.
- "snapshot.
sinks:
- snapshot_sink
- name: snapshot_source
events:
- "volume.
- "volume.create.end"
- "volume.
- "volume.update.end"
sinks:
- volume_sink
sinks:
- name: snapshot_sink
transformers:
triggers:
publishers:
- notifier://
- name: volume_sink
transformers:
triggers:
publishers:
- notifier://
excerpt from agent-notificai
...
2015-06-17 17:29:22.169 89692 DEBUG ceilometer.pipeline [-] Pipeline config file: /etc/ceilometer
2015-06-17 17:29:22.178 89692 INFO ceilometer.pipeline [-] Pipeline config: {'sources': [{'events': ['snapshot.
shot_source', 'sinks': ['snapshot_sink']}, {'events': ['volume.
publishers': ['notifier://'], 'transformers': None, 'name': 'snapshot_sink', 'triggers': None}, {'publishers': ['notifier://'], 'transformers': None, 'name': 'volume_sink', 'triggers': None}]}
2015-06-17 17:29:22.178 89692 INFO ceilometer.pipeline [-] detected decoupled pipeline config format
...
Hence question - why "source" names from event_pipeline ain't checked in the same way as "sink" names do?
Thanks,
Yurii
Changed in ceilometer: | |
assignee: | nobody → Rohit Jaiswal (rohit-jaiswal-3) |
Changed in ceilometer: | |
status: | New → In Progress |
Changed in ceilometer: | |
status: | In Progress → Fix Committed |
Changed in ceilometer: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | liberty-2 → 5.0.0 |
I think this also is a problem with pipeline.yaml, since there is common validation for both. Addressing this is important in view of https:/ /blueprints. launchpad. net/ceilometer/ +spec/reload- file-based- pipeline- configuration, which allows pipeline changes on-the-fly.