Versions Compared

Key

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

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Run performance basic test, depends on performance criteria availability for level 1
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01Participate to Stability runs Level 1
  • 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
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01Reach CII passing badge, increasing test coverage as remaining item
  • 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
Scalability01Reach Level 1 single site horizontal scaling
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11Using LOG4J common framework for logging
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11API documentation provided
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation


...

    • API Incoming Dependencies

  • List the API this project is expecting from other projects.
    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 Name

    API Description

    API Definition Date

    API Delivery date

    API Definition link (i.e.swagger)

...

  • NoneNoneNoneNoneNone


    • API Outgoing Dependencies

    API this project is delivering to other projects.

    API Name

    API Description

    API Definition Date

    API Delivery date

    API Definition link (i.e.swagger)

...

  • ProvisiningAPI for creating,deleting and listing the administrative objectsAug 02 2017March 08 2018AAF API
    Admin APIAPI for the admin accessAug 02 2017March 08 2018AAF API
    CADICADI ( CODE ACCESS DATA IDENTITY)Aug 02 2017March 08 2018AAF API





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

    Name

    Description

    Version

...




  • DockerContainer engine1.12
    Cassandradatabase container2.1.16



    In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

    Testing and Integration Plans

    Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

    Describe the plan to integrate and test the release deliverables within the overall ONAP system.
    Confirm that resources have been allocated to perform such activities.

    AAF will invest in CSIT tests to allow further integration testing, AAF already provided some tests as part of R1.

    Gaps

    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 identified

    Impact

...

  • Testing/Integrationlimited testing of final product
  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

  • This section may be used to document internal milestones that the team agreed on.

    Also, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, provide these agreements and dates in this section.

    It is not expected to have a detailed project plan.

    Date

    Project

    Deliverable

    To fill outAAFAAF - CertMan,oAuth

    Documentation, Training

http://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html

...