yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1830014@xxxxxxxxxxxxxxxxxx>]

We discussed that rfe again on the drivers meeting today: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.2021-09-10-14.05.log.html#l-18
As use case originally given in the spec (debugging CI) isn't really issue anymore, and as we see that implementation of that proposal would be pretty complex, we decided to decline that RFE.

** Changed in: neutron
       Status: New => Won't Fix

** Changed in: neutron
       Status: Won't Fix => Confirmed

** Changed in: neutron
   Importance: Undecided => Wishlist

** Tags removed: rfe-triaged
** Tags added: rfe

** Changed in: neutron
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1830014

Title:
  [RFE] add API for neutron debug tool "probe"

Status in neutron:
  Won't Fix

Bug description:
  Recently, due to this bug:
  https://bugs.launchpad.net/neutron/+bug/1821912
  We noticed that sometimes the guest OS is not fully UP, but test case is trying to login it. A simple idea is to ping it first, then try to login. So we hope to find a way for tempest to verify the neutron port link state. In high probability, the DB resource state is not reliable. We need an independent mechanism to check the VM network status. Because tempest is "blackbox" test, it can run in any host, we can not use the current resources under the existing mechanism, such as qdhcp-namepace or qrouter-namepace to do such check.

  Then this RFE is up. We have neutron-debug tool which include a "probe" resource in the agent side.
  https://docs.openstack.org/neutron/latest/cli/neutron-debug.html
  We could add some API to neutron, and let the proper agent to add such "probe" for us.
  In agent side, it will be a general agent extension, you can enable it to the ovs-agent, L3-agent or DHCP-agent.
  Once you have such "probe" resource in the agent side, then you can run any command in it.
  This will be useful for neutron CI to check the VM link state.

  So a basic workflow will be:
  1. neutron tempest create router and connected to one subnet (network-1)
  2. neutron tempest create one VM
  3. neutron tempest create one floating IP and bind it to the VM-1 port
  4. create a "probe" for network-1 via neutron API
  5. ping the VM port until reachable in the "probe" namespace
  6. ssh the VM by floating IP
  7. do the next step

  One more thing, we now have set the "neutron-debug" tool as deprecated:
  https://bugs.launchpad.net/neutron/+bug/1583700
  But we can remain that "probe" mechanism.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1830014/+subscriptions