 |
Work Item Reference | Type | STF | Technical Body in Charge |
Standard Not Ready For Download |
||
| PWI_NFV_1815_v2 | GS | NFV | |||||
| Current Status (Click to View Full Schedule) |
Latest Version |
Cover Date | Standstill | Creation Date | |||
|
|
View Standstill Information | 2018-11-27 | |||||
| Rapporteur | Technical Officer | Harmonised Standard | |||||
Marcus Brunner
|
Laurent Vreck
|
No | |||||
| Title |
Network Functions Virtualisation (NFV) Management and Orchestration Continuous Software Delivery and Feedback Interface Continuous Software Delivery and Feedback Interface |
||||||
|
Scope and Field of Application |
For more agile setups, the best common practice is to use continuous integration and deployment methodologies. The background and methodology and what that means for NFV is discussed in GR TST006. One sub-feature required is that software is continuously delivered and installed in the appropriate infrastructure including the test, pre-production, or production environments. The second sub-feature in scope is the feedback on failed tests, performance data, and logs in order for the software developer to fix and improve the software. The specification relies on other features in NFV including the software modification (FEAT02 and FEAT03) and some future sub-features derived from TST006 including automated testing of VNFs etc. |
||||||
|
Supporting Organizations |
SWISSCOM | ||||||
