<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 08/24/2015 09:06 PM, 陈迪豪 wrote:<br>
<blockquote cite="mid:tencent_3F7CFF0C2EF0978852897BF8@qq.com"
type="cite">
<div>Thanks Ben,</div>
<div><br>
</div>
<div>We will reconfigure manila to use the correct network. I'm
still wondering will it have an effect on our existing services?
Some users have create shares in our environment(240.0.0.0/8 is
an example and we're using the available one). What if we
upgrade manila to use something like 10.240.0.0/24, can they
continue to use the existing shares in 240.0.0.0/8?</div>
<div><includetail>
<div> </div>
</includetail></div>
</blockquote>
<br>
It's possible, but it will depend on your network configuration. As
I said below, class E addresses are invalid, so the fact that it
works at all is a bit surprising. I'm sure if it's working now,
there is a way it can continue to work, but there's too many unknown
variables for me to tell you how.<br>
<br>
My recommendation would be to stop using the 240.0.0.0/8 addresses
altogether and move everything to valid IP addresses. That move
might end up being disruptive, so the sooner you do it the less
problems it will cause.<br>
<br>
-Ben<br>
<br>
<br>
<br>
<blockquote cite="mid:tencent_3F7CFF0C2EF0978852897BF8@qq.com"
type="cite">
<div><includetail>
<div> </div>
<div style="font:Verdana normal 14px;color:#000;">
<div style="FONT-SIZE: 12px;FONT-FAMILY: Arial
Narrow;padding:2px 0 2px 0;">------------------ Original ------------------</div>
<div style="FONT-SIZE: 12px;background:#efefef;padding:8px;">
<div id="menu_sender"><b>From: </b> "Ben
Swartzlander"<a class="moz-txt-link-rfc2396E" href="mailto:ben@swartzlander.org"><ben@swartzlander.org></a>;</div>
<div><b>Date: </b> Mon, Aug 24, 2015 09:42 PM</div>
<div><b>To: </b> <a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.">"openstack-dev@lists."</a><a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a>;
<wbr></div>
<div><b>Subject: </b> Re: [openstack-dev]
[openstack][manila]How to change the network ofmanila
without affecting the existing service</div>
</div>
<div> </div>
On 08/23/2015 09:01 PM, 陈迪豪 wrote:<br>
<blockquote
cite="mid:tencent_7B18AD8F674C390B0286AB11@qq.com"
type="cite">
<div>We has deployed manila service in production. But we
have found some problems when deploy it in 240.0.0.0/8
which is blocked by Windows. That means Windows users
can't use the file system service if we're deploying it
in this network.</div>
<div><br>
</div>
</blockquote>
<br>
240.0.0.0/8 is a class E address, which is invalid, so
blocking by your OS is correct behavior. You should use one
of the RFC1918 IP address ranges for actual traffic.<br>
<br>
<blockquote
cite="mid:tencent_7B18AD8F674C390B0286AB11@qq.com"
type="cite">
<div>I'm wondering how can we change the network of manila
without affecting the existing service?</div>
<div><br>
</div>
<div>Can we leave the existing virtual machines which
continue to serve while restarting manila with the new
configuration? Does it work for the existing service?</div>
</blockquote>
<br>
Manila doesn't offer a way to change the network
accessibility of existing shares. In the future we'll be
able to do share network changes and migrations, but today
you have the following options:<br>
* If you're using a driver with share servers, create a new
share network with the correct network subnet and create new
shares using that network.<br>
* If you're using a driver without share servers, simply
reconfigure your storage controller, and restart the Manila
service.<br>
<br>
-Ben<br>
<br>
<br>
<blockquote
cite="mid:tencent_7B18AD8F674C390B0286AB11@qq.com"
type="cite"> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=OpenStack-dev-request@lists.openstack.org&cc=&bcc=&su=&body=','_blank');return false;">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
<!--<![endif]--></includetail></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>