I tend to say 2) is the best option. There are many open source or
commercial backup software, and both for VMs and volume.
If we do option 1), it reminds me to implement something similar to VMware
method, and it will cause nova really heavy.
On Sun, Aug 31, 2014 at 4:04 AM, Preston L.
I also believe (2) is the most workable option.
Full disclosure ... my current job is at EMC, and we just shipped a backup
product for the VMware vCloud (the one used for VMware vCloud Air -
http://vcloud.vmware.com/http://vcloud.vmware.com/).
First release of that project was wrapping up, and I
You are thinking of written-for-cloud applications. For those the state
should not persist with the instance.
There are a very large number of existing applications, not written to the
cloud model, but which could be deployed in a cloud. Those applications are
not all going to get re-written (as
Looking to put a proper implementation of instance backup into OpenStack.
Started by writing a simple set of baseline tests and running against the
stable/icehouse branch. They failed!
https://github.com/dreadedhill-work/openstack-backup-scripts
Scripts and configuration are in the above. Simple
On 08/29/2014 02:48 AM, Preston L. Bannister wrote:
Looking to put a proper implementation of instance backup into
OpenStack. Started by writing a simple set of baseline tests and running
against the stable/icehouse branch. They failed!
The current backup APIs in OpenStack do not really make sense (and
apparently do not work ... which perhaps says something about usage and
usability). So in that sense, they could be removed.
Wrote out a bit as to what is needed:
I think the purpose of nova VM is not for persistent usage, and it should
be used for stateless. However, there are use cases to use VM to replace
bare metal applications, and it requires the same coverage, which I think
VMware did pretty well.
The nova backup is snapshot indeed, so it should be
