Re: [openstack-dev] [cinder] volume replication

which etherpad should we mainly follow ? On Mon, Feb 16, 2015 at 2:38 PM, Ronen Kat <ronen...@il.ibm.com> wrote: Ruijing, hi, Are you discussing the network/fabric between Storage A and Storage B? If so, assumption in Cinder is that this is done in advance by the storage administrator. T

[openstack-dev] [cinder] volume replication

etween storage A and Storage B.   For FC, we need to zone storage A & storage B in FC switch.   Thanks, -Ruijing   From: Ronen Kat [mailto:ronen...@il.ibm.com] Sent: Sunday, February 15, 2015 4:46 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-d

Re: [openstack-dev] [cinder] documenting volume replication

ion Hi, Ronen,   I don’t know how to edit https://etherpad.openstack.org/p/cinder-replication-redoc and add some comments in email.   1.     We may add asynchronized and synchronized type for replication. 2.     We may add CG for replication 3.     We may add to initialize connection for replicat

[openstack-dev] [cinder] documenting volume replication

As some of you are aware the spec for replication is not up to date, The current developer documentation, http://docs.openstack.org/developer/cinder/api/cinder.volume.driver.html, cover replication but some folks indicated that it need additional details. In order to get the spec and documentatio

[openstack-dev] [Cinder] Volume replication - driver support walk through

Hello, The initial code for managing volume replication in Cinder is now available as work-in-progress - see https://review.openstack.org/#/c/106718 I expect to remove the work-in-progress early next week. I would like to hold a walk through of the replication feature for Cinder driver owners

Re: [openstack-dev] [cinder][replication-api] extra_specs too constant

of course impact the actual RPO, but I think this is outside the scope of this 1st revision - I would like to see this mechanism enhanced in the next revision. Ronen, From: Philipp Marek To: openstack-dev@lists.openstack.org, Cc: Ronen Kat/Haifa/IBM@IBMIL Date: 11/07/2014 04

Re: [openstack-dev] [nova][libvirt] Block migrations and Cinder volumes

The use-case for block migration in Libvirt/QEMU is to allow migration between two different back-ends. This is basically a host based volume migration, ESXi has a similar functionality (storage vMotion), but probably not enabled with OpenStack. Btw, if the Cinder volume driver can migrate the vo

[openstack-dev] [Cinder] Volume replication design session

Hello, For those who attended the design session on volume replication, thank you, for those who didn't., the Etherpad with the discussion notes is available for your reference at https://etherpad.openstack.org/p/juno-cinder-volume-replication During the session there were people who indicated

[openstack-dev] Disaster Recovery for OpenStack - plan for Juno design summit - discussion reminder

For those who are interested we will discuss the disaster recovery use-cases and how to proceed toward the Juno summit on April 2 at 17:00 UTC (1PM ET) - invitation below. Agenda and previous discussion history in the Etherpad link below. Call-in: https://www.teleconference.att.com/servlet/glb

[openstack-dev] Disaster Recovery for OpenStack - call for stakeholder - discussion reminder

For those who are interested we will discuss the disaster recovery use-cases and how to proceed toward the Juno summit on March 19 at 17:00 UTC (invitation below) Call-in: https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6406941&accessNumber=1809417783#C2 Passcode:

[openstack-dev] Disaster Recovery for OpenStack - community interest for Juno and beyond - meeting notes and next steps

! Ronen, - Forwarded by Ronen Kat/Haifa/IBM on 05/03/2014 08:05 PM - From: Ronen Kat/Haifa/IBM To: openstack-dev@lists.openstack.org, Date: 04/03/2014 01:16 PM Subject:Disaster Recovery for OpenStack - call for stakeholders Hello, In the Hong-Kong summit, there was

[openstack-dev] Disaster Recovery for OpenStack - call for stakeholder

Hello, In the Hong-Kong summit, there was a lot of interest around OpenStack support for Disaster Recovery including a design summit session, an un-conference session and a break-out session. In addition we set up a Wiki for OpenStack disaster recovery - see https://wiki.openstack.org/wiki/Disa

Re: [openstack-dev] Towards OpenStack Disaster Recovery

From: Caitlin Bestler To: openstack-dev@lists.openstack.org, Date: 21/10/2013 06:55 PM Subject:Re: [openstack-dev] Towards OpenStack Disaster Recovery >> >> Hi all, >> We (IBM and Red Hat) have begun discussions on enabling Disaster Recovery >> (DR) in OpenStack. >> >> We have cre

Re: [openstack-dev] Cinder Backup documentation - to which doc it should go?

. Regards, __ Ronen I. Kat Storage Research IBM Research - Haifa Phone: +972.3.7689493 Email: ronen...@il.ibm.com From: Emilien Macchi To: OpenStack Development Mailing List , Cc: Ronen Kat/Haifa/IBM@IBMIL Date: 03/09/2013 02:57 PM Subject

[openstack-dev] Cinder Backup documentation - to which doc it should go?

I noticed the complains about code submission without appropriate documentation submission, so I am ready to do my part for Cinder backup I have just one little question. Not being up to date on the current set of OpenStack manuals, and as I noticed that the block storage admin guide lost a l

Re: [openstack-dev] Proposal for Raksha, a Data Protection As a Service project

Hi Murali, Thanks for answering. I think the issues you raised indeed make sense, and important ones. We need to provide backup both for: 1. Volumes 2. VM instances (VM image, VM metadata, and attached volumes) While the Cinder-backup handles (1), and is a very mature service, it does not provid

Re: [openstack-dev] Proposal for Raksha, a Data Protection As a Service project

Hi Murali, I think the idea to provide enhanced data protection in OpenStack is a great idea, and I have been thinking about backup in OpenStack for a while now. I just not sure a new project is the only way to do. (as disclosure, I contributed code to enable IBM TSM as a Cinder backup driver)