Open Stack

Don't you also have the issue of having those nodes unavailable during the time when their IP changes and someone gets around to updating and re-propagating those rings right?  Depending on the size of that window and how much traffic is going on at the time you may very well end up with a lot of extra data movement as incoming data makes it to handoffs (assuming their  addresses didn't change) and then back again after the rings reflect the new addresses of the primary(ies).  

-Paul

-----Original Message-----
From: John Dickinson [mailto:me at not.mn] 
Sent: Monday, August 18, 2014 11:54 AM
To: Jyoti Ranjan
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] [Swift] IP address of Swift nodes : need help

If the IP for a storage node changes, you'll need to update the rings where that server's drives are. You can update the IP with the `swift-ring-builder set_info ...` command and then use "write_ring" to serialize it. Doing this will not cause any data movement in the cluster. Removing the server and re-adding it to the ring will cause data movement.

So, no, it's not strictly necessary to use static IPs. You'll be saving yourself some management overhead if you do, though.

--John




On Aug 18, 2014, at 11:42 AM, Jyoti Ranjan <jranjan at gmail.com> wrote:

> Hi,
> 
> We are deploying Swift clusters where we do have IP addresses assigned to Swift nodes via DHCP. Curious to know, what will happen if IP address of a give node change that node is made part of Swift cluster. For e.g. let us assume that Swift object node got IP 192.168.10.2 and later it changes to 192.168.10.9 because of DHCP. Will running Swift cluster get affected?
> 
> In other words, is it necessary to use static IP for Swift nodes?
> 
> 
> Regards,
> Jyoti Ranjan
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack