Public bug reported:

Problem Description
===================
A routing metric is a quantitative value that is used to evaluate the path cost.
But neutron can't specify a different metric with the same destination address.
It 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

API impact
==========

"router": {
        "admin_state_up": true,
        "routes": [
            {
                "destination": "179.24.1.0/24",
                "nexthop": "172.24.3.99"
                "metric": "100"
            }
        ]
}

Proposal
========

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

References
==========

NULL

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
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:
  New

Bug description:
  Problem Description
  ===================
  A routing metric is a quantitative value that is used to evaluate the path 
cost.
  But neutron can't specify a different metric with the same destination 
address.
  It 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

  API impact
  ==========

  "router": {
          "admin_state_up": true,
          "routes": [
              {
                  "destination": "179.24.1.0/24",
                  "nexthop": "172.24.3.99"
                  "metric": "100"
              }
          ]
  }

  Proposal
  ========

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

  References
  ==========

  NULL

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to