openstack
/
fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
9,505 Commits 4 Branches 3 Tags 267 MiB
Go to file
Aleksandr Didenko dc8edb6e66 Modular noop tests 
We can run noop tests via 'rake spec'. This will allow us to:

  - Make sure that catalog compiles and there are no dependency
    cycles in the graph.
  - Use RSpec tests to check that needed puppet resources present
    in the catalog for specific astute.yaml configuration.

In order to test just execute these commands:
  export WORKSPACE=/tmp/fuel_noop_tests
  mkdir -p $WORKSPACE
  ./utils/jenkins/fuel_noop_tests.sh

It iterates over astsute.yaml files and runs rspec tests for puppet
tasks configured in the astute.yaml for the node.

In order to run specific test and/or specific astute.yaml, you can
set appropriate env variables. For example:
  export NOOP_TEST="keystone/*"
  export NOOP_YAMLS="tests/noop/astute.yaml/novanet_flat.primary-controller.yaml"
  ./utils/jenkins/fuel_noop_tests.sh

If you also want to store puppet logs in case of errors, please set
PUPPET_LOGS_DIR env variable:
  export PUPPET_LOGS_DIR=/tmp/puppet_error_logs

If you want to store all the delcarated File and Package resources,
please set NOOP_SAVE_RESOURCES_DIR env variable:
  export NOOP_SAVE_RESOURCES_DIR=/tmp/puppet_resources

Related-bug: #1402738
Implement blueprint deployment-dryrun

Fuel CI temporarily disabled since this change does not affect
MOS deplyoment process, only CI itself.

Fuel-CI: disable

Change-Id: I38b23832d1e8701440aacb300256f513c466c762
 		2015-04-09 11:56:33 +03:00
deployment/puppet Merge "Make block device mapping timeout configurable" 2015-04-08 16:24:50 +00:00
tests/noop Modular noop tests 2015-04-09 11:56:33 +03:00
utils Modular noop tests 2015-04-09 11:56:33 +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.