OpenStack Ansible-like tool for parallel node operations: two-way data transfer, log collection, remote command execution
Go to file
2016-05-14 01:01:09 +00:00
doc/source fix: docs; fuel-notifications moved to the specific versions 2016-04-19 09:15:36 +00:00
rq Fix keystone CLI deprecation warnings 2016-05-14 01:01:09 +00:00
timmy Improve output, fix warnings, incr. def. loglevel, clean by default 2016-05-13 03:07:09 +00:00
.gitignore Add .gitignore for .pyc files 2016-05-13 03:08:12 +00:00
config.yaml Implement #15 - RC version, once_by still broken 2016-05-09 01:03:43 +00:00
MANIFEST.in fix: rq.yaml is added to setup 2016-05-05 13:33:00 +00:00
README.md added: some docs 2016-04-14 13:27:56 +00:00
rq.yaml Improve output, fix warnings, incr. def. loglevel, clean by default 2016-05-13 03:07:09 +00:00
setup.cfg add: simple setup functions 2016-04-08 12:33:39 +00:00
setup.py fix: flake8 warns, setup.py 2016-05-12 10:38:52 +00:00
sphinx-build.sh fix: docs 2016-04-15 05:41:34 +00:00
timmy.py added: compat script with setup module 2016-04-09 07:09:01 +00:00

======= Specification

  • The tool is based on https://etherpad.openstack.org/p/openstack-diagnostics
  • Should work fine on the following environments that were tested: 4.x, 5.x, 6.x, 7.0, 8.0
  • Operates non-destructively.
  • Can be launched on any host within admin network, provided the fuel node IP is specified and access is possible to Fuel and other nodes via ssh from local system.
  • Parallel launch, only on the nodes that are 'online'. Some filters for nodes are also available.
  • Commands (from ./cmds directory) are separated according to roles (detected automatically) by the symlinks. Thus, the command list may depend on release, roles and OS. In addition, there can be some commands that run everywhere. There are also commands that are executed only on one node according to its role, using the first node of this type they encounter.
  • Modular: possible to create a special package that contains only certain required commands.
  • Collects log files from the nodes using filters
  • Some archives are created - general.tar.bz2 and logs-*
  • Checks are implemented to prevent filesystem filling due to log collection, appropriate error shown.
  • Can be imported in other python scripts (ex. https://github.com/f3flight/timmy-customtest) and used as a transport and structure to access node parameters known to Fuel, run commands on nodes, collect outputs, etc. with ease.