| 2015-04-22 17:41:17 |
Nischal Sheth |
bug |
|
|
added bug |
| 2015-04-22 17:41:17 |
Nischal Sheth |
attachment added |
|
Screen Shot 2015-04-22 at 10.35.30 AM.png https://bugs.launchpad.net/bugs/1447273/+attachment/4381670/+files/Screen%20Shot%202015-04-22%20at%2010.35.30%20AM.png |
|
| 2015-04-22 17:44:02 |
Nischal Sheth |
description |
There are 2 different entities in the bgp configuration.
First is the bgp-router object which represents either
a control node or a physical router such as MX.
Second is the bgp-peering relationship (link) between
2 bgp-routers.
UI currently uses BGP Peer for both.
Proposal is to use the term BGP Router for the first
entity. Referring to the attachment, the following
changes need to be made.
- Rename the entry under Infrastructure from BGP Peer
to BGP Router.
- The text at the top of the page should also be changed
to BGP Router.
- When the user edits an entry in this list, the title for the
popup should be Edit BGP Router.
- Change "Peer Type" to "Router Type" or just "Type".
The text "Available Peers" and "Configured Peers" should
stay unchanged since those refer to the second entity
i.e. a peering relationship. |
There are 2 different entities in the bgp configuration. First is the bgp-
router object which represents either a control node or a physical router
such as MX. Second is the bgp-peering relationship (link) between 2 bgp-
routers.
UI currently uses the term BGP Peer for both.
Proposal is to use the term BGP Router for the first entity. Referring
to the attachment, the following changes need to be made.
- Rename the entry under Infrastructure from BGP Peer to BGP Router
- The text at the top of the page should also be changed to BGP Router
- When user edits an entry, the title for popup should be Edit BGP Router
- Change "Peer Type" to "Router Type" or just "Type"
The text "Available Peers" and "Configured Peers" should stay unchanged
since those refer to the second entity i.e. a peering relationship. |
|
| 2015-04-22 17:44:08 |
Nischal Sheth |
nominated for series |
|
juniperopenstack/trunk |
|
| 2015-04-22 17:44:08 |
Nischal Sheth |
bug task added |
|
juniperopenstack/trunk |
|
| 2015-04-28 19:32:18 |
Nischal Sheth |
information type |
Proprietary |
Public |
|
| 2015-04-29 22:47:18 |
Nischal Sheth |
juniperopenstack/trunk: milestone |
|
r2.30-fcs |
|
| 2015-05-08 18:05:11 |
Nischal Sheth |
description |
There are 2 different entities in the bgp configuration. First is the bgp-
router object which represents either a control node or a physical router
such as MX. Second is the bgp-peering relationship (link) between 2 bgp-
routers.
UI currently uses the term BGP Peer for both.
Proposal is to use the term BGP Router for the first entity. Referring
to the attachment, the following changes need to be made.
- Rename the entry under Infrastructure from BGP Peer to BGP Router
- The text at the top of the page should also be changed to BGP Router
- When user edits an entry, the title for popup should be Edit BGP Router
- Change "Peer Type" to "Router Type" or just "Type"
The text "Available Peers" and "Configured Peers" should stay unchanged
since those refer to the second entity i.e. a peering relationship. |
There are 2 different entities in the bgp configuration. First is the bgp-
router object which represents either a control node or a physical router
such as MX. Second is the bgp-peering relationship (link) between 2 bgp-
routers.
UI currently uses the term BGP Peer for both.
Proposal is to use the term BGP Router for the first entity. Referring
to the attachment, the following changes need to be made.
- Rename the entry under Infrastructure from BGP Peer to BGP Router
- The text at the top of the page should also be changed to BGP Router
- When user edits an entry, the title for popup should be Edit BGP Router
- Change "Peer Type" to "Router Type" or just "Type" |
|
| 2015-05-08 18:52:58 |
Nischal Sheth |
nominated for series |
|
juniperopenstack/r2.20 |
|
| 2015-05-08 18:52:58 |
Nischal Sheth |
bug task added |
|
juniperopenstack/r2.20 |
|
| 2015-05-08 18:53:03 |
Nischal Sheth |
juniperopenstack/r2.20: importance |
Undecided |
Medium |
|
| 2015-05-08 18:53:11 |
Nischal Sheth |
juniperopenstack/r2.20: assignee |
|
Rahul (rahuls) |
|
| 2015-05-08 18:53:13 |
Nischal Sheth |
juniperopenstack/r2.20: milestone |
|
r2.20-fcs |
|
| 2015-05-08 20:47:21 |
Nischal Sheth |
summary |
Use of BGP Peer is overloaded for 2 different entities |
Use Router instead of Peer when referring to bgp-router object |
|
| 2015-05-15 12:02:52 |
Rahul |
juniperopenstack/r2.20: assignee |
Rahul (rahuls) |
Siva Bavanasi (kbsiva) |
|
| 2015-05-15 12:03:06 |
Rahul |
juniperopenstack/trunk: assignee |
Rahul (rahuls) |
Siva Bavanasi (kbsiva) |
|
| 2015-05-21 02:49:10 |
OpenContrail Admin |
juniperopenstack/r2.20: status |
New |
Fix Committed |
|
| 2015-05-21 06:47:29 |
OpenContrail Admin |
juniperopenstack/trunk: status |
New |
Fix Committed |
|
