Versions Compared

Old Version 8

changes.mady.by.user James Forsyth

Saved on

compared with

New Version 9

changes.mady.by.user James Forsyth

Saved on

Key

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

...

Project NameEnter the name of the project
Target Release NameEnter the name of the release you are targeting to deliverBeijing
Project Lifecycle StateEither Incubation, Core, Mature.  Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended.AT&T, Amdocs, ZTE, Orange, Techmahindra

Scope

What is this release trying to address?

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01The target is to capture baseline performance, but it is unclear what we'll be capturing.
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01Unclear what kinds of random transactions will be sent to AAI.  Assuming it will be random runs of existing use cases w/ Robot or jmeter
  • 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
Resiliency12AAI will leverage OOMs single site failure detection and recovery
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01AAI will get to 50+ test coverage, most repos already above 50% ONAP SONAR
  • 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
Scalability01

AAI will leverge OOM; currently working on a clustered solution for cassandra on docker

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-539

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11AAI uses EELF and will continue to do so in Beijing
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...