Upgrade the OVF spec to use the latest --ovf20 output format

Description

Currently, PMM OVF specification uses a very old (released in 2008) --ovf10 open virtualization format (read more). This has several downsides, particularly:

  • --ovf10 produces SHA1 checksums, which are deprecated and no longer supported by modern operating systems

  • we have to tweak the OVF manifest manually to make it comply with OS security requirements

  • the old virtualization format may not be supported by some environments

 

Solution

Use the most recent OVF 2.0 format (via --ovf20 parameter) in PMM OVF specification. OVF 2.0 introduces enhancements such as improved metadata handling, better support for virtual hardware, and additional features for cloud environments.

How to test

  • Locate the .ovf descriptor file

  • Check the <OvfEnvelope> element, which should specify the OVF format version, refers to v2, for example: <ovf:Envelope xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/2">

    • grep -E 'ovf:version|envelope' path/to/filename.ovf

How to document

None

Activity

Details

Assignee

Reporter

Priority

Needs QA

Yes

Needs Doc

Yes

Smart Checklist

Created February 19, 2025 at 9:03 AM
Updated February 25, 2025 at 10:18 AM

Flag notifications