Page Comparison

...

Harden the OOF development platform (Highest priority)
- Deployment scripts, CSIT, CI for different streams, Nexus image cleanup
- Using Music as a service
Maintaining current S3P levels of the project as new functional requirements are supported (Highest priority)
- Security enhancements progressing towards Silver badge
  - All internal communication encrypted
  - AAF integration - role-based access control and authorization for all calls (depending on Python support from AAF)
  - Code coverage: achieve 60% target code coverage
- Performance: Creating a plan for performance improvements
- Manageability:
  - Adherence to log specification v1.2 - ONAP Application Logging Specification v1.2 (Casablanca)
  - Externalized config management
- Usability
  - Adherence to ONAP API Common Versioning Strategy (CVS) Proposal
  - move all internal and external facing APIs to Swagger 2.0

HPA enhancements (resources from Intel)
- Service Assurance - streaming telemetry about health of platform (CPU pinning, and NUMA) - primarily from OpenStack
Homing enhancements improving the deployability of Services Using ONAP platform
- Homing multiple simultaneous instances of the service: queueing homing requests based on discovering dependency on shareable resources (resources from AT&T)
- Considering Latency Reduction (in addition to geographical distances) for homing optimization (resources from AT&T)
- Enhanced capacity checks (resources from VMWare)
5G SON Optimization (resources from Nokia, AT&T)
- PCI optimization POC using OSDF
- Health Checks, CSIT, Dockerization, K8S HELM Chart, S3P with 60% code coverage
Edge Automation through ONAPONAP (resources from VMWare)
- HAS in Edge Orchestration
- Enhanced capacity checks

...

Versions Compared