#12 | update readme with the section supported configuration

[hoavt]

connect #12

@hieptranquoc Please review this pr.

[hieptranquoc]

@hoavt It should be detailed, rather than listed. Specifies the function of each major configure.

[hieptranquoc]

@hoavt we can create example directory, and put config.example.yaml in it.

[hoavt]

@hoavt It should be detailed, rather than listed. Specifies the function of each major configure.

Their function are mentioned in the configuration file. Why do we need to rewrite them anymore? When we have any changes in the config file, we don;t need to change the README file anymore.

[hoatle]

it's expected that users should know how to use by referring docs, not the source code. Docs should explain in more details for what and why, which param is required, which is optional, what is the default value, etc.

[hoatle]

examples are expected for different config types: variables, plugins, default and nodes, etc.

[hoavt]

@hieptranquoc Please review, and add more examples for "default" and "variables". Moreover, which params need to be explained more, please help me to explain them. which param is required, which is optional...

[hoavt]

@hieptranquoc Please review the new commit.

[hoavt]

@hieptranquoc please review.

[hoatle]

need to split the examples into the following example configs:

• examples/variables.yaml
• examples/plugins.yaml
• examples/vm-vb-providers.yaml
• examples/file-provisioner.yaml
• examples/shell-provisioner.yaml
• examples/ansible-local-provisioner.yaml
• examples/chef-solo-provisioner.yaml
• examples/multi-nodes.yaml

how to run and expected outcome and behavior should be explained.