In Liberty we cannot run more then one notification agent in cloud
without coordination. So, we have several approaches how to
solve this problem:
1. Run one notification agent under pcs.
pros: we keep transformers
cons: one notification agent is not enough for big envs
2. Change config and not to gather "delta" and "util" by default
pros: ok from performance PoV; no changes in puppet
cons: transformer-based meters are not generated
We've chosen the second approach. If tranformers will be needed, we can
deploy our redis plugin, switch on coordination mode and add transformers
back to config.
Removed unit tests tested default pipeline.cfg, not the functionality.
That is why is is safe to remove them.
Closes-bug: #1537708
Change-Id: Ib3b21b0a967be34eda002820228aa4892d733d5d
(cherry picked from commit 5861466ef4035cdd7f6d4dac8ebc30479637dfaa)
Reviewed: https:/ /review. fuel-infra. org/33184
Submitter: Pkgs Jenkins <email address hidden>
Branch: mcp/newton
Commit: 55d51f15f9f9edb 6a69dd367858ae9 d84aee3563
Author: Nadya Shakhat <email address hidden>
Date: Tue May 2 11:33:26 2017
Remove transformers from pipeline.yaml
In Liberty we cannot run more then one notification agent in cloud
without coordination. So, we have several approaches how to
solve this problem:
1. Run one notification agent under pcs.
pros: we keep transformers
cons: one notification agent is not enough for big envs
2. Change config and not to gather "delta" and "util" by default
pros: ok from performance PoV; no changes in puppet
cons: transformer-based meters are not generated
We've chosen the second approach. If tranformers will be needed, we can
deploy our redis plugin, switch on coordination mode and add transformers
back to config.
Removed unit tests tested default pipeline.cfg, not the functionality.
That is why is is safe to remove them.
Closes-bug: #1537708 4eda002820228aa 4892d733d5d d7f6d4dac8ebc30 479637dfaa)
Change-Id: Ib3b21b0a967be3
(cherry picked from commit 5861466ef4035cd