Re: [openstack-dev] [Fuel] Backup of information about nodes.

2014-11-08 Thread Mike Scherbakov
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. We have been considering
considering making separate swift role, though it never happened to get
resources for it.

Thanks,

On Fri, Oct 24, 2014 at 9:01 PM, Adam Lawson alaw...@aqorn.com wrote:

 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.
 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 Thu, Oct 23, 2014 at 2:59 AM, Tomasz Napierala tnapier...@mirantis.com
  wrote:


 On 22 Oct 2014, at 21:03, Adam Lawson alaw...@aqorn.com 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...@mirantis.com







 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Mike Scherbakov
#mihgen
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Fuel] Backup of information about nodes.

2014-10-24 Thread Adam Lawson
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.
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 Thu, Oct 23, 2014 at 2:59 AM, Tomasz Napierala tnapier...@mirantis.com
wrote:


 On 22 Oct 2014, at 21:03, Adam Lawson alaw...@aqorn.com 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...@mirantis.com







 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Fuel] Backup of information about nodes.

2014-10-23 Thread Tomasz Napierala

On 22 Oct 2014, at 21:03, Adam Lawson alaw...@aqorn.com 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...@mirantis.com







___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Re: [openstack-dev] [Fuel] Backup of information about nodes.

2014-10-22 Thread Sergii Golovatiuk
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 avoloc...@mirantis.com
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
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Fuel] Backup of information about nodes.

2014-10-22 Thread Adam Lawson
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 
sgolovat...@mirantis.com 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 avoloc...@mirantis.com
 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
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev