Displaying 20 results from an estimated 5000 matches similar to: "[PATCH v6] v2v: Add -o rhv-upload output mode."
2018 Mar 08
6
[PATCH v5 0/4] v2v: Add -o rhv-upload output mode.
Mainly minor fixes and code cleanups over the v4 patch.
There are still several problems with this patch, but it is in a
reviewable state, especially the Python code.
Rich.
2018 Apr 05
2
[PATCH v8] v2v: Add -o rhv-upload output mode (RHBZ#1557273).
v7 was here:
https://www.redhat.com/archives/libguestfs/2018-March/msg00143.html
Since then:
- Earlier patches are now upstream.
- The to-do list is moved from the commit message to the TODO file.
- This version forces -of raw + -oa sparse and gives an error in
any other mode. We intend to lift these restrictions later.
- Tested against latest imageio which supports longer timeouts,
2018 Apr 10
2
[PATCH v9] v2v: Add -o rhv-upload output mode (RHBZ#1557273).
v8 was here:
https://www.redhat.com/archives/libguestfs/2018-April/msg00022.html
v8 -> v9:
- Addresses the only feedback from Tomáš.
Rich.
2018 Mar 08
2
Re: [PATCH v5 4/4] v2v: Add -o rhv-upload output mode.
On Thu, Mar 8, 2018 at 11:37 AM Richard W.M. Jones <rjones@redhat.com>
wrote:
> PROBLEMS:
> - Target cluster defaults to "Default".
> - Using Insecure = True, is that bad?
> - -of qcow2 does not work, with multiple problems
> - Need to attach disks to VMs somehow
>
> This adds a new output mode to virt-v2v. virt-v2v -o rhv-upload
> streams images
2018 Mar 06
5
[PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
Previous versions:
v3: https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html
v2: https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html
v1: https://www.redhat.com/archives/libguestfs/2018-February/msg00139.html
This completely rethinks the approach taken by the previous patches.
Instead of trying to involve qemu's curl driver, this uses a small
Python 3
2019 Sep 16
16
[PATCH 0/8] v2v: various fixed for -o rhv-upload
This patch series fixes various issues in the rhv-upload output mode:
- properly find and use RHV resources
- cleanup orphan disks, and possibly the current disk transfer on
failure
In reality, the first 4 patches deal with resources, and the other 4
with cleanups. The latter block can be theoretically sent alone --
I just happened to start working on it as part of my "let's fix
2018 Mar 22
12
[PATCH v7 0/6] v2v: Add -o rhv-upload output mode (RHBZ#1557273).
v6 was here:
https://www.redhat.com/archives/libguestfs/2018-March/msg00126.html
This makes a number of significant changes:
- Input and output options now use a uniform set of -io and -oo
parameters.
- For -o rhv-upload, we use ‘-oo rhv-cafile=/tmp/ca.pem’ etc. The
‘--rhv*’ options have been dropped.
- Rearranges the documentation.
- As before includes (untested) support for zero,
2020 Jan 10
7
[v2v PATCH 0/6] Various Python pycodestyle fixes
Fixes the majority of the pycodestyle issues in the Python scripts, and
fix the existing test-v2v-python-syntax.sh to use pycodestyle to
actually perform style checks.
Pino Toscano (6):
PEP 8: adapt whitespaces in lines
PEP 8: move imports at the top
PEP 8: adapt empty lines
tests: find all the Python scripts for syntax checks
-o rhv-upload: remove unused Python imports
Revamp check
2018 Feb 27
5
[PATCH v2 0/3] v2v: Add -o rhv-upload output mode.
This patch set is still for discussion only. See 3/3 for the current
list of problems.
However this will upload an image to an oVirt or RHV server, although
you must have absolutely the latest snapshot version of 4.2 for it to
work.
Rich.
2018 Mar 12
1
[PATCH RHEL 7] RHEL 7: -o rhv-upload: Use Python 2 instead of Python
For interest only, here is the patch required to make -o rhv-upload
work with Python 2 (for RHEL 7). I don't think we want this upstream.
A couple of remarks:
* It's supposed to be possible to add ‘coding: utf-8’ to the top of
.py files to make Python 2 accept that the file is UTF-8 (otherwise
it gives an error on loading). However I added this and it didn't
appear to make any
2018 Mar 01
7
[PATCH v3 0/6] v2v: Add -o rhv-upload output mode.
v2 -> v3:
- Lots of code cleanups.
- Documentation.
However this is still spooling the file into a temporary before the
upload. It turns out that fixing this is going to require a small
change to qemu.
Rich.
2018 Feb 22
11
[PATCH 0/5] v2v: Add -o rhv-upload output mode.
The first four patches are straightforward.
The final patch adds the -o rhv-upload output mode. It is
still spooling into a temporary file because I've had some
trouble getting streaming conversions working. There are
other problems as outlined in the commit message, so this
patch is not ready for upstream but is good for discussion.
Also I hit this, which I'm assuming for now will be
2018 Mar 21
3
Re: [PATCH v6] v2v: Add -o rhv-upload output mode.
On Wed, Mar 21, 2018 at 3:34 PM Richard W.M. Jones <rjones@redhat.com>
wrote:
> PROBLEMS:
> - -of qcow2 does not work, with multiple problems
> * needs to set NBD size to something larger than virtual size
>
> This adds a new output mode to virt-v2v. virt-v2v -o rhv-upload
> streams images directly to an oVirt or RHV >= 4 Data Domain using the
> oVirt SDK v4.
2020 Mar 11
4
[PATCH v2v v3 0/2] rhv-upload: Validate UUIDs and check they don't exist already
My stab v3 at fixing this: https://bugzilla.redhat.com/show_bug.cgi?id=1789279
It took me quite some time to go through the whole rfc 4122 just to realize we
do not need to do anything with the versions.
v3:
- Do the check in precheck
- Fix for Lazy evaluation of regexp UUID
v2:
- https://www.redhat.com/archives/libguestfs/2020-January/msg00221.html
- Use EEXIST instead of EINVAL
- Put the
2019 Sep 27
1
[PATCH] v2v: -o rhv-upload: make -oo rhv-cafile optional
It makes little sense to require the oVirt certificate, especially when
the verification of the connection (-oo rhv-verifypeer) is disabled by
default. The only work done with the certificate in that case is
checking that it is a valid certificate file.
Hence, make -oo rhv-cafile optional, requiring it only when
-oo rhv-verifypeer is enabled.
---
v2v/output_rhv_upload.ml | 16
2018 Mar 11
2
Re: [PATCH v5 4/4] v2v: Add -o rhv-upload output mode.
On Thu, 8 Mar 2018 09:37:19 +0000
"Richard W.M. Jones" <rjones@redhat.com> wrote:
> PROBLEMS:
> - Target cluster defaults to "Default".
> - Using Insecure = True, is that bad?
Since you have --rhv-cafile mandatory, there is no reason to set
Insecure=True.
> - -of qcow2 does not work, with multiple problems
> - Need to attach disks to VMs somehow
2018 Mar 09
1
Re: [PATCH v5 4/4] v2v: Add -o rhv-upload output mode.
On 03/08/2018 12:57 PM, Nir Soffer wrote:
> On Thu, Mar 8, 2018 at 11:37 AM Richard W.M. Jones <rjones@redhat.com
> <mailto:rjones@redhat.com>> wrote:
>
> PROBLEMS:
> - Target cluster defaults to "Default".
> - Using Insecure = True, is that bad?
> - -of qcow2 does not work, with multiple problems
> - Need to attach disks
2019 Sep 19
2
[PATCH 1/2] v2v: add optional tmpdir parameter for Python_script
Add an optional parameter for Python_script.create, to specific the
temporary directory to use instead of creating a new one.
---
v2v/python_script.ml | 13 ++++++++-----
v2v/python_script.mli | 5 ++++-
2 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/v2v/python_script.ml b/v2v/python_script.ml
index 3159373a1..6bb14ec1f 100644
--- a/v2v/python_script.ml
+++
2019 Sep 19
1
Re: [PATCH 2/2] v2v: -o rhv-upload: use same tmpdir for Python scripts
On Thu, Sep 19, 2019 at 02:30:05PM +0200, Pino Toscano wrote:
> Make use of the temporary directory of the rhv-upload mode also for the
> Python scripts that the mode creates, instead of creating new
> directories.
> ---
> v2v/output_rhv_upload.ml | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/v2v/output_rhv_upload.ml
2018 Mar 21
0
[PATCH v6] v2v: Add -o rhv-upload output mode.
PROBLEMS:
- -of qcow2 does not work, with multiple problems
* needs to set NBD size to something larger than virtual size
This adds a new output mode to virt-v2v. virt-v2v -o rhv-upload
streams images directly to an oVirt or RHV >= 4 Data Domain using the
oVirt SDK v4. It is more efficient than -o rhv because it does not
need to go via the Export Storage Domain, and is possible for