Scratch pad for Beijing planning. Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.
Release 2 Mission:
Simplify the process of developing and onboarding VNFs. Expand ONAP's VNF ecosystem.
Highlights:
- Better integration with SDC for automatic onboarding – DONE
- Update pkgtools/marketplace to support VNF packaging model. Update VNF template to align with vnfd information model.
- add pkgtools to pypi
- Integrate VVP (ICE) tools to allow us to validate VNF packaging (not acceptance testing)
- Improve code quality & code coverage – DONE
- Improve security (S3P) (https, SOL004, possibly certificate validation)
Enhance functionality, Introduce security, Integrate with ONAP use-case flow and progress towards being carrier grade with high quality.
...
standalone validation tool
Backlog Items
- Function tests (common tools to allow VNF testing using robot framework)
- VES validation
- VNF templates (align with SDC)
Non functional & stability items:
- Security – authentication/authorization, Support Https - DONE (Https)
- Quary APIs not working, query framework needs to be enhanced - DONE
- DB operates without transactions
- Enhance error handling, introduce error codes to rest services. - DONE
- Enable swagger - DONE
- Validate csar content using ‘aria’ or configuration instead of the current static way
...
- Uploading and validation of images.
- Clean up the code - DONE
- Remove Open-O Traces
- Remove un-used code and bring the code coverage above 60%
- Optimize the client code and remove third party code from the repository.
- Csar packages are stored on local disk – may be lost – perhaps use volume or DB - DONE
- Enable the ‘life cycle test’ project which currently does nothing
- Interface with SDC - DONE
Carrier Grade Requirements
...