Change the way how we track deployment 79/22679/1
authorMichal Skalski <mskalski@mirantis.com>
Tue, 20 Sep 2016 07:38:32 +0000 (09:38 +0200)
committerMichal Skalski <mskalski@mirantis.com>
Tue, 4 Oct 2016 08:42:24 +0000 (08:42 +0000)
commitb295ae64a96d2c74ad562d70849e3d67f8b7c1ee
treee032b3c30fc33d033a06b3781b455f3ce3364629
parent8e501a8589db2c5f29a43b5fb2d253c431397b4f
Change the way how we track deployment

Use fuel2 for start deployment. Since it does not return progress
use deployment task to provide this information. Currently used
'deploy-changes' will behave the same:
https://bugs.launchpad.net/fuel/+bug/1565026

Try to handle situation when nodes temporary go offline. With
deploy-changes environment still was in 'new' state in this situtation
which causes timeouts from jenkins.

JIRA: FUEL-196

Change-Id: I6548a5ec807551388e845044c282b7af32eb9100
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
(cherry picked from commit b73526033c5c5b93ca96f411a1d90dc5c49b9228)
deploy/cloud/deployment.py