Explore placing automatically generated props in another file

[keith-turner]

Some ansible task modify the muchos props file. This could be surprising for a user that wishes to get repeatable performance from a config file. Also, there may be confusing cases when running multiple clusters concurrently. One possible way to avoid this would be to generate another file for automatic props per cluster. This file could possibly be placed in conf/auto/<cluster>.props. The python library for reading config files seems to easily support multiple props files.

https://stackoverflow.com/questions/4029946/multiple-configuration-files-with-python-configparser

I think this change could be beneficial from a usability perspective. However, I am uncertain about how much complexity it could add to the implementation. If the implementation complexity is too high, it may not be worthwhile.

[keith-turner]

Opened this issue based on the following comment.

https://github.com/apache/fluo-muchos/pull/304#discussion_r363978658

[keith-turner]

https://docs.python.org/2/library/configparser.html#ConfigParser.RawConfigParser.read