ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
Network Functions Virtualisation (NFV) Release 3; Protocols and Data Models; VNF Snapshot Package specification
Network Functions Virtualisation (NFV) Release 3; Protocols and Data Models; VNF Snapshot Package specification
DGS/NFV-SOL010ed331
General Information
Standards Content (Sample)
ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
GROUP SPECIFICATION
Network Functions Virtualisation (NFV) Release 3;
Protocols and Data Models;
VNF Snapshot Package specification
Disclaimer
The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.
---------------------- Page: 1 ----------------------
2 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
Reference
DGS/NFV-SOL010ed331
Keywords
data, model, NFV, protocol, stage 3, virtualisation
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 VNF Snapshot Package . 6
4.1 VNF Snapshot Package format . 6
4.2 VNF Snapshot Package file contents and structure . 7
4.2.1 General . 7
4.2.2 VNF Snapshot Package manifest file. 7
4.2.3 VNF Snapshot Record in the VNF Snapshot Package . 9
5 Adding security to VNF Snapshot Package . 9
5.1 VNF Snapshot Package authenticity and integrity . 9
5.2 Certificate files in the VNF Snapshot Package. 10
5.3 Conventions in the manifest file . 11
5.4 Signature of individual artifacts . 11
Annex A (informative): VNF Snapshot Package Examples . 12
A.1 Basic VNF Snapshot Package example . 12
A.2 VNF Snapshot Package example including VNFD . 12
Annex B (informative): Change History . 13
History . 15
ETSI
---------------------- Page: 3 ----------------------
4 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Network Functions
Virtualisation (NFV).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 4 ----------------------
5 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
1 Scope
The present document specifies the structure and format of a VNF Snapshot Package file and of the artifacts it contains,
fulfilling the requirements specified in ETSI GS NFV IFA 011 [1] for a VNF Snapshot Package, to be used within a
NFV-MANO administrative domain or where all artifacts are managed by the same security domain within the network.
The present document does not support using a VNF Snapshot Package across different NFV-MANO administrative
domains or where artifacts are managed by different security domains within the network.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI GS NFV-IFA 011: "Network Functions Virtualisation (NFV) Release 3; Management and
Orchestration; VNF Descriptor and Packaging Specification".
[2] IETF RFC 3339 (July 2002): "Date and Time on the Internet: Timestamps".
[3] ETSI GS NFV-SOL 005: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point".
[4] ISO/IEC 21320-1 (2015): "Information Technology -- Document Container File -- Part 1: Core".
[5] ETSI GS NFV-SOL 004: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; VNF Package and PNFD Archive specification".
[6] Recommendation ITU-T X.509: "Information technology - Open Systems Interconnection - The
Directory: Public-key and attribute certificate frameworks".
[7] IETF RFC 5652 (September 2009): "Cryptographic Message Syntax (CMS)".
[8] IETF RFC 2315 (March 1998): "PKCS #7: Cryptographic Message Syntax Version 1.5".
[9] ETSI GS NFV-SOL 003: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; RESTful protocols specification for the Or-Vnfm Reference Point".
ETSI
---------------------- Page: 5 ----------------------
6 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI GS NFV 003: "Network Functions Virtualisation (NFV); Terminology for Main Concepts in
NFV".
[i.2] ETSI GS NFV-SOL 001: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; NFV descriptors based on TOSCA specification".
[i.3] ETSI GS NFV-SOL 006: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; NFV descriptors based on YANG specification".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GS NFV 003 [i.1] and the following apply:
NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in
ETSI GS NFV 003 [i.1].
VNF Snapshot Package provider: creator of the VNF Snapshot Package
NOTE: The NFVO is a VNF Snapshot Package provider as producer of the VNF Snapshot Package management
interface specified in ETSI GS NFV-SOL 005 [3].
VNF Snapshot Record: file that contains runtime information representing a VNF instance at the time when the
snapshot is taken
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS NFV 003 [i.1] and the following apply:
TOSCA Topology and Orchestration Specification for Cloud Applications
VNFSR VNF Snapshot Record
YAML YAML Ain't Markup Language
4 VNF Snapshot Package
4.1 VNF Snapshot Package format
The VNF Snapshot Package shall be a ZIP archive file whose format shall conform to ISO/IEC 21320-1 [4]. In the rest
of the present document, this file is referred to as the "VNF Snapshot Package file".
ETSI
---------------------- Page: 6 ----------------------
7 ETSI GS NFV-SOL 010 V3.3.1 (2020-12)
4.2 VNF Snapshot Package file contents and structure
4.2.1 General
A VNF Snapshot Package shall contain:
• a VNF Snapshot Record (VNFSR) file;
• and additional files.
A VNF Snapshot Package may contain:
• The VNFD corresponding to the snapshotted VNF.
If a VNFD is present in the VNF Snapshot Package, the VNFD file shall be a ZIP archive file as specified in
clause 10.4.4 of ETSI GS NFV-SOL 003 [9]. It shall be an exact copy of the VNFD in the VNF Package from which
the snapshotted VNF was instantiated and be located at the root of the VNF Snapshot Package file. That copy can be
used for troubleshooting by entities external to NFV-MANO. The VNFD in the VNF Snapshot Package is not intended
to be used by NFV-MANO entities, e.g. for VNF snapshot reversal.
NOTE 1: ETSI GS NFV-SOL 001 [i.2] specifies the structure and format of the VNFD based on TOSCA
specifications.
NOTE 2: ETSI GS NFV-SOL 006 [i.3] specifies the structure and format of the VNFD based on YANG
specifications.
Examples of a VNF Snapshot Package file are described in annex A.
4.2.2 VNF Snapshot Package manifest file
A VNF Snapshot Package shall contain a manifest file located at the root of the VNF Snapshot Package file. The name
and extension of the manifest file shall be "manifest.mf". The name and extension are case-insensitive.
The manifest file shall start with the VNF Snapshot Package metadata in the form of name-value pairs. Each pair shall
appear on a different line. The "name" and the "value" shall be separated by a colon and, optionally, one or more
blanks. The order of the name-value pairs is not significant.
The name shall be one of those specified in table 4.2.2-1 and the values shall comply with the provisions specified in
table 4.2.2-1. All of these pairs in table 4.2.2-1 shall be in the manifest file.
ETSI
-----------------
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.