Versions Compared

Old Version 3

changes.mady.by.user Dan Timoney

Saved on

compared with

New Version 4

changes.mady.by.user Dan Timoney

Saved on

Key

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

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance010Awaiting guidance from Benchmark subcommittee
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01N/AAs a project that provides a library framework, CCSDK has no standalone component that can be soaked
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency12While CCSDK itself has no standalone component, it does provide an OpenDaylight docker container used by SDNC and APPC. In Beijing, CCSDK will support a clustered OpenDaylight configuration in Kubernetes, as well as a clustered database, to allow for automated detection and recovery within a site.
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01CCSDK will achieve 50% code coverage
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage + 50% test coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability01N/AScaling does not apply to CCSDK itself, as a set of libraries.
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11CCSDK will support ONAP standard logging.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11See readthedocs and wiki.
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation


API Incoming Dependencies

...

...

API

...

API
NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

  • API Outgoing Dependencies

...

A&AI : schemasA&AI schemas used by CCSDK aaa-service moduleDefined in seed codeIncluded in seed codeTBD
SDC : distribution clientAPI used by ueb-listener (in CCSDK sdnc-northbound repo) to receive artifacts from SDCDefined in seed codeIncluded in seed codeTBD

API Outgoing Dependencies


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
Maven librariesLibraries used as dependencies by SDN-C, APP-C, DCAE and OOMIncluded in seed codeDelivered in seed codeJavadoc will be provided
Docker 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


Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

...