Jump to: navigation, search

Difference between revisions of "Steth"

m
m
Line 5: Line 5:
  
 
__TOC__
 
__TOC__
 +
 +
 +
== Mission ==
 +
 +
Steth - the introspection tool for OpenStack networking
  
  
Line 20: Line 25:
 
party tools(like iperf, tcpdump, etc.) to help operators keep tracking on VM
 
party tools(like iperf, tcpdump, etc.) to help operators keep tracking on VM
 
networking.
 
networking.
 
 
== Mission ==
 
 
Steth is an introspection tool for OpenStack networking. Only proved to be
 
working in ML2 with OVS for now.
 
  
  
Line 33: Line 32:
 
* [http://steth.readthedocs.org/en/latest/ Online] version at ReadTheDocs
 
* [http://steth.readthedocs.org/en/latest/ Online] version at ReadTheDocs
  
== Contributions ==
+
 
 +
== Contributions are welcome ==
  
 
All kinds of contributions are welcomed, such as documentation, bug fixes and new
 
All kinds of contributions are welcomed, such as documentation, bug fixes and new
 
features.If you have a new feature or idea, ask for feedback first before spending lots
 
features.If you have a new feature or idea, ask for feedback first before spending lots
 
of time on something.
 
of time on something.
 +
 +
You can also post message in the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Developer mailinglist], prefixed with [steth].
 +
  
 
== Contributors ==
 
== Contributors ==
Line 49: Line 52:
 
|-  
 
|-  
 
|Zhi Chang || changzhi@unitedstack.com || changzhi || UTC+08:00 || {{#timel: g:i A| +8 hours }}  || Developer
 
|Zhi Chang || changzhi@unitedstack.com || changzhi || UTC+08:00 || {{#timel: g:i A| +8 hours }}  || Developer
|-        
+
|-  
 
|}
 
|}

Revision as of 02:28, 20 April 2016

Steth is an inspection tool that can aid in pinpointing issues before deployment and during operation of an OpenStack environment. It is modelled as agent(s)/client in which a controller interacts with agents deployed in your environment.


Mission

Steth - the introspection tool for OpenStack networking


Background

OpenStack networking can be deloyed as different architectures, such as ML2 with OVS(legacy and DVR), Linux bridge, OVN, Dragonflow and so forth. However, they all need enviromental prerequisites. For instance, VLAN needs to be configured as we expect; bandwidth should meet our requirements; connection between nodes should be active, etc.

Besides, with some well-deployed architectures, troubleshooting for VM networking is difficult. For instance, why VM cannot get an IP address; or why it cannot connect to Internet, etc. Steth integrates useful scripts and third party tools(like iperf, tcpdump, etc.) to help operators keep tracking on VM networking.


Documentation

  • Introduction to Steth to do Network Inspection (Chinese language) SpeakerDeck
  • Online version at ReadTheDocs


Contributions are welcome

All kinds of contributions are welcomed, such as documentation, bug fixes and new features.If you have a new feature or idea, ask for feedback first before spending lots of time on something.

You can also post message in the OpenStack Developer mailinglist, prefixed with [steth].


Contributors

Name Email IRC Nick Timezone Local time Role
Wei Wang wangwei@unitedstack.com wangwei UTC+08:00 6:53 AM Project Technical Lead (PTL)
Wei Yao yaowei@unitedstack.com yaowei UTC+08:00 6:53 AM Developer
Zhi Chang changzhi@unitedstack.com changzhi UTC+08:00 6:53 AM Developer