Comment 1 for bug 1709199

From: Dheeraj Gautam <email address hidden>
Date: Tuesday, August 15, 2017 at 8:15 AM
To: Hari Prasad Killi <email address hidden>
Cc: Chhandak Mukherjee <email address hidden>, Abhay Joshi <email address hidden>
Subject: EVPN VXLAN support from Server-Manager (bug-id #1709199)

Hi Hari,

Chhandak has for EVPN VXLAN provisioning support via Server-Manager (https://bugs.launchpad.net/juniperopenstack/+bug/1709199 ). So far based on my discussion with him, I understood that for EVPN VxLAN support changes are to be done:
• Tor-agent need not be configured, as TSN will directly talk to switch.
• Some of existing parameters for top_of_rack json, will not be used as tor agent is done.
• TSN will make use of netconf to talk to switch.
• Configure physical router with TSN without tor-agent.

Based on above understanding, I am trying to understand what changes are expected to be done from Server-Manager side. From R4.0 onwards, computes are configured via compute-server-setup.sh and SM doesn’t have any role during that.

-Dheeraj