...
- Full and comprehensive VNF/Software Application(VF), and service design, which includes, not limited to:
- Onboarding VNF/VF
- Workflow design
- lifecycle flows
- change management flows
- Close loop design
- policy design
- Service function chaining Design
- VNF/VF License Design
- VF/VNF deployment flavor design
- Collaborative design
- versioning
- Design Lifecycle
- VNF/VF/SERVICE testing and certification
- Distribution to ONAP
- TOSCA parser
- External API- for VNF/VF and service design service
- Image management
- Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
- Specify any interface/API specification proposed,
- Identity a list of features and functionality will be developed.
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
Scope
- Full and comprehensive VNF, and service design, which includes, not limited to:
- Onboarding VNF
- Workflow design
- Close loop design
- Distribution to ONAP
- External API
- Image management
- Collaborative design
Architecture Alignment
- How the existing functionality is going to align in ONAP
- How it will integrate with:
- VNF-SDK
- ICE (VNF certification)
- Modeling
- How it will integrate with:
- What kind of dependency other projects will have with SDC, e.g SO modeling?
- How will multi VIM project influence on the input/ output we have for SDC?
- How to align to standards like ETSI VNF packaging?
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
- How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
- Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.
Resources:
current integration and new integrations for SDC in ONAP
- How the existing functionality is going to align in ONAP
- How it will integrate with:
- VNF-SDK
- ICE (VNF certification)
- Modeling
- How it will integrate with:
- What kind of dependency other projects will have with SDC, e.g SO modeling?
- How will multi VIM project influence on the input/ output we have for SDC?
- how do we keep close integration with the VIM that impacts modeling
- How to align to standards like ETSI VNF packaging/OASIS TOSCA/TMF?
Resources:
- Primary Contact Person: Michael Lando Gerrit ID ml636r Company AT&T
- David Shadmi Gerrit ID sd200p Company AT&T
- Liron Shtraichman Gerrit ID lironsh Company AMDOCS
- Tal Halfon mail Halfon.Tal@amdocs.com Company AMDOCS)
- Mark Pond mail mpond@amdocs.com Company AMDOCS
- An Ho(HUAWEI) Gerrit ID anipbu Company HUAWEI
- KACHOROVSKY, ARKADY mail ak314p@intl.att.com Company AT&T Primary Contact Person
- Names, gerrit IDs, and company affiliations of the committersNames and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
...