Additionaly I have to updates all topology and docs to address
this change. And yes, I propose to deploy 3 rabbitmq too.
Change-Id: I9db9fcb7a5f78312dabc23ed2ff56cb0a9748f4d
This removes all the references to stacklight from the
topology-example.yaml file. This means that for people
following the current documentation and creating their
topology configuration from topology-example.yaml StackLight
will not be deployed, neither logging nor monitoring.
In addition, this commit adds
a topology-with-stacklight-example.yaml file that does
include the topology configuration needed for deploying
StackLight. We will need some specific documentation
describing how to deploy StackLight.
Change-Id: I0b9a15c88c28f8175fcacc6bda38423a112b91df
This commits modifies the topology example file to add the
stacklight-collector service to the stacklight-collector
role.
Change-Id: I2757276a9b7bfdae8eba003bfff7747ff35bb16d
"stacklight" is what is used in the Git repository name, and
what should now be used instead of "lma".
Change-Id: Ia10dbf27e146ddd5ffd174734bc6d569b9c3ff34
This patch removes support of hardcoded node selectors.
This patch allows to specify dynamic node selection policy via
configs.
If service is not specified in topology config, service deployment skipped.
Selectors works via affinity feature in kubernetes.
Change-Id: I1f8defd90169cd08fd2ac191c3b186efae5da010
Andreas Jaeger