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 the service rather than at the guest.
Most of the "merging" logic could be part of the jinja template we already have. This will allow the guest to be agnostic of the type of config file and less logic in the guest. -Craig On Wed, Nov 13, 2013 at 1:19 PM, Denis Makogon <dmako...@mirantis.com>wrote: > 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 <cp16...@gmail.com> > >> 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 the >> configs to the end of the main config file (my.cnf for mysql example). >> >> >> -Craig Vyvial >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
