On Thu, 22 Feb 2018 11:41:05 +0100
Tomáš Golembiovský <tgole...@redhat.com> wrote:

> The main reason for creating different OVF is that it can be used to create VM
> by oVirt REST API. The RHV export domain flavor cannot be used that way.
> 
> v1 -> v2:
> - introduced flavour types instead of booleans
> - instead of referring to the new flavour as "standard OVF" or "fixed OVF" I
>   refer to it as oVirt flavour. While it is more conforming than the one used
>   in export domain it can still contain some oVirt specific pieces.

- I also added the list of flavours to --machine-readable output

    Tomas

> 
> Tomáš Golembiovský (3):
>   v2v: tests: check generated OVF
>   v2v: ovf: Create OVF more aligned with the standard
>   v2v: vdsm: add --vdsm-fixed-ovf option
> 
>  v2v/Makefile.am                          |   2 +
>  v2v/cmdline.ml                           |  10 ++
>  v2v/create_ovf.ml                        | 159 
> ++++++++++++++++++++++---------
>  v2v/create_ovf.mli                       |  21 +++-
>  v2v/output_rhv.ml                        |   3 +-
>  v2v/output_vdsm.ml                       |  10 +-
>  v2v/output_vdsm.mli                      |   1 +
>  v2v/test-v2v-o-rhv.ovf.expected          |  92 ++++++++++++++++++
>  v2v/test-v2v-o-rhv.sh                    |  21 ++++
>  v2v/test-v2v-o-vdsm-options.ovf.expected |  92 ++++++++++++++++++
>  v2v/test-v2v-o-vdsm-options.sh           |  20 +++-
>  v2v/virt-v2v.pod                         |  20 ++++
>  12 files changed, 400 insertions(+), 51 deletions(-)
>  create mode 100644 v2v/test-v2v-o-rhv.ovf.expected
>  create mode 100644 v2v/test-v2v-o-vdsm-options.ovf.expected
> 
> -- 
> 2.16.1
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>

_______________________________________________
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs

Reply via email to