Re: [openstack-dev] [Trove] Backup/restore namespace config move has leftovers

2014-08-02 Thread Mark Kirkwood
On 02/08/14 18:24, Denis Makogon wrote: Mark, we don't have to add backup/restore namespace options to datastores that does't support backup/restore feature. You should take a look how backup procedure is being executed at Trove-API service site, see

Re: [openstack-dev] [Trove] Backup/restore namespace config move has leftovers

2014-08-02 Thread Denis Makogon
суббота, 2 августа 2014 г. пользователь Mark Kirkwood написал: On 02/08/14 18:24, Denis Makogon wrote: Mark, we don't have to add backup/restore namespace options to datastores that does't support backup/restore feature. You should take a look how backup procedure is being executed at

Re: [openstack-dev] [Trove] Backup/restore namespace config move has leftovers

2014-08-01 Thread Denis Makogon
On Fri, Aug 1, 2014 at 2:30 AM, Mark Kirkwood mark.kirkw...@catalyst.net.nz wrote: In my latest devstack pull I notice that backup_namespace restore_namespace have moved from the default conf group to per datastore (commit 61935d3). However they still appear in the common_opts section of

Re: [openstack-dev] [Trove] Backup/restore namespace config move has leftovers

2014-08-01 Thread Mark Kirkwood
On 01/08/14 21:35, Denis Makogon wrote: I'd suggest to file a bug report and fix given issue. Done. https://bugs.launchpad.net/trove/+bug/1351545 I also took the opportunity to check if all the currently defined datastores had backup/restore_namespace set - they didn't, so I noted that