Adam - sorry, looks like your question was missed.
It seems to be not directly related to the original email topic, but anyway
- currently Fuel doesn't deploy standalone Swift nodes.
Swift is used only on controllers. So you are correct, you can add more
Swift capacity by adding more controllers. W
Okay and one other question which I must have missed; is it possible to
expand Swift capacity through Fuel? I notice Swift is installed on the
Controllers but if we need to expand Swift capacity, does that necessarily
mean Fuel requires the addition of more Controllers?
*Adam Lawson*
AQORN, Inc.
On 22 Oct 2014, at 21:03, Adam Lawson wrote:
> What is current best practice to restore a failed Fuel node?
It’s documented here:
http://docs.mirantis.com/openstack/fuel/fuel-5.1/operations.html#restoring-fuel-master
Regards,
--
Tomasz 'Zen' Napierala
Sr. OpenStack Engineer
tnapier...@miranti
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 Golov
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
env
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.
