Seems to me there are three threads here. The Freezer folk were given a task, and did the best possible to support backup given what OpenStack allowed. To date, OpenStack is simply not very good at supporting backup as a service. (Apologies to the Freezer folk if I misinterpreted.)
The patches (finally) landing in QEMU in support of incremental backup could be the basis for efficient backup services in OpenStack. This is all fairly high risk, in the short term. The bits that landed in QEMU 2.4 may not be sufficient (there are more QEMU patches trying to land). When put into production, we may find faults. For use in OpenStack, we may need changes in libvirt, and/or in Nova. (Or *maybe* not if usage for backup proves orthogonal.) The only way to work out the prior is to start. The timeline could be months or years. There is a need for a common API for backup as a service in the cloud. Something more than imitating AWS. Allow some room for vendors with differing approach. I see the above as not competing, but aspects of the same problem.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
