,
-Ruijing
From: Ronen Kat [mailto:ronen...@il.ibm.com]
Sent: Tuesday, February 3, 2015 9:41 PM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [cinder] documenting volume replication
As some of you are aware the spec for replication
is not up to date
or FC) between 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-dev
etherpad on rep and
CG, 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
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
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
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 philipp.ma...@linbit.com
To: openstack-dev@lists.openstack.org,
Cc: Ronen Kat/Haifa/IBM@IBMIL
Date: 11/07/2014 04:10 PM
Subject:[openstack
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
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
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:
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=1accessCode=6406941accessNumber=1809417783#C2
Passcode:
,
- 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 a lot of interest
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
From: Caitlin Bestler caitlin.best...@nexenta.com
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
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
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
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)
16 matches
Mail list logo
