Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »


This page provides a summary of project-by-project El Alto release updates. The table shows the list of approved projects. In addition, it also lists a few subcommittees (use-case, architecture, security) and OVP.

ProjectKey UpdatesBenefits
A&AI
  • Converting all microservices to Alpine, created common images for users to select either Alpine or Ubuntu, reduced the number of microservices that is started by default for the demo
  • Updated to newer versions of spring boot — in the process of moving to spring-boot 2, but many of the microservices are still running 1.5.21
  • Updated to JanusGraph 0.2.3, which is a seamless upgrade from 0.2.0 which was used in Dublin
  • Code footprint reduction
  • Greater stability
AAF
  • Engaged Global Location Strategy for Locator (from Dublin)
  • Engaged Certificate Dynamic Generation for Apps (from Dublin)
  • Miscellaneous improvements and fixes
  • Greater scalability
  • Greater security
  • Greater stability
APP-C
  • Upgraded OpenDaylight (ODL) version to Fluorine SR2
  • 14 bug fixes
  • 5 security fixes
  • Expanded support for VNF configuration
  • Greater stability, security
CLAMP
  • All major security issues resolved
  • Front-end GUI framework moving from Angular to the  React
  • Genericity and Re-factoring reduces code footprint(size) by around 40%
  • Increased security
  • Code footprint reduction
CCSDK
  • OpenDaylight Fluorine SR2 (version 0.5.4) and OpenDaylight Neon SR1
  • Support Netconf notifications
  • Controller Design Studio Initiative –
    • Automated vLB_CDS SDC Model Distribution via Robot Script
    • Automated E2E Run Time MACRO Execution for vLB_CDS use case via Robot Script 
    • Consolidated controller blueprint pod into blueprint processor pod. 
  • 45 bugs fixed
Captured in APP-C/SDN-C
DCAE
  • DCAE Platform/Deployment updates
    • Dashboard deployed via Helm
      • All DCAE Platform components: Cloudify, ConfigBindingService, InventoryAPI, ServiceChangeHandler, PolicyHandler, Healthcheck moved to Helm in Dublin
    • DCAE Cloudify deployed MS pods auto-cleanup (triggered via Helm)
    • DCAE MS Deployment options
      • Static deployment
        • Support integration usecases
      • Dynamic deployment
        • Cloudify/cli or Dashboard or CLAMP
  • Dynamic Topic/feed support
    • Dmaap Plugin enhancement (to support DMAAP-BusController interface)
    • Bootstrap updates
      • Configmap, consul entry, Update k8s plugin key to include configmap,
    • k8s plugin enhancement to support dynamic feed
    • Verified dynamic topic/feed on DMAAP Message Router and Data router interfacing components.
      • DataFileCollector and Pm-Mapper were pilot ms
    • Bp-gen tool enhanced to support dmaap plugin integrated blueprint generation
  • TLS Enablement for platform components
    • ConfigBindingService (deployment for El-Alto supports 2 parallel service – HTTP and HTTPS to mitigate client migration impact)
    • Deployment Handler
    • InventoryAPI
    • Cloudify Container
  • Other Security updates
    • Image optimization
      • CBS, Inventory-API, ServiceChangeHandler, HV-VES, PRH, Son-handler
    • Non-root
      • SON-handler, PRH, ServiceChangeHandler, CBS, Inventory-API, HV_VES
  • Increased usability
  • Dynamic topic/feed support for increased flexibility in closed loops
  • Greater security
DMaaPDMaaP Message Router:
  • New Features
    • Cert based authentication support in Message Router
    • Improved Kafka and Zookeeper cluster lookup
    • Pluggable Kafka server.properties,log4j.properties and Message Router logback.xml
  • Bug Fixes
    • Fixed for security vulnerabilities in Message Router
    • Fixed authorization issues in Message Router

DMaaP Data Router:

  • New Features
    • Enhanced logging to match Platform Maturity Logging Spec.
  • Bug Fixes
    • Fixed for security vulnerabilities in Message Router
  • Greater security, stability
  • Enhanced logging
Documentation
  • Documentation improvements
  • Swagger Integration
--
External API Framework
  • 4 bug fixes
  • Greater stability
Holmes
  • No updates
--
Integration
  • Increase E2E Test Automation
--
Logging
  • Reduce the number of vulnerability issues.  There are 15 issues addressed for this release.
  • Greater security and stability
MSB
  • Minor functional enhancements—delete custom services, register https services via MSB mgmt. UI
  • 2 bug fixes
  • Greater stability, security, usability
Modeling
  • A new repo has been created (modeling/etsicatalog), which provides package management service and parser service as Micro Service
  • New model specification publication
    • root model
    • business and interaction model
    • VES 7.1 model
  • provide general micro service for package management and parser service
  • new models covering more area
MultiCloud
  • Rebased most MultiCloud services to python3
  • Rebased MultiCloud services to latest Django packages to fix security vulnerability issues
  • 7 critical bugs fixed
  • Improved usability of MultiCloud k8s plugin
  • ONAP4K8S profile is added - A smaller ONAP if the cloud regions are all Kubernetes based.
  • ISTIO based security for ONAP4K8S profile is verified.
  • Enhancements to work with OVN Network operators, Provider network operator.
  • Greater stability, security, usability
Music
  • MUSIC Control Panel UI based on ONAP Portal SDK
  • Eliminating ZK and building mechanism with Cassandra Light Weight Transaction for locking to simplify containerization and boost performance
  • AAF CADI Support
  • Keyspace Based logging
  • Internal retry mechanisms
  • MUSIC API improvements to allow multiple non-blocking reads to improve performance
  • MDBC 2.0 - Allows apps to gain resiliency and performance benefits of MUSIC without rewriting existing JDBC code, supports mixture of tables requiring immediate and eventual consistency. Built support for MySQL, MariaDB and Postgres database. Utilized existing open source Avatica project and filled the solution gaps with connection pool support and optimization.
  • Remediation of all 9 open Black Duck, 28 Fortify and 5 Sonar reported issues.
  • Greater security, stability, usability
  • New enhancements to make it easier for workloads to consume Music 
CLI
  • Multi-level orchestration capability (how platform helps to support the hierarchy of service->domain->resource level orchestration and this platform would help to perform orchestration at each level and across.) Python, or similar scripting/workflow engine can be used for this
  • VNF Test Platform(VTP) has used the Open Command Platform (OCOMP) – part of ONAP CLI project, for VNF life cycle testing (create and delete)
  • Enabled as experimental (dev) mode
  • Used for end-end automation of VNF service provision and termination for both HEAT and TOSCA based VNF service
  • Multi-level orchestration capability
  • Used for increasing test coverage  and OVP
  • Ability to use CLI as an alternative to GUI/API
OOM
  • 25 bug fixes
  • Higher stability
OOF
  • CMSO (Change Management Scheduler Optimization) enhancements - Schedule a workflow in SO and track status to completion
  • Automation on policy model uploading for vCPE, vFW use cases
  • 10 Bug fixes
  • 4 Vulnerabilities fixed
  • Enhancements for change management scheduling
UUI
  • Adaptive Pages : change the Home, Customer, Lifecycle Management and Package Management modules to adaptive pages that can be normally displayed in all screen sizes
    • Mock Data Scheme : build mock data scheme to support the development and preview in local environment in case of lack of server environment
    • Document Enhancement : enrich README.md to introduce the general situation and add CHANGELOG.md to record the commit messages
    • Structure Optimization : restructure the project to increase the development efficiency and improve the performance
    • Function Optimization : delete useless modules and simplify some apis to improve loading speed of the project
  • 2 bug fixes
  • Improved usability with support for different screen sizes
  • Greater stability and performance 
Policy
  • 56 minor enhancements or fixes
    • Policy Lifecycle API handling of Version fields
    • Improvement of Docker image generation
    • Code cleanup: sonar, checkstyle and code coverage for core components
    • 22 Bug Fixes
  • Initial CDS API and Actor integration
  • XACML PDP retrieval of Policy Types to support ability of dynamic policy translation using "matchable" metadata fields.
  • CII Silver Badging for core components
    • Various upgrades of dependencies for security fixes
  • Greater stability and security
Portal
  • Bug fixes and security enhancements
    • Specifically, addressed OJSI security enhancements and also fixed security issues reported by NexusIQ scan tool. As part of maintenance, enhanced known MariaDB/UX bugs and improved deployment helm charts.
  • Greater stability and security
SDN-C
  • New functionality such as ODL Neon, implementing a Configuration database, Netconf enhancements including receiving notification from RAN
  • 41 bug fixes
  • 11 security fixes
  • Closed loops can use Netconf notification
  • Ability to store configurations
  • Expanded configuration capabilities
  • Greater stability and security
SDC
  • Fixed 12 OJSI tickets
  • Integrated with AAF for certificates, so SDC works in HTTPS-only mode;
  • 8% more test coverage
  • Migrated to OParent
  • Upgraded DB infrastructure (Titan to JanusGraph)
  • And fixed 60 defects
  • Greater stability, security
SO
  • 84 enhancements
  • 156 bug fixes
  • Greater stability
VF-C
  • VF-C added 15 csit test cases to cover more API and code branch
  • Optimized NSLCM, catalog, VNFLCM code and 20% code reduction
  • Leverage existing VF-C capabilities to Support OVP TOSCA VNF validation.
  • Integrate with CLI and improve the VF-C usability
  • Greater stability
  • Code footprint reduction
VID
  • 4 bug fixes
  • 1 security fix
  • Greater stability and security
VNFSDK 
  • TOSCA based VNF validation enabled for support OVP & CVC.
  • TOSCA based VNF compliance check based on some operator requirements.
  • SDC now integrated VNFSDK VTP on VNF validation.
  • ETSI SOL004 Security check (CMS signature validation) enabled.
  • Code quality improvement.(e.g. replace the Jackson to Gson, sonar issue fix)
  • A C++ implement of VES spec 7.0.1 on ves-agent.
  • VNF SDK: improved support for ETSI SOL004
VNFRQTS
  • Defined reference test cases for VNF onboarding and instantiation to further expand the compliance badge scope available in the OPNFV Verified Program (OVP).
    • Covers both Heat-based and TOSCA-based VNFs
  • Over 30 requirement changes across VNF packaging, security, monitoring, and management to ensure VNF Providers can more readily integrate with ONAP in a compliant and secure manner
  • VNF Requirements: 30 additional VNF requirements around VNF packaging, security, monitoring, and management to improve VNF interop and security compliance
VVP


  • New features:
    • VNF Preload Generation
      • Executing the VVP validation scripts will now generate valid preloads for each VF module present in a VNF
      • This simplifies the creation of preloads, and greatly reduces the chance of errors during instantiation due to an incomplete or malformed preload
      • Supports both VNF API and GR API formats
  • Security, Performance, and Bug Fixes:
    • Improved performance of validating complex VNFs by > 30%
    • Improved security by adding bandit library to perform code scans on each commit
    • Aligned VVP validation scripts with the latest version of the VNF Heat Template Requirements
    • Improved error messages, enhanced report readability for users
    • Refactored code to reduce code complexity and increase code re-use


  • VVP: Day 0 config simplification for testing, greater security, performance, stability 
Benchmark

Completed

  • The performance test script of vfw has been developed 90%. Before we have run the basic functions on the B version, we have not tested the concurrent version in the B version. Last month and the integration group meeting, the integration team suggested that we switch to the D version of the vfw performance test.
  • The vcpe performance test script has been developed. On the onap dublin version, we create only one virtual machine model. And use the modified vcpe script to create a service instance and virtual machine. The concurrent creation of a single virtual machine script, the completion of 20 concurrent tests, and the recording of test results

Work in progress

  • Find the reason why the virtual machine was not successfully created in the 20 concurrent test in the vcpe performance test.
  • Transplant the beijing version of the benchmark test mock server, simulate openstack request processing, and then concurrently create a virtual machine test.

Use Case Subcommittee No new use cases--
Arch SubcommitteeNo architectural change--
Security Subcommittee
  • AAF Auto-Configuration and Certificate Generation

  • Upgrade to latest oParent 2.1


Modeling SubcommitteeDeveloped and published new information model specifications for:
  • root model
  • business and interaction model
  • VES 7.1 model

Information Integration

  • The Root model establishes a common base for the ONAP information model
  • The general Business Interaction model provides a means to tie in concepts such as Service Order, VES Events, and Licenses into ONAP's model hierarchy
  • The VES model describes ONAP's Event Streaming information as implemented
Infrastructure Improvements
  • Self-Serve Release
  • Kick-Off Dockerhub Migration
  • Release Management Automation
  • Activation of jS Test Coverage
  • Improve tool-chain efficiency
  • Improve software quality
General
  • Total 3571 issues being addressed
  • Test coverage increase TBD
  • Footprint reduction - A&AI, CLAMP
  • Stability proof TBD
  • Scalability proof TBD
  • Performance proof TBD

  • No labels