日本語版はこちら

Abustract

The needs for our Network Orchestrator are diversified as LINE’s datacenter network continues to spread.
We’ve already used Network Orchestrator for some time, however,
we recently redeveloped Network Orchestrator to be adaptable to the diversifying needs. The new Network Orchestrator resolve the following problems using OSS tools such as Ansible, Docker, etcd and Pyang … – vendor-agnostic environment – scalability regardless of the number of switches under control – providing triggers to apply a configuration with right timing
(e.g. when a server connects to the switches and when the system receives the request – human error prevention – to handle problems caused by automation (e.g. apply incorrect configuration to every switch I’m sure the above problems are for not only our orchestrator but most of network orchestrator. In this session, I’ll explain how our new Network Orchestrator overcomes the above problems and
also discuss the common problems for Network Orchestrators and how to overcome them.

Place

SAIGOU(First Hall)

Date

Day2 Thursday, Jan 27th, 2022/12:00~13:00(1Hours 00Minutes)

Presenter

福田 守昴
LINE株式会社

Subaru Fukuda