Skip to content
Snippets Groups Projects
01-introduction.md 1.58 KiB
Newer Older
  • Learn to ignore specific revisions
  • Manuel Kieweg's avatar
    Manuel Kieweg committed
    # Introduction
    Lorem ipsum at nusquam appellantur his, labitur bonorum pri no [@dueck:trio]. His no decore nemore graecis. In eos meis nominavi, liber soluta vim cu. Sea commune suavitate interpretaris eu, vix eu libris efficiantur.
    
    ## Motivation
    
    ## Overarching Project Goals
    
    * Keep It Simple, Stupid (KISS)
    * Reuse existing technologies bits wherever possible
    * Integrate state-of-the-art technologies and methodologies
    * Document, Document, Document
    * Automate almost everything right from the beginning
    * be an excellent citizen: test, test, test
    
    Some unsorted thoughts the be ordered yet:
    
    * Storage of information in some external database, make use of database features, e.g., for state replication
    * eye towards web-technologies/features, such as externalisation of state
    * one API to "talk"  administratively to the network controller
    * core of controller should be kept simple/lean, i.e., just the basic primitives
    * core should be extended by modules to add functionality beyond basics
    * modules should be loaded (or unloaded) during runtime of the controller core
    
    * reuse existing software if possible and if those are stable, i.e., documented, maintained etc,  on a long time
    
    Manuel Kieweg's avatar
    Manuel Kieweg committed
    
    
    ## Structure of this Memo
    
    
    ## Use Cases to be considered
    
    The development of a general purpose SDN controller is not the primary goal at this early stage of the project.
    Instead there are two use cases to be considered in the implemenation works that are currently ongoing:
    * Primary: optical domain SDN-controller for the CoCSN project
    * Secondary: SDN-controller for our local labs to manage an Ethernet-based lab environment