x/timmy
Code Issues Proposed changes

fix: docs; fuel-notifications moved to the specific versions

Browse Source
This commit is contained in:
adobdin 2016-04-19 09:15:36 +00:00
parent 7e2abe63e5
commit deebaf76e5
4 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/source/specification.rst
View File

@ -2,15 +2,15 @@
Specification
=======
* This tool is based on https://etherpad.openstack.org/p/openstack-diagnostics
* 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. Completely safe.
* Can be launched not only on the master node, if the master node's IP is specified.
* Parallel launch, only on the nodes that are 'online'.
* Commands (from ./cmds directory) are separated by roles (detected automatically) by the symlinks. So the command list may depend on release, roles and OS, there also can be commands that run everywhere. Also there are commands that are executed *only on one node* by its *role*, first encountered.
* Human-readable format output of 'fuel node list'
* Modular: possible to create a special package that contains only some required commands.
* some archives are being created - *general.tar.bz2* and *logs-***
Back to :doc:`Index </index>`.
* 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.

0
rq/cmds/by-role/fuel/fuel-notifications → rq/cmds/release-6.1/fuel/fuel-notifications
View File

1
rq/cmds/release-7.0/fuel/fuel-notifications Symbolic link
View File

@ -0,0 +1 @@
../../cmds/fuel-notifications

1
rq/cmds/release-8.0/fuel/fuel-notifications Symbolic link
View File

@ -0,0 +1 @@
../../cmds/fuel-notifications