<div dir="ltr">Great :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 16, 2015 at 3:46 PM, Ronen Kat <span dir="ltr"><<a href="mailto:RONENKAT@il.ibm.com" target="_blank">RONENKAT@il.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Good question, I have:</font>
<br>
<br><a href="https://etherpad.openstack.org/p/cinder-replication-redoc" target="_blank"><font color="blue" face="sans-serif">https://etherpad.openstack.org/p/cinder-replication-redoc</font></a>
<br><a href="https://etherpad.openstack.org/p/cinder-replication-cg" target="_blank"><font color="blue" face="sans-serif">https://etherpad.openstack.org/p/cinder-replication-cg</font></a>
<br><a href="https://etherpad.openstack.org/p/volume-replication-fix-planning" target="_blank"><font color="blue" face="sans-serif">https://etherpad.openstack.org/p/volume-replication-fix-planning</font></a>
<br>
<br><font face="sans-serif">Jay seems to be the champion for moving
replication forward, I will let Jay point the way.</font>
<br>
<br><font face="sans-serif">-- Ronen</font>
<br>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">Zhipeng Huang <<a href="mailto:zhipengh512@gmail.com" target="_blank">zhipengh512@gmail.com</a>></font>
<br><span class=""><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif">"OpenStack Development
Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font>
<br></span><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">16/02/2015 09:14 AM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [openstack-dev]
[cinder] volume replication</font>
<br>
<hr noshade><div><div class="h5">
<br>
<br>
<br><font size="3">Hi Ronen,</font>
<br>
<br><font size="3">Xingyang mentioned there's another etherpad on rep and
CG, which etherpad should we mainly follow ?</font>
<br>
<br><font size="3">On Mon, Feb 16, 2015 at 2:38 PM, Ronen Kat <</font><a href="mailto:RONENKAT@il.ibm.com" target="_blank"><font size="3" color="blue"><u>RONENKAT@il.ibm.com</u></font></a><font size="3">>
wrote:</font>
<br><font size="3" color="#004080" face="Calibri">Ruijing</font><font size="3" face="sans-serif">,
hi,</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>
Are you discussing the network/fabric between Storage A and Storage B?
<br>
If so, assumption in Cinder is that this is done in advance by the storage
administrator.</font><font size="3"> </font><font size="3" face="sans-serif"><br>
The design discussions for replication resulted in that the driver is fully
responsible for replication and it is up to the driver to implement and
manage replication on its own.</font><font size="3"> </font><font size="3" face="sans-serif"><br>
Hence, all vendor specific setup actions like creating volume pools, setup
network on the storage side are considered prerequisite actions and outside
the scope of the Cinder flows.</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>
If someone feels that is not the case, or should not be the case, feel
free to chime in.</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>
Or does this relates to setting up the data path for accessing both Storage
A and Storage B?</font><font size="3"> </font><font size="3" face="sans-serif"><br>
Should this be setup in advance? When we attach the primary volume to the
VM? Or when promoting the replica to be primary?</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>
-- Ronen</font><font size="3"> <br>
<br>
<br>
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
From: </font><font size="1" face="sans-serif">"Guo,
Ruijing" <</font><a href="mailto:ruijing.guo@intel.com" target="_blank"><font size="1" color="blue" face="sans-serif"><u>ruijing.guo@intel.com</u></font></a><font size="1" face="sans-serif">></font><font size="3">
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
To: </font><font size="1" face="sans-serif">"OpenStack
Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="blue" face="sans-serif"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="sans-serif">></font><font size="3">
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Date: </font><font size="1" face="sans-serif">16/02/2015
02:29 AM</font><font size="3"> </font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Subject: </font><font size="1" face="sans-serif">Re:
[openstack-dev] [cinder] documenting volume replication</font><font size="3">
<br>
</font>
<hr noshade><font size="3"><br>
<br>
</font><font size="3" color="#004080" face="Calibri"><br>
Hi, Ronen</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
3) I mean storage based replication. In normal, volume replication support
FC or iSCSI. We need to setup FC or iSCSI before we do volume replication.</font><font size="3">
</font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
Case 1) </font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
Host ------FC------Storage A -------iSCSI -------- Storage B ----FC-----
Host</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
Case 2)</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
Host ------FC------Storage A -------FC -------- Storage B ----FC----- Host</font><font size="3">
</font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
As above diagram, we need to setup connection (iSCSI or FC) between storage
A and Storage B.</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
For FC, we need to zone storage A & storage B in FC switch.</font><font size="3">
</font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
Thanks,</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
-Ruijing</font><font size="3"> </font><font size="3" color="#004080" face="Calibri"><br>
</font><font size="3"> </font><font size="3" face="Calibri"><b><br>
From:</b> Ronen Kat [</font><a href="mailto:RONENKAT@il.ibm.com" target="_blank"><font size="3" color="blue" face="Calibri"><u>mailto:RONENKAT@il.ibm.com</u></font></a><font size="3" face="Calibri">]
<b><br>
Sent:</b> Sunday, February 15, 2015 4:46 PM<b><br>
To:</b> OpenStack Development Mailing List (not for usage questions)<b><br>
Subject:</b> Re: [openstack-dev] [cinder] documenting volume replication</font><font size="3">
</font><font size="3" face="Times New Roman"><br>
</font><font size="3"> </font><font size="3" face="Arial"><br>
Hi </font><font size="3" color="#004080" face="Calibri">Ruijing</font><font size="3" face="Arial">,</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
<br>
Thanks for the comments.</font><font size="3" face="Times New Roman"> </font><font size="3" face="Arial"><br>
Re (1) - driver can implement replication in any means the driver see fit.
It can be exported and be available to the scheduler/drive via the "capabilities"
or "driver" extra-spec prefixes.</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
Re (3) - Not sure I see how this relates to storage side replication, do
you refer to host side replication?</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
<br>
Ronen</font><font size="3" face="Times New Roman"> <br>
<br>
</font><font size="1" color="#5f5f5f" face="Arial"><br>
<br>
From: </font><font size="1" face="Arial">"Guo,
Ruijing" <</font><a href="mailto:ruijing.guo@intel.com" target="_blank"><font size="1" color="blue" face="Arial"><u>ruijing.guo@intel.com</u></font></a><font size="1" face="Arial">></font><font size="3" face="Times New Roman">
</font><font size="1" color="#5f5f5f" face="Arial"><br>
To: </font><font size="1" face="Arial">"OpenStack
Development Mailing List (not for usage questions)" <</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="blue" face="Arial"><u>openstack-dev@lists.openstack.org</u></font></a><font size="1" face="Arial">></font><font size="3" face="Times New Roman">
</font><font size="1" color="#5f5f5f" face="Arial"><br>
Date: </font><font size="1" face="Arial">15/02/2015
03:41 AM</font><font size="3" face="Times New Roman"> </font><font size="1" color="#5f5f5f" face="Arial"><br>
Subject: </font><font size="1" face="Arial">Re:
[openstack-dev] [cinder] documenting volume replication</font><font size="3" face="Times New Roman">
</font>
<div align="center"><a name="14b916ff3eca8b14_14b911e4b0b8c5f3__MailEndCompose"></a>
<hr noshade></div>
<br><font size="3" face="Times New Roman"><br>
<br>
</font><font size="3" color="#004080" face="Calibri"><br>
<br>
Hi, Ronen,</font><font size="3" face="Times New Roman"> <br>
</font><font size="3" color="#004080" face="Calibri"><br>
I don’t know how to edit </font><a href="https://etherpad.openstack.org/p/cinder-replication-redoc" target="_blank"><font size="3" color="blue" face="Arial"><u>https://etherpad.openstack.org/p/cinder-replication-redoc</u></font></a><font size="3" face="Arial">
and add some comments in email.</font><font size="3" face="Times New Roman">
<br>
</font><font size="3" face="Arial"><br>
1. We may add asynchronized and synchronized type for replication.</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
2. We may add CG for replication</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
3. We may add to initialize connection for replication</font><font size="3" face="Times New Roman">
<br>
</font><font size="3" color="#004080" face="Calibri"><br>
Thanks,</font><font size="3" face="Times New Roman"> </font><font size="3" color="#004080" face="Calibri"><br>
-Ruijing</font><font size="3" face="Times New Roman"> <br>
</font><font size="3" face="Calibri"><b><br>
From:</b> Ronen Kat [</font><a href="mailto:RONENKAT@il.ibm.com" target="_blank"><font size="3" color="blue" face="Calibri"><u>mailto:RONENKAT@il.ibm.com</u></font></a><font size="3" face="Calibri">]
<b><br>
Sent:</b> Tuesday, February 3, 2015 9:41 PM<b><br>
To:</b> OpenStack Development Mailing List (</font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="3" color="blue" face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size="3" face="Calibri">)<b><br>
Subject:</b> [openstack-dev] [cinder] documenting volume replication</font><font size="3" face="Times New Roman">
<br>
</font><font size="3" face="Arial"><br>
As some of you are aware the spec for replication is not up to date, <br>
The current developer documentation, </font><a href="http://docs.openstack.org/developer/cinder/api/cinder.volume.driver.html" target="_blank"><font size="3" color="blue" face="Arial"><u>http://docs.openstack.org/developer/cinder/api/cinder.volume.driver.html</u></font></a><font size="3" face="Arial">,
cover replication but some folks indicated that it need additional details.</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
<br>
In order to get the spec and documentation up to date I created an Etherpad
to be a base for the update.</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
The Etherpad page is on </font><a href="https://etherpad.openstack.org/p/cinder-replication-redoc" target="_blank"><font size="3" color="blue" face="Arial"><u>https://etherpad.openstack.org/p/cinder-replication-redoc</u></font></a><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
<br>
I would appreciate if interested parties would take a look at the Etherpad,
add comments, details, questions and feedback.</font><font size="3" face="Times New Roman">
</font><font size="3" face="Arial"><br>
<br>
Ronen,</font><font size="3" face="Times New Roman"> </font><font size="3" face="Courier New">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><font size="3" color="blue" face="Courier New"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="3" color="blue"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="blue" face="Courier New"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><tt><font size="3">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font></tt><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><tt><font size="3" color="blue"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></tt></a><font size="3" color="blue"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="3" color="blue"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><font size="3"><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><font size="3" color="blue"><u>OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</u></font></a><font size="3" color="blue"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="blue"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size="3"><br>
</font>
<br><font size="3"><br>
</font>
<br>
<br><font size="3">-- </font>
<br><font size="3">Zhipeng (Howard) Huang</font>
<br>
<br><font size="3">Standard Engineer</font>
<br><font size="3">IT Standard & Patent/IT Prooduct Line</font>
<br><font size="3">Huawei Technologies Co,. Ltd</font>
<br><font size="3">Email: </font><a href="mailto:huangzhipeng@huawei.com" target="_blank"><font size="3" color="blue"><u>huangzhipeng@huawei.com</u></font></a>
<br><font size="3">Office: Huawei Industrial Base, Longgang, Shenzhen</font>
<br>
<br><font size="3">(Previous)</font>
<br><font size="3">Research Assistant</font>
<br><font size="3">Mobile Ad-Hoc Network Lab, Calit2</font>
<br><font size="3">University of California, Irvine</font>
<br><font size="3">Email: </font><a href="mailto:zhipengh@uci.edu" target="_blank"><font size="3" color="blue"><u>zhipengh@uci.edu</u></font></a>
<br><font size="3">Office: Calit2 Building Room 2402</font>
<br>
<br></div></div><font size="3">OpenStack, OpenDaylight, OpenCompute affcienado </font><tt><font>__________________________________________________________________________<span class=""><br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</span></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>
</font></tt>
<br>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Zhipeng (Howard) Huang</div><div dir="ltr"><br></div><div dir="ltr">Standard Engineer</div><div>IT Standard & Patent/IT Prooduct Line</div><div dir="ltr">Huawei Technologies Co,. Ltd</div><div dir="ltr">Email: <a href="mailto:huangzhipeng@huawei.com" target="_blank">huangzhipeng@huawei.com</a></div><div dir="ltr">Office: Huawei Industrial Base, Longgang, Shenzhen</div><div dir="ltr"><br></div><div dir="ltr">(Previous)<br><div>Research Assistant</div><div>Mobile Ad-Hoc Network Lab, Calit2</div><div>University of California, Irvine</div><div>Email: <a href="mailto:zhipengh@uci.edu" target="_blank">zhipengh@uci.edu</a></div><div>Office: Calit2 Building Room 2402</div><div><br></div><div>OpenStack, OpenDaylight, OpenCompute affcienado </div></div></div></div></div>
</div>