aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json
diff options
context:
space:
mode:
authorRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>2018-03-12 17:03:30 +0000
committerRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>2018-03-21 09:15:44 +0000
commitb5436b214662c629c168c7af760f1f235b99669a (patch)
tree8f8a90c3a03b565d8c60fcd8801e76af4aa9d06f /dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json
parentbf892d9cf62b6bc64ea76d8b69a8fe3751cabd75 (diff)
Install RabitMQ for RPC messaging between processes
In NetworkServices Tescases, the TGs (traffic generators) run the traffic in a separate process. In order to synchronize the traffic injection and the runner interval loops, an RPC server is needed to publish/subscribe events. RabbitMQ is a well supported MQ in Linux (used in OpenStack or collectd) and supported by Python implemented projects like oslo.messaging [1]. RabbitMQ default configuration: - Port: 5672 - User/password: yardstick/yardstick [1]https://github.com/openstack/oslo.messaging JIRA: YARDSTICK-1068 Change-Id: I15db294ee430fb38e574a59b9ce1bf0f8b651a67 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Diffstat (limited to 'dashboard/Prox_BM_BNG-QoS-4Port-1507804267386.json')
0 files changed, 0 insertions, 0 deletions