Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Dulko, Michal
> From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com] > Sent: Tuesday, September 15, 2015 4:54 PM > > Hi, > > Let me see if i got this: > - running 3 (multiple) c-vols won't automatically give you failover > - each c-vol is "master" of a certain number of volumes > -- if the c-vol is

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread John Griffith
On Tue, Sep 15, 2015 at 8:53 AM, Eduard Matei < eduard.ma...@cloudfounders.com> wrote: > Hi, > > Let me see if i got this: > - running 3 (multiple) c-vols won't automatically give you failover > ​correct ​ > - each c-vol is "master" of a certain number of volumes > ​yes ​ > -- if the c-vol is

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Duncan Thomas
@cloudfounders.com] > *Sent:* Tuesday, September 15, 2015 8:54 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Cinder]Behavior when one cinder-volume > service is down > > > > Hi, > > > > Let me see if

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread D'Angelo, Scott
) Subject: Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down Thanks Scott, But the question remains: if the "hacks" are not recommended then how can i perform Evacuate when the c-vol service of the volumes i need evacuated is "down", but there are two

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Eduard Matei
Hi, Let me see if i got this: - running 3 (multiple) c-vols won't automatically give you failover - each c-vol is "master" of a certain number of volumes -- if the c-vol is "down" then those volumes cannot be managed by another c-vol What i'm trying to achieve is making sure ANY volume is

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread D'Angelo, Scott
deployments. From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com] Sent: Tuesday, September 15, 2015 8:54 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down Hi, Let me see if i got this: - running 3

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Eduard Matei
Thanks Scott, But the question remains: if the "hacks" are not recommended then how can i perform Evacuate when the c-vol service of the volumes i need evacuated is "down", but there are two more controller node with c-vol services running? Thanks, Eduard

[openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Eduard Matei
Hi, This all started when we were testing Evacuate with our storage driver. We thought we found a bug (https://bugs.launchpad.net/cinder/+bug/1491276) then Scott replied that we should be running cinder-volume service separate from nova-compute. For some internal reasons we can't do that - yet,

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread Dulko, Michal
> From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com] > Sent: Tuesday, September 15, 2015 4:04 PM > > Hi, > > This all started when we were testing Evacuate with our storage driver. > We thought we found a bug > (https://bugs.launchpad.net/cinder/+bug/1491276) then Scott replied that > we

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

2015-09-15 Thread John Griffith
On Tue, Sep 15, 2015 at 8:04 AM, Eduard Matei < eduard.ma...@cloudfounders.com> wrote: > Hi, > > This all started when we were testing Evacuate with our storage driver. > We thought we found a bug (https://bugs.launchpad.net/cinder/+bug/1491276) > then Scott replied that we should be running