On 11/07/2014 10:50 AM, David Moreau Simard wrote:
Giulio, Right. The volume part is tricky because the volume is ultimately tied to one cinder-volume instance. I don't have a magic solution for that yet.
yep but this can be worked around by customizing the host= setting in Cinder so all instances of cinder-volume look like a single 'host'
this was discussed with Cinder guy here, which I am in touch with too, and is known to expose some issues due to multiple cinder-volume instances potentially trying to get access to the same volume when multiple tasks are queued ... yet this is 'known stuff' and they are already working on a 'state machine' for Cinder which will fix the a/a scenario
until then, the idea is to deploy cinder-volume in a a/p scenario, yet customizing the host= setting
-- Giulio Fidente GPG KEY: 08D733BA | IRC: giulivo -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
