Presentation by Ikuo Nakajima at APRICOT 2019 on Wednesday, 27 February 2019.

1. Automation of Clos network with eBGP
at LINE
Ikuo Nakajima
<ikuo.nakajima@linecorp.com>

3. For coming services, we need agility and capacity in
our infrastructure.

4. Issues in a previous traditional network architecture
1. Capacity
Significant loss of bandwidth in east-west traffic
Limited scalability with L2 redundancy technologies
2. Agility
Time-consuming manual processes

5. 5 stage Clos Network with white boxes

6. Non-Blocking Architecture

7. L2 or L3 link between ToRs and Servers

8. BGP Routing on the host

9. Clos architecture proven to be beneficial in...
1. Capacity
Non-Blocking Architecture
scalability with box switches and L3 links
2. Agility
Automation <= Not mentioned yet

10. Many Nodes and Cables

11. Steps in our automated development

12. Initial Setting

13. Cable Connection Check

14. BGP Configuration on Cumulus

15. Generation of inventory files with the database/dict

16. Installation of BGP configuration with Ansible

17. Tools for Automated development

18. Future work
Simplify the template file that became complicated to deal with some functions
like MLAG and ACL.
Make a user friendly GUI to edit values in DB.
Enhance the monitoring tool to check the entire status of eBGP peering, routing
information, and latency of traffic.
Build multi-tenancy on Clos network