<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.nonlistpara, li.nonlistpara, div.nonlistpara
{mso-style-name:nonlistpara;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:575013922;
mso-list-type:hybrid;
mso-list-template-ids:-503648046 928932838 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:SimSun;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes, I’m asking about plans for gateway-mediated-with-ganesha.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I want to know what would you do to achieve “</span><b>And later the Ganesha core would be extended
to use the infrastructure used by generic driver to provide network separated multi-tenancy. The core would manage Ganesha service running in the service VMs, and the VMs themselves that reside in share networks.</b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Because after I studied current infrastructure of generic driver, I guess directly use it for Ganesha
would now work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This is what I have learned from code:<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">Manila create service_network and service_subnet based on configurations in manila.conf:<o:p></o:p></p>
<p class="nonlistpara"><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#E46C0A"> service_network_name = manila_service_network</span></b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#984807"><o:p></o:p></span></p>
<p class="nonlistpara"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#E46C0A"> service_network_cidr = 10.254.0.0/16</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#984807"><o:p></o:p></span></p>
<p class="nonlistpara"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#E46C0A"> service_network_division_mask = 28</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#984807"><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">service_network is created when manila-share service start.<o:p></o:p></p>
<p class="MsoNormal">service_subnet is created when manila-share service get a share create command, and no share-server exists for current share-network.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-family:Wingdings"><span style="mso-list:Ignore">ð<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Service_subnet create at the same time as share-server created.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Yes, it can be pre-created, manila would check if subnet with no name already exist.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
<p class="MsoNormal">-chen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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"><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""> Deepak Shetty [mailto:dpkshetty@gmail.com]
<br>
<b>Sent:</b> Thursday, February 12, 2015 2:09 PM<br>
<b>To:</b> Li, Chen<br>
<b>Cc:</b> OpenStack Development Mailing List (not for usage questions) (openstack-dev@lists.openstack.org)<br>
<b>Subject:</b> Re: [openstack-dev] [Manila]Question about gateway-mediated-with-ganesha<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Feb 12, 2015 at 6:41 AM, Li, Chen <<a href="mailto:chen.li@intel.com" target="_blank">chen.li@intel.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Deepak,</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p><a name="14b7c4e8906ac58b__MailEndCompose"><span style="font-size:10.0pt;font-family:Wingdings">Ø</span></a><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">When you say VM, its confusing, whether you are referring to service VM or</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">tenant VM. Since you are also saying share-server, I presume you mean</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">service VM!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Courier New""> </span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">IIUC each share-server VM (also called service VM) is serving all VMs</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">created by a tenant. In other words, generic driver creates 1 service VM</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">per tenant, and hence serves all the VMs (tenant VMs) created by that tenant</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">Manila experts on the list can correct me if I am wrong here. Generic</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">driver creates service VM (if not already present for that tenant) as part</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">of creating a new share and connect the tenant network to the service VM</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">network via neutron router (creates ports on the router which helps connect</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">the 2 different subnets), thus the tenant VMs can ping/access the service</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">VM. There is no question and/or need to have 2 service VMs talk to each</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">other, because they are serving different tenants, thus they need to be</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:Wingdings">Ø</span><span style="font-size:7.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New"">isolated!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Sorry for the bad
<span style="font-family:SimSun">expression, yes, I mean service VM.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:SimSun"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:SimSun">I don<span lang="ZH-CN">’</span>t agree with
<span lang="ZH-CN">“</span></span><span style="font-size:10.0pt;font-family:"Courier New"">each share-server VM (also called service VM) is serving all VMs created by a tenant</span><span lang="ZH-CN" style="font-family:SimSun">”</span><span style="font-family:SimSun">.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Because from my practices , 1 service VM is created for 1 share-network.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">A share-network -> A service VM -> shares which are created with the same “share-network”.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">You are probably right, I don't remember the insides of share-network now, but I always created 1 share-network, so i always had the notion of 1 service VM per tenant.<br>
<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">A tenant(the tenant concept in keystone) can has more than one share-networks, even a same neutron network & subnet can be “registered” to several share-networks if user do want
to do that.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Actually, I didn’t see strong connections between manila shares and tenant (the concept in keystone), but this is other topics then.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">But, I think I get your point about service VMs need to be isolated.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I agree with that.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>Typically GlusterFS will be deployed on storage nodes (by storage admin)<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>that are NOT part of openstack. So having the share-server talk/connect<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>with GlusterFS is equivalent to saying "Allow openstack VM to talk with<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>non-openstack nodes", in other words "Connect the neutron network to<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>non-neutron network (also called provider/host network)".<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This is the part I disagree.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What exactly do you disagree here ?<br>
<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>This is achieved by ensuring your openstack Network node is configured to<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>forward tenant traffic to provider network, which involves neutron skills<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>and some neutron black magic :)<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>To know what this involves, pls see section "Setup devstack networking to<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>allow Nova VMs access external/provider network" in my blog @<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span><a href="http://dcshetty.blogspot.in/2015/01/using-glusterfs-native-driver-in.html" target="_blank">http://dcshetty.blogspot.in/2015/01/using-glusterfs-native-driver-in.html</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>This should be taken care by your openstack network admin who should<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>configure the openstack network node to allow this to happen, this isn't a<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>Manila / GlusterFS driver responsibility, rather its an openstack<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>deployment option thats taken care by the network admins during openstack<o:p></o:p></pre>
<pre style="margin-left:21.0pt"><span style="font-family:Wingdings">Ø</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif""> </span>deployment.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">What I want to do is enable GluserFS with Manila with Ganesha in my environment.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I’m working as a cloud admin.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">So, what I expecting is,<o:p></o:p></p>
<p style="margin-left:.25in">1.<span style="font-size:7.0pt"> </span>I need to prepare a GlusterFS cluster<o:p></o:p></p>
<p style="margin-left:.25in">2.<span style="font-size:7.0pt"> </span>I need to prepare images and other stuff for service VM<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Right now, i think all we support is running Ganesha inside the GlusterFS server node only. I don't think we have qualified<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">the scenario where Ganesha is running in service VM. The Blueprint talks about doing this in near future.<br>
<br>
Ccing Csaba and Ramana who are the right folks to comment more on this.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p style="margin-left:.25in">3.<span style="font-size:7.0pt"> </span>I need to configure my GluserFS cluster<span lang="ZH-CN" style="font-family:SimSun">’</span>s information (IPs, volumes) into manila.conf<o:p></o:p></p>
<p style="margin-left:.25in"> <o:p></o:p></p>
<p style="margin-left:.25in"><span style="font-family:Wingdings">ð</span><span style="font-size:7.0pt">
</span>All things can work if I start Manila now, Yeah !<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The only thing I know is manila would create VMs to connect to my GlusterFS cluster.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Currently, the neutron network & subnet where service VMs work is created by Manila.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Manila called them service_network & service_subnet.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">So, I don’t think it is possible for me to configure the network before I create shares.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">service_network and service_subnet is pre-created i thought ? Even if it isn't you can bridge the service_network with provider network after the service_network is created (Ideally it should have been pre-created)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Another problem is there is no router I can used to let service_network connected to GlusterFS cluster.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Because service_subnet are already connected to user’s router ( if connect_share_server_to_tenant_network = False)<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you read my blog, it talks about connecting tenant network to GlusterFS cluster which is on the host/provider network<br>
For your case, it maps to connecting service VM (service_network and service_subnet) to GlusterFS cluster. You can either<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">use the existign router or create a new router and have it connect the service_subnet with the external subnet on which GlusterFS is running.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">thanx,<br>
deepak<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>