| 2015-11-24 23:32:31 |
Ramu Ramamurthy |
bug |
|
|
added bug |
| 2015-11-24 23:32:31 |
Ramu Ramamurthy |
attachment added |
|
sample code diff for diagnostics extension https://bugs.launchpad.net/bugs/1519537/+attachment/4524935/+files/diagnostics-extension-code-diff.txt |
|
| 2015-11-24 23:36:17 |
Ramu Ramamurthy |
description |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root-shell access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to
the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be
processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root-shell access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
|
| 2015-11-24 23:40:48 |
Ramu Ramamurthy |
description |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root-shell access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root-shell access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Neutron Command-line Client supports the following new commands
----------------------------------------------------------------
neutron l2-diagnostics --network-id <> --port-id <> agent
neutron dhcp-diagnostics --network-id <> --port-id <> --ping agent
neutron l3-diagnostics --network-id <> --port-id <> --ping agent
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
|
| 2015-11-24 23:47:14 |
Ramu Ramamurthy |
description |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root-shell access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Neutron Command-line Client supports the following new commands
----------------------------------------------------------------
neutron l2-diagnostics --network-id <> --port-id <> agent
neutron dhcp-diagnostics --network-id <> --port-id <> --ping agent
neutron l3-diagnostics --network-id <> --port-id <> --ping agent
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Neutron Command-line Client supports the following new commands
----------------------------------------------------------------
neutron l2-diagnostics --network-id <> --port-id <> agent
neutron dhcp-diagnostics --network-id <> --port-id <> --ping agent
neutron l3-diagnostics --network-id <> --port-id <> --ping agent
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
|
| 2015-11-25 00:19:46 |
Ramu Ramamurthy |
description |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension. The structured
content can be parsed by automation to pin-point problems or at least help get to the next step of the debugging much faster than done manually.
In addition, there should be diagnostics/operational support to ping a neutron port from the dhcp or l3 agents.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs (limited by policy to admin-only). The outputs are structured so, they can be processed by other tools.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Neutron Command-line Client supports the following new commands
----------------------------------------------------------------
neutron l2-diagnostics --network-id <> --port-id <> agent
neutron dhcp-diagnostics --network-id <> --port-id <> --ping agent
neutron l3-diagnostics --network-id <> --port-id <> --ping agent
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
Problem
----------
Debugging common networking/neutron problems (1. cannot ping VM, 2. cannot ping FIP),
tends to be manual, and requires root access to look into the state of the agents or the datapath
on different hosts.
Neutron needs to provide a "diagnostics" extension api which can be used for debugging networking problems.
Each agent/driver exposes its own state in a structured (json) format via the diagnostics extension.
Nova "diagnostics" serves as an example here.
https://wiki.openstack.org/wiki/Nova_VM_Diagnostics
Fix
----
A "diagnostics" extension is added to neutron
Each agent and corresponding drivers supports a get_diagnostics() API invoked from neutron-server upon
the following GET APIs limited by policy to admin-only.
GET: /agent/:id/diagnostics
example output from neutron-ovs agent: OVS bridges, ports and flows
GET: /agent/:id/diagnostics/network/:id
example output from dhcp-agent (dnsmasq driver): contents of host,lease files
GET: /agent/:id/diagnostics/port/:id
example output from dhcp-agent: dhcp transactions for that port (from dnsmasq logs)
example output from ovs-agent: stats on qvo,qbr,tap interfaces
GET: /agent/:id/diagnostics/port/:id/security-groups
example output from l2-agent (iptables-firewalldriver): iptables rules programmed (ingress/egress/spoofing) for that port
GET: /agent/:id/diagnostics/port/:id/ping
This is an "operational" command - ping the port from the agent (dhcp/l3) network/router namespace
Neutron Command-line Client supports the following new commands
----------------------------------------------------------------
neutron l2-diagnostics --network-id <> --port-id <> agent
neutron dhcp-diagnostics --network-id <> --port-id <> --ping agent
neutron l3-diagnostics --network-id <> --port-id <> --ping agent
Sample Diagnostics Extension Code
------------------------------------------
See Attached Code Diff |
|
| 2015-11-25 01:24:46 |
Ramu Ramamurthy |
bug |
|
|
added subscriber Ryan Moats |
| 2015-11-25 18:16:31 |
Ramu Ramamurthy |
bug |
|
|
added subscriber Bhalachandra Banavalikar |
| 2015-12-02 18:17:34 |
Doug Wiegley |
neutron: status |
New |
Confirmed |
|
| 2015-12-04 00:45:00 |
Armando Migliaccio |
neutron: importance |
Undecided |
Wishlist |
|
| 2015-12-04 22:21:22 |
Ramu Ramamurthy |
neutron: assignee |
|
Ramu Ramamurthy (ramu-ramamurthy) |
|
| 2015-12-22 02:32:10 |
Armando Migliaccio |
neutron: assignee |
Ramu Ramamurthy (ramu-ramamurthy) |
|
|
| 2015-12-22 02:32:25 |
Armando Migliaccio |
marked as duplicate |
|
1507499 |
|
| 2016-03-31 14:50:11 |
Boden R |
bug |
|
|
added subscriber Boden R |
