RETIRED, Fuel Library
Go to file
Alexey Deryugin 1722961c12 Use default value of kombu_reconnect_delay for all services
Current reconnection time is 5.0 which is pretty long.
This patch switches kombu_reconnect_delay to its default
value - 1.0 which is the same for all services.

Change-Id: I0d2418f940e7036ad71264da7ad10d7a32bb329b
Closes-bug: #1560097
Closes-Bug: #1440134
2016-06-17 06:16:16 +00:00
debian Revert "Clean rabbitmq dump of auto-delete queues" 2016-01-26 14:38:49 +00:00
deployment Use default value of kombu_reconnect_delay for all services 2016-06-17 06:16:16 +00:00
files Stop process when rabbit is running but is not connected to master. 2016-05-06 12:27:38 +02:00
specs Revert "Clean rabbitmq dump of auto-delete queues" 2016-01-26 14:38:49 +00:00
tests Fill cinder scheduler filters from cinder modular manifest 2016-03-09 14:31:06 +00:00
utils Puppet gem version bump in 'fuel_syntax_check.sh' 2016-05-10 16:52:29 +03:00
.gitignore Fix error in the noops tests framework 2015-08-11 16:14:15 +03:00
.gitreview Update paths due to stackforge migration. 2015-10-20 14:38:38 +02:00
CHANGELOG Edit Changelog 2013-05-23 13:38:03 +03:00
Gemfile pin google-api-client to 0.9.4 2016-04-18 14:20:43 +00:00
LICENSE LICENCE added 2014-06-05 20:00:54 +00:00
README.md RabbitMQ FAQ notes prettified 2013-05-08 23:19:41 +04:00
Rakefile Fix openstack ci lint job for stable branches 2015-12-08 10:06:26 +00:00

README.md

Fuel is the Ultimate Do-it-Yourself Kit for OpenStack

Purpose built to assimilate the hard-won experience of our services team, it contains the tooling, information, and support you need to accelerate time to production with OpenStack cloud.

OpenStack is a very versatile and flexible cloud management platform. By exposing its portfolio of cloud infrastructure services compute, storage, networking and other core resources — through ReST APIs, it enables a wide range of control over these services, both from the perspective of an integrated Infrastructure as a Service (IaaS) controlled by applications, as well as automated manipulation of the infrastructure itself.

This architectural flexibility doesnt set itself up magically; it asks you, the user and cloud administrator, to organize and manage a large array of configuration options. Consequently, getting the most out of your OpenStack cloud over time in terms of flexibility, scalability, and manageability requires a thoughtful combination of automation and configuration choices.

Mirantis Fuel for OpenStack was created to solve exactly this problem.