similar to: Re: [libguestfs/libguestfs] OpenStack support (#38)

You can now use -o rhv (-o rhev is supported for compatibility). --- p2v/gui.c | 5 +- p2v/virt-p2v.pod | 13 ++- v2v/Makefile.am | 8 +- v2v/OVF.ml | 30 +++---- v2v/OVF.mli | 2 +- v2v/changeuid.mli

I'm pleased to announce libguestfs 1.40, a library and a set of tools for accessing and modifying virtual machine disk images. This release represents about a year of work by many contributors. I'd like to call out in particular substantial contributions from: Pino Toscano, Tomáš Golembiovský, Nir Soffer and Nikolay Ivanets. See the release notes below for full details. You can get

On Mon, Mar 16, 2020 at 02:55:11PM +0100, Pino Toscano wrote: > The 'openstack' output mode requires few options, and virt-p2v does not > have the GUI bits for specifying them. > > Similar to commit 9b009aa4a3898648fe68301d1c5ed774a0bf2e38 (for > rhv-upload). > --- > ssh.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/ssh.c

From: Alban Lecorps <alban.lecorps at ubisoft.com> The "-oo" option will be useful primarily for the openstack output mode (currently disabled, from commit b74c126629e3, "Ignore 'openstack' driver", 2020-03-16). Use a ConfigStringList knob for "-oo", and for each OPTION=VALUE element in that list, create a separate "-oo OPTION=VALUE" option.

The 'openstack' output mode requires few options, and virt-p2v does not have the GUI bits for specifying them. Similar to commit 9b009aa4a3898648fe68301d1c5ed774a0bf2e38 (for rhv-upload). --- ssh.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/ssh.c b/ssh.c index 9dd2d8a..ce0caaa 100644 --- a/ssh.c +++ b/ssh.c @@ -1018,10 +1018,11 @@ static void

On Wed, Sep 26, 2018 at 09:57:22AM +0200, Fabien Dupont wrote: > Hi, > > There has been discussion about the OpenStack output and Richard asked for > a public thread on this list, so here it is. > > For v2v from VMware to RHV, there is a Python script that does some extra > steps to create the virtual machine after the disks have been converted. We > want to have the same

On Wed, Sep 26, 2018 at 11:39 AM Richard W.M. Jones <rjones@redhat.com> wrote: > On Wed, Sep 26, 2018 at 09:57:22AM +0200, Fabien Dupont wrote: > > Hi, > > > > There has been discussion about the OpenStack output and Richard asked > for > > a public thread on this list, so here it is. > > > > For v2v from VMware to RHV, there is a Python script that

You can now use -o rhv (-o rhev is supported for compatibility). --- v2v/Makefile.am | 8 +- v2v/OVF.ml | 30 +++---- v2v/OVF.mli | 2 +- v2v/changeuid.mli | 4 +- v2v/cmdline.ml | 12 +-- v2v/convert_windows.ml

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1792141 Let the user pass "-oo" options from the kernel cmdline and from the GUI to virt-v2v. This is primarily useful with the OpenStack output mode, so reenable that mode. Cc: Alban Lecorps <alban.lecorps at ubisoft.com> Laszlo Alban Lecorps (1): Introduce "p2v.output.misc" for passing "-oo" options

Hi, There has been discussion about the OpenStack output and Richard asked for a public thread on this list, so here it is. For v2v from VMware to RHV, there is a Python script that does some extra steps to create the virtual machine after the disks have been converted. We want to have the same behavior for OpenStack, i.e. have virt-v2v create the instance once the volumes have been created.

If ‘virt-v2v -oo insecure’ is used then ‘openstack --insecure’ flag is added whenever we invoke the openstack command. This turns of SSL certificate validation. --- v2v/output_openstack.ml | 14 +++++++++++++- v2v/virt-v2v-output-openstack.pod | 1 + v2v/virt-v2v.pod | 7 +++++++ 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/v2v/output_openstack.ml

If ‘virt-v2v -oo verify-server-certificate=false’ is used then ‘openstack --insecure’ flag is added whenever we invoke the openstack command. This turns off SSL certificate validation. The default is to verify the server certificate (which is the default of the openstack command). --- v2v/output_openstack.ml | 16 +++++++++++++++- v2v/test-v2v-o-openstack.sh | 2 ++

On Wed, Sep 26, 2018 at 02:40:54PM +0200, Fabien Dupont wrote: > [Adding Tomas Golembiovsky] > > Well, that's mainly IMS related challenges. We're working on > OpenStack output support and migration throttling and this implies > changes to virt-v2v-wrapper. This is then the opportunity to think > about virt-v2v-wrapper maintenance and feature set. It has been >

(Apologies if I missed anyone off the To: line. Please add anyone else who is interested, but keep the libguestfs public mailing list) I did some preparatory work on adding the new ‘virt-v2v -o openstack’ output mode. I've put it in a private (non-FFwd) branch here: https://github.com/rwmjones/libguestfs/tree/openstack Most of the work was refactoring virt-v2v so that we have all of the

I'm please to announce libguestfs 1.36, a library and a set of tools for accessing and modifying virtual machine disk images. This release represents about 7 months of work by many contributors. I'd like to call out in particular substantial code contributions from: Pino Toscano, Tomáš Golembiovský, Cédric Bosdonnat, Roman Kagan, Dawid Zamirski and Matteo Cafasso. Also our testing team:

Virt-v2v is a program for converting virtual machines to run on KVM, ones imported from other hypervisors like VMware, Xen and more, and with the companion tool virt-p2v from physical machines too. I'm pleased to announce the release of virt-v2v 1.42. This is a new stable branch. Significantly the tool is now released separately and on a different schedule from libguestfs. Manual:

Add a new output mode to virt-v2v: similar to -o local, the written metadata is a JSON file with the majority of the data that virt-v2v knowns about (or collects) during the conversion. This is meant to be used only when no existing output mode is usable, and a guest needs to be converted to run on KVM anyway. The user of this mode is supposed to use all the data in the JSON, as they contain

Add a new output mode to virt-v2v: similar to -o local, the written metadata is a JSON file with the majority of the data that virt-v2v knowns about (or collects) during the conversion. This is meant to be used only when no existing output mode is usable, and a guest needs to be converted to run on KVM anyway. The user of this mode is supposed to use all the data in the JSON, as they contain

Save the content of the environment on the conversion server, so it is one additional help when debugging failed conversions. --- p2v/conversion.c | 5 +++++ p2v/virt-p2v.pod | 6 ++++++ 2 files changed, 11 insertions(+) diff --git a/p2v/conversion.c b/p2v/conversion.c index 3c379cb..b8bab34 100644 --- a/p2v/conversion.c +++ b/p2v/conversion.c @@ -1061,6 +1061,11 @@ generate_wrapper_script

Since RHV 3.6.10, the default network name is 'ovirtmgmt' instead of 'rhvm'. This is just a documentation change. --- p2v/virt-p2v.pod | 10 +++++----- v2v/cmdline.ml | 2 +- v2v/virt-v2v.pod | 12 ++++++------ 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod index ea685be..4a5f587 100644 --- a/p2v/virt-p2v.pod +++