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

Denis Makogon dmakogon at mirantis.com
Sat Aug 2 07:14:48 UTC 2014


суббота, 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
>> Trove-API service site, see
>> https://github.com/openstack/trove/blob/master/trove/backup/models.py
>> (Method called _validate_can_perform_action)
>>
>> If you'll have another questions, feel free to catch me up at IRC
>> (denis_makogon).
>>
>>
> Thanks Denis - I did wonder if it was an optional specification! Doh!
> However, while I'm a bit ignorant wrt redis and cassandra, I do have a bit
> todo with mongo and that certainly *does* support backup/restore...
>
>
Thank to you too, Mark. There were already filed several BPs related to
back/restore procedure: for Cassandra, for Mongodb( through mongodump and
tayra). Some of them are already hanging at review queue.

Best regards,
Denis Makogon


> Cheers
>
> Mark
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140802/6400eacb/attachment.html>


More information about the OpenStack-dev mailing list