<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"ＭＳ 明朝";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@ＭＳ 明朝";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:99.25pt 85.05pt 85.05pt 85.05pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Hi Avishay-san,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Thank you for your review and comments for my proposal. I commented in-line.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>>So the way I see it, the value here is a generic driver that can work with any storage. The downsides:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">A generic
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">driver for any storage is an one of benefit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">But main benefit of proposed driver is as follows.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">- Reduce hardware based storage workload by offloading the workload to software based volume operation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Conventionally, operations to a</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">n</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
enterprise storage such as volume creation, deletion, snapshot, etc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">are only permitted system administrator and they handle these operations after carefully examining.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">In OpenStack cloud environment, every user have a permission to execute these storage operations<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">via cinder. As a result, workloads of storages have been increasing and it is difficult to manage<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">the workloads.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">If we have two drivers in regards to a storage, we can use both way as the situation demands.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">E</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">x</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> As for "Standard" type storage, use
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">proposed
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">software based LVM cinder driver.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> As for "High performance" type storage, use hardware based cinder driver.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">As a result, we can offload the workload of standard type storage from physical storage to cinder host.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>>1. The admin has to manually provision a very big volume and attach it to the Nova and Cinder hosts.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> Every time a host is rebooted,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I thinks current FC-based cinder drivers using scsi scan to find created LU.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"># echo "- - -" > /sys/class/scsi_host/host#/scan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">The admin can find additional LU using this, so host reboot are not required.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> or introduced, the admin must do manual work. This is one of the things OpenStack should be trying
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> to avoid. This can't be automated without a driver, which is what you're trying to avoid.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Yes. Some admin manual work is required and can</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">t
be automated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I would like to know whether these operations are acceptab</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">l</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">e
range to enjoy benefits from<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">my proposed driver.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>>2. You lose on performance to volumes by adding another layer in the stack.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I think this is case by case. When user use a cinder volume for D</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">ATA
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">B</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">ASE</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">,
they prefer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">raw volume and proposed driver ca</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">n’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">t
provide raw </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">cinder
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">volume.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">In this case, I recom</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">m</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">e</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">n</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">d
"High performance" type storage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">LVM is a defa</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">u</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">lt
feature in many Linux distribution. Also LVM is used many enterprise<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">sy</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">s</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">tems
and I think there is not critical performance loss.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>>3. You lose performance with snapshots - appliances will almost certainly have more efficient snapshots<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> than LVM over network (consider that for every COW operation, you are reading synchronously over the network).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> (Basically, you turned your fully-capable storage appliance into a dumb JBOD)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">I agree that storage has efficient COW snapshot feature, so we can create new Boot Volume<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">from glance quickly. In this case, I recomme</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">n</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">d
"High performance" type storage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">LVM can</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">t
create nested snapshot with shared LVM now. Therefore, we can</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">t
assign<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">writ</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">a</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">ble
LVM snapshot to instances.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Is this answer for your
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">comment</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> In short, I think the cons outweigh the pros. Are there people deploying OpenStack who would deploy
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">>> their storage like this?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Please consider
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">above</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> main
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">benefit</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">Mitsuhiro Tanino <<a href="mitsuhiro.tanino@hds.com"><span style="color:blue">mitsuhiro.tanino@hds.com</span></a>><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA">
<b>HITACHI DATA SYSTEMS<o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;mso-fareast-language:JA"> c/o Red Hat, 314 Littleton Road, Westford, MA 01886<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Avishay Traeger [mailto:avishay@stratoscale.com]
<br>
<b>Sent:</b> Wednesday, May 21, 2014 4:36 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Cc:</b> Tomoki Sekiyama<br>
<b>Subject:</b> Re: [openstack-dev] [Cinder] Support LVM on a shared LU<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">So the way I see it, the value here is a generic driver that can work with any storage. The downsides:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">1. The admin has to manually provision a very big volume and attach it to the Nova and Cinder hosts. Every time a host is rebooted, or introduced, the admin must do manual work. This is one of the things OpenStack
should be trying to avoid. This can't be automated without a driver, which is what you're trying to avoid.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2. You lose on performance to volumes by adding another layer in the stack.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3. You lose performance with snapshots - appliances will almost certainly have more efficient snapshots than LVM over network (consider that for every COW operation, you are reading synchronously over the network).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">(Basically, you turned your fully-capable storage appliance into a dumb JBOD)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">In short, I think the cons outweigh the pros. Are there people deploying OpenStack who would deploy their storage like this?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Thanks,<br>
Avishay<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">On Tue, May 20, 2014 at 6:31 PM, Mitsuhiro Tanino <<a href="mailto:mitsuhiro.tanino@hds.com" target="_blank">mitsuhiro.tanino@hds.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Hello All,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
I’m proposing a feature of LVM driver to support LVM on a shared LU.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
The proposed LVM volume driver provides these benefits.<br>
- Reduce hardware based storage workload by offloading the workload to software based volume operation.<br>
- Provide quicker volume creation and snapshot creation without storage workloads.<br>
- Enable cinder to any kinds of shared storage volumes without specific cinder storage driver.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
- Better I/O performance using direct volume access via Fibre channel.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
In the attachment pdf, following contents are explained.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
1. Detail of Proposed LVM volume driver<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
1-1. Big Picture<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
1-2. Administrator preparation<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
1-3. Work flow of volume creation and attachment<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
2. Target of Proposed LVM volume driver<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
3. Comparison of Proposed LVM volume driver<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Could you review the attachment?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Any comments, questions, additional ideas would be appreciated.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Also there are blueprints, wiki and patches related to the slide.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<a href="https://blueprints.launchpad.net/cinder/+spec/lvm-driver-for-shared-storage" target="_blank">https://blueprints.launchpad.net/cinder/+spec/lvm-driver-for-shared-storage</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<a href="https://blueprints.launchpad.net/nova/+spec/lvm-driver-for-shared-storage" target="_blank">https://blueprints.launchpad.net/nova/+spec/lvm-driver-for-shared-storage</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<a href="https://wiki.openstack.org/wiki/Cinder/NewLVMbasedDriverForSharedStorageInCinder" target="_blank">https://wiki.openstack.org/wiki/Cinder/NewLVMbasedDriverForSharedStorageInCinder</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<a href="https://review.openstack.org/#/c/92479/" target="_blank">https://review.openstack.org/#/c/92479/</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<a href="https://review.openstack.org/#/c/92443/" target="_blank">https://review.openstack.org/#/c/92443/</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black">Mitsuhiro Tanino <<a href="http://mitsuhiro.tanino@hds.com" target="_blank">mitsuhiro.tanino@hds.com</a>></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> <b>HITACHI DATA SYSTEMS</b></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:black"> c/o Red Hat, 314 Littleton Road, Westford, MA 01886</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>