<div dir="ltr">What is current best practice to restore a failed Fuel node?</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><font><div style="font-family:arial;font-size:small"><b><i><br>Adam Lawson</i></b></div><div><font><font color="#666666" size="1"><div style="font-family:arial"><br></div><div style="font-family:arial;font-size:small">AQORN, Inc.</div><div style="font-family:arial;font-size:small">427 North Tatnall Street</div><div style="font-family:arial;font-size:small">Ste. 58461</div><div style="font-family:arial;font-size:small">Wilmington, Delaware 19801-2230</div><div style="font-family:arial;font-size:small">Toll-free: (844) 4-AQORN-NOW ext. 101</div><div style="font-family:arial;font-size:small">International: +1 302-387-4660</div></font><font color="#666666" size="1"><div style="font-family:arial;font-size:small">Direct: +1 916-246-2072</div></font></font></div></font></div><div style="font-family:arial;font-size:small"><img src="http://www.aqorn.com/images/logo.png" width="96" height="39"><br></div></div></div>
<br><div class="gmail_quote">On Wed, Oct 22, 2014 at 10:40 AM, Sergii Golovatiuk <span dir="ltr"><<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Andrew,<br><br></div>Thank you for sharing your ideas. We have similar blueprint where you should be able to save/restore information about your environment<br><br><a href="https://blueprints.launchpad.net/fuel/+spec/save-and-restore-env-settings" target="_blank">https://blueprints.launchpad.net/fuel/+spec/save-and-restore-env-settings</a><br><br></div>For development, it's very useful when you need to create the identical environment (including networks) or other specific tasks. Also you may use the case to backup information about a cluster and restore one particular node.<br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Wed, Oct 22, 2014 at 6:07 PM, Andrey Volochay <span dir="ltr"><<a href="mailto:avolochay@mirantis.com" target="_blank">avolochay@mirantis.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px">Hi, everyone.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">For one project we need to have backup of info about nodes (astute.yaml). In case the Fuel and a Node-n is down.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">How a bad idea to keep a copy of the astute.yaml file of each node to each node of the cluster?</div><div style="font-family:arial,sans-serif;font-size:13px">For example:</div><div style="font-family:arial,sans-serif;font-size:13px">pod_state/node-1.yaml</div><div style="font-family:arial,sans-serif;font-size:13px">pod_state/node-2.yaml</div><div style="font-family:arial,sans-serif;font-size:13px">pod_state/node-3.yaml</div><div style="font-family:arial,sans-serif;font-size:13px">pod_state/node-n.yaml</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">I have idea. Add new deployment engine for astute.yaml and switcher of engines. Then we will be able to choose between two ways.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">engine here: fuel-astute/lib/astute/deployment_engine</div><span><font color="#888888"><div><br></div>-- <br><div dir="ltr"><div><span style="color:rgb(153,153,153)">Regards,<br>Andrey Volochay</span><br></div></div>
</font></span></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>