openstack/fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
8,917 Commits 4 Branches 3 Tags 267 MiB
7a75e103af
Go to file
Bogdan Dobrelya 7a75e103af Adapt corosync for Fuel 
* Fix *_real evaluation for erb templates
 (TODO contribute to puppetlabs-corosync upstream)
* Add corosync v2 support
 (TODO contribute to puppetlabs-corosync upstream)
* Adjust logging options for corosync.conf
 (TODO contribute to puppetlabs-corosync upstream)
* Remove 'retries' references for cs_property
* Fix missing block until ready call for cs_property flush
 (TODO contribute to puppetlabs-corosync upstream)
* Rename custom cs_* providers tuned for a parallel execution
  and move them to the pacemaker module:
  - cs_resource
  - cs_rsc_colocation
  - cs_rsc_location
  - cs_rsc_order
* TODO Fix Pacemaker module rspecs (disabled in utils for now)
* Enable rspecs for corosync module

Fuel-ci: disable
related blueprint corosync-2

Change-Id: Ib04360291f99f790f442c4f7382a863206078e27
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2015-01-23 11:05:09 +01:00
deployment/puppet Adapt corosync for Fuel 2015-01-23 11:05:09 +01:00
docs merge with fuel-777 (22053e4e5f) branch 2013-07-30 20:35:42 +04:00
utils Adapt corosync for Fuel 2015-01-23 11:05:09 +01:00
.gitignore Update .gitignore file 2014-12-22 10:48:04 +02: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

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.