1、American National StandardDeveloped byfor Information Technology Open Virtualization Format(OVF) SpecificationINCITS 469-2015INCITS 469-2015INCITS 469-2015Revision ofINCITS 469-2010American National Standardfor Information Technology Open Virtualization Format(OVF) SpecificationSecretariatInformatio
2、n Technology Industry CouncilApproved October 30, 2015American National Standards Institute, Inc.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is est
3、ablished when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be co
4、nsidered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, proc
5、esses, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an America
6、n National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The
7、procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.Ame
8、rican National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2015 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or other
9、wise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to
10、the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the impl
11、ementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.i CONTENTS Fore
12、wordiv 1 Scope 1 2 Normative references 1 3 Terms and definitions 3 4 Symbols and abbreviated terms 5 5 OVF package 5 5.1 OVF package structure . 5 5.2 Virtual disk formats . 6 5.3 OVF package options . 7 5.4 Distribution as a set of files . 7 6 OVF descriptor 7 7 Envelope element 8 7.1 File referen
13、ces 8 7.2 Content element 9 7.3 Extensibility . 10 7.4 Conformance 10 8 Virtual hardware description 11 8.1 VirtualHardwareSection 11 8.2 Extensibility . 12 8.3 Virtual hardware elements 12 8.4 Ranges on elements . 14 9 Core metadata sections 16 9.1 DiskSection . 17 9.2 NetworkSection . 18 9.3 Resou
14、rceAllocationSection . 18 9.4 AnnotationSection . 19 9.5 ProductSection 19 9.5.1 Property elements 20 9.6 EulaSection . 22 9.7 StartupSection 22 9.8 DeploymentOptionSection 23 9.9 OperatingSystemSection 24 9.10 InstallSection . 24 9.11 EnvironmentFilesSection 25 9.12 BootDeviceSection 25 9.13 Shared
15、DiskSection . 26 9.14 ScaleOutSection . 26 9.15 PlacementGroupSection and PlacementSection 27 9.16 EncryptionSection . 29 10 Internationalization 30 10.1 Internal resource bundles . 31 10.2 External resource bundles 31 10.3 Message content in external file . 31 11 OVF environment and OVF environment
16、 file 31 11.1 Transport media 32 11.2 Transport media type 33 ANNEX A (informative) Symbols and conventions 34 ANNEX B (normative) OVF XSD . 35 ANNEX C (informative) OVF mime type registration template 36 ANNEX D (informative) OVF examples . 38 ii D.1 Examples of OVF package structure 38 D.2 Example
17、s of distribution of files 38 D.3 Example of envelope element 39 D.4 Example of file references 40 D.5 Example of content element . 40 D.6 Examples of extensibility 40 D.7 Examples of VirtualHardwareSection . 41 D.8 Examples of virtual hardware elements 42 D.9 Example of ranges on elements . 42 D.10
18、 Example of DiskSection 43 D.11 Example of NetworkSection 43 D.12 Example of ResourceAllocationSection 44 D.13 Example of annotation 44 D.14 Example of Product section 44 D.15 Example of EULA section . 45 D.16 Example of StartupSection . 45 D.17 Example of DeploymentOptionSection . 45 D.18 Example o
19、f OperatingSystemSection . 46 D.19 Example of InstallSection . 46 D.20 Example of EnvironmentFilesSection . 47 D.21 Example of BootDeviceSection 47 D.22 Example of SharedDiskSection 48 D.23 Example of ScaleOutSection 48 D.24 Example of PlcementGroupSection 49 D.25 Example of EncryptionSection 50 D.2
20、6 Example of internationalization . 51 D.27 Example of message content in an external file . 52 D.28 Example of environment document 53 ANNEX E (informative) Network port profile examples . 54 E.1 Example 1 (OVF descriptor for one virtual system and one network with an inlined network port profile)
21、54 E.2 Example 2 (OVF descriptor for one virtual system and one network with a locally referenced network port profile) 56 E.3 Example 3 (OVF descriptor for one virtual system and one network with a network port profile referenced by a URI) 57 E.4 Example 4 (OVF descriptor for two virtual systems an
22、d one network with two network port profiles referenced by URIs) 59 E.5 Example 5 (networkportprofile1.xml) 62 E.6 Example 6 (networkportprofile2.xml) 62 ANNEX F (informative) Deployment considerations 63 F.1 OVF package structure deployment considerations . 63 F.2 Virtual hardware deployment consid
23、erations 63 F.3 Core metadata sections deployment considerations 63 iii Tables Table 1 XML namespace prefixes . 8 Table 2 Actions for child elements with ovf:required attribute 12 Table 3 HostResource element . 13 Table 4 Elements for virtual devices and controllers . 14 Table 5 Core metadata sectio
24、ns 16 Table 6 Property types . 21 Table 7 Property qualifiers . 22 Table 8 Availability attributes . 28 Table 9 Affinity Attributes . 29 Table 10 Allowed combinations of scoped affinity and availability 29 Table 11 Core sections for OEF 32 ivForeword (This foreword is not part of American National S
25、tandard INCITS 469-2015.)The Open Virtualization Format (OVF) Specification describes an open, secure, effi-cient, and extensible format for the packaging and distribution of software to be run invirtual systems.The OVF package enables the authoring of portable virtual systems and the transportof vi
26、rtual systems between virtualization platforms. The key properties of the formatare as follows: - Optimized for distribution: OVF supports content verification and integ-rity checking based on industry-standard public key infrastructure, and itprovides a basic scheme for management of software licen
27、sing.- Optimized for a simple, automated user experience: OVF supportsvalidation of the entire package and each virtual system or metadatacomponent of the OVF during the installation phases of the virtual system(VS) lifecycle management process. It also packages with the packagerelevant user-readabl
28、e descriptive information that a virtualization plat-form can use to streamline the installation experience. - Supports both single VS and multiple-VS configurations: OVF sup-ports both standard single VS packages and packages containing com-plex, multi-tier services consisting of multiple interdepe
29、ndent VSs.- Portable VS packaging: OVF is virtualization platform neutral, while alsoenabling platform-specific enhancements to be captured. It supports thefull range of virtual hard disk formats used for hypervisors today, and it isextensible, which allows it to accommodate formats that may arise i
30、n thefuture. Virtual system properties are captured concisely and accurately.- Vendor and platform independent: OVF does not rely on the use of aspecific host platform, virtualization platform, or guest software.- Extensible: OVF is immediately useful - and extensible. It is designed tobe extended a
31、s the industry moves forward with virtual appliance tech-nology. It also supports and permits the encoding of vendor-specificmetadata to support specific vertical markets.- Localizable: OVF supports user-visible descriptions in multiple locales,and it supports localization of the interactive process
32、es during installationof an appliance. This capability allows a single packaged appliance toserve multiple market opportunities.- Open standard: OVF has arisen from the collaboration of key vendors inthe industry, and it is developed in an accepted industry forum as a futurestandard for portable vir
33、tual systems.It is not an explicit goal for OVF to be an efficient execution format. A hypervisor is al-lowed but not required to run software in virtual systems directly out of the Open Vir-tualization Format. This standard contains seven annexes. Annex B is normative and is considered partof this
34、standard. Annexes A and C through G are informative and are not consideredpart of this standard.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101
35、K Street, NW, Suite 610, Washington, DC20005.vThis standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing m
36、embers:Philip Wennblom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. .Scott FosheeSteve Zilles (Alt.)AIM Global, Inc. Steve HallidayChuck Evanhoe (Alt.)Mary Lou Bosco (Alt.)Dan Kimball (Alt.)Apple.Helene WorkmanMarc Braner (Alt.)David Singer (Alt.
37、)Distributed Management Task Force (DMTF) John Crandall Jeff Hilland (Alt.)Lawrence Lamers (Alt.)EMC Corporation .Gary Robinson Stephen Diamond (Alt.)Farance, Inc. .Frank Farance Timothy Schoechle (Alt.)Futurewei Technologies, Inc. Yi ZhaoTimothy Jeffries (Alt.)Wilbert Adams (Alt.)GS1GO .Frank Shark
38、eyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation .Steve HolbrookAlexander Tarpinian (Alt.)IEEEJodie HaaszDon Wright (Alt.)Noelle Humenick (Alt.)Christy Bahn (Alt.)Justin Casto (Alt.)Intel Corporation .Philip Wennblom Grace Wei (Alt.)Stephen Balogh (Alt
39、.)Microsoft CorporationLaura Lindsay John Calhoon (Alt.)National Institute of Standards then text; then tables. Figures are for illustrative purposes only and are not a normative part of the standard. A table may constrain the text but it shall not conflict with it. The profile conforms to the cited
40、 CIM Schema classes where used. Any requirements contained in the cited CIM Schema classes shall be met. If a conflict arises the CIM Schema takes precedence. The profile conforms to the cited OVF XML Schema. It may constrain the schema but it shall not conflict with it. If a conflict arises the OVF
41、 XML Schema takes precedence. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this American National Standard. All standards are subject to revision, and parties to agreements based on this American National Standard a
42、re encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. The following referenced documents are indispensable for the application of this document. For dated or versioned references, only the edition cited (including any corrigenda or DMTF u
43、pdate versions) applies. For references without a date or version, the latest published edition of the referenced document (including any corrigenda or DMTF update versions) applies. DMTF DSP0004, Common Information Model (CIM) Infrastructure Specification 2.7, http:/www.dmtf.org/standards/published
44、_documents/DSP0004_2.7.pdf DMTF DSP0223, Generic Operations 1.0, http:/www.dmtf.org/standards/published_documents/DSP0223_1.0.pdf DMTF DSP0230, WS-CIM Mapping Specification 1.0, http:/www.dmtf.org/sites/default/files/standards/documents/DSP0230_1.0.2.pdf DMTF DSP1001, Management Profile Specificatio
45、n Usage Guide 1.1, http:/www.dmtf.org/standards/published_documents/DSP1001_1.1.pdf INCITS 469-2015 2 DMTF DSP1041, Resource Allocation Profile (RAP) 1.1, http:/www.dmtf.org/standards/published_documents/DSP1041_1.1.pdf DMTF DSP1043, Allocation Capabilities Profile (ACP) 1.0, http:/www.dmtf.org/stan
46、dards/published_documents/DSP1043_1.0.pdf DMTF DSP1047, Storage Resource Virtualization Profile 1.0, http:/www.dmtf.org/standards/published_documents/DSP1047_1.0.pdf DMTF DSP1050, Ethernet Port Resource Virtualization Profile 1.0, http:/www.dmtf.org/standards/published_documents/DSP1050_1.0.pdf DMTF
47、 DSP1057, Virtual System Profile 1.0, http:/www.dmtf.org/standards/published_documents/DSP1057_1.0.pdf DMTF DSP8023, OVF XML Schema Specification for OVF Envelope 2.0, http:/schemas.dmtf.org/ovf/envelope/2/dsp8023_2.0.xsd DMTF DSP8027, OVF XML Schema Specification for OVF Environment 1.1, http:/sche
48、mas.dmtf.org/ovf/environment/1/dsp8027_1.1.xsd DMTF DSP8049, Network Port Profile XML Schema, http:/schemas.dmtf.org/ovf/networkportprofile/1/dsp8049_1.0.xsd IETF RFC1738, T. Berners-Lee, Uniform Resource Locators (URL), December 1994, http:/tools.ietf.org/html/rfc1738 IETF RFC1952, P. Deutsch, GZIP
49、 file format specification version 4.3, May 1996, http:/tools.ietf.org/html/rfc1952 IETF RFC2616, R. Fielding et al, Hypertext Transfer Protocol HTTP/1.1, June 1999, http:/tools.ietf.org/html/rfc2616 IETF Standard 66, Uniform Resource Identifiers (URI): Generic Syntax, http:/tools.ietf.org/html/rfc3986 IETF Standard 68, Augmented BNF for Syntax Specifications: ABNF, http:/tools.ietf.org/html/rfc5234 ISO 9660, 1988 Information processing-Volume and file structure of CD-ROM for information interchange, http:/www.iso.org/iso/iso_catalogue/catalogue_tc
