Here's a straw-man: * 5 storage nodes * 2 proxy servers
5 storage nodes for a reasonable zone breakdown for 3 replicas; separate proxy nodes for security segregation (working to avoid unencrypted, unauthenticated rsync having any chance of leaking through the net) and network segregation (separating replication traffic); and at 2 proxies for HA. Regards, Tom On 05/09/13 06:38, Snider, Tim wrote: > I'd like to get input from the community on a 'realistic' size of a small > Swift cluster that might be deployed & used in the field for production. SAIO > / test / lab setups aren't a consideration. I'm interested in hearing about > both private and public cluster sizes that are deployed for production use. > 4 nodes or fewer doesn't seems pretty small - 6 or 8 seems like a more > realistic size of a small cluster. But I don't have any actual data/customer > experience for those assumptions. > Followup questions: > Given that cluster size, do all nodes act as both Swift proxy and storage > nodes? I assume they do. > How big does a cluster get before node roles are separated? > Thanks for the input, > Tim > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
