[sos-devel] [PATCH] [plugins/openstack_neutron] Add netns dumps for DVR namespaces

[Ma, Stephen B.]

Of course *something else* or *some administrator* can create a namespace with starting with "fip", "snat",  "qrouter", or "qdhcp".  But that is highly unlikely.  Only neutron creates and destroy these namespaces.

Do you need any  help in looking into how add checks to see whether neutron is running?  Do I need to resubmit my patch again?

-----Original Message-----
From: Bryn M. Reeves [mailto:bmr at redhat.com] 
Sent: Monday, December 01, 2014 7:02 AM
To: Ma, Stephen B.
Cc: sos-devel at redhat.com
Subject: Re: [sos-devel] [PATCH] [plugins/openstack_neutron] Add netns dumps for DVR namespaces

On Fri, Nov 28, 2014 at 06:09:44PM +0000, Ma, Stephen B. wrote:
> Hi Bryn,
> 
> The fip and snat namespaces are created by the neutron-l3-agent when it is running in the dvr or dvr_snat mode.  They are not used outside of neutron.

That's still not what I mean ;)

There is nothing to stop *something else* creating namespaces with those prefixes; therefore we cannot assume that because we find those prefixes in use that we're looking at a Neutron DVR configuration. We should only assume that in the case that we already know that the system is running OpenStack Neutron.
 
> One thing to note is that when Neutron is running on a machine, it does not necessary implies that qdhcp, qrouter, fip, or the snat namespaces are present on the machine.   For example, neutron-l3-agent manages the qrouter, fip, and snat namespaces.  When the agent crashed, these namespaces are left behind.  So if you run sosreport at the time the agent is not running, I would still like to see the information on these 3 namespaces.  The information would provide clues as to what is the problem.

That's not a problem; we can collect data for them regardless of whether the agent is running or not.

Regards,
Bryn.