RETIRED, Fuel Library
Go to file
Igor Yozhikov e96c4d1fd3 Add heat auth_encryption_key handling
* Heat auth_encryption_key now readed from nailgun
via osnailyfacter and it should be used for heat-engine
instances in cloud.
* Disabled start-up and run via pacemaker in case
of HA mode for heat-engine.

Change-Id: Icc65f5316762421f1477e32fbd9c3f7071f0a2aa
Related-Bug: #1387345
2014-11-13 14:40:13 +03:00
deployment/puppet Add heat auth_encryption_key handling 2014-11-13 14:40:13 +03:00
docs merge with fuel-777 (22053e4e5f) branch 2013-07-30 20:35:42 +04:00
utils Run syntax check for OCF scripts 2014-10-09 12:30:54 +03:00
.gitignore Make rdoc script 2013-09-16 15:59:43 +04:00
.gitreview Setup git-review 2013-12-11 14:31:13 +04:00
CHANGELOG Edit Changelog 2013-05-23 13:38:03 +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

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.