openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,980 Commits 4 Branches 3 Tags 267 MiB
Go to file
Alex Schultz 5c3e685c9c Moving socat to a fuel-misc dependency 
fuel-misc provides haproxy-status which needs socat. Additionally we
are currently requiring the socat package in several places in
puppet to try and satisfy this dependancy. This will consolidate
them into a single requirement where it is needed.

Depends-On: I951b137627880b20ece3c64e6a0c8b6ab473daab
Change-Id: If3069c8c7bc68337596195e27e2213a4c9ec3540
Closes-Bug: 1479033
 		2015-09-25 13:13:34 +00:00
debian Moving socat to a fuel-misc dependency 2015-09-25 13:13:34 +00:00
deployment Moving socat to a fuel-misc dependency 2015-09-25 13:13:34 +00:00
files Interpolate vars in ns_IPaddr2 ocf 2015-09-23 17:23:57 +03:00
specs Moving socat to a fuel-misc dependency 2015-09-25 13:13:34 +00:00
tests Moving socat to a fuel-misc dependency 2015-09-25 13:13:34 +00:00
utils Merge "Add module reset logic for librarian" 2015-09-24 11:20:17 +00:00
.gitignore Fix error in the noops tests framework 2015-08-11 16:14:15 +03: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.