<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Another project for diagnosing OVS in Neutron:</div>
<div><br>
</div>
<div>
<div><a href="https://github.com/CiscoSystems/don">https://github.com/CiscoSystems/don</a></div>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Ganesh</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Salvatore Orlando <<a href="mailto:salv.orlando@gmail.com">salv.orlando@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, 21 September 2015 2:55 pm<br>
<span style="font-weight:bold">To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [neutron] Neutron debugging tool<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">It sounds like indeed that easyOVS covers what you're aiming too.
<div>However, from what I gather there is still plenty to do in easy OVS, so perhaps rather than starting a new toolset from scratch you might build on the existing one.</div>
<div><br>
</div>
<div>Personally I'd welcome its adoption into the Neutron stadium as debugging control plane/data plane issues in the neutron reference impl is becoming difficult also for expert users and developers.</div>
<div>I'd just suggest renaming it because calling it "OVS" is just plain wrong. The neutron reference implementation and OVS are two distinct things.</div>
<div><br>
</div>
<div>As concern neutron-debug, this is a tool that was developed in the early stages of the project to verify connectivity using "probes" in namespaces. These probes are simply tap interfaces associated with neutron ports. The neutron-debug tool is still used
in some devstack exercises. Nevertheless, I'd rather keep building something like easyOVS and then deprecated neutron-debug rather than develop it.</div>
<div><br>
</div>
<div>Salvatore</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 21 September 2015 at 02:40, Li Ma <span dir="ltr"><<a href="mailto:skywalker.nick@gmail.com" target="_blank">skywalker.nick@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
AFAIK, there is a project available in the github that does the same thing.<br>
<a href="https://github.com/yeasy/easyOVS" rel="noreferrer" target="_blank">https://github.com/yeasy/easyOVS</a><br>
<br>
I used it before.<br>
<div class="HOEnZb">
<div class="h5"><br>
On Mon, Sep 21, 2015 at 12:17 AM, Nodir Kodirov <<a href="mailto:nodir.qodirov@gmail.com">nodir.qodirov@gmail.com</a>> wrote:<br>
> Hello,<br>
><br>
> I am planning to develop a tool for network debugging. Initially, it<br>
> will handle DVR case, which can also be extended to other too. Based<br>
> on my OpenStack deployment/operations experience, I am planning to<br>
> handle common pitfalls/misconfigurations, such as:<br>
> 1) check external gateway validity<br>
> 2) check if appropriate qrouter/qdhcp/fip namespaces are created in<br>
> compute/network hosts<br>
> 3) execute probing commands inside namespaces, to verify reachability<br>
> 4) etc.<br>
><br>
> I came across neutron-debug [1], which mostly focuses on namespace<br>
> debugging. Its coverage is limited to OpenStack, while I am planning<br>
> to cover compute/network nodes as well. In my experience, I had to ssh<br>
> to the host(s) to accurately diagnose the failure (e.g., 1, 2 cases<br>
> above). The tool I am considering will handle these, given the host<br>
> credentials.<br>
><br>
> I'd like get community's feedback on utility of such debugging tool.<br>
> Do people use neutron-debug on their OpenStack environment? Does the<br>
> tool I am planning to develop with complete diagnosis coverage sound<br>
> useful? Anyone is interested to join the development? All feedback are<br>
> welcome.<br>
><br>
> Thanks,<br>
><br>
> - Nodir<br>
><br>
> [1] <a href="http://docs.openstack.org/cli-reference/content/neutron-debug_commands.html" rel="noreferrer" target="_blank">
http://docs.openstack.org/cli-reference/content/neutron-debug_commands.html</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">--<br>
<br>
Li Ma (Nick)<br>
Email: <a href="mailto:skywalker.nick@gmail.com">skywalker.nick@gmail.com</a><br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>