| 2018-03-29 08:06:39 |
zhangyanxian |
bug |
|
|
added bug |
| 2018-03-29 10:37:27 |
zhangyanxian |
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 |
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
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.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
|
| 2018-03-29 10:40:19 |
zhangyanxian |
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
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.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
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
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.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
|
| 2018-03-29 11:07:38 |
zhangyanxian |
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
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.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
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 route.
This value can be set by the user or have a default value.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
openstack router set --route destination=CIDR,gateway=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
|
| 2018-03-29 11:35:32 |
zhangyanxian |
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 route.
This value can be set by the user or have a default value.
For example:
neutron router-update --route destination=CIDR,nexthop=IP_ADDR,
metric=METRIC ROUTER
openstack router set --route destination=CIDR,gateway=IP_ADDR,
metric=METRIC ROUTER
API impact
==========
"router": {
"admin_state_up": true,
"routes": [
{
"destination": "179.24.1.0/24",
"nexthop": "172.24.3.99"
"metric": "100"
}
]
}
References
==========
NULL |
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 |
|
| 2018-03-29 11:35:58 |
zhangyanxian |
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 |
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 |
|
| 2018-03-31 01:32:45 |
zhaobo |
tags |
|
ap rfe |
|
| 2018-03-31 01:33:12 |
zhaobo |
tags |
ap rfe |
api rfe |
|
| 2018-04-02 06:03:09 |
eroc Jiang |
bug |
|
|
added subscriber eroc Jiang |
| 2018-04-02 06:04:05 |
eroc Jiang |
neutron: status |
New |
Confirmed |
|
| 2018-04-02 07:46:29 |
zhangyanxian |
neutron: assignee |
|
zhangyanxian (zhang-yanxian) |
|
| 2018-04-02 18:21:26 |
Swaminathan Vasudevan |
neutron: importance |
Undecided |
Wishlist |
|
| 2018-04-05 07:26:06 |
Bence Romsics |
bug |
|
|
added subscriber Bence Romsics |
| 2019-02-18 07:11:53 |
XU Xiaodan |
bug task added |
|
python-openstackclient |
|
| 2019-02-18 07:13:15 |
XU Xiaodan |
python-openstackclient: status |
New |
Confirmed |
|
| 2019-02-18 07:13:15 |
XU Xiaodan |
python-openstackclient: assignee |
|
XU Xiaodan (xiaodan) |
|
| 2019-02-22 08:47:47 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2019-02-22 08:47:47 |
OpenStack Infra |
neutron: assignee |
zhangyanxian (zhang-yanxian) |
XU Xiaodan (xiaodan) |
|
| 2019-06-18 16:26:48 |
Brian Haley |
tags |
api rfe |
api rfe rfe-triaged |
|
| 2019-06-18 16:28:49 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2019-07-01 08:14:10 |
OpenStack Infra |
neutron: assignee |
XU Xiaodan (xiaodan) |
Bin Lu (369283883-o) |
|
| 2019-09-27 09:46:16 |
Slawek Kaplonski |
tags |
api rfe rfe-triaged |
api rfe-triaged |
|
| 2019-10-03 13:51:56 |
Slawek Kaplonski |
tags |
api rfe-triaged |
api l3-dvr-backlog rfe-triaged |
|
| 2020-06-25 13:21:57 |
Slawek Kaplonski |
tags |
api l3-dvr-backlog rfe-triaged |
api l3-dvr-backlog rfe-postponed |
|
| 2020-06-25 13:22:02 |
Slawek Kaplonski |
neutron: status |
In Progress |
Opinion |
|
| 2020-09-25 15:46:31 |
Slawek Kaplonski |
neutron: assignee |
Bin Lu (369283883-o) |
|
|
| 2020-09-25 15:46:37 |
Slawek Kaplonski |
tags |
api l3-dvr-backlog rfe-postponed |
api l3-dvr-backlog rfe-postponed timeout-abandon |
|
