[EVPN VXLAN]: [Build 4.1.0.0-35] Nova compute is running on TSN node
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
High
|
Kumar Harsh | |||
R4.1 |
Fix Committed
|
High
|
Kumar Harsh | |||
Trunk |
Fix Committed
|
High
|
Kumar Harsh |
Bug Description
On EVPN VXLAN cluster nova-compute is running on TSN node. SO, in turn, VM is allowed to launch on TSN node. Typically in OVSDV solution, we don't allow to launch VM on TSN node.
In EVPN VXLAN solution role of TSN has reduced just to DHCP/DNS server. So we want use TSN as compute as well or not has to be decided. Opening this bug as tracking one.
root@5b11s14:~# nova service-list
+----+-
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+-
| 3 | nova-conductor | 5b11s14 | internal | enabled | up | 2017-11-
| 4 | nova-console | 5b11s14 | internal | enabled | up | 2017-11-
| 5 | nova-scheduler | 5b11s14 | internal | enabled | up | 2017-11-
| 6 | nova-consoleauth | 5b11s14 | internal | enabled | up | 2017-11-
| 7 | nova-compute | 5b11s14 | nova | enabled | up | 2017-11-
| 8 | nova-compute | 5b11s15 | nova | enabled | up | 2017-11-
| 9 | nova-compute | 5b11s17 | nova | enabled | up | 2017-11-
+----+-
root@5b11s14:~# cat /etc/contrail/
# Agent mode : can be vrouter / tsn / tsn-no-forwarding / tor (default is vrouter)
agent_mode =tsn-no-forwarding
tsn_servers = 172.16.180.101 172.16.180.103
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
assignee: | nobody → Hari Prasad Killi (haripk) |
milestone: | none → r4.1.0.0-fcs |
information type: | Proprietary → Public |
description: | updated |
Changed in juniperopenstack: | |
importance: | Critical → High |
assignee: | Hari Prasad Killi (haripk) → Kumar Harsh (hkumar) |
Review in progress for https:/ /review. opencontrail. org/37145
Submitter: Kumar Harsh (<email address hidden>)