Updated armband
authorMichal Skalski <mskalski@mirantis.com>
Tue, 27 Sep 2016 15:17:18 +0000 (15:17 +0000)
committerGerrit Code Review <gerrit@172.30.200.206>
Tue, 27 Sep 2016 15:17:18 +0000 (15:17 +0000)
commitecc2fd5439fbf17e573f34a4772f5eae203bd537
tree182215206e7166fc59b2bc036f599ba7c8a39510
parent8f59c00171478596437e88a1eea868f12b2a877b
Updated armband
Project: fuel  f2fde8258dedfbbeae52d0c9b1d3a634fd290877

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>
upstream/fuel