2019 21st International Conference on Transparent Optical Networks (ICTON) 2019
DOI: 10.1109/icton.2019.8840430
|View full text |Cite
|
Sign up to set email alerts
|

Container-Based Microservices SDN Control Plane for Open Disaggregated Optical Networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 2 publications
0
5
0
Order By: Relevance
“…There is no flexible isolated allocation of resources to components in such a system. Unfortunately, most of the SDN controllers are monolithic by design [17] [18] [19] with tight coupling between applications and controller core. An organic organisation of such a system with diverse roles and functions is to separate the functions into communicating modules with dedicated resources.…”
Section: ) Flexible Resource Allocation and Application Isolationmentioning
confidence: 99%
See 1 more Smart Citation
“…There is no flexible isolated allocation of resources to components in such a system. Unfortunately, most of the SDN controllers are monolithic by design [17] [18] [19] with tight coupling between applications and controller core. An organic organisation of such a system with diverse roles and functions is to separate the functions into communicating modules with dedicated resources.…”
Section: ) Flexible Resource Allocation and Application Isolationmentioning
confidence: 99%
“…[16] defines monolithic application as a single, self-contained unit where components are interconnected and interdependent, resulting in a tightly coupled code. Popular controllers such as ONOS and ODL are monolithic [17] [18] [19]. Due to such tight coupling, monolithic software is heavily technology stack dependent and does not isolate resources leading to inefficient resource allocation.…”
Section: B Contributionsmentioning
confidence: 99%
“…In [20,23], the authors experimentally showed a basic cloudnative SDN controller and studied the latency overhead that the communication between microservices introduced, and they performed basic demonstrations of two of the most fundamental benefits of the cloud-native approach, self-healing and auto-scaling. In [24,25] the authors demonstrated the ability of a microservices-based SDN controller to swap modules on the fly, using Open Network Operating System [26] (ONOS) or OpenDaylight [27] (ODL) SDN controllers (monolithic) as the core module. Other projects hosted by the Linux Foundation [28] that started as monolithic controllers have changed their path and have begun the transition to a microservices-based architecture.…”
Section: Related Workmentioning
confidence: 99%
“…Other frameworks like KANDOO [9] and ORION [10] are logically distributed, but require full (KANDOO) or hybrid (ORION) hierarchy to work. Container-based (or micro-services-based) SDN architectures [11], distribute the services of a monolithic SDN controller across the network. This allows the system to achieve greater scalability and modularity at the cost of higher latency [12] and of heavier difficult management, due to micro-service orchestration and load balancing.…”
Section: A Related Work On Multi-controller Sdn Frameworkmentioning
confidence: 99%