As a first step, I moved the ChangeProp installs on restbase-dev100[45] to /home/mobrovac/code/change-propagation, removed the SystemD units and re-enabled Puppet there. The next step should be to set up the deployment repo's Scap config, but we have to figure out a way how to do it since each of the two CP instances needs to have a distinctive set of rules and talk to a different Kafka cluster altogether. The latter could be done by exploiting MirrorMaker so as to talk to the same Kafka cluster, but we still have to find a solution to the former problem.

Please let me know if you guys think this is something it can happen this quarter

In T199428#4429043, @Nuria wrote:

Please let me know if you guys think this is something it can happen this quarter

I think so, since CP is already puppetised. As I pointed out in my previous comment, we need to figure out how to set up the configs correctly and we should be good to go.

each of the two CP instances needs to have a distinctive set of rules

Why? We can have the same set of rules just like we have in production, some of them will just do nothing, what's the problem?

In T199428#4433190, @Pchelolo wrote:

each of the two CP instances needs to have a distinctive set of rules

Why? We can have the same set of rules just like we have in production, some of them will just do nothing, what's the problem?

Because regardless of MirrorMaker, one config needs to read eqiad.* topics and the other codfw.* ones.