openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,164 Commits 4 Branches 3 Tags 267 MiB
Go to file
iberezovskiy 6f78b4214f Return back nova floating IP range support 
This patch: a88bc1906a
  was missed by mistake in adapt of nova module,
  which broke deployment with nova network.
  So, we should move back this provider as addition
  to adapt nova module.

  Add noop test coverage for this resource.

  Closes-bug: #1472529

  TODO (iberezovskiy): rework this change using
  one of the following ways:
    1. Get rid of usage of custom ruby-openstack and
       ruby-netaddr packages and propose
       this patch to upstream module
    2. Move floating ip range support out of nova module
    3. Merge new functions to nova_floating provider
       and use it in deployment
      (also with proposed patch to upstream)

Change-Id: Ie1f48b9bb58b8ab205ee1b7eabe9fc4787aa8011
 		2015-07-10 08:29:41 +00:00
debian Rename clustercheck to galeracheck 2015-06-24 16:18:32 -05:00
deployment/puppet Return back nova floating IP range support 2015-07-10 08:29:41 +00:00
files Merge "Restart rabbit if can't list queues or found memory alert" 2015-07-09 07:25:16 +00:00
specs fuel-migrate script 2015-07-02 18:22:47 +03:00
tests Return back nova floating IP range support 2015-07-10 08:29:41 +00:00
utils Adapt synced openstacklib module 2015-07-07 12:14:37 +03: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.