Module configuration key naming

Baohua Yang <yangbaohua@...>

Hi, all
     I notice that for most modules, the naming of the configuration key follows the lower camel case, such as "subnetConfig“, "userLinks", "staticRoute", "hostConfig"... 
     After getting the module content, we can leverage this to parse the information.
     However, for the container manager module, the name is "container-config", which is specially different. Is there any reason for this?
     Will submit a patch if necessary.

Best wishes!