Commit Graph

6 Commits

Author SHA1 Message Date
Andreas Jaeger 3e5483d1dc Retire repository
Fuel (from openstack namespace) and fuel-ccp (in x namespace)
repositories are unused and ready to retire.

This change removes all content from the repository and adds the usual
README file to point out that the repository is retired following the
process from
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

See also
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011647.html

Depends-On: https://review.opendev.org/699362
Change-Id: If0c2011947c9eb63f59093812b5f9f95ce56a6f8
2019-12-18 09:39:30 +01:00
Vladimir Kuklin a5c7f47454 Ressurect --start|--end options for graph execution
Change-Id: I22d96ed91a63d498e1e4ace69cdd50d3f6246dc3
CLoses-bug: #1612616
2016-09-12 14:50:57 +00:00
Dmitry Ilyin b106c0557d Add Simulator class and command
The simulatir tool can be used either to virtually
run the deployment to find out the task run order
or to plot the entire graph or its subset.

> Run deployment from the YAML dumped by Astute
astute-simulator -y /path/to/yaml/file.yaml

> Run deployments with task failure emulation
astute-simulator -y /path/to/yaml/file.yaml -f ntp-client/2,heat-db/1 -P

> Using node and task name filters
astute-simulator -y /path/to/yaml/file.yaml -g openstack -G '^2$' -p

Related-bug: #1569839

Change-Id: I6f583347e2f039a470410900c38d7a1d70151b56
2016-07-14 21:54:44 +00:00
Vladimir Sharshov (warpc) 5a9f87c080 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
2016-06-06 20:50:22 +03:00
Dmitry Ilyin d2a5d4f5fa Refactored node and task concurrency
Change-Id: Ifbc756a4653d65eeee73bbc112f3ba89582db7d7
2016-02-19 20:26:38 +03:00
Dmitry Ilyin 8fdc4e3a70 Update fuel_deployment to 0.3.0
* Reimplement graph plot method
* Add weights feature
* Change process to cluster
* Add tests

Change-Id: I0ee6eaa255fdf2629052cf6233df46a5ce92399d
2015-12-21 21:21:58 +03:00