Digging and Tracing system for OpenStack
Go to file
Kun Huang 472f4ae4d2 add utils for client side
move common functions there

Change-Id: I51bf2dd4425b5cc385cc0fd5d3734bc71548f740
2015-11-11 12:37:32 +08:00
devstack enable dtrace marker in cPython (ubuntu) 2015-10-31 18:22:10 +08:00
doc add allinone deployment image 2015-11-10 23:48:45 +08:00
scalpels add utils for client side 2015-11-11 12:37:32 +08:00
scripts add utils for client side 2015-11-11 12:37:32 +08:00
tests support list all agents/tracers 2015-11-03 12:29:03 +08:00
tools fake pep8 2015-10-25 01:05:32 +08:00
.gitignore add git ignore 2015-10-20 17:33:28 +08:00
.gitreview add gitreview 2015-10-23 19:49:46 +08:00
.testr.conf add tox-related stuff 2015-10-23 23:06:30 +08:00
LICENSE Initial commit 2015-09-16 14:20:51 +08:00
README.rst mv readme.md to readme.rst 2015-11-11 09:14:17 +08:00
requirements.txt add oslo.messaging requirements 2015-11-09 01:42:39 +08:00
setup.cfg mv readme.md to readme.rst 2015-11-11 09:14:17 +08:00
setup.py add simple python framework 2015-10-20 15:39:06 +08:00
test-requirements.txt add tox-related stuff 2015-10-23 23:06:30 +08:00
tox.ini fix unit test job and doc job 2015-10-25 09:23:31 +08:00

Scalpels

Scalpels is distributed tracing or digging system for OpenStack.

Background

OpenStack is made of multiple Python-based projects. Each project has similiar but different architecture. Scalpels gathers useful scripts or 3rd tools to help operator find what happen in your cloud.

Contribute

This project is prototype now and under development. If you have interests in this work, please contact @kun_huang, at #openstack-chinese channel.

Single Node Architecture

This type of deployment is used as POC in OpenStack community CI.

All-in-One deployment

Multiple Node Architecture

This is under Designing:

Multiple deployment

Ideas

Each project will have scripts working:

  • on python calls
  • on sql queries
  • on filesystem I/O
  • on RPC calls if need
  • on necessary system calls
  • on common system statistics