Volume Documentation for scaling out across nodes needed

Bug #882752 reported by Anne Gentle
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Medium
Razique Mahroua

Bug Description

from: http://docs.openstack.org/diablo/openstack-compute/admin/content/managing-volumes.html#comment-343556215
It isn't clear from this document whether it is possible to have multiple servers offering up volumes, the example seems to just use an LVM volume group on the cloud controller. I certainly hope it is possible to scale this out...?

In talking to Jesse Andrews, he said generally speaking you don't want your volume node to be the controller node, but volumes can be on as many nodes as you want.

Changed in openstack-manuals:
assignee: nobody → Razique Mahroua (razique)
status: New → In Progress
Tom Fifield (fifieldt)
Changed in openstack-manuals:
importance: Undecided → Medium
Revision history for this message
Tom Fifield (fifieldt) wrote :

No progress in months - marking as "confirmed"

Changed in openstack-manuals:
status: In Progress → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (stable/diablo)

Fix proposed to branch: stable/diablo
Review: https://review.openstack.org/8109

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (stable/diablo)

Reviewed: https://review.openstack.org/8109
Committed: http://github.com/openstack/openstack-manuals/commit/44ed19634a35c55d3e73d3659e3f5cfbf1c1aba0
Submitter: Jenkins
Branch: stable/diablo

commit 44ed19634a35c55d3e73d3659e3f5cfbf1c1aba0
Author: razique <email address hidden>
Date: Mon Jun 4 02:27:55 2012 +0200

    Fixes bug #882752 Volume Documentation for scaling out across nodes needed
    Updates the nova-volume section with proper doc. convention

    Change-Id: Ia378029c1521c494e9f08170e2ba21c979c82d3c

tags: added: in-stable-diablo
Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Confirmed → Fix Released
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.