EVPN VXLAN: Server Manager provisioning support required

Bug #1709199 reported by chhandak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
Fix Committed
Wishlist
Hari Prasad Killi
R4.1
Fix Committed
Wishlist
Hari Prasad Killi
Trunk
Fix Committed
Wishlist
Hari Prasad Killi

Bug Description

Server Manager provisioning support required for EVPN VXLAN solution.

Following needs to be done :
1. Configuring QFX 5100 as Leaf switch with netconf (As MX)
2. Configuring QFX10K as Leaf or Spine (Based on user definition) with netconf (As MX)
3. Enabling VXLAN routing
4. Configuring TSN without tor agent and associating to Physical Device

chhandak (chhandak)
Changed in juniperopenstack:
importance: Undecided → High
assignee: nobody → Abhay Joshi (abhayj)
milestone: none → r4.0.1.0
information type: Proprietary → Public
summary: - EVPN VXLAN: Server Manager provisioning support
+ EVPN VXLAN: Server Manager provisioning support required
description: updated
Abhay Joshi (abhayj)
Changed in juniperopenstack:
importance: High → Wishlist
Revision history for this message
Abhay Joshi (abhayj) wrote :

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

Revision history for this message
Abhay Joshi (abhayj) wrote :

Hari,

As per Dheeraj's discussion with Chhandak no change is needed in SM for the above feature provisioning support. If that is not the case, please detail what needs to be done and reassign so that we can look into it.

Thanks,

Abhay

Changed in juniperopenstack:
assignee: Abhay Joshi (abhayj) → Hari Prasad Killi (haripk)
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.