Ioannis Papapanagiotou

These sound good and I am in favor of `rejoin_wait_period` instead of `rejoin_cluster_wait_period`. We want to make sure that nothing breaks from these changes.

@akbarahmed One more thing that came to my mind this morning is that we want to make sure that these changes are backward compatible. From a short discussion I had...

@akbarahmed I am working on pushing some of the command line arguments to the YAML file: https://github.com/Netflix/dynomite/pull/370 (not ready) YAML file seems to become the industry practice compared to multiple...

#370 has been merged... Moving to the next round soon!

@shailesh33 I agree with the above terms... I think @akbarahmed effort is really timely and it will improve significantly the on boarding of new folks!

I will be adding `enable_gossip`, `mbuf_size` and `max_msgs` as part of the effort moving it from the command line.

#386 has been merged for `enable_gossip`. Moving on to the other two.

@akbarahmed completed `mbuf_size` and `alloc_msgs_max` https://github.com/Netflix/dynomite/pull/387 transfer to YAML, but still allowing backward compatibility. Feel free to do any other YAML changes. I will add the appropriate changes to DM...

@shailesh33 +1 and it seems you are already on this way :) https://github.com/Netflix/dynomite/pull/393

We have documentation on containers and Dynomite in the Docker folder. Does this help?