commit 1a8e53cb5bf41b7afc2333cef91b162455ebe1f9
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Tue May 24 20:46:30 2016 +0300
Gracefully stop if tolerance limit exceeded
Several changes:
- support fault tolerance group;
- support internal stop deployment instead of raise in
case of error;
- do not show last run summary debug report from mcollective;
- fix support of detecting offline nodes before run deployment;
- support fail on error behavior.
Support fault tolerance group
Nailgun send fault tolerance group which inform Astute about
available number of error nodes in this deployment and importance
of every node in this task.
If number of error exceeds number of available errors, deployment
will stop.
Support internal stop deployment instead of raise in case of error
Before this change Astute is end processing, marks all nodes
as error and do not waiting of puppet process on nodes.
Now we use same way that used in case of stop deployment.
Mark failed nodes as error, another nodes as skipped(stopped),
ready nodes as ready. Also Astute will wait before current
tasks end.
Do not show last run summary debug report from mcollective
For now moment it not so useful, but quickly filled log file
and difficult debug process
Fix support of detecting offline nodes before run deployment
Astute gets response from mcollective to detect node availability.
If node do not respond, it will mark as failed. It also support
fault tollerance mechanism
Support fail on error behavior
From this moment task which setup fail_on_error if false,
task marks as skipped instead of failed in case of error.
Change-Id: Ica2a4ae64b4dfa4f7fccfbc95108d1412c40dc3f
Closes-Bug: #1435610
(cherry picked from commit 5a9f87c08062d3f0a23116b1a339da3252a69f24)
Reviewed: https:/ /review. openstack. org/326485 /git.openstack. org/cgit/ openstack/ fuel-astute/ commit/ ?id=1a8e53cb5bf 41b7afc2333cef9 1b162455ebe1f9
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 1a8e53cb5bf41b7 afc2333cef91b16 2455ebe1f9
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Tue May 24 20:46:30 2016 +0300
Gracefully stop if tolerance limit exceeded
Several changes:
- support fault tolerance group;
- support internal stop deployment instead of raise in
case of error;
- do not show last run summary debug report from mcollective;
- fix support of detecting offline nodes before run deployment;
- support fail on error behavior.
Support fault tolerance group
Nailgun send fault tolerance group which inform Astute about
available number of error nodes in this deployment and importance
of every node in this task.
If number of error exceeds number of available errors, deployment
will stop.
Support internal stop deployment instead of raise in case of error
Before this change Astute is end processing, marks all nodes
as error and do not waiting of puppet process on nodes.
Now we use same way that used in case of stop deployment.
Mark failed nodes as error, another nodes as skipped(stopped),
ready nodes as ready. Also Astute will wait before current
tasks end.
Do not show last run summary debug report from mcollective
For now moment it not so useful, but quickly filled log file
and difficult debug process
Fix support of detecting offline nodes before run deployment
Astute gets response from mcollective to detect node availability.
If node do not respond, it will mark as failed. It also support
fault tollerance mechanism
Support fail on error behavior
From this moment task which setup fail_on_error if false,
task marks as skipped instead of failed in case of error.
Change-Id: Ica2a4ae64b4dfa 4f7fccfbc95108d 1412c40dc3f 0a23116b1a339da 3252a69f24)
Closes-Bug: #1435610
(cherry picked from commit 5a9f87c08062d3f