← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1759790] Re: [RFE] metric for the route

 

Due to no activity in this RFE for long time, I'm marking it as
"postponed" for now. Feel free to reopen it if You will want to discuss
that again on drivers meeting and if You will want to work on that.

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

** Changed in: neutron
       Status: In Progress => Opinion

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

Title:
  [RFE] metric for the route

Status in neutron:
  Opinion
Status in python-openstackclient:
  Confirmed

Bug description:
  Problem Description
  ===================

  A routing metric is a quantitative value used to evaluate the path cost.
  But neutron can't specify a different metric with the same destination address,which is useful to realize FRR(Fast Reroute) in Telecoms and NFV scenario.

  There is no optional argument for metric:
  root@ubuntudbs:/home/dbs# neutron router-update --help
  neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
  usage: neutron router-update [-h] [--name NAME] [--description DESCRIPTION]
                               [--admin-state-up {True,False}]
                               [--distributed {True,False}]
                               [--route destination=CIDR,nexthop=IP_ADDR | --no-routes]
                               ROUTER

  root@ubuntudbs:/home/dbs# openstack router set --help
  usage: openstack router set [-h] [--name <name>] [--description <description>]
                              [--enable | --disable]
                              [--distributed | --centralized]
                              [--route destination=<subnet>,gateway=<ip-address>]
                              [--no-route] [--ha | --no-ha]
                              [--external-gateway <network>]
                              [--fixed-ip subnet=<subnet>,ip-address=<ip-address>]
                              [--enable-snat | --disable-snat] [--tag <tag>]
                              [--no-tag]
                              <router>

  Proposal
  ========

  A new optional argument metric can be added to set the metric for the routes.
  This value can be set by the user or have a default value.

  Command Line Client Impact
  --------------------------

  ::

    openstack router set [--route destination=<subnet>,
                                  gateway=<ip-address>,
                                  metric=<metric>] <router>

    neutron router-update [--route destination=CIDR,
                                   nexthop=IP_ADDR,
                                   metric=METRIC | --no-routes] ROUTER

  Argument metric is optional.

  REST API Impact
  ---------------

  A new API extension to the routes resource is going to be introduced.
  Set the metric for the routes :

  .. code-block:: python

     PUT /v2.0/routers/{router_id}
     Accept: application/json
     {
         "router": {
             "routes": [
              {
                  "destination": "179.24.1.0/24",
                  "nexthop": "172.24.3.99"
                  "metric": "100"
              }
          ]
         }
     }

  References
  ==========

  .. [1] api-ref for the neutron router,
     https://developer.openstack.org/api-ref/network/v2/index.html#routers-routers

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


References