Difference between revisions of "Neutron/quantum-network-connection-monitoring-service"

Revision as of 23:36, 27 March 2013

Scope:

This service provide quantum network monitoring service. - monitoring service will create a probe port with specified quantum network - User can ping from the probe port or l3-agent or dhcp - User can nc -vz to check tcp port from the probe port - User can nc -l to access the probe port - User can traceroute

Note this is extended version of quantum-debug command

Use Cases

For development - Quantum developer can check network functionalities using this function

For User - User can get health check of network connections Test or investigate network connection on the operation

Implementation Overview:

- This spec is based on service insertion blueprint

Data Model Changes:

No change Monitoring service will use port's device owner attribute

Configuration variables

API's

TBD

Plugin Interface

No

Required Plugin support:

No

Dependencies:

No

CLI Requirements:

quantum probe-create <net-id> quantum probe-delete <net-id> quantum probe-ping <probe-id> ipaddress quantum probe-nc-check <probe-id> ipaddress port quantum probe-nc-listen <probe-id> port

Horizon Requirements:

ping/ nc/ traceroute from horizon UI

@@ Line 1: / Line 1: @@
+== Scope: ==
-'''Scope:'''''' '''[Short overview and high level description of what the blueprint is trying to achieve.]
 This service provide quantum network monitoring service.
 - monitoring service will create a probe port with specified quantum network
-- User can ping from the probe port
+- User can ping from the probe port or l3-agent or dhcp
 - User can nc -vz to check tcp port from the probe port
 - User can nc -l to access the probe port
+- User can traceroute
 Note this is extended version of quantum-debug command
-'''Use Cases'''''':'''''' '''[Short overview and high level description of what the blueprint is trying to achieve.]
+== Use Cases ==
 For development
@@ Line 17: / Line 17: @@
 For User
 - User can get health check of network connections
+Test or investigate network connection on the operation
-'''Implementation Overview: '''[Provide an overview of the implementation and any algorithms that will be used]
+== Implementation Overview: ==
 - This spec is based on service insertion blueprint
-'''Data Model Changes: '''[Are you introducing new model classes, or extending existing ones?]
+== Data Model Changes: ==
 No change
 Monitoring service will use port's device owner attribute
-'''Configuration variables:''' [List and explanation of the     new configuration variables (if they exist)]
+== Configuration variables ==
-'''API's: '''[List and explanation of the     new API's (if they exist)]
+== API's ==
 TBD
-'''Plugin Interface: '''[Does this feature introduce any change?]
+== Plugin Interface ==
 No
-'''Required Plugin support: '''[What should the plugins do to support this new feature? (If applicable)]
+== Required Plugin support: ==
 No
-'''Dependencies: '''[List of python packages and/or OpenStack components? (If applicable)]
+== Dependencies: ==
 No
-'''CLI Requirements: '''[List of CLI requirements (If applicable)]
+== CLI Requirements: ==
 quantum probe-create <net-id>
@@ Line 53: / Line 53: @@
 quantum probe-nc-listen <probe-id> port
-'''Horizon Requirements: '''[List of Horizon requirements (If applicable)]
+== Horizon Requirements: ==
-'''Usage Example: '''[How to run/use/interface with the new feature.  (If applicable)]
-'''Test Cases: '''[Description of various test cases.  (If applicable)]
-<span style="font-size: large; color: green; background: yellow">OK</span>
+ping/ nc/ traceroute from horizon UI