SDN-C

Project Name:

Proposed name for the project: SDN-C
Proposed name for the repository: SDNC

Project description:

The SDN-C project provides a global network controller, built on the Common Controller Framework, which manages, assigns and provisions network resources. As a "global" controller, the SDN-C project is intended to run as one logical instance per enterprise, with potentially multiple geographically diverse virtual machines / docker containers in clusters to provide high availability. The project also will support the ability to invoke other local SDN controllers, including third party SDN controllers.

Scope:

The following features are in scope for the SDN-C project for ONAP release 1:
- Enhancements to support the ONAP release 1 use cases (vCPE, VoLTE)
  - Yang models,
  - Directed graphs
  - New Adapters needed to support use cases (details to be determined during planning phase)
- Support for third party controllers:
  - Adapter to allow DG to connect to netconf devices (netconf-lite)
- High availability (local)
The following features will be defined for the project backlog:
- Configuration versioning : ability to roll back the configuration
- CLI adaptor : abstraction later for CLI adaptor
- Support for third party controllers:
  - Adapter layer to interface with downstream controllers
- Geo diversity
- QoS logic support?

Architecture Alignment:

- How does this project fit into the rest of the ONAP Architecture?
  - This project provides the global network controller used by ONAP to manage network resources
- How does this align with external standards/specifications?
  - Netconf, YANG
- Are there dependencies with other open source projects?
  - OpenDaylight
  - ONAP Common Controller Framework
  - Service Orchestrator (main client calling SDN-C)
  - Microservice Bus (if that is used for the SO - SDNC interface)