Feature Tracking
Introduction
| Current mirror date: 2018.05.22 | This page is a mirror of the Feature Tracking page on the NFV private wiki. Information on the private wiki page is frequently updated, whilst the present page is regularly mirrored. Links to contributions will require authentication with an ETSI Online Account. |
Some introduction will be put here including guidelines, process description and tutorials.
- Link to Release 3 implementation process
- Link to the "consolidated IFA Release 3 Feature plan". Refer to NFVIFA(17)000914 and revisions. Latest version NFVIFA(17)000914r4
- Training for Feature Primes
- Process
- Wiki editing
- Naming conventions: e.g. FEAT00_IFA007_[Contribution name]
- To build a link to all contributions belonging to a feature, replace FEAT99 in the link stated below with the Feature short name for your feature e.g. FEAT15:
https://portal.etsi.org/Contribution.aspx?Tb_Id=789&searchText=FEAT99&IncludeSubTb=True&sort=pk_contribution&sortorder=DESC&NbItemsPerPage=50&Year=2017,2018
- Note: Agreed content can be added to Pseudo meeting --> If the access is restricted, this may only work within a workgroup.
- Related/Dependent Features: Please indicate other features which relate to the ongoing work. Details can be given in the implementation plan or in the issues section.
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add interface X in to IFA007. CR draft [LINK] | IFA | March-2018 | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT02: VNF software modification
Overview
| Feature Prime | Stefan Arntzen, Huawei . |
| Feature description | This feature addresses the initiation and the coordination of the software modification process related to VNFs. Goal is to minimise the impact of software modification on service availability. |
| Target Release | Release 3 (2018-X-X) |
| Impacted WIs | IFA007, IFA008, IFA011, IFA013, IFA010 (not approved) |
| Related/Dependent Features | FEATxx FEATyy |
| Status | Ongoing (0% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Stefan Arntzen (Huawei) Maria Toeroe (Ericsson) Shaoji Ni (Huawei) |
| Last Updated | 20xx-xx-xx |
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add functionality description of VNF software modification synchronisation in to IFA010. | IFA010 | January-2018 | Open |
| 002 | Define metadata to allow to synchronize the software modification process | IFA | February-2018 | Open |
| 003 | Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Or-Vnfm reference point | IFA007 | April-2018 | Open |
| 004 | Derive the requirements from REL006 for an interface for the coordination of VNF software modifications actions on the Ve-Vnfm reference point | IFA008 | April-2018 | Open |
| 005 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point | IFA007 | May-2018 | Open |
| 006 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point | IFA008 | May-2018 | Open |
| 007 | Finalize CRs for the changes from 001, 002, 005, 006 | July-2018 | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT03: NFVI software modification
Overview
| Feature Prime | Maria Toeroe, Ericsson. |
| Feature description | This feature addresses the support for the coordination of the NFVI software modification process with the VNFs hosted on the NFVI in order to minimize impact on service availability. |
| Target Release | Release 3 drop 1 (2018-X-X) |
| Impacted WIs | IFA005, IFA006, IFA007, IFA008, IFA010, potential impact on IFA011, IFA013 |
| Related/Dependent Features | FEATxx FEATyy |
| Status | Ongoing (10% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Maria Toeroe (Ericsson) Stefan Arntzen (Huawei) Shaoji Ni (Huawei) Mehmet Toy (Verizon) |
| Last Updated | 2018-03-27 |
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Based on REL006 add functionality description of NFVI software modification support to IFA010 for the VIM, VNFM and NFVO. | IFA010 | December-2017 | Open |
| 002 | Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point | IFA005 | January-2018 | Open |
| 003 | Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point | IFA006 | January-2018 | Open |
| 004 | Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point | IFA008 | January-2018 | Open |
| 005 | Based on REL006 specify the requirements for an interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point | IFA007 | January-2018 | Open |
| 006 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vi reference point | IFA005 | March-2018 | Open |
| 007 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Vi-Vnfm reference point | IFA006 | March-2018 | Open |
| 008 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Ve-Vnfm reference point | IFA008 | March-2018 | Open |
| 009 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point | IFA007 | March-2018 | Open |
| 010 | Specify the interface for the coordination of the NFVI software modifications with the hosted VNFs on the Or-Vnfm reference point | March-2018 | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT04: Host Reservation
Overview
| Feature Prime | Gerald KUNZMANN (DOCOMO Communications Lab.) |
| Feature description | The present enhancement proposes adding the capability to the NFV-MANO architectural framework to support the reservation of compute hosts (see clause 3.1 in GS NFV-PER 001) in the NFVI. Detailed feature proposal is available in IFA_Enhancement_Host_Reservation |
| Target Release | Release 3 drop 1 (2018-05) |
| Impacted WIs | IFA005 MegaCR in NFVIFA(18)000420r1 (Agreed MegaCR) (new text in clauses 2.2, 5.2, 5.3.X, 5.3.Y, 5.3.Z, 7.X, 7.Y, 8.X; updates clause 8.7.4) IFA007 MegaCR in NFVIFA(18)000421r1 (Agreed MegaCR) (updates clauses 6.3.2 "Grant VNF Lifecycle Operation operation" and 8.3.3 "GrantInfo information element") IFA010 MegaCR in NFVIFA(18)000419r3 (Agreed MegaCR) (new text in clauses 2.2, 3.1, 6.1.6, 6.X, 8.2.3, 8.X, A.2) IFA013 MegaCR in NFVIFA(18)000422r2 (Agreed MegaCR) (new text in clauses 5.2, 5.X, 7.X, 8.X) |
| Related/Dependent Features | N/A |
| Status | Ongoing (95% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Arturo Martin De Nicolas (Ericsson LM) Bertrand Souville (DOCOMO Communications Lab.) Joan Triay (DOCOMO Communications Lab.) |
| Last Updated | 2018-05-15 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Specify a requirement for the VIM to support the capability of handling reservation of resources at the host level. Specify a requirement for the NFVO to support requesting the reservation of resources at the host level. CR drafts: NFVIFA(17)0001086 (VIM) Status: FEAT Agreed NFVIFA(18)000146 (NFVO) Status: FEAT Agreed |
IFA010 | January-2018 | Completed |
| 002 | Specify requirements for an interface specialized on NFVI management on the Or-Vi to support the reservation of resources at the host level. CR draft NFVIFA(18)000053 Status: FEAT Agreed |
IFA005 | January-2018 | Completed |
| 003 | Specify an interface and its operations to support the reservation of resources at the host level. CR draft NFVIFA(18)000145r2 Status: FEAT Agreed |
IFA005 | February-2018 | Completed |
| 004 | Extend Annex A.2 to introduce physical compute host reservation. CR draft NFVIFA(18)000205 Status: FEAT Agreed |
IFA010 | March-2018 | Completed |
| 005 | Extend clause 6.3.2 Grant VNF Lifecycle Operation operation. CR draft NFVIFA(18)000206r2 Status: FEAT Agreed |
IFA007 | March-2018 | Completed |
| 006 | Enhancements of capacity management due to new functionality of host reservation: - Specify a requirement for the VIM to support NFVI capacity management. - Specify a requirement for the NFVO to support NFVI capacity management. CR drafts: NFVIFA(18)000207r2 (NFVO) Status: FEAT Agreed NFVIFA(18)000208r1 (VIM) Status: FEAT Agreed |
IFA010 | March-2018 | Completed |
| 007 | Specify an interface (IFA005, clause 7.X) and its operations to support Compute Hosts Capacity Management. CR draft NFVIFA(18)000364 Status: FEAT Agreed |
IFA005 | March-2018 | Completed |
| 008 | A new interface and its operations may be needed in IFA013 for notifications from the NFVO related to resource capacity shortage. CR drafts: NFVIFA(18)000365r1 Status: FEAT Agreed NFVIFA(18)000418 Status: Available |
IFA013 | March-2018 | Ongoing |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT05 Network Slicing
Overview
The latest version of NFV EVE Network Slicing Report (EVE012 V3.1.1) can be downloaded at [1].
| Feature Prime | Anatoly Andrianov (Nokia), Cristina Badulescu (Ericsson), Ulrich Kleber (Huawei), Bhumip Khasnabish (ZTE) |
| Feature description | EVE to IFA REL SEC Feature NFVSLICE EVE012 network slicing
Support Network Slicing by defining the necessary requirements and enhancements of interfaces, as discussed in NFV(17)000252. |
| Target Release | Release 3 (2018) |
| Impacted WIs | IFA005, IFA006, IFA010, IFA011, IFA012, IFA013, IFA014, SECxx, RELxx |
| Related/Dependent Features | Some topics depend on: FEAT07 Policy Management FEAT08&09 Multi-Domain |
| Status | Started, < 10% complete |
| Contributions | All feature contributions Agreed content Latest status on Feature Dashboard (check for newer versions) |
| Feature team |
Anatoly Andrianov, Nokia |
| Last Updated | 2018-03-07 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add Functional requirements to support NFVSLICE in IFA010 (e.g. prioritization of virtualised resource management, support of multi-tenancy)
Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA010 is required.
|
IFA010 | Feb-2018 | Started |
| 002 | Identify and add new parameters for NSD to allow support of the network slice and network slice subnet.
Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA014 |
IFA014 | March-2018 | Open |
| 003 | Investigate whether any new parameters in VNFD may be needed.
Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA011 |
IFA011 | March-2018 | Open |
| 004 | Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE lifecycle capabilities which include:
- Determining the requirements on the lifecycle of the Network Service used as part of a Network Slice - Determining the requirements for the lifecycle of the Network Service used as part of a Network Slice Subnet Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA013 |
IFA013 | June-2018 | Open |
| 005 | Investigate whether any new parameters in Os-Ma-Nfvo reference point may be needed to realize NFVSLICE feature capabilities which include:
- Determining the requirements for policy handling for Network Service instance - Determining the requirements for performance and fault data handling - Determining the requirements for LCM handling Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA013 |
IFA013 | June-2018 | Open |
| 006 | Investigate whether any new parameters in Or-Vi reference point may be needed to realize NFVSLICE feature capabilities which include:
- Determining the resource requirements for Network Service instance - Communicating resource prioritization related data Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA005 |
IFA005 | June-2018 | Open |
| 007 | Investigate whether any new parameters in Vnfm-Vi reference point may be needed to realize NFVSLICE feature capabilities which include:
- Determining the resource requirements for VNF/C instances - Communicating resource prioritization related data Note: According to EVE012 further analysis is necessary on whether there is any impact on the IFA006 |
IFA006 | June-2018 | Open |
| 008 | Investigate whether any enhancements are needed for Application and Service Management Interface
and Information Model Specification. |
IFA012 | June-2018 | Open |
| 009 | Investigate whether any Security requirements may be needed to realize the following features:
Note: Affected documents to be discussed with SEC WG |
SEC | Dec-2018 | Open |
| 010 | Reliability requirements to realize the following features:
Note: Affected documents to be discussed with SEC WG |
REL | Dec-2018 | Open |
Other Contributions
- Analyse NGMN Requirements on Slicing: NFVIFA(18)000017r1
- LS to 3GPP SA5 on NFV support for Network Slicing NFV(18)000065r2
Issues
List of issues raised based on the feature implementation.
Security Considerations
see action 009
FEAT06: Enhancement Network Service (NS) Package
Overview
More information and current status can be found on the wiki for FEAT06NSPackage
| Feature Prime | Bhumip Khasnabish (ZTE), Haibin Chu (Ericsson) and Yaoye Zhang (Huawei) |
| Feature description | An NS Package is an archive including the meta-model descriptors NSD and other files (scripts, security materials, possible rules, policies, NS over multi-tenants, etc.), that are required to manage an NS from design to test/verification to validation/certification to runtime management; the holistic end-to-end NS lifecycle, as discussed in NFV(17)000247. |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | IFA010, IFA012 (TBC), IFA013, and IFA014. Note-1: We identify the impacted specifications in IFA WG only. The impacted specifications in other WGs (e.g. SOL, TST, SEC, REL, etc) needs to be addressed separately and the chairs of SOL and TST WGs have been informed. We will follow up the impacts on SEC and REL WGs. Note-2: The impact on IFA012 is dependent on the ISG's decision whether IFA012 is released as GS or GR by the end of Y2017. |
| Related/Dependent Features | FEATxx FEATyy |
| Mega-CRs | IFA010 [not available] IFA012 [not available] IFA013 [not available] IFA014 [not available] |
| New Specification | No new WI is expected in IFA WG. Name of New Specification in SOL WG is to be defined WI Status [WID to be prepared] |
| Status | Ongoing (0% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Bhumip Khasnabish (ZTE) Haibin Chu (Ericsson) Yaoye Zhang (Huawei) Maopeng Zhang (ZTE) Lingli Deng (CMCC) |
| Last Updated | 20xx-xx-xx |
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add use case description of NS packaging to IFA014 Annex. CR draft NFVIFA(17)000956r10 |
IFA014 | Mar.-2018 | Started |
| 002 | Update the NS packaging requirement in IFA014.Add a new clause 5.X to describe the NS packaging requirement, including the NS packaging structure, content, identification, integrity, etc. CR draft NFVIFA(17)000959r8 |
IFA014 | Mar.-2018 | Started |
| 003 | Update the functional requirements on NFVO in IFA010. Add new functional requirements on NFVO about NS package management by either adding a new clause (e.g. 6.6.X) or updating the existing clause (i.e. 6.6.1). CR draft NFVIFA(17)000958r5 |
IFA010 | Apr.-2018 | Started |
| 004 | Update the interface requirement on NSD or NS package management interface in IFA013. Add new requirements of NS package management interface by either adding a new clause (i.e. 5.3.X) or updating the existing clause (i.e. 5.3.1). CR draft NFVIFA(17)000947r2 |
IFA013 | Apr.-2018 | Started |
| 005 | Update the existing NSD management interface or add a new NS Package management interface in IFA013. Add new operations and notifications related to NS package management interface by either adding a new clause (i.e. 7.X) or updating the existing clause (i.e. 7.2). Current PNFD management may be updated as well based on the requirement discussion in action #002. CR draft NFVIFA(17)000947r2 |
IFA013 | Apr.-2018 | Started |
| 006 | Update the NSD management related chapters in IFA012, if the IFA012 is released as GS in Rel.2. CR draft [LINK] |
IFA012 | ???-2018 | Open |
Issues
List of issues raised based on the feature implementation.
•Below technical issues are identified:
->Current PNFD has its own management operations, e.g. On-board PNFD, etc.
->After the concept of NS package enhancement is introduced, the issue of merging them into NS package management operations needs to be addressed.
->The issue of backward compatibility with current NSD management interface needs to be addressed.
•The impacts on SOL and TST WGs have been discussed. While the impacts on SEC and REL WGs need to be discussed.
Security Considerations
List of security considerations implied by the feature.
FEAT07: MANO Policy Management (MANO_PLC)
Overview
| Feature Prime | Haitao Xia (Huawei) |
| Feature description | This feature addresses the interface operation definition when policy management is introduced to NFV-MANO |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | IFA010 IFA013 IFA007 IFA008 IFA005 IFA006 |
| Related/Dependent Features | no dependency |
| Status | Ongoing (80% complete) |
| Contributions | All contributions |
| Feature team | Haitao Xia (Huawei) |
| Last Updated | 2018-05-11 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add functional requirements of policy management for the NFVO, VNFM and VIM Feature agreed CRs: |
IFA010 | Jan-2018 | Completed |
| 002 | Specify a new interface of policy management over Os-Ma-nfvo reference point, including the interface requirements, policy management operations and corresponding information model Feature agreed CRs: |
IFA013 | Mar-2018 | Completed |
| 003 | Derive policy management interface over Nfvo-vnfm, Ve-Vnfm, Nfvo-Vi, Vi-vnfm reference point based on the output of IFA013 interface operation definition Feature agreed CRs: IFA007/008/005/006 Mega CR: |
IFA007 IFA008 IFA005 IFA006 |
May-2018 | Ongoing |
| 004 | Define information model enhancement to the NFV descriptor (e.g., NSD) when necessary Conclusion: Based on the discussion output of NFVIFA(18)000135r1,there is no necessity to introduce policy descriptor to the NSD information model |
IFA014 | Feb-2018 | Completed |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT08: Support of composite NS across multi-domain (MANOMD_NS)
Overview
| Feature Prime | Haitao Xia (Huawei), Arturo Martin de Nicolas (Ericsson) |
| Feature description | This feature addresses the architectural changes needed for the support of composite network services across multiple administrative domains |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | IFA010 IFA030 (new deliverable) |
| Related/Dependent Features | no dependency |
| Status | Ongoing (80% complete) |
| Contributions | All contributions |
| Feature team | Haitao Xia (Huawei) Arturo Martin de Nicolas (Ericsson) |
| Last Updated | 2018-05-11 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Determine the content skeleton and input for introduction Approved contributions: |
IFA030 | Jan-2018 | Completed |
| 002 | Add NFVO functional requirement description derived from Table 6.3-2 of IFA028 to IFA010 Feature agreed contributions: |
IFA010 | May-2018 | Ongoing |
| 003 | Add interface requirement description of Or-Or reference point derived from Table 6.3-1 of IFA028 Approved contributions: |
IFA030 | Apr-2018 | Completed |
| 004 | Define Or-Or interface functions of NSD management, NS LCM, NS PM and NS FM which are derived from IFA013 GS and necessary adaptation is made Approved contributions: |
IFA030 | Apr-2018 | Completed |
| 005 | Define Or-Or interface functions of NS lifecycle granting and NS instance usage notification Approved contributions: |
IFA030 | Apr-2018 | Completed |
| 006 | Develop Or-Or operational flows as informative Annex (when necessary) Conclusion: No operational flows are expected to be included in IFA030 GS: |
IFA030 | Mar-2018 | Completed |
| 007 | New GS (IFA030) clean-up, EN resolution
NFVIFA(18)000441 Status: Available |
IFA030 | May-2018 | Ongoing |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT10: Mgmt & Connectivity Multi-Site Services (MCMSS)
Overview
| Feature Prime |
Hiroshi Dempo |
| Feature description | Following the recommendations written in IFA022, this feature is to specify management requirements, interfaces and information models to support connectivity for Multi-Site Services |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | IFA005, IFA007, IFA010, IFA011, IFA013, IFA014, IFA022, IFA032 |
| Related/Dependent Features | FEATxx FEATyy |
| Status | Ongoing (20% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Hiroshi Dempo (NEC Europe Ltd.) Zarrar Yousaf (NEC Europe Ltd.) |
| Last Updated | 2018-03-22 |
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | - Approve FEAT10 and new WI draft titled “Reference point between NFVO and WIM- Interface and Information Model Specification" | None | Oct-2017 | Done |
| 002 |
- Approve IFA022 as a stable draft
|
IFA022 | Dec-2017 | Done |
| 003 |
- Specify general and functional recommendations for Multi-Site Service
|
IFA010 | Jan/ 2018 | Started |
| 004 |
- Specify Os-Ma-Nfvo reference point interface and information model specification for Multi-Site Service
|
IFA013 | Mar-2018 | Started |
| 005 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and VIM for Multi-Site Service |
IFA005 | Mar-2018 | Open |
| 006 |
- Specify enhancements to Or-Vnfm ref. point interfaces and information model to address the case of VNF multi-site deployment. - Make relevant changes to the scope and overview sections to include the support for Multi-site Service on Or-Vnfm reference point
|
IFA007 | Mar-2018 | Started |
| 007 | - Specify parameters for the VNFD file relevant for the support of Multi-Site Service | IFA011 | May-2018 | Open |
| 008 | - Specify parameters for the NSD file relevant for the support of Multi-Site Service
|
IFA014 | May-2018 | Open |
| 009 |
- Specify Or-Vi reference point interfaces and information model specification between NFVO and WIM for Multi-Site Service
NOTE: As written in ID#2, naming of the ref. point is FFS. Purpose of the specification is to focus on virtualised network resource management subset of existing IFA005, and necessary extensions/enhancements particular to managing resources in the WAN |
IFA032 | May-2018 | Started |
Issues
List of issues raised based on the feature implementation.
- All topics can start from the beginning but the progress needs to be managed on the action IDs (e.g. individual mega CRs and new deliverable basis)
- The target dates are set according to the requirement categories in IFA022 (CRs for general, functional, reference point and information element, descriptor, or new deliverable)
- Discussion for IFA032 may take more time than CRs but finalise before the 1st drop of Release 3.
Security Considerations
List of security considerations implied by the feature.
FEAT11: NFV_M&M (NFV-MANO management)
Overview
| Feature Prime | Yaoye Zhang (Huawei) Joan Triay (DOCOMO) |
| Feature description | Following the recommendations written in IFA021, this feature is to enable the management of the NFV Management and Orchestration functional blocks identified by the NFV Architectural Framework. |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | ETSI GS NFV-IFA 010 |
| Related/Dependent Features | None |
| New Specification | ETSI GS NFV-IFA 031 ("NFV; Management and Orchestration; Requirements and interfaces for NFV-MANO management Specification") |
| Status | Ongoing (80% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Yaoye Zhang (HUAWEI) Joan Triay (DOCOMO) Gerald Kunzmann (DOCOMO) |
| Last Updated | 2018-05-15 |
Implementation Plan
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Specify high-level requirement for the NFV Architectural Framework to support the management of NFV-MANO functional entities. CR draft: - NFVIFA(17)0001065 status: FEAT AGREED at IFA#79 |
IFA010 | Nov-2017 | Completed |
| 002 | Specify a requirement set for the NFVO, the VNFM, as well as the VIM as a managed entity to support NFV-MANO fault, performance, configuration and information, state and log management by a managing entity. CR draft: - NFVIFA(17)0001066 status: FEAT AGREED at IFA#79 |
IFA010 | Nov-2017 | Completed |
| 003 | Skeleton, scope and introduction description for the new deliverable. Contributions: - Skeleton overview/draft: NFVIFA(17)0001067r1 Status: for discussion and NOTED - Skeleton: NFVIFA(18)000009r1 Status: APPROVED at IFA#83 - Scope: NFVIFA(18)000046 status: APPROVED at IFA#84 |
IFA031 | Nov-2017 | Completed |
| 004 | Add description of the general framework and interfaces for NFV-MANO management using as a reference “Solution D” and “Solution E” descriptions available in clauses 7.1.4 and 7.1.5 of ETSI GR NFV-IFA 021. Contributions: - NFVIFA(17)0001068 status: APPROVED at IFA#79 - Relationship NFV-MANO services and interfaces: NFVIFA(18)000351 status: APPROVED at IFA#100 |
IFA031 | Nov-2017 | Completed |
| 005 | Specify a requirement set for the different interfaces to be supported, which include: - NFV-MANO fault management interface - NFV-MANO performance management interface - NFV-MANO configuration and information management interface - NFV-MANO state management interface, and - NFV-MANO log management interface. Contributions: - Requirement set: NFVIFA(17)0001069 Status: APPROVED at IFA#79 - Overview and conventions: NFVIFA(18)000085 Status: APPROVED at IFA#87 |
IFA031 | Dec-2017 | Completed |
| 006 | Specify the NFV-MANO functional entity information elements that will be reused in multiple interface definitions using as a reference the “Solution A” description available in clause 7.1.1 of ETSI GR NFV-IFA 021. Contributions: - For configuration and information mgmt: NFVIFA(18)000015r4 Status: APPROVED at IFA#84 - For performance mgmt: NFVIFA(18)000047r1 Status: APPROVED at IFA#84 - For state mgmt: NFVIFA(18)000086r3 Status: APPROVED at IFA#89 - For fault mgmt: NFVIFA(18)000215r2 Status: APPROVED at IFA#93 - For log mgmt: NFVIFA(18)000219r3 Status: APPROVED at IFA#98 |
IFA031 | Dec-2017 | Completed |
| 007 | Specify the interface for NFV-MANO configuration management using as a reference the “Solution F” description in clause 7.1.6.5 of ETSI GR NFV-IFA 021. Contributions: - Configuration I/F and related IE: NFVIFA(18)000015r4 Status: APPROVED at IFA#84 |
IFA031 | Jan-2018 | Completed |
| 008 | Specify the interface for NFV-MANO performance management using as a reference the “Solution F” description available in clause 7.1.6.4 of ETSI GR NFV-IFA 021. Contributions: - Performance I/F and related IE: NFVIFA(18)000047r1 Status: APPROVED at IFA#84 |
IFA031 | Jan-2018 | Completed |
| 009 | Specify the interface for NFV-MANO fault management using as a reference the “Solution F” description available in clause 7.1.6.3 and the fault reporting information modelling in “Solution B” in clause 7.1.2 of ETSI GR NFV-IFA 021. Contributions: -Fault I/F and related IE: NFVIFA(18)000215r2 Status: APPROVED at IFA#93 |
IFA031 | Feb-2018 | Completed |
| 010 | Specify the interface for NFV-MANO state management using as a reference the “Solution F” description available in clause 7.1.6.6. Contributions: - State I/F and related IE: NFVIFA(18)000086r3 Status: APPROVED at IFA#89 |
IFA031 | Feb-2018 | Completed |
| 011 | Specify the interface for NFV-MANO log management using as a reference the “Solution F” description available in clause 7.1.6.7. Contributions - Log I/F and related IE: NFVIFA(18)000219r3 Status: APPROVED at IFA#98 |
IFA031 | Mar-2018 | Completed |
| 012 | Specify the definitions of performance metrics using as a reference the “Solution C” description available in clause 7.1.3 of ETSI GR NFV-IFA 021. Contributions: - Performance measurement definitions template: NFVIFA(18)000225r2 Status: APPROVED at IFA#94 - Measured objects: NFVIFA(18)000226r1 Status: APPROVED at IFA#94 - NFV-MANO entity resource measurements: NFVIFA(18)000227r1 Status: APPROVED at IFA#94 - Managed objects for performance measurements: NFVIFA(18)000292 Status: APPROVED at IFA#96 - NFV-MANO service measurements: NFVIFA(18)000293 Status: APPROVED at IFA#96 - NFV-MANO interface producer measurements: NFVIFA(18)000294r3 Status: APPROVED at IFA#98 - NFV-MANO interface consumer measurements: NFVIFA(18)000295r3 Status: APPROVED at IFA#98 - Additional managed objects: NFVIFA(18)000350r1 Status: APPROVED at IFA#100 - ... |
IFA031 | Mar-2018 | Completed |
| 013 | Resolution of editor's notes and final review of the document draft. Contributions: - Clause 7 EN resolution dependency state information: NFVIFA(18)000405 Status: APPROVED at IFA#100 - Clause 7 EN resolution MANO configuration: NFVIFA(18)000406 Status: Open - Clause 7 EN resolution MANO configuration information element: NFVIFA(18)000406r1 Status: Open - Clause 7 EN resolution list of interfaces: NFVIFA(18)000434 Status: Open - Clause 6, 7, and 8 EN resolution on PmJob and Threshold Objects: NFVIFA(18)000436 Status: Open - Clause 8.2 adding ManoInterfaceConsumer measured object NFVIFA(18)000437r1 Status: Open - Clause 8 EN resolution PM description improvements: NFVIFA(18)000438 Status: Open - Adding Annex for information flows with flow related to configuration: NFVIFA(18)000449 Status: Open |
IFA031 | May-2018 | Started |
| 014 | Review of security aspects. Security-related editor's notes are available throughout the IFA031 GS draft. The contributions needed to resolve those editor's notes which are specific to security topics will be listed here. Contributions: - ... |
IFA031 | Jun-2018 | Not started |
Word version of the implementation plan in contribution NFVIFA(17)000897r1 (check for latest revision). It is very likely that the information contained in this wiki is more recent and updated more frequently.
Issues
List of issues raised based on the feature implementation.
With regards to specific planning action:
- Action 004: description is deemed complete, but needs to be checked with some additional clarification or references to possible informative flows are needed.
- Action 007: main content is available and approved, but some editor's notes need to be resolved (see action 013).
- Action 008: main content is available and approved, but some editor's notes need to be resolved (see action 013).
- Action 010: main content is available and approved, but some editor's notes need to be resolved (see action 013).
- Action 004/006/008/010/011: need to analyze and define the relationship of NFV-MANO Service and interfaces.
- Action 009: main content is available and approved, but some editor's notes need to be resolved (see action 013).
- Action 009: the "heartbeat" functionality was deleted in the approved FM interface and IE contribution (see NFVIFA(18)000215r2). It needs to be resolved how the heartbeat functionality relates to fault management, or whether it needs a specific interface for it.
- Action 011: main content is available and approved, but some editor's notes need to be resolved (see action 013).
- Action 012: main content is available and approved, but some editor's notes need to be resolved (see action 013).
Other issues:
- (Jan. 2018) At IFA#84 F2F meeting: discussed the possibility of having some informative information flows to show examples on how the interfaces can be used. An Annex could be added.
Security Considerations
List of security considerations implied by the feature.
- As captured in some editor's notes in clause 6: Editor’s Note: actors in the operations are “consumer” and “NFV-MANO functional entity”. The consumer is intended to be an authorized consumer, thus, not all possible consumers may be authorized to access all operations. Further description and analysis about this is expected to be part of the “Security Considerations” clause.
- Action 014 (added in May 2018) to list specific security related contributions.
FEAT15: VNF Snapshotting
Overview
| Feature Prime | Jörg Aelken (Ericsson LM) |
| Feature description | The VNF_PHOTO is a feature that has been investigated and described in the published ETSI GR NFV-TST 005. A VNF Snapshot is a replication of a VNF instance at a specific point in time with a corresponding VNF Snapshot Package which is collection of files representing a VNF Snapshot. The feature implementation enables operations on and management of VNF Snapshots and their corresponding packages. |
| Target Release | Release 3 drop 1 (2018-06) |
| Impacted WIs | IFA005, IFA006, IFA007, IFA008, IFA010, IFA011, IFA013 |
| Related/Dependent Features | N/A |
| Mega-CRs | IFA005 [not available] IFA006 [not available] IFA007 [not available] IFA008 [not available] IFA010 [not available] IFA011 [not available] IFA013 [not available] |
| New Specification | Not required |
| Status | In Progress 65% completed |
| Contributions | All feature contributions Agreed content |
| Feature team | Bertrand Souville (DOCOMO) Gerald Kunzmann (DOCOMO) Jörg Aelken (Ericsson LM) |
| Last Updated | 2018-05-17 |
Implementation Plan
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add functional requirements on the NFVO (IFA010 6.2.x) to support granting for VNF/VNFC Snapshot operations, based on Clause 7.2.1 in TST005 (recommendation Nfvo.001). CR draft NFVIFA(17)0001010r1 Status: feature agreed |
IFA010 | November-2017 | Completed |
| 002 | Add functional requirements on the VNFM (IFA010 7.x) to support VNF/VNFC Snapshot operations and VNF/VNFC Snapshot Packaging, based on Clause 7.2.2 in TST005 (recommendations Vnfm.001 to Vnfm.009). CR draft NFVIFA(17)0001021r2 Status: feature agreed |
IFA010 | November-2017 | Completed |
| 003 | Add functional requirements on the VIM (IFA010 8.x) to support virtualized resource Snapshot capabilities based on Clause 7.2.3 in TST005 (recommendations Vim.001 and Vim.002). CR draft NFVIFA(17)0001032r4 Status: feature agreed |
IFA010 | November-2017 | Completed |
| 004 | Add requirement on Virtualised Resources Management interface on the Or-Vi reference point (IFA005 clause 5.3.5) to support attaching/detaching Volumes to virtualized compute resources, based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.001 and OrVi-Vcrm.002). CR draft NFVIFA(18)000030 Status: feature agreed |
IFA005 | December-2017 | Completed |
| 005 | Add new operation for attaching/detaching Volumes, including new information elements, to Virtualized Compute Resources Management interface (IFA005 clause 7.3.1.x), based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.001 and OrVi-Vcrm.002). CR draft NFVIFA(18)000031r1 Status: feature agreed |
IFA005 | December-2017 | Completed |
| 006 | Add values to the computeOperation parameter descriptions of the OperateComputeRequest and OperateComputeResponse of the Virtualized Compute Management interface (IFA005 clause 7.3.1.6) to support quiescing/unquiescing and reverting to Snapshot virtualised compute resources, based on Clause 7.5.2 in TST005 (recommendations OrVi-Vcrm.003 to OrVi-Vcrm.005). CR draft NFVIFA(17)0001082 Status: feature agreed |
IFA005 | December-2017 | Completed |
| 007 | Add value to the storageOperation parameter description of the OperateStorageRequest of the Virtualized Storage Management interface IFA005 clause 7.5.1.6.2) to support reverting to Snapshot virtualised storage resources, based on Clause 7.5.2 in TST005 (recommendation OrVi-Vsrm.001). CR draft NFVIFA(17)0001083 Status: feature agreed |
IFA005 | December-2017 | Completed |
| 008 | Mirror requirements from IFA005 towards IFA006, i.e. - Add requirement on Virtualised Resources Management interfaces on the Vi-Vnfm reference point (IFA006 clause 5.3.3) to support attaching/detaching Volumes to virtualized compute resources, based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.001 and ViVnfm-Vcrm.002). CR draft NFVIFA(18)000033 Status: feature agreed - Add new operation for attaching/detaching Volumes, including information elements, to Virtualized Compute Resources Management interface (IFA006 clause 7.3.1.x), based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.001 and ViVnfm-Vcrm.002). CR draft NFVIFA(18)000035r1 Status: feature agreed - Add values to the computeOperation parameter descriptions of the OperateComputeRequest and OperateComputeResponse of the Virtualized Compute Management interface (IFA006 clause 7.3.1.6) to support quiescing/unquiescing and reverting to Snapshot virtualised compute resources, based on Clause 7.5.1 in TST005 (recommendations ViVnfm-Vcrm.003 to ViVnfm-Vcrm.005). CR draft NFVIFA(17)0001084 Status: feature agreed - Add value to the storageOperation parameter description of the OperateStorageRequest of the Virtualized Storage Management interface (IFA006 clause 7.5.1.6.2) to support reverting to Snapshot virtualised storage resources, based on Clause 7.5.1 in TST005 (recommendation ViVnfm-Vsrm.001). CR draft NFVIFA(17)0001085 Status: feature agreed |
IFA006 | December-2017 | Completed |
| 009 | Add a requirement on the Or-Vnfm reference point (IFA007 clause 5.2) to support a Snapshot Package Management interface produced by the VNFM, based on Clause 7.5.3 in TST005 (recommendation Or-Vnfm.001) and Clause 7.5.4 in TST005 (recommendation OrVnfm-Vspm.001). CR draft NFVIFA(18)000006r2 Status: feature agreed |
IFA007 | January-2018 | Completed |
| 010 | Add requirements on a new Snapshot Package Management interface on the Or-Vnfm reference point (IFA007 clause 5.3.x) to support VNF Snapshot Package operations, based on Clause 7.5.4 in TST005 (recommendations OrVnfm-Vspm.002 to OrVnfm-Vspm.005). CR draft NFVIFA(18)000007r3 Status: feature agreed |
IFA007 | January-2018 | Completed |
| 011 | Add new Snapshot Package Management interface specification (IFA007 clause 7.x) to support VNF Snapshot Package operations, based on Clause 7.5.4 in TST005 (recommendations OrVnfm-Vspm.002 to OrVnfm-Vspm.005). CR draft NFVIFA(18)000008r14 Status: available |
IFA007 | January-2018 | Ongoing |
| 012 | Add a requirement on the Ve-Vnfm-vnf reference point (IFA008 clause 5.3.0) to support a VNF Snapshot Notification interface produced by the VNFM, based on Clause 7.5.5 in TST005 (recommendation Ve-Vnfm-vnf.001) and Clause 7.5.6 in TST005 (recommendation VeVnfmvnf-Vsn.001). Status: Not needed according to alternative solution (see note) |
IFA008 | January-2018 | Not needed |
| 013 | Add requirements on the Ve-Vnfm-em and Ve-Vnfm-vnf reference points (IFA008 clause 5.2.1.1 and 5.3.1.1) to support receiving confirmations upon sent VNF lifecycle management operation occurrence notifications related to VNF Snapshots to enable the continuation or abortion of a VNF Snapshot operation after required modifications in the VNF triggered by the notification. This solution was preferred over and replaces the original intended solution of adding requirements on a new VNF Snapshot Notification interface on the Ve-Vnfm-vnf reference point (IFA008 clause 5.3.1.x) to support VNF Snapshot notifications, based on Clause 7.5.6 in TST005 (recommendations VeVnfmvnf-Vsn.002 and VeVnfmvnf-Vsn.003). (see note) CR draft NFVIFA(18)000012 Status: feature agreed |
IFA008 | January-2018 | Completed |
| 014 | Add specifications on the VNF Lifecycle Management interface (IFA008 clause 7.2.x) to receive confirmations upon sent VNF lifecycle management operation occurrence notifications related to VNF Snapshot to enable the continuation or abortion of a VNF Snapshot operation after required modifications in the VNF triggered by the notification. This solution was preferred over and replaces the original intended solution of adding a new VNF Snapshot Notification interface specification (IFA008 clause 7.x) to support VNF Snapshot notifications, based on Clause 7.5.6 in TST005 (recommendations VeVnfmvnf-Vsn.002 and VeVnfmvnf-Vsn.003). (see note) CR draft NFVIFA(18)000013 Status: feature agreed |
IFA008 | January-2018 | Completed |
| 015 | Add requirements on VNF Lifecycle Management interface on the Ve-Vnfm-em reference point (IFA008 clause 5.2.1.1) to support querying/deleting available VNF/VNFC Snapshot information and to support create/revert to VNF/VNFC Snapshot operations, based on Clause 7.5.7 in TST005 (recommendations VeVnfmem-Vlm.001 and VeVnfmem-Vlm.002). CR draft NFVIFA(18)000070r1 Status: feature agreed |
IFA008 | January-2018 | Completed |
| 016 | Add new operations for querying/deleting information on available VNF/VNFC Snapshots and creating/reverting to VNF/VNFC Snapshots, including information elements, to VNF Lifecycle Management interface (IFA008 clause 7.2.x), based on Clause 7.5.7 in TST005 (recommendations VeVnfmem-Vlm.001 and VeVnfmem-Vlm.002). CR draft NFVIFA(18)000071r2 Status: feature agreed |
IFA008 | January-2018 | Completed |
| 017 | Add requirements on NS Lifecycle Management interface on the Os-Ma-Nfvo reference point (IFA013 clause 5.3.2) to support querying/deleting available VNF/VNFC Snapshot information and to support create/revert to VNF/VNFC Snapshot operations, based on Clause 7.5.8 in TST005 (recommendations OsMaNfvo-Nslm.001 and OsMaNfvo-Nslm.002). CR draft NFVIFA(18)000230r3 Status: feature agreed |
IFA013 | February-2018 | Completed |
| 018 | Add new values to the updateType for deleting VNF Snapshot information and for creating/reverting to VNF Snapshots and new parameters, including information elements, to the Update NS operation of the NS Lifecycle Management interface (IFA013 clause 7.3.5), based on Clause 7.5.8 in TST005 (recommendations OsMaNfvo-Nslm.001 and OsMaNfvo-Nslm.002). CR draft NFVIFA(18)000231r5 Status: feature agreed |
IFA013 | February-2018 | Completed |
| 019 | Add Opconfig Information Elements to enable the configuration of LCM snapshot operations (IFA011 clause 7.1.5). CR draft NFVIFA(18)000457 Status: feature agreed |
IFA011 | March-2018 | Completed |
| 020 | Add new events to the LifeCycleManagementScript related to VFN Snapshotting (IFA011 clause 7.1.13). CR draft NFVIFA(18)000458r1 Status: feature agreed |
IFA011 | March-2018 | Completed |
| 021 | Add a new attribute to the Vdu information element (IFA011 clause 7.1.6.2.2) with a content of a new information element for VNFC Snapshot descriptor. CR draft [LINK to be added later] |
IFA011 | March-2018 | Open |
| 022 | Add the specification of a new information element for a VNFC Snapshot descriptor (IFA011 clause 7.1.6.x), based on Clause 7.3 in TST005 (recommendations Vnfsd.005 to Vnfsd.016). CR draft [LINK to be added later] |
IFA011 | March-2018 | Open |
| 023 | Mirror VNF lifecycle management interface extensions for Snapshots from IFA008 to IFA007: - Add requirements on VNF Lifecycle Management interface on the Or-Vnfm reference point (IFA007 clause 5.3.4) to support querying/deleting available VNF Snapshot information and to support create/revert to VNF Snapshot operations. CR draft NFVIFA(18)000126r1 Status: feature agreed - Add new operations for querying/deleting information on available VNF Snapshots and creating/reverting to VNF Snapshot, including information elements, to VNF Lifecycle Management interface (IFA007 clause 7.2.x). CR draft NFVIFA(18)000127r3 Status: feature agreed |
IFA007 | February-2018 | Completed |
| 024 | Extend the Grant VNF Lifecycle Operation operation of the VNF Lifecycle Operation Granting interface (IFA007 clause 6.3.2) to support granting of VNF Snapshot operations. CR draft NFVIFA(18)000144 Status: feature agreed |
IFA007 | February-2018 | Completed |
| 025 | Mirror VNF Snapshot Package Management interface specifications from IFA007 to IFA013: - Add a requirement on the Os-Ma-nfvo reference point (IFA013 clause 5.2) to support a VNF Snapshot Package Management interface produced by the NFVO. CR draft NFVIFA(18)000130r2 Status: feature agreed - Add requirements on a new Snapshot Package Management interface on the Os-Ma-nfvo reference point (IFA013 clause 5.3.x) to support VNF Snapshot Package operations. CR draft NFVIFA(18)000131r3 Status: feature agreed - Add new Snapshot Package Management interface specification (IFA013 clause 7.x) to support VNF Snapshot Package operations. CR draft NFVIFA(18)000132r7 Status: available |
IFA013 | February-2018 | Ongoing |
| 026 | Mirror trigger conditions for VnfLcmOperationOccurrenceNotification from IFA008 to IFA007: - Add trigger conditions for VnfLcmOperationOccurrenceNotification for create and revert-to VNF Snapshots to information elements and notifications related to VNF Lifecycle Changes (IFA007 clause 8.6.2.2). CR draft NFVIFA(18)000281 Status: feature agreed |
IFA007 | April-2018 | Completed |
| 027 | Add description on filters and attributes for VNF Snapshot information, including information elements, to the Query NS operation of the NS Lifecycle Management interface (IFA013 clauses 7.3.6 and 8.3.3). CR draft NFVIFA(18)000284r1 Status: feature agreed |
IFA013 | April-2018 | Completed |
| 028 | Add support of a VNFC Snapshot Package Management interface to Ve-Vnfm-em reference point: - Add requirements on a new VNFC Snapshot Package Management interface on the Ve-Vnfm-em reference point (IFA008 clause 5.2.x). CR draft NFVIFA(18)000424 Status: feature agreed - Add specification of the VNFC Snapshot Package Management interface on the Ve-Vnfm-em reference point (IFA008 clauses 7.X, 9.Y). CR draft NFVIFA(18)000460 Status: available |
IFA008 | May-2018 | Ongoing |
| 029 | Add support for requesting transfer of VNF Snapshot Package image artefacts from the NFVO towards the VIM. CR draft [tbd] Status: not available |
IFA007 | May-2018 | Open |
| 030 | Add support for granting of VNF Snapshot Package operations. CR draft [tbd] Status: not available |
IFA013 | May-2018 | Open |
| NOTE: An alternative solution for a VNF Snapshot Notification Interface in IFA008 could be to add a new VNF Snapshot notification type to the VNF LCM interface. The final solution will be developed when working on the items for IFA008. After investigation of the alternative, it was decided to implement this alternative by re-using the VNF lifecycle notification interface and adding an operation to enable the VNF/EM to confirm the received notification concerning VNF snapshotting. | ||||
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT16: Service Availability Level
Overview
| Feature Prime | Stefan Arntzen, Huawei. |
| Feature description | Short description of the feature |
| Target Release | Release 3 drop 1 (2018-X-X) |
| Impacted WIs | IFA007 (not approved) IFA008 (not approved) |
| Related/Dependent Features | FEATxx FEATyy |
| Status | Ongoing (5% complete) |
| Contributions | All feature contributions Agreed content |
| Feature team | Shaoji Ni (Huawei) Stefan Arntzen (Huawei) |
| Last Updated | 2018-02-07 |
Implementation Plan
Items to consider in the implementation plan
- Detailed description what has to be done in which work item.
- Timeplan of when the team plans to conclude a particular action in the implementation plan.
| ID | Action | Impacted WG(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Add terminology of the “service availability level (SAL)” and the description of the mapping between the “SAL” and service availability and reliability requirements. | IFA010 | December-2017 | Open |
| 001 | Specify requirements for the VIM to support the capability for supporting SAL for the assignment/reservation of resources. Specify requirements for the NFVO/VNFM to support SAL for requesting the assignment/reservation of resources. | IFA010 | December-2017 | Open |
| 001 | Specify requirements for an NFVI resource management on the Or-Vi/Vi-Vnfm to support SAL for the assignment/reservation of resources. | IFA005/006 | December-2017 | Open |
| 001 | Add the parameter of SAL into “VnfDF”, “vdu profile”, “VirtualLinkDescFlavour” of VNFD | IFA011 | February-2018 | Open |
| 001 | Add a requirement and the parameter of SAL into “Network service deployment flavour” of NSD | IFA014 | February-2018 | Open |
| 001 | Specify operations of the assignment/reservation of resources in Or-Vi/Vi-Vnfm interfaces to support SAL by adding the parameter of “SAL” into the Virtual resource assignment/reservation requests | IFA005/006 | June-2018 | Open |
Issues
List of issues raised based on the feature implementation.
Security Considerations
List of security considerations implied by the feature.
FEAT17: Cloud-Native VNF and NFV Architecture PaaS
Overview
| Feature Prime | Jörg Aelken (Ericsson LM) Ulrich Kleber (Huawei Technologies Co.,Ltd) |
| Feature description | The VNFCLOUD feature is currently being specified in ETSI GS NFV-EVE 011, the NFVPAAS feature is currently being studied in ETSI GR NFV-IFA 029. The VNFCLOUD will implement mechanisms for the life-cycle management of NFV Micro-Services while NFVPAAS will enhance the NFV architecture to support identified PaaS-like capabilities and cloud-native design principles for VNFs. |
| Target Release | Release 3 drop 2 |
| Impacted WIs | IFA007, IFA008, IFA010, IFA011, IFA029 further impacts expected, but to be defined |
| Related/Dependent Features | FEATxx FEATyy |
| New Specification | Name of New Specification to be defined WI Status [WID to be prepared] |
| Status | Pending 0% completed |
| Feature team | Ulrich Kleber (Huawei Technologies Co.,Ltd) Jörg Aelken (Ericsson LM) |
| Last Updated | 2017-12-12 |
Implementation Plan
| ID | Action | Impacted WI(s) | Target completion | Status |
|---|---|---|---|---|
| 001 | Analyse EVE011 for potential architectural enhancements and include them in IFA029. | IFA029 | February-2018 | Open |
| 002 | Update feature implementation request for VNFCLOUD if necessary and create feature implementation request for NFVPAAS. Implementation request NFV(17)000276 |
N/A | March-2018 | Open |
| 003 | Prepare detailed feature implementation plan. Feature implementation plan [LINK to be added later] |
N/A | March-2018 | Open |
| 004 | New potential work item approved (if applicable) | N/A | April-2018 | Open |
Issues
Background Information
According to its latest definition, the ETSI NFV Release 3 includes objectives:
- To specify requirements and enhancements to NFV Architectural Framework to support PaaS features.
- To specify non-functional parameters to classify and characterize VNF cloud-native implementations.
They are reflected in the following two features and corresponding work items:
| Feature ID | Title | Work Item |
|---|---|---|
| R03.F19 | NFV Architecture PaaS (NFVPAAS) | IFA029 |
| R03.F20 | Cloud-Native VNF (VNFCLOUD) | EVE011 |
During the work on the two work items it was discovered that both features are very much related and the envisioned solutions and implementations might overlap and will target the same impacted work items.
During discussions in IFA#73 it was further identified that EVE011, even though it is normative, should be considered as stage 1 requirements on cloud-native on a high abstraction level without taking the actual implementation into consideration. It was further identified in this meeting that IFA029 as a GR looks at architectural aspects of both Cloud Native and PaaS.
Feature implementation approach
This feature implementation plan proposes to implement both features, VNFCLOUD and NFVPAAS, together. It is proposed to delay the feature implementation and aim for ETSI NFV Release 3 drop 2 with the following approach:
- Finalize EVE011 and get it approved
- Analyze EVE011 for potential architectural impacts and evolve them in IFA029
- Get IFA029 in a stable stage
- Implement both features based on recommendations from IFA029 and recommendations from EVE011 which could be directly implemented
Security Considerations
List of security considerations implied by the feature.