yahoo-eng-team team mailing list archive

[Yair Fried <yfried@xxxxxxxxxx>]

Public bug reported:

When cloud admin is shutting down l3-agent via API (without evacuating routers first) it stands to reason he would like traffic to stop routing via this agent (either for maintenance or maybe because a security breach was found...).
Currently, even when an agent is down, traffic keeps routing without any affect.

Agent should set all interfaces inside router namespace  to DOWN so no
more traffic is being routed.

Alternatively, agent should set routers admin state to DOWN, assuming
this actually affects the router.

Either way, end result should be - traffic is not routed via agent when
admin brings it down.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  When cloud admin is shutting down l3-agent via API (without evacuating routers first) it stands to reason he would like traffic to stop routing via this agent (either for maintenance or maybe because a security breach was found...).
  Currently, even when an agent is down, traffic keeps routing without any effect.
  
  Agent should set all interfaces inside router namespace  to DOWN so no
  more traffic is being routed.
  
  Alternatively, agent should set routers admin state to DOWN, assuming
- this actually effects the router.
+ this actually affects the router.
  
  Either way, end result should be - traffic is not routed via agent when
  admin brings it down.

** Description changed:

  When cloud admin is shutting down l3-agent via API (without evacuating routers first) it stands to reason he would like traffic to stop routing via this agent (either for maintenance or maybe because a security breach was found...).
- Currently, even when an agent is down, traffic keeps routing without any effect.
+ Currently, even when an agent is down, traffic keeps routing without any affect.
  
  Agent should set all interfaces inside router namespace  to DOWN so no
  more traffic is being routed.
  
  Alternatively, agent should set routers admin state to DOWN, assuming
  this actually affects the router.
  
  Either way, end result should be - traffic is not routed via agent when
  admin brings it down.

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

Title:
  admin_state_up=False on l3-agent doesn't affect active routers

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When cloud admin is shutting down l3-agent via API (without evacuating routers first) it stands to reason he would like traffic to stop routing via this agent (either for maintenance or maybe because a security breach was found...).
  Currently, even when an agent is down, traffic keeps routing without any affect.

  Agent should set all interfaces inside router namespace  to DOWN so no
  more traffic is being routed.

  Alternatively, agent should set routers admin state to DOWN, assuming
  this actually affects the router.

  Either way, end result should be - traffic is not routed via agent
  when admin brings it down.

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