Comment 7 for bug 1402738

Reviewed: https://review.openstack.org/153198
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=dc8edb6e66d8a76e70fb92732924575258ba910c
Submitter: Jenkins
Branch: master

commit dc8edb6e66d8a76e70fb92732924575258ba910c
Author: Aleksandr Didenko <email address hidden>
Date: Thu Dec 11 12:26:44 2014 +0200

    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