| Status | Choose One:
|
|---|
|
| Submitter |
|---|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Names of additional contributors
Each proposal should have at least 1 JIRA ticket for tracking purposes. Please open the ticket as a Task in the VNF Requirements project.
Abstract
Short introduction to the problem being solved and approach
Rationale
Detail what is the motivation for this proposal and why it should be adopted
Other Options Considered
If applicable, list out any other alternative approaches that were considered and why they were not pursued
Proposal
Detail of the proposal. This should also address how the changes should be made including any tool chain enhancements, content updates, and potential stakeholder reviews.
References
| Contributors | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Proposed Release | Honolulu | ||||||||
| JIRA Ticket(s) |
|
Abstract
ETSI NFV SOL work group has released v3.3.1 of the SOL001&SOL004 specifications and the ETSI NFV IFA work group has released v4.1.1 of the IFA011 specifications.
We would like to enable the onboarding of VNF packages that are compliant with v3.3.1. We would also like to propose custom changes derived from the IFA011 v4.1.1 to support containerized VNFs.
The corresponding Information model changes for v3.3.1 and v4.1.1 have been accepted by the modeling team and are now merged into the ONAP IM.
We have commitments from various companies to contribute code into SDC, SO, ETSI Catalog, A&AI, to support these changes.
Rationale
Compliance with the 3.3.1 version of SOL004 and SOL001 will enable standardized support for Change VNF Package feature which will enable upgrade functionality.
The custom CNF changes that we want to introduce will support the ability to onboard container based VNF packages, incorporation of those VNFs into Network Services with SDC and deployment of those Network Services/VNFs through SO.
Other Options Considered
We considered incorporating the required CNF changes using the 2.6.1 series but felt that we needed several features that introduced in subsequent releases.
Proposal
- The Information Model changes for 3.3.1 and 4.1.1 have been proposed and the model changes accepted.
- Update the VNF Requirements to comply with v3.3.1 of the SOL004 and SOL001 specifications
- Propose modifications to v3.3.1 model to support containerized VNFs as described in IFA011 v4.1.1
- Review changes with VNF Requirements team
- Review changes with SDC team, AAI Team, SO Team
- Develop sample VNF packages that comply with the new specification
- Validate that SDC can onboard the packages
- Validate that SDC can build Network Services using the VNFs and CNFs in those packages
- Validate the ETSI Catalog can store and access those packages
- Validate that SO can deploy the Network Service and catalog the VNFs/CNFs
References
ETSI-Alignment Support for HonoluluLinks to any addtional resources referenced in or related to this proposal.