суббота, 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
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
https://github.com/openstack/trove/blob/mas
Sent from my iPhone
> On Aug 2, 2014, at 8:04, Mark Kirkwood wrote:
>
>> 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
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
On Fri, Aug 1, 2014 at 2:30 AM, Mark Kirkwood 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
>
>
> trove/common/cfg.p
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
trove/common/cfg.py
This seems like an oversight - or is there something I'm missing
