[fuel] [cinder] Fuel doesn't provide a functionality to manage Cinder backends when multi backend feature is needed

Bug #1587257 reported by Andrey Volochay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Toolbox

Bug Description

Detailed bug description:
  During deploying an environment via MOS8.0, I have faced with following bug.

  Fuel has no functionality to manage backends for Cinder. Plus, there are no standard instructions on how plugin developer should safely manage cinder backends during deployment by means of FUEL.

  By default, when you enable two or more plugins that manage Cinder backends (and support multi backend), whomever is the last in the deployment order wins the only seat in the config.

Steps to reproduce:
 1) Have MOS8.0 environment
 2) Install two or more Fuel plugins for Cinder that support multi backend
 3) Enable and configure mentioned plugins
 4) Deploy an environment

Reproducibility:
 Whenever you use two and more Fuel plugins that manage backends for Cinder

Impact:
 Customers that use plugins for MOS and are going to set two or more different dedicated storage systems

Additional information:
 There is an attached document that describes this situation for NetApp

Revision history for this message
Andrey Volochay (wallavv) wrote :
Ilya Kutukov (ikutukov)
Changed in fuel:
importance: Undecided → Wishlist
milestone: none → 10.0
status: New → Confirmed
importance: Wishlist → High
importance: High → Wishlist
assignee: nobody → Fuel Plugins Bugs (fuel-plugins-bugs)
assignee: Fuel Plugins Bugs (fuel-plugins-bugs) → Fuel Plugin Cinder Netapp (fuel-plugin-cinder-netapp-team)
Ilya Kutukov (ikutukov)
Changed in fuel:
assignee: Fuel Plugin Cinder Netapp (fuel-plugin-cinder-netapp-team) → Fuel Toolbox (fuel-toolbox)
importance: Wishlist → High
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 10.0 → 10.1
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 10.1 → 11.0
tags: added: feature
Revision history for this message
Robert Duncan (rduncan-t) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.