openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,435 Commits 4 Branches 3 Tags 267 MiB
Go to file
Alex Schultz 46018e1a25 Initial librarian-puppet-simple configuration 
This change adds support to leverage a Puppetfile located in the
deployment folder to add additional upstream modules.  A new script
called update_modules.sh is now available in the deployment directory
that will run librarian-puppet-simple to update the modules.  The noop
tests have been updated to leverage this script prior to running the
tests. Additionally the fuel-library spec has been updated to execute
the update_modules.sh script as part of the rpm build process.

It should be noted that this is going to use librarian-puppet-simple
which only supports git references and tarballs and provides no
dependancy lookup. This is a much simpler way of pulling in the modules.

Partial blueprint: fuel-puppet-librarian

Change-Id: I5e628f159d2d11121af741bcc1218f292cd2b96e
 		2015-07-31 10:43:59 -05:00
debian Add new tasks for configure and deploy vms 2015-07-14 14:54:41 +02:00
deployment Initial librarian-puppet-simple configuration 2015-07-31 10:43:59 -05:00
files Merge "Make ntpd listen all interfaces" 2015-07-30 13:46:35 +00:00
specs Initial librarian-puppet-simple configuration 2015-07-31 10:43:59 -05:00
tests Merge "Add if check to Sahara/Murano modules" 2015-07-31 15:28:41 +00:00
utils Initial librarian-puppet-simple configuration 2015-07-31 10:43:59 -05:00
.gitignore Add the task graph plotting tool 2015-03-02 17:32:04 +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.