x/timmy
Code Issues Proposed changes
OpenStack Ansible-like tool for parallel node operations: two-way data transfer, log collection, remote command execution
313 Commits 4 Branches 34 Tags 1.5 MiB
Python 76.5%
Shell 18.6%
RPM Spec 4.9%
1960efbbec
Go to file
Dmitry Sutyagin 1960efbbec Change exit codes, list exit codes in a doc
2016-08-25 13:53:09 +03:00
doc/source Change exit codes, list exit codes in a doc 2016-08-25 13:53:09 +03:00
rq Fix #52, config changes, new parameter 2016-08-05 16:18:54 +00:00
specs fix: using macros instead of absolute path 2016-06-30 15:21:12 +03:00
timmy Change exit codes, list exit codes in a doc 2016-08-25 13:53:09 +03:00
.gitignore ignore tmp files 2016-06-08 11:40:36 +00:00
.travis.yml fix: travis config 2016-08-24 13:28:27 +00:00
build-rpm.sh Define fixed python requirement for built rpm 2016-06-10 02:10:55 +00:00
config.yaml fix: exclude filter should be array 2016-08-16 10:17:11 +00:00
MANIFEST.in Move default rqfile to rq directory 2016-08-02 12:23:58 +00:00
README.md added: some docs 2016-04-14 13:27:56 +00:00
requirements-doc.txt try to add exctension for sphinx 2016-07-08 10:20:20 +00:00
requirements.txt Add empty requirements.txt for Travis-CI 2016-08-03 16:36:57 +03:00
setup.cfg Define fixed python requirement for built rpm 2016-06-10 02:10:55 +00:00
setup.py fix: #55, flake8, utf8 decode parameter added 2016-08-10 10:18:29 +00:00
sphinx-build.sh added: environment file with global parameters for setup and docs 2016-05-28 17:28:25 +00:00
timmy.py added: licenses to files 2016-06-15 07:13:50 +00:00

README.md

============= Specification

Mirantis OpenStack Ansible-like tool for parallel node operations: two-way data transfer, log collection, remote command execution

  • The tool is based on https://etherpad.openstack.org/p/openstack-diagnostics
  • Should work fine in the following environments that have been tested: 4.x, 5.x, 6.x, 7.0, 8.0, 9.0
  • Operates non-destructively.
  • Can be launched on any host within admin network, provided the fuel node IP is specified and access to Fuel and other nodes is possible via ssh from the 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 overfilling due to log collection, appropriate error shown.
  • Can be imported into 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.