Support ZeroMQ messaging driver in cinder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Unassigned |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/cinder" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 3320a8943827e82
Author: Vivek Dhayaal <email address hidden>
Date: Sun Jan 24 11:17:37 2016 +0530
Support ZeroMQ messaging driver in cinder
NOTE:This patch introduces support for ZeroMQ driver for cinder single
backend case.
Multi-backend will be addressed in the next patch as part of the
blueprint.
CHANGES:ZeroMQ driver requires hostname for message delivery as there is no
broker inbetween.
So, extract the hostname and feed to the messaging client for zeromq
driver.
For the record, ZeroMq is a very lightweight distributed messaging system
specially designed for high throughput/low latency scenarios.
Addition of support for ZeroMQ would help cinder scale out with high
performance and be highly available as there is no centralised broker.
DocImpact
Document the configurations for ZeroMQ driver for Cinder
Change-Id: Ic4b4301e5d7ca1
Closes-Bug: #1440631
partially Implements bp cinder-
affects: | cinder → openstack-manuals |
Changed in openstack-manuals: | |
status: | Confirmed → Fix Released |
Vivek, please add information to this bug report so the docs folks know what needs to be added or updated in the documentation. It can then be switched over to the openstack-manuals project.