Versions Compared

Old Version 8

changes.mady.by.user Gervais-Martial Ngueko

Saved on

compared with

New Version Current

changes.mady.by.user Gervais-Martial Ngueko

Saved on

Key

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

...

The other ONAP projects CLAMP depends on are:

  • SDC/DCAE-D : Rest based interface exposed by the SDC, Distribution of service to DCAE + SDC UX UI SDKDistribution of Templates to CLAMP via SDC distribution client jar
  • DCAE: Rest based interface exposed by DCAE, Common Controller Framework, DCAE microservices onboarded (TCA, Stringmatch, Holmes (optional))
  • Policy: Rest based interface (the Policy team provide a "jar" to handle the communication), both XACML and Drools PDP, APIs to App-C/VF-C/SDN-C
  • DMaaP: Message bus within DCAE and cross-ONAP
  • VNF use cases : defines what type(s) of control loop(s) can be implemented and configured by CLAMP

...

Platform Maturity

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
Performance0

0

(given CLAMP is runtime design time there is no point to adhere to L2 requirement) 

Run performance basic test, depends on performance criteria availability for level 1 - not able to commit to more than what was done on Beijing
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11

Participate to Stability runs Level 1

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-100

  • 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
Resiliency11

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-83

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security11
  • Reach CII passing badge, increasing test coverage as remaining item
  • AAF CADI integration
  • Infrastructure setup for js test coverage



  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage, including no critical and high known vulnerabilities>60 days old
  • 2 – CII Silver badge; internal/external communication encrypted; role-based access control and authorization for all calls based on CADI
  • 3 – CII Gold
Scalability11

Level 1 single site horizontal scaling

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-102

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

1

(2, if CLAMP can get more resource from the community)


  • 1 – single logging system across components; instantiation in < 1 hour

  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
    ; All application logging to adhere to
    ONAP Application Logging Specification v1.2

  • 3 - Transaction tracing across components

Usability1

1

Documentation only for this release - Stretch to have automated API docs (Swagger)

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-32

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCLAMP-31

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

    (2, if CLAMP can get more resource from the community)

    CLAMP is not anticipating new API at this point, so we are technically compliant with API CVS at this point

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

      All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines; All existing APIs must be documented in Swagger 2.0

    • 3 - UI consistency; usability testing; API Documentation

      (changed and external APIs follow policy)

    • 4 - API Documentation (all follow policy)




       


    API Incoming Dependencies

    List the API this release is expecting from other ONAP component(s) releases.
    Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

    Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

    API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
    Same as BeijingAPI exposed by SDC to get list of Alarms and service information'sDate for which the API is reviewed and agreedAlready availableLink toward the detailed API description
    Same as BeijingSDC Client(jar library provided by SDC team) used to get service template (describing control loop flow) and blueprint id( to know which blueprint has been distributed to DCAE for this Control Loop template)Already available
    		Already available
      API exposed by Policy to create/update guard policies 
    (used for scale out use case operational policies)    		 ongoing TBD 
    Same as BeijingAPI exposed by Policy to create/update policies 
    		Already available
    Same as BeijingAPI exposed by DCAE to start/stop a Closed Loop
    		Already available
    Same as BeijingAPI exposed by DCAE to trigger the deployment/undeployment of a Control Loop template
    		Already available
    Same as Beijing API exposed by DCAE to get status of a Closed Loop
    		Already available

    ...

    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryproject=CLAMP and issuetype in (bug) and status != closed
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    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).

    ...

    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

    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).

    Risk identifiedMitigation PlanContingency Plan
    new policy api(and contents) for guard policies creation not defined yet 


     "vf_module_id" usage for scale out use case not yet completely confirmed implement textbox to manually enter target parameter(for policy api call)use the textbox to enter the value of whatever vf_module id's we need to make the CL works 

    Resources

    Link toward the Resources Committed to the Release centralized page.

    Release Milestone

    ...

    The project team comply with the ONAP Charter.

    Release Key Facts

    Fill out and provide a link toward the centralized Release Artifacts.