Denis,
I'm proposing that #3 and #4 sorta be swapped from your list where we merge
the config group parameters into the main config and send down the file
like we do now. So the guest does not need to handle the merging. The logic
is the same just the location of the logic to merge be handled by
I disagree. Guest should be able to do (for now two things):
1. Installing db, post-install configuration (dpkg reconfigure, etc.)
2. Allowing to apply outcome configuration in dictionary format.
As i mentioned earlier. There could be a problem with updating full config
file. Reason is simple:
We need to determine if we should not use a separate file for the overrides
config as it might not be supported by all dbs trove supports. (works well
for mysql but might not for cassandra as we discussed in the irc channel)
To support this for all dbs we could setup the jinja templates to add
I would like to see this functionality in the next way:
1. Creating parameters group.
2. Validate and Save.
3. Send to an instance those parameters in dict representation.
4. Merge into main config.
PS: #4 is database specific, so it's should be handled by manager.
2013/11/13 Craig Vyvial
