openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,030 Commits 4 Branches 3 Tags 267 MiB
Go to file
Dmitry Mescheryakov bb5340e01f Start RabbitMQ app on notify 
On notify, if we detect that we are a part of a cluster we still
need to start the RabbitMQ application, because it is always
down after action_start finishes.

Closes-Bug: #1496386
Change-Id: I307452b687a6100cc4489c8decebbc3dccdbc432
(cherry picked from commit c1900b49e6)
 		2016-01-20 16:46:56 +00:00
debian Make log rotation more bulletproof 2015-06-15 08:07:21 +00:00
deployment/puppet Merge "Fix mock nbd block devices" into stable/6.1 2015-12-04 14:26:15 +00:00
files Start RabbitMQ app on notify 2016-01-20 16:46:56 +00:00
specs Update paths due to stackforge migration. 2015-10-20 13:06:43 +00:00
tests/noop Avoid neighbour table overflow problem 2015-11-30 14:51:54 +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 Fix openstack ci lint job for stable branches 2015-11-26 10:30:56 +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-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.