openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,050 Commits 4 Branches 3 Tags 267 MiB
Go to file
Alexey Deryugin 234335f3cb 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: I8e0230bf48620a8b5e1d7339e419b9b682e5cbd8
Closes-bug: #1560097
Closes-Bug: #1440134
 		2016-06-17 06:16:29 +00:00
debian Make log rotation more bulletproof 2015-06-15 08:07:21 +00:00
deployment/puppet Use default value of kombu_reconnect_delay for all services 2016-06-17 06:16:29 +00:00
files Add SST check to mysql_status 2016-04-22 13:19:52 +00:00
specs Update paths due to stackforge migration. 2015-10-20 13:06:43 +00:00
tests/noop Fix show_image_direct_url value for glance-api 2016-04-21 14:11:04 +03:00
utils Fix openstack ci lint job for stable branches 2015-11-26 10:30:56 +00:00
.gitignore Add the task graph plotting tool 2015-03-02 17:32:04 +03:00
.gitreview Update paths due to stackforge migration. 2015-10-20 13:06:43 +00: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:23:51 +03: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-11-26 10:30:56 +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 doesn’t 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.