ANSI INCITS ISO IEC 17203-2011 Information Technology C Open Virtualization Format (OVF) Specification.pdf

1、 INCITS/ISO/IEC 17203-20112012 (ISO/IEC 17203-2011, IDT) Information technology Open Virtualization Format (OVF) specification INCITS/ISO/IEC 17203-20112012 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but

2、 shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this a

3、rea. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use

4、 by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Approval: 6/5/2012 Pu

5、blished by American National Standards Institute, 25 West 43rd Street, New York, New York 10036 Copyright 2012 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO), International Ele

6、ctrotechnical Commission (IEC), American National Standards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ITI. All reque

7、sts pertaining to this standard should be submitted to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America ii ITIC 2012 All rights reserved ISO/IEC 17203:2011(E) ISO/IEC 2011 All rights reserved iiiForeword ISO (the International Organization for Standardization) a

8、nd IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal w

9、ith particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC h

10、ave established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joi

11、nt technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights

12、. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 17203 was prepared by ANSI INCITS (as INCITS 469:2010) and was adopted, under a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its

13、approval by the national bodies of ISO and IEC. American National StandardDeveloped byfor Information Technology Open Virtualization Format(OVF) SpecificationINCITS 469-2010INCITS 469-2010INCITS 469-2010American National Standardfor Information Technology Open Virtualization Format(OVF) Specificatio

14、nSecretariatInformation Technology Industry CouncilApproved July 20, 2010 American 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 develo

15、per.Consensus is established 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

16、and objections be considered, 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

17、 usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an inte rpretation of any A merican NationalStandard. Moreover, no person shall have the right or authority to issue aninterp

18、retation of an American National Standard in the name of the AmericanNational Standards Institute. Re quests 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 orwith

19、drawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to r eaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational

20、 Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2010 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic r

21、etrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610Washington, 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 dis

22、close such patents to 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

23、 required for the implementation 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 st

24、andard.CONTENTS Foreword.iii 1 Scope1 2 Normative References.1 3 Terms and Definitions.2 4 Symbols and Abbreviated Terms4 5 OVF Packages4 5.1 OVF Package Structure4 5.2 Virtual Disk Formats6 5.3 Distribution as a Single File6 5.4 Distribution as a Set of Files.7 6 OVF Descriptor7 7 Envelope Element.

25、8 7.1 File References.9 7.2 Content Element.10 7.3 Extensibility.11 7.4 Conformance12 8 Virtual Hardware Description.13 8.1 VirtualHardwareSection13 8.2 Extensibility.14 8.3 Virtual Hardware Elements.14 8.4 Ranges on Elements.17 9 Core Metadata Sections19 9.1 DiskSection.19 9.2 NetworkSection.21 9.3

26、 ResourceAllocationSection.21 9.4 AnnotationSection.22 9.5 ProductSection22 9.6 EulaSection.25 9.7 StartupSection26 9.8 DeploymentOptionSection27 9.9 OperatingSystemSection29 9.10 InstallSection.29 10 Internationalization29 11 OVF Environment31 11.1 Environment Document31 11.2 Transport.33 ANNEX A (

27、informative) Symbols and Conventions.34 ANNEX B (informative) Change Log35 ANNEX C (normative) OVF XSD.36 Bibliography37 i INCITS 469-2010 ii Tables Table 1 XML Namespace Prefixes8 Table 2 Actions for Child Elements with ovf:required Attribute.14 Table 3 HostResource Element.16 Table 4 Elements for

28、Virtual Devices and Controllers.17 Table 5 Core Metadata Sections.19 Table 6 Property Types25 Table 7 Property Qualifiers25 Table 8 Core Sections33 Foreword(This foreword is not part of American National Standard INCITS 469-2010.)The Open Virtualization Format (OVF) Specification describes an open,

29、secure, por-table, efficient and extensible format for the packaging and distribution of software to be run in virtual machines. The key properties of the format are as follows: - Optimized for distribution: OVF supports content verification and integrity checking based on industry-standard public k

30、ey infrastructure, and it provides a basic scheme for management of software licensing.- Optimized for a simple, automated user experience: OVF supports valida-tion of the entire package and each virtual machine or metadata component of the OVF during the installation phases of the virtual machine (

31、VM) lifecycle management process. It also packages with the package relevant user-read-able descriptive information that a virtualization platform can use to stream-line the installation experience. - Supports both single VM and multiple-VM configurations: OVF supports both standard single VM packag

32、es and packages containing complex, multi-tier services consisting of multiple interdependent VMs.- Portable VM packaging: OVF is virtualization platform neutral, while also en-abling platform-specific enhancements to be captured. It supports the full range of virtual hard disk formats used for hype

33、rvisors today, and it is exten-sible, which allow it to accommodate formats that may arise in the future. Vir-tual machine properties are captured concisely and accurately.- Vendor and platform independent: OVF does not rely on the use of a specific host platform, virtualization platform, or guest o

34、perating system.- Extensible: OVF is immediately useful - and extensible. It is designed to be ex-tended as the industry moves forward with virtual appliance technology. It also supports and permits the encoding of vendor-specific metadata to sup-port specific vertical markets.- Localizable: OVF sup

35、ports user-visible descriptions in multiple locales, and it supports localization of the interactive processes during installation of an ap-pliance. This capability allows a single packaged appliance to serve multiple market opportunities.- Open standard: OVF has arisen from the collaboration of key

36、 vendors in the industry, and it is developed in an accepted industry forum as a future stan-dard for portable virtual machines.It is not an explicit goal for OVF to be an efficient execution format. A hypervisor is allowed but not required to run software in virtual machines directly out of the Ope

37、n Virtualization Format.This standard contains four annexes. Annex C is normative and is considered part ofthis standard. Annexes A, B, and D are informative and are not considered part ofthis standard.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcom

38、e. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC20005.iiiThis standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all

39、 committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, IncScott FosheeSteve Zilles (Alt.)AIM Global, Inc.Dan MullenCharles Biss (Alt.)A

40、pple Computer, Inc.Kwok LauHelene Workman (Alt.)David Singer (Alt.)Distributed Managment Task ForceJohn CrandallJeff Hilland (Alt.)Electronic Industries AllianceEdward Mikoski, Jr.Henry Cuschieri (Alt.)EMC CorporationGary RobinsonFarance, IncFrank FaranceTimothy Schoechle (Alt.)GoogleZaheda BhoratGS

41、1 US.Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company.Karen HigginbottomPaul Jeran (Alt.)IBM CorporationGerald LaneRobert Weir (Alt.)IEEEBill AshTerry DeCourcelle (Alt.)Jodie Haasz (Alt.)Bob Labelle (Alt.)Intel.Philip WennblomGrace Wei (Alt.)Stephen Ba

42、logh (Alt.)Lexmark International.Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft CorporationJim HughesDave Welsh (Alt.)Mark Ryland (Alt.)John Calhoun (Alt.)National Institute of Standards 160-bit digest in 40-digit hexadecimal hex-digit = “0“ | “1“ | “2“ | “3“ | “4“ | “5“ | “6“ | “7“ | “8“

43、| “9“ | “a“ | “b“ | “c“ | “d“ | “e“ | “f“ sp = %x20 nl = %x0A EXAMPLE 2: The following example show the partial contents of a manifest file: SHA1(package.ovf)= 237de026fb285b85528901da058475e56034da95 SHA1(vmdisk1.vmdk)= 393a66df214e192ffbfedb78528b5be75cc9e1c3 An OVF package may be signed by signin

44、g the manifest file. The digest of the manifest file is stored in a certificate file with extension .cert file along with the base64-encoded X.509 certificate. The .cert file shall have the same base name as the .ovf file and be a sibling of the .ovf file. A consumer of the OVF package shall verify

45、the signature and should validate the certificate. The format of the certificate file shall be as follows: certificate_file = manifest_digest certificate_part manifest_digest = algorithm “(“ file_name “)“ “=“ sp signed_digest nl algorithm = “SHA1“ signed_digest = *( hex-digit) certificate_part = cer

46、tificate_header certificate_body certificate_footer certificate_header = “-BEGIN CERTIFICATE-“ nl certificate_footer = “-END CERTIFICATE-“ nl certificate_body = base64-encoded-certificate nl ; base64-encoded-certificate is a base64-encoded X.509 ; certificate, which may be split across multiple line

47、s hex-digit = “0“ | “1“ | “2“ | “3“ | “4“ | “5“ | “6“ | “7“ | “8“ | “9“ | “a“ | “b“ | “c“ | “d“ | “e“ | “f“ sp = %x20 nl = %x0A EXAMPLE 3: The following list of files is an example of a signed OVF package: package.ovf package.mf package.cert de-DE-resources.xml vmdisk1.vmdk vmdisk2.vmdk resource.iso

48、 EXAMPLE 4: The following example shows the contents of a sample OVF certification file, where the SHA1 digest of the manifest file has been signed with a 512 bit key: SHA1(package.mf)= 7f4b8efb8fe20c06df1db68281a63f1b088e19dbf00e5af9db5e8e3e319de 7019db88a3bc699bab6ccd9e09171e21e88ee20b5255cec3fc28

49、350613b2c529089 5 INCITS 469-2010 -BEGIN CERTIFICATE- MIIBgjCCASwCAQQwDQYJKoZIhvcNAQEEBQAwODELMAkGA1UEBhMCQVUxDDAKBgNV BAgTA1FMRDEbMBkGA1UEAxMSU1NMZWF5L3JzYSB0ZXN0IENBMB4XDTk1MTAwOTIz MzIwNVoXDTk4MDcwNTIzMzIwNVowYDELMAkGA1UEBhMCQVUxDDAKBgNVBAgTA1FM RDEZMBcGA1UEChMQTWluY29tIFB0eS4gTHRkLjELMAkGA1UECxMCQ1MxGzAZBgNV BAMTElNTTGVheSBkZW1vIHNlcnZlcjBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC3 LCXcScWua0PF