<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394">Hi Fausto,</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394">where can I find information about implemented and currently working functionalities?</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394">Thank you,</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394">Giuseppe</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:#0b5394"><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-07 13:28 GMT+02:00 Marzi, Fausto <span dir="ltr"><<a href="mailto:fausto.marzi@hp.com" target="_blank">fausto.marzi@hp.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Giuseppe, Avishay, all,<br>
<br>
In the Company where I'm currently working on, there are 4 Engineers full time dedicated to Freezer.<br>
<br>
Your consideration Avishay make totally sense. There are also other points that probably needs to be taken in consideration for DR as:<br>
<br>
- Backup and restore synchronized across multiple services:<br>
This is important, as for instance Nova depends on many other OS service (i.e. cinder, glance, etc).<br>
<br>
- When users execute a backup of a VM, it is also expected that the Cinder Volumes, the images and the users/tenants can also be point-in-time restored<br>
<br>
- It is important to be able to restore data, even if any one of the OS Services is down (i.e. Keystone or Swift are not available).<br>
<br>
- The orchestration between Nova and Cinder to execute full VM + Cinder backups is important<br>
<br>
- Have a unified API and Web UI in Horizon is also a nice to have<br>
<br>
These and more are the challenges that in the Freezer Team we are solving.<br>
<br>
Being totally honest, Freezer has been used to backup many services in a reasonably big OpenStack instance for a year now.<br>
However, it's only 6 months there's a dedicated Team working on it, so many things still needs to be done.<br>
<br>
For any real time interaction, we are in #openstack-freezer on Freenode , so feel free to say Hi if you are around : )<br>
<br>
Contributors are most welcome.<br>
<br>
Thanks,<br>
Fausto<br>
<span class=""><br>
-------- Forwarded Message --------<br>
Subject: Re: [Openstack] [OpenStack] [Disaster Recovery] How can you do<br>
it?<br>
Date: Tue, 7 Jul 2015 11:44:17 +0200<br>
From: Giuseppe Galeota <<a href="mailto:giuseppegaleota@gmail.com">giuseppegaleota@gmail.com</a>><br>
To: Avishay Traeger <<a href="mailto:avishay@stratoscale.com">avishay@stratoscale.com</a>><br>
CC: <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a> <<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>><br>
<br>
<br>
<br>
Thank you all.<br>
What can you tell me about the following projects:<br>
<br>
- <a href="https://wiki.openstack.org/wiki/Raksha" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Raksha</a><br>
- <a href="https://github.com/stackforge/freezer" rel="noreferrer" target="_blank">https://github.com/stackforge/freezer</a><br>
<br>
Will they become OpenStack project?<br>
<br>
Thanks,<br>
Giuseppe<br>
<br>
2015-07-06 21:33 GMT+02:00 Avishay Traeger <<a href="mailto:avishay@stratoscale.com">avishay@stratoscale.com</a><br>
</span><mailto:<a href="mailto:avishay@stratoscale.com">avishay@stratoscale.com</a>>>:<br>
<div><div class="h5"><br>
As David mentioned, there is a spectrum of possible solutions for<br>
disaster recovery. The solution, as always, depends on the<br>
requirements. In disaster recovery, those requirements are<br>
expressed as:<br>
1. RPO - Recovery Point Objective - "If a disaster strikes, how far<br>
back will it set me?"<br>
2. RTO - Recovery Time Objective - "If a disaster strikes, how long<br>
until my workload is up and running?"<br>
<br>
The answers to both are independent and can range from "Not at all"<br>
to minutes or hours or days.<br>
<br>
A solution with high RPO and RTO is backup. Once in a while<br>
transfer your images, snapshots of your VMs and volumes, and your<br>
SQL DB to another site. If disaster strikes you can manually run<br>
your workloads from the last backup, and you have your metadata<br>
backed up too (keystone users/tenants, nova flavors, etc.).<br>
<br>
A solution with lower RPO and RTO is replication. Work is being done<br>
in Cinder to enable continuous volume replication between storage<br>
backends. You can put your Glance images in multiple locations or<br>
in multi-site Swift, and replicate your DB as well. Ideally you<br>
will be able to get to some consistent state between your data and<br>
metadata, which is not easy. For failover, you can use Heat or some<br>
other orchestration tool.<br>
<br>
There are solutions with zero RPO and RTO, where workloads run<br>
active/active in multiple sites. There are also other solutions in<br>
the spectrum.<br>
<br>
In short, the building blocks are starting to appear, but a full<br>
solution is not yet available.<br>
<br>
<br>
On Mon, Jul 6, 2015 at 8:08 PM, David Medberry<br>
</div></div><span class=""> <<a href="mailto:openstack@medberry.net">openstack@medberry.net</a> <mailto:<a href="mailto:openstack@medberry.net">openstack@medberry.net</a>>> wrote:<br>
<br>
Yes.<br>
<br>
<a href="http://docs.openstack.org/openstack-ops/content/snapshots.html" rel="noreferrer" target="_blank">http://docs.openstack.org/openstack-ops/content/snapshots.html</a><br>
API Image Create detailed here:<br>
<br>
Nova:<br>
<a href="http://developer.openstack.org/api-ref-compute-v2.1.html" rel="noreferrer" target="_blank">http://developer.openstack.org/api-ref-compute-v2.1.html</a><br>
It is a snapshot of the instance's image (not of the instance's<br>
in memory state).<br>
<br>
Cinder:<br>
<a href="http://developer.openstack.org/api-ref-blockstorage-v2.html" rel="noreferrer" target="_blank">http://developer.openstack.org/api-ref-blockstorage-v2.html</a><br>
<br>
<a href="http://lmgtfy.com/?q=nova+image+create+api" rel="noreferrer" target="_blank">http://lmgtfy.com/?q=nova+image+create+api</a><br>
<a href="http://lmgtfy.com/?q=cinder+snapshot+api" rel="noreferrer" target="_blank">http://lmgtfy.com/?q=cinder+snapshot+api</a><br>
<br>
<br>
On Mon, Jul 6, 2015 at 11:02 AM, Giuseppe Galeota<br>
</span> <<a href="mailto:giuseppegaleota@gmail.com">giuseppegaleota@gmail.com</a> <mailto:<a href="mailto:giuseppegaleota@gmail.com">giuseppegaleota@gmail.com</a>>><br>
<span class=""> wrote:<br>
<br>
Thank you David,all,<br>
<br>
I would like to know if are there Nova/Cinder Rest APIs to<br>
execute VM/volume snapshot?<br>
<br>
Thank you all,<br>
Giuseppe<br>
<br>
2015-07-06 18:40 GMT+02:00 David Medberry<br>
</span> <<a href="mailto:openstack@medberry.net">openstack@medberry.net</a> <mailto:<a href="mailto:openstack@medberry.net">openstack@medberry.net</a>>>:<br>
<span class=""><br>
Giuseppe,<br>
<br>
A great deal of Disaster Recovery planning relies on you<br>
/ your organization to define what they mean by DR<br>
planning. Yes, Nova snaps (instance snaps) and Cinder<br>
snaps (volume snaps) can be used in DR. Additionally,<br>
depending on your architecture you can utilize Swift (if<br>
it is geo distributed, it gives you some measure of DR<br>
resilience.)<br>
<br>
I'm not aware of a howto or manual on this topic though<br>
as it varies so much based on arch and definition it's<br>
not effective to make a generalized recommendation.<br>
<br>
On Mon, Jul 6, 2015 at 10:02 AM, Giuseppe Galeota<br>
<<a href="mailto:giuseppegaleota@gmail.com">giuseppegaleota@gmail.com</a><br>
</span><span class=""> <mailto:<a href="mailto:giuseppegaleota@gmail.com">giuseppegaleota@gmail.com</a>>> wrote:<br>
<br>
Dear all,<br>
how can I implement a Disaster Recovery plan in<br>
OpenStack? Is there some project?<br>
<br>
Can I use the Nova/Cinder APIs to create snapshot<br>
and upload them somewhere?<br>
<br>
Thanks,<br>
Giuseppe<br>
<br>
_______________________________________________<br>
Mailing list:<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
</span> <mailto:<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>><br>
<span class=""> Unsubscribe :<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Mailing list:<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
</span> <mailto:<a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>><br>
Unsubscribe :<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
<br>
<br>
<br>
--<br>
*Avishay Traeger*<br>
/Storage R&D/<br>
<span class=""><br>
Mobile:<a href="tel:%2B972%2054%20447%201475" value="+972544471475">+972 54 447 1475</a><br>
</span> E-mail: <a href="mailto:avishay@stratoscale.com">avishay@stratoscale.com</a> <mailto:<a href="mailto:avishay@stratoscale.com">avishay@stratoscale.com</a>><br>
<br>
<br>
<br>
Web <<a href="http://www.stratoscale.com/" rel="noreferrer" target="_blank">http://www.stratoscale.com/</a>> | Blog<br>
<<a href="http://www.stratoscale.com/blog/" rel="noreferrer" target="_blank">http://www.stratoscale.com/blog/</a>> | Twitter<br>
<<a href="https://twitter.com/Stratoscale" rel="noreferrer" target="_blank">https://twitter.com/Stratoscale</a>> | Google+<br>
<<a href="https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts" rel="noreferrer" target="_blank">https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts</a>> |<br>
Linkedin <<a href="https://www.linkedin.com/company/stratoscale" rel="noreferrer" target="_blank">https://www.linkedin.com/company/stratoscale</a>><br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>