<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/27/2015 06:39 PM, Li, Chen wrote:<br>
<blockquote
cite="mid:988E98D31B01E44893AF6E48ED9DEFD401BA8E72@shsmsx102.ccr.corp.intel.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@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:"\@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:11.0pt;
font-family:"Calibri","sans-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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal">Hi list,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have some questions.<o:p></o:p></p>
<p class="MsoNormal">Hope can get help from you guys.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Manila has two driver modes.<o:p></o:p></p>
<p class="MsoNormal">For handle share server drivers, the
share-network is easy to understand.<o:p></o:p></p>
<p class="MsoNormal">For not handle share-servers drivers,
manila request admin to do everything before manila-share
service start, and when the service is running, it only serves
requests do not contain "share-network".<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I kept confusing about which/why users
would create shares without "share-network". Although when
working with this kind of driver, the manila-share service can
only support one specific network restricted by the backend.
But “users” do not know backends, they should always want to
create shares with "share-network", because users always want
to connect shares to their instances that lives in the cloud
with “share-network”.</p>
</div>
</blockquote>
<blockquote
cite="mid:988E98D31B01E44893AF6E48ED9DEFD401BA8E72@shsmsx102.ccr.corp.intel.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal">Then I have been told that these shares
created without "share-network" are assumed to be used on a
"public network".
<o:p></o:p></p>
<p class="MsoNormal">The "public network" do make a clear
explanation about why "share-network" not matter anymore.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">But, when I build my cloud with Manila,
what I want to do is let backends to serve my “Flat network”.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I want to have 2 backends in Manila, both
of them are “<b><i>not</i></b> handle share-servers drivers”.<o:p></o:p></p>
<p class="MsoNormal">I set 192.168.6.253 for backend1 and create
a “Flat network” in neutron with subnet 192.168.6.0/24 with IP
range from 192.168.6.1-192.168.6.252.<o:p></o:p></p>
<p class="MsoNormal">I set 192.168.7.253 for backend2 and create
a “Flat network” in neutron with subnet 192.168.7.0/24 with IP
range from 192.168.7.1-192.168.7.252.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The reason I build my cloud like this is
because I want to do some performance tests on both backends,
to compare the two backends.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think it should not hard to do it, but
manila do not support that currently.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, is this the behavior should work ?<o:p></o:p></p>
<p class="MsoNormal">Or anything else I missed ?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p><br>
</p>
</div>
</blockquote>
<br>
Manila needs to support backends that can create share servers and
backends that can't create share servers. We do this because of the
reality that different storage systems have different capabilities
and designs, and we don't want to block anything that can reasonably
described as a shared filesystem from working with Manila.<br>
<br>
For the purposes of Manila, a share server is a logically isolated
instance of a file share server, with its own IP address, routing
tables, security domain, and name services. Manila only tracks the
existence of share servers that were created as the result of a
share-create operation. Share servers created by manila have IP
addresses assigned by Manila, and can be expected to be deleted by
Manila sometime after the last share on that share server is
deleted. Backends that simply create shares on a preexsting storage
systems are not referred to as share servers and networking concerns
for those systems are out of scope for Manila.<br>
<br>
The reason we distinguish between so-called "flat" and "segmented"
networks is to accommodate the reality that in the real world,
storage systems often exist inside labs and datacenters where the
network is not under the control of the storage admin. This was a
key point we identified during Juno and one of the major reasons for
the network rearchitecture during Kilo. If a storage controller is
connected into a flat subnet it may be able to create share servers
on that subnet, but nothing more fancy. To participate in multiple
subnets some form of network virtualization or segmentation is
required and oftentimes that's not possible either due to lack of
support on the storage controller, lack of support in the network
due to physical or administrative limitations, or even lack of
sophistication on the part of the deployer (don't discount this last
one -- the difficulty of getting the network right is a major
blocker for admins who want to try out Manila).<br>
<br>
What flat network means from Manila's perspective is that share
servers may be created but only on a network predefined by the
administrator, and not on any tenant-defined network. Connectivity
between the tenant network and the share server network is
considered out of scope for Manila. Segmented network means that
Manila presumes complete control of the network through some
powerful plugin such as Neutron such that Manila can connect share
servers to any network specified by the tenant, and Manila assumes
responsibility for establishing any needed routes.<br>
<br>
In your case if you have a driver that doesn't handle share servers,
then the network is complete out of scope for Manila. Drivers that
don't manage share servers have neither flat not segment networking
in Manila, they have NO networking.<br>
<br>
I'll do a followup mail on the UI changes that are coming around
share networks and the mess that they have become. For now, you just
have to know that share networks should not be used with drivers
that don't manage share servers, and they should be used with
drivers that do manage share servers.<br>
<br>
-Ben Swartzlander<br>
<br>
</body>
</html>