Glenn Matthews

Thanks! You want section 9.8 (DeploymentOptionSection): > * Each Item has an optional ovf:configuration attribute, containing a list of configurations separated by a single space character. If not specified, the...

"Disks with no images" - as in Disk elements with no associated fileRef? COT recognizes these as valid but I don't currently have support for creating them. Wouldn't be hard...

http://stackoverflow.com/questions/10448200/how-to-parse-multiple-sub-commands-using-python-argparse may be relevant

This should be less of an issue if #39 is fixed to reduce unnecessary copies/read/write operations.

Thanks for the report! I verified that the OVF specification allows for multiple `ProductSection` elements, so this is indeed a bug. Can you provide your complete OVF XML content for...

Duplicate of #73, but I'll leave this open separately until the submitter replies.

Thanks for the report! While the OVF specification definitely allows multiple ProductSections under a VirtualSystem, I haven't previously seen any "in-the-wild" OVFs that actually do so. Would you mind providing...

I'm not opposed to adding new subcommands to create/edit/delete generic hardware `Item` elements - the existing `cot edit-hardware` command is complex enough that I wouldn't want to add this functionality...

Sorry for the delayed response! Can you confirm whether you have `ovftool` installed?

Of course if we fix #6 then this issue becomes moot :)