Versions Compared

Old Version 1

changes.mady.by.user Dan Timoney

Saved on

compared with

New Version Current

changes.mady.by.user Dan Timoney

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.


Deliverable NameDeliverable DescriptionDeliverable Location
CCSDK
SDNC Source CodeSource code for
CCSDK
SDNC projectONAP gerrit
CCSDK
SDNC Maven ArtifactsCompiled code that can be referenced in other projects as maven dependenciesONAP Nexus
CCSDK
SDNC Docker Containers

Docker containers associated with SDNC project:

  • Ansible server container
  • Controller (OpenDaylight) container
Database
  • DMAAP listener container
Directed Graph Builder
  • SDC (UEB) listener container
ONAP Nexus
DocumentationUser and developer guidesONAP Wiki
CCSDK
SDNC CI/CD automationScripts to automate compilation and deployment of maven artifacts and docker containers

ONAP gerrit

ONAP Jenkins


Sub-Components

Subcomponents of each ONAP project may be found on the Resources and Repositories (Deprecated) page on this wiki.  Please see the CCSDK SDNC section of that page for subcomponent list of SDNC.

ONAP Dependencies

SDN-C depends on the following projects:

  • Active and Available Inventory (A&AI)
  • Common Controller SDK (CCSDK).
  • Service Design and Creation (SDC)
  • Data Movement as a Platform (DMaaP)
  • Documentation
  • Integration
  • External API
  • Modeling
  • Multi VIM/Cloud
  • Policy

Architecture

High level architecture diagram

CCSDK is delivered as a set of libraries accessible as Maven dependencies, as well as a set of base Docker containers. The docker containers themselves are intended to be used by other projects as a basis for their own controller-specific docker containers.

The following diagram illustrates how CCSDK is used by the controller projects:

Image RemovedThe following diagram shows the high level architecture of SDNC:

Image Added

The major architectural components of the SDN-C controller are:

  • Device Data Models : Yang models that define interfaces to devices (virtual or physical) that the SDNC configures
  • Service Network Data Models : Yang models that define data maintained within the SDNC about the network used by the set of services supported by this SDNC instance
  • Service Chain Data Models : Yang models that define how services supported by an SDNC instance can be chained
  • Service Data Models : Yang models that define data maintained within the SDNC for the set of services it supports
  • Directed Graphs : programmable logic, updatable at run time with no restart, that define the behavior of the SDNC
  • Service Logic Interpreter : module provided by CCSDK which allows platform to execute directed graphs
  • API Handler : code (mostly generate from service Yang models) which implements RESTCONF API into SDNC.  Most API handlers should follow the following pattern:
    • Call directed graph named after invoked RPC, passing RESTCONF RPC parameters as Java Properties object.
    • Return results from directed graph invocation as response to RESTCONF RPC
  • Interface adaptors - code that allows directed graphs to invoke external interfaces


Platform Maturity

Please fill out the centralized wiki page: Guilin Frankfurt Release Platform Maturity


API Incoming Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
A&AI :
schemasA&AI schemas used by CCSDK aaa-service module
VNFAPI used to read/write information about VNFsDefined in seed codeIncluded in seed codeTBD
SDC : distribution
client
API used
by ueb-listener (in CCSDK sdnc-northbound repo) to receive
to distribute artifacts from SDC to subscribersDefined in seed codeIncluded in seed codeTBD
DMaaPAPI used to receive DHCP event notification8/23/178/23/17DMaaP API


API Outgoing Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
Maven libraries
Healthcheck
Libraries used as dependencies by SDN-C, APP-C, DCAE and OOM
API used to verify that platform is available and healthyIncluded in seed codeDelivered in seed code
Javadoc will be providedDocker containersBase docker containers will be provided which can be used by SDN-C and APP-C as a basis for their docker containersIncluded in seed codeDelivered in seed code
TBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)
Generic VNF API

API used to request resources for VNFs. Will be deprecated in Beijing in favor of Generic Resource API.

Note: This API is deprecated in Frankfurt and will be removed in Guilin

Included in seed codeDelivered in seed codeTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)
Generic Resource APIAPI used to request resources for VNFs. This API is a superset of the generic VNF API, which it replacesIncluded in Amsterdam releaseDelivered in AmsterdamTBD (requested Confluence OPEN API to be installed so this can be published on ONAP Wiki)

Third Party Products Dependencies

NameDescriptionVersion
OpenDaylightOpenDaylight SDN Controller PlatformSodium
SR3
SR4

Testing and Integration Plans

...

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out

Known Defects and Issues

Please refer to TBD

Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Guilin Risks

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

Please update the following centralized wiki: Frankfurt Guilin Documentation

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...