[doc] cinder-volume should run as active/standby
Bug #1528840 reported by
slava valyavskiy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Maria Zlatkova | ||
7.0.x |
Won't Fix
|
High
|
Fuel Documentation Team | ||
8.0.x |
Fix Released
|
High
|
Maria Zlatkova | ||
Future |
Invalid
|
Undecided
|
Fuel Documentation Team | ||
Mitaka |
Invalid
|
High
|
Maria Zlatkova |
Bug Description
There are currently concerns over the cinder-volume service ability
to run as a fully active-active service. During the Mitaka timeframe, this is being worked on, see:
https:/
Thus, cinder-volume shall only be running on one of the controller nodes, even if it will be configured on all nodes
This bug has been forked from discussion in https:/
description: | updated |
Changed in fuel: | |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel Documentation Team (fuel-docs) → Maria Zlatkova (mzlatkova) |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
status: | Confirmed → Invalid |
tags: | added: release-notes |
tags: |
added: release-notes-done removed: release-notes |
To post a comment you must log in.
Customer requested documentation on how to configure this in Mirantis SFDC ticket 12797. Customer is running MOS 6.1. Please advise.