c20b2f8463
* Add the OSD activation and check if osd process for each OSD is started. * Change the process of adding OSDs to cluster. Now Ceph OSDs are added one by one instead of by all together. This allows to check the every OSD status during adding to cluster. Change-Id: I8e64c1b15ed92e6fb5939b6f41728efacae64319 Closes-bug: #1419884 |
||
---|---|---|
deployment/puppet | ||
utils | ||
.gitignore | ||
.gitreview | ||
CHANGELOG | ||
LICENSE | ||
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.