Versions Compared

Old Version 7

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

compared with

New Version 8

changes.mady.by.user Vijay Venkatesh Kumar

Saved on

Key

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

...

Project NameEnter the name of the project
Target Release NameCasablanca
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Ericsson, Tech Mahindra, Cisco

Scope

What is this release trying to address?

...

3. Adding to mS suite of collectors and event processors

Platform Maturity (i.e., S3P ) Target

  • Resiliency
    • Level 2 - regression from Beijing for existing components
  • Scalability
    • Level 1 - regression from Beijing for existing components
    • Mutli-site support   **Dependency on OOM Team (Stretch Goal, not currently committed for Casablanca)
  • Stability
    • Level 2 - regression from Beijing.
  • Security
    • Level 1
    • Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Dependency on DMaaP project for BusController delivery (Stretch Goal, not currently committed for Casablanca)
    • Securing api/interface and authorization via AAF (Stretch Goal, not currently committed for Casablanca due to following 1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)

...


Following new services will be introduced for R3

...

In addition, DCAE team will work on following as (Stretch Goal, not currently committed for Casablanca due to resource constraint / external dependencies /unclear requirement )

  • Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Dependency on DMaaP project for BusController delivery
  • Performance optimization
    • VESCollector
    • TCA (new TCA service independent of CDAP will be contributed for R3).
  • VES 6.0 upgrade support
    • Primarily VES Collector updates for new domains and transformation
      (Security requirement for mutual TLS needs further clarification)
  • DCAE onboarding tool (dcae_cli) enhancement and environment support
  • Mutli-site support   **Dependency on OOM Team
  • Securing api/interface and authorization via AAF (Need further clarification/support from Security/AAF team -  1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)
  • Following R2 items (descoped due to time/resource constraint) will be continued to enhanced for platform integration and /S3P needs
    1. Mapper MS
    2. Heartbeat MS
    3. PNDA
    integration
    1. Integration prep-work

Use Cases

DCAE will provide support for the following use cases, currently planning on test support with no code changes expected:

...

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance12
    • 0 -- none
    • 1 – baseline performance criteria identified and measured
    • 2 & 3 – performance improvement plans created & implemented
Stability22
    • 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
Resiliency22
    • 0 – none
    • 1 – manual failure and recovery (< 30 minutes)
    • 2 – automated detection and recovery (single site)
    • 3 – automated detection and recovery (geo redundancy)
Security1

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear and cannot be committed to.

1+


Securing api/interface and authorization via AAF (Stretch Goal, not currently committed for Casablanca due to following 1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)


Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Dependency on DMaaP project for BusController delivery (Stretch Goal, not currently committed for Casablanca)



    • 0 – none
    • 1 – CII Passing badge + 50% Test Coverage
    • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
    • 3 – CII Gold
Scalability1

1

Mutli-site support   **Dependency on OOM Team (Stretch Goal, not currently committed for Casablanca)


    • 0 – no ability to scale
    • 1 – single site horizontal scaling
    • 2 – geographic scaling
    • 3 – scaling across multiple ONAP instances
Manageability1

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (independent upgrade) and cannot be committed to.



    • 1 – single logging system across components; instantiation in < 1 hour
    • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability1

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (related to tutorial documentation) and cannot be committed to.


    • 1 – user guide; deployment documentation; API documentation
    • 2 – UI consistency; usability testing; tutorial documentation


    • API Incoming Dependencies

...