<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 24, 2017 at 3:17 PM, Jiří Stránský <span dir="ltr"><<a href="mailto:jistr@redhat.com" target="_blank">jistr@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 24.5.2017 15:02, Marios Andreou wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, May 24, 2017 at 10:26 AM, Carlos Camacho Gonzalez <<br>
<a href="mailto:ccamacho@redhat.com" target="_blank">ccamacho@redhat.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey folks,<br>
<br>
Based on what we discussed yesterday in the TripleO weekly team meeting,<br>
I'll like to propose a blueprint to create 2 features, basically to backup<br>
and restore the Undercloud.<br>
<br>
I'll like to follow in the first iteration the available docs for this<br>
purpose [1][2].<br>
<br>
With the addition of backing up the config files on /etc/ specifically to<br>
be able to recover from a failed Undercloud upgrade, i.e. recover the repos<br>
info removed in [3].<br>
<br>
I'll like to target this for P as I think I have enough time for<br>
coding/testing these features.<br>
<br>
I already have created a blueprint to track this effort<br>
<a href="https://blueprints.launchpad.net/tripleo/+spec/undercloud-backup-restore" rel="noreferrer" target="_blank">https://blueprints.launchpad.n<wbr>et/tripleo/+spec/undercloud-ba<wbr>ckup-restore</a><br>
<br>
What do you think about it?<br>
<br>
</blockquote>
<br>
+1 from me as you know but adding my support on the list too. I think it is<br>
a great idea - there are cases especially around changing network config<br>
during an upgrade for example where the best remedy is to restore the<br>
undercloud for the network definitions (both neutron config and heat db).<br>
</blockquote>
<br></span>
+1 i think there's not really an easy way out of these issues other than a restore. We already recommend doing a backup before upgrading [1], so having something that can further help operators in this regard would be good.<br>
<br></blockquote><div><br></div><div>Hey Jiri, Marios!!!</div><div><br></div><div>Sorry for the delayed reply here. </div><div><br></div><div>Yeahp, that's what I'll like to achieve, more than recover the UC, this is about to restore it to a point we know it was working correctly.</div><div><br></div><div>Now, I'm following Ben's advise for this new iteration, taking a part the big method which is currently meking the backup into small ones for finishing the unit thests.<br></div><div> </div><div>Cheers,</div><div>Carlos.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jirka<br>
<br>
[1] <a href="http://tripleo.org/post_deployment/upgrade.html" rel="noreferrer" target="_blank">http://tripleo.org/post_deploy<wbr>ment/upgrade.html</a><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
thanks,<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Carlos.<br>
<br>
[1]: <a href="https://access.redhat.com/documentation/en-us/red_hat_" rel="noreferrer" target="_blank">https://access.redhat.com/docu<wbr>mentation/en-us/red_hat_</a><br>
enterprise_linux_openstack_pla<wbr>tform/7/html/back_up_and_<br>
restore_red_hat_enterprise_lin<wbr>ux_openstack_platform/restore<br>
<br>
[2]: <a href="https://docs.openstack.org/developer/tripleo-docs/post_" rel="noreferrer" target="_blank">https://docs.openstack.org/dev<wbr>eloper/tripleo-docs/post_</a><br>
deployment/backup_restore_unde<wbr>rcloud.html<br>
<br>
[3]: <a href="https://docs.openstack.org/developer/tripleo-docs/" rel="noreferrer" target="_blank">https://docs.openstack.org/dev<wbr>eloper/tripleo-docs/</a><br>
installation/updating.html<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>