What is current best practice to restore a failed Fuel node?
*Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Wed, Oct 22, 2014 at 10:40 AM, Sergii Golovatiuk < [email protected]> wrote: > Hi Andrew, > > Thank you for sharing your ideas. We have similar blueprint where you > should be able to save/restore information about your environment > > https://blueprints.launchpad.net/fuel/+spec/save-and-restore-env-settings > > 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. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Wed, Oct 22, 2014 at 6:07 PM, Andrey Volochay <[email protected]> > wrote: > >> Hi, everyone. >> >> For one project we need to have backup of info about nodes (astute.yaml). >> In case the Fuel and a Node-n is down. >> >> How a bad idea to keep a copy of the astute.yaml file of each node to >> each node of the cluster? >> For example: >> pod_state/node-1.yaml >> pod_state/node-2.yaml >> pod_state/node-3.yaml >> pod_state/node-n.yaml >> >> I have idea. Add new deployment engine for astute.yaml and switcher of >> engines. Then we will be able to choose between two ways. >> >> engine here: fuel-astute/lib/astute/deployment_engine >> >> -- >> Regards, >> Andrey Volochay >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
