2cd8c10151
1) Add test to check whether catalog contains injection of files which actually should be installed as packages 2) Add more fixtures with astute yamls 3) Shared examples structure refactoring 4) Remove File.exists? checks from install_ssh_keys 5) Add rspec and puppet debug options 6) Misc fixes to make rspec actually work Change-Id: I8217594cd9f2c0f19c840c0abed37d94ff80eb75 blueprint: package-fuel-components |
||
|---|---|---|
| debian | ||
| deployment/puppet | ||
| files | ||
| specs | ||
| tests/noop | ||
| 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.