diff options
| author |   Michal Skalski <mskalski@mirantis.com> | 2016-10-07 09:24:05 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@opnfv.org> | 2016-10-07 09:24:05 +0000 |
| commit | f68ad3ff3302ae34c7d70f52413e8e4dda17c697 (patch) | |
| tree | d9cc5b02b63a53bd3ccb333f01523dc440f6b20f /upstream/fuel | |
| parent | eb424346906089a37de45bb742d6ee5cb4a75a8d (diff) | |
Update git submodules
* Update upstream/fuel from branch 'stable/colorado'
- Merge "Change the way how we track deployment" into stable/colorado
- 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)
Diffstat (limited to 'upstream/fuel')
| m--------- | upstream/fuel | 0 |
1 files changed, 0 insertions, 0 deletions
diff --git a/upstream/fuel b/upstream/fuel -Subproject 7aacec4fe6941e180fe1b89100c7bef3f44a641 +Subproject 264570be3db76f351c462891edbd3f7e8d4a1e3 |