Comment 15 for bug 1569839

Reviewed: https://review.openstack.org/305401
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e4fbfe80ed468848429d7577396b68d6ffdc2d0e
Submitter: Jenkins
Branch: master

commit e4fbfe80ed468848429d7577396b68d6ffdc2d0e
Author: Vladimir Kuklin <email address hidden>
Date: Thu May 5 12:51:46 2016 +0300

    Allow a user to run dry-run deployment

    Now following handlers:

         /clusters/:cluster_id/changes/
         /clusters/:cluster_id/changes/redeploy/
         /clusters/:cluster_id/deploy/
         /clusters/:cluster_id/deploy_tasks/

    ?dry_run=1 that is telling Astute not to run cluster executionat all.

    Dry run assumes that it does not actually affect
    cluster status regardless of their result.

    Also, remove redundant update of nodes statuses to 'deploying'
    within OpenStackConfigManager and DeploymentTaskManager as it should be
    done by receiever.

    Do not set cluster status to 'deployment' for these nodes in order to
    retain its real status

    Modify stop deployment tests to move failing stop deployment for already
    deployed clusters to another test class. Since 9.0 we can run stop
    deployment for new clusters.

    Change-Id: I374fc86b63af64411d4a5ca45ff6c3680cb44897
    Partial-bug: #1569839