EVPN VXLAN: Contrail should be modeled to allow associating TSN to Physical Router alone without Tor Agent
Bug #1709195 reported by
chhandak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
Critical
|
Siva Bavanasi | |||
Trunk |
Fix Committed
|
Critical
|
Siva Bavanasi |
Bug Description
Description:
With EVPN VXLAN solution we still need TSN for a TOR but there will be no TOR Agent. TSN will be used as DHCP and DNS server for BMS.
Today UI only allows associating virtual routers configured as Tor Agent. Then TSN can be configured for a respective TOR Agent. This schema should be changed.
TOR can have TSN added as virtual router alone without any Tor Agent
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
assignee: | nobody → Siva Bavanasi (kbsiva) |
milestone: | none → r4.0.1.0 |
information type: | Proprietary → Public |
To post a comment you must log in.
TSN alone use case has to be supported from vrouter, accordingly ui will be changed.