Yeah, a builtin method to distribute rings would be nice.
The puppet module (puppet-swift) does do this. I'm guessing most people are going to use some configuration management tool (Pupper, Ansible etc) to manage their deployment (especially if installing the rest of Openstack too).
Cheers Mark On 26/04/16 22:57, Peter Brouwer wrote:
Hi Mark, Having pondered of this a bit, it made me realize that capacity management in swift being deployed on enterprise level ( lets say 25+ storage nodes) might be a bit of a challenge for a sysadmin. Would it be an idea to consider the following addition to the ringbuilder tools for future releases. Implement a mechanism to automatically ( optional via command line argument(s) ) distribute the newly created swift ring build structures to all the participating storage nodes. Options of specifying the storage nodes to copy to could be; 1) Via command line arg 2) From the Ip part of the disks belonging to the ring build structure 3) A merge of the above 2 ( in case storage servers share attached storage from an external subsystem ( using shared filesystem) and the IP part contains localhost) This way the inconsistency between hash tables on different swift storage nodes can be easily controlled and time of differences can be kept to a minimum. A next step in this function could be a pause in accepting client traffic till all hash tables have been copied.
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
