Thanks Ben and that save me days.
We will do it soon and try not to affect the existing users. When this's done,
we're glad to share our experience about upgrading and reconfiguring manila.
Thanks again.
Regards,
tobe
------------------ Original ------------------
From: "Ben Swartzlander"<[email protected]>;
Date: Tue, Aug 25, 2015 10:26 AM
To: "openstack-dev@lists."<[email protected]>;
Subject: Re: [openstack-dev] [openstack][manila]How to change the
networkofmanila without affecting the existing service
On 08/24/2015 09:06 PM, 陈迪豪 wrote:
Thanks Ben,
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?
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.
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.
-Ben
------------------ Original ------------------
From: "Ben
Swartzlander"<[email protected]>;
Date: Mon, Aug 24, 2015 09:42 PM
To: "openstack-dev@lists."<[email protected]>;
Subject: Re: [openstack-dev]
[openstack][manila]How to change the network ofmanila without
affecting the existing service
On 08/23/2015 09:01 PM, 陈迪豪 wrote:
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.
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.
I'm wondering how can we change the network of
manila without affecting the existing service?
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?
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:
* 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.
* If you're using a driver without share servers, simply
reconfigure your storage controller, and restart the Manila
service.
-Ben
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions) Unsubscribe:
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions) Unsubscribe:
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
