...
...
- June 28, 2017 Workflow review
Chengli Wang and Lingli Deng from China Mobile presented VoLTE use case. They went through the work flow for service design, instantiation, auto healing/auto scaling and termination. 31 Participants joined the meeting and discussion. The meeting recording can be accessed here: https://zoom.us/recording/play/zClGuWa2cFq-g3YEWC-sZ74V9iJaHAx2Iw7ePKuhh1q1ttjSSFXRyoJhYxpmk8bC
Meeting minutes:
At high level, there are edge and core data centers in the use case. EPC components split between edge and core data centers. Similarly IMS components also split between edge and core. A WAN network with underlay and overlay connects the two data center.
...
5. Depend on the interface and capability of SDN local controller, we will decide in the next meeting how modules (MultiVIM, Neutron, SDN local controller, SDN WAN controller, DC-GW) work together to provide VXLAN overlay between data centers via EVPN.
July 20, 2017 DC Gateway Local Controller Interface
During the meeting, we discussed local DC gateway controller sample APIs to manage EVPN VXLAN overlay network between two data centers.
- Explained one option of how DC gateway controller interacts with DC gateway, Neutron and compute node.
- Discussed DC gateway controller sample APIs to create L2&L3 EVPN VXLAN overlay network between DCs. Other APIs to support read, update and delete EVPN VXLAN overlay network are also available. SDN-C team agreed that the APIs looked good.
- VIM team and Multi-VIM team also described other options for DC network to support VXLAN overlay. We will have further discussions of those options after R1.
The action items:
- Have a table to define the source for the parameters (import route target, export route target, networks, etc.) used in controller APIs. The source can be from vendor or SDC, etc.
- Should make decision on whether L2, L3 or L2&L3 VXLANs are required for R1.
The slides used in the meeting:
| View file | ||||
|---|---|---|---|---|
|