?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.
Reviewed: https:/ /review. openstack. org/323274 /git.openstack. org/cgit/ openstack/ fuel-web/ commit/ ?id=90c120b518c d2c0713d99bf8e1 2790deecdc96ea
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 90c120b518cd2c0 713d99bf8e12790 deecdc96ea
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:
?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' Manager and DeploymentTaskM anager as it should be
within OpenStackConfig
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: I374fc86b63af64 411d4a5ca45ff6c 3680cb44897
Partial-bug: #1569839