This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/DSP0243 at Thu, 03 Nov 2022 00:16:58 GMT SourceForge : View Wiki Page: DSP0243

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: scrm-wg     Wiki > DSP0243 > View Wiki Page
wiki2038: DSP0243

Standard

1. The name of the specification

Open Virtualization Format (OVF)

2. A short statement (<100 words) of the purpose and function of the specification

The Open Virtualization Format (OVF) Specification describes an open, secure, portable, 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 key infrastructure, and it provides a basic scheme for management of software licensing.
  • Optimized for a simple, automated user experience - OVF supports validation of the entire package and each virtual machine or metadata component of the OVF during the installation phases of the virtual machine (VM) lifecycle management process. It also packages with the package relevant user-readable descriptive information that a virtualization platform can use to streamline the installation experience.
  • Supports both single VM and multiple-VM configurations - OVF supports both standard single VM packages and packages containing complex, multi-tier services consisting of multiple interdependent VMs.
  • Portable VM packaging - OVF is virtualization platform neutral, while also enabling platform-specific enhancements to be captured. It supports the full range of virtual hard disk formats used for hypervisors today, and it is extensible, which will allow it to accommodate formats that may arise in the future. Virtual 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 operating system.
  • Extensible - OVF is immediately useful — and extensible. It is designed to be extended as the industry moves forward with virtual appliance technology. It also supports and permits the encoding of vendor-specific metadata to support specific vertical markets.
  • Localizable - OVF supports user-visible descriptions in multiple locales, and it supports localization of the interactive processes during installation of an appliance. This capability allows a single packaged appliance to serve multiple market opportunities.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

Version 1.0.0d Preliminary September 4, 2008

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

Virtualization Management (VMAN)

5. URI for the normative text of the specification

http://www.dmtf.org/standards/published_documents/DSP0243_1.0.0.pdf

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

Distributed Management Task Force (DMTF)

7. URI for the SDO

http://www.dmtf.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Preliminary

9. The language or languages in which the specification is available.

US English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Configuration Management: Controlling a resource's operational parameters.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html ) Physical layer Data link layer Network layer Transport layer Session layer Presentation layer Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support


OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

Proposed work Contributions received Preliminary SDO draft Initial public review Final approval Product availability End-of-life (superseded, withdrawn, etc.)

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.dmtf.org/about/policies/

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

http://www.dmtf.org/about/policies/disclosures/

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

18. Known implementations of the specification (by owner name or URI).

http://www.dmtf.org/about/marketplace/

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

This specification depends on the following documents. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

  • : Please identify where reference specification is within SDO member organizations or not and current level of approval as the level of question.
 




The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.scrm-wg/wiki/DSP0243 at Thu, 03 Nov 2022 00:16:58 GMT