Displaying 20 results from an estimated 600 matches similar to: "[PATCH] v2v: -o openstack: Check openstack binary exists before running it."
2020 Feb 04
1
[PATCH v2v] openstack: Increase Cinder volume attach timeout to 5 minutes (RHBZ#1685032).
In some cases we have observed the time taken for a Cinder volume to
attach to the conversion appliance can be longer than the current 60
seconds. Increase the timeout to 5 minutes.
Thanks: Ming Xie.
---
v2v/output_openstack.ml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/v2v/output_openstack.ml b/v2v/output_openstack.ml
index caaedf452..e395ccb37 100644
---
2020 Apr 06
0
[v2v PATCH 2/2] Consolidate handling of temporary files/dirs
Create two temporary directories for all the files created during the
virt-v2v run:
1) tmpdir, created as $TMPDIR/virt-v2v.XXXXXX, for all the small files
2) cachedir, created as $LIBGUESTFS_CACHEDIR/virt-v2v.XXXXXX, for the
big files (e.g. disks)
This way there is no need to manually schedule all the temporary files
and directories for removal when the application quits.
---
v2v/input_ova.ml
2018 Nov 19
1
[PATCH] v2v: -o openstack: Option to add --insecure flag to openstack command.
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
2019 Apr 03
1
[PATCH] UNTESTED v2v: openstack: Read server-id from metadata service.
Random old patch that I had in my queue. Posting it as a backup,
it is still untested.
Rich.
2019 Jan 08
1
[PATCH] v2v: -o openstack: Don't echo full commands (RHBZ#1664310).
They can contain passwords or tokens if for example the
‘-oo os-password’ option is used.
Thanks: Tomáš Golembiovský, Brett Thurber.
---
v2v/output_openstack.ml | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/v2v/output_openstack.ml b/v2v/output_openstack.ml
index 95c42cbed..3ff1e1269 100644
--- a/v2v/output_openstack.ml
+++ b/v2v/output_openstack.ml
@@ -177,8
2018 Nov 20
0
[PATCH v2] v2v: -o openstack: -oo verify-server-certificate=(true|false) (RHBZ#1651432).
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 ++
2020 Aug 25
0
[PATCH v2v] v2v: -o openstack: Allow guests to be converted to UEFI (RHBZ#1872094).
Since this output method was written the code has always been capable
of adding the hw_firmware_type = uefi image property, and this
property has been supported since at least OpenStack 12 which is years
old.
Interestingly now all of the output modes support both BIOS and UEFI.
---
v2v/output_openstack.ml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/v2v/output_openstack.ml
2018 Nov 20
0
[PATCH v3] v2v: -o openstack: Allow -oo insecure (RHBZ#1651432).
Previously we allowed arbitrary flags to be passed through to the
underlying openstack CLI command, provided they have the format
‘--key=value’. We want to pass the ‘--insecure’ flag through, but
that doesn't have the key=value form. However a small modification to
the matching rules would allow this.
The effect of this change is that you can now use ‘virt-v2v -oo
insecure’ to turn off SSL
2018 Jul 27
1
Preparatory work on virt-v2v -o openstack mode
(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
2018 Aug 29
2
[PATCH 0/2] v2v: Add -o openstack target.
This patch implements output to OpenStack Cinder volumes using
OpenStack APIs.
It has only been lightly tested, but appears to work.
There are some important things to understand about how this works:
(1) You must run virt-v2v in a conversion appliance running on top of
OpenStack. And you must supply the name or UUID of this appliance to
virt-v2v using the ‘-oo server-id=NAME|UUID’ parameter.
2018 Sep 26
0
Re: OpenStack output workflow
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
>
2018 Aug 30
3
[PATCH v2 0/2] v2v: Add -o openstack target.
v1 was here:
https://www.redhat.com/archives/libguestfs/2018-August/thread.html#00287
v2:
- The -oa option now gives an error; apparently Cinder cannot
generally control sparse/preallocated behaviour, although certain
Cinder backends can.
- The -os option maps to Cinder volume type; suggested by Matt Booth.
- Add a simple test.
2020 Apr 06
4
[v2v PATCH 1/2] v2v: nbdkit: change base dir for nbdkit sockets/pidfiles
Since this new temporary directory will contain UNIX sockets for
communicating with nbdkit, then its path must not be too long.
Use the existing directory that libguestfs exposes for this, i.e.
sockdir.
---
v2v/nbdkit.ml | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/v2v/nbdkit.ml b/v2v/nbdkit.ml
index 65317f9b..46b20c9d 100644
--- a/v2v/nbdkit.ml
+++ b/v2v/nbdkit.ml
2018 Nov 20
3
[PATCH v4 0/2] v2v: -o openstack: -oo verify-server-certificate=(true|false) (RHBZ#1651432).
The first patch restricts passthrough parameters to ones matching
"os-*". This was how it was documented, but not how it was
implemented.
The second patch is the same as v2 here:
https://www.redhat.com/archives/libguestfs/2018-November/msg00187.html
Rich.
2018 Nov 20
3
[PATCH v3] v2v: -o openstack: Allow -oo insecure (RHBZ#1651432).
A smaller change than v2, we simply generalize the ability to pass
through flags to the underlying openstack command, allowing the
--insecure flag to be specified directly.
Rich.
2017 Oct 04
1
Re: [PATCH 2/9] ocaml: Replace pattern matching { field = field } with { field }.
On Wednesday, 4 October 2017 14:56:23 CEST Richard W.M. Jones wrote:
> If you have a struct containing ‘field’, eg:
>
> type t = { field : int }
>
> then previously to pattern-match on this type, eg. in function
> parameters, you had to write:
>
> let f { field = field } =
> (* ... use field ... *)
>
> In OCaml >= 3.12 it is possible to abbreviate
2018 Sep 26
3
Re: OpenStack output workflow
On Wed, Sep 26, 2018 at 4:25 PM Richard W.M. Jones <rjones@redhat.com>
wrote:
> 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.
2020 Jan 28
2
[v2v PATCH 1/2] Add back guestcaps as parameter of output#prepare_targets
It will be used to do extra checks in the output before copying the
disks.
Partially revert commit 3bafec4e693a25ef1c84abc0fd1bc3251862c7de.
---
v2v/output_glance.ml | 2 +-
v2v/output_json.ml | 2 +-
v2v/output_libvirt.ml | 2 +-
v2v/output_local.ml | 2 +-
v2v/output_null.ml | 2 +-
v2v/output_openstack.ml | 2 +-
v2v/output_qemu.ml | 2 +-
v2v/output_rhv.ml
2013 Aug 09
1
a fast table() for the 1D case
Hi,
table1D() below can be up to 60x faster than base::table() for the 1D
case. Here are the detailed speedups compared to base::table().
o With a logical vector of length 5M: 11x faster
(or more if 'useNA="always"')
o With factor/integer/numeric/character of length 1M and 9 levels
(or 9 distinct values for non-factors):
2017 Mar 19
0
RFC: (in-principle) native unquoting for standard evaluation
On Mon, Mar 20, 2017 at 7:36 AM, Radford Neal <radford at cs.toronto.edu> wrote:
> Michael Lawrence (as last in long series of posters)...
>
>> Yes, it would bind the language object to the environment, like an
>> R-level promise (but "promise" of course refers specifically to just
>> _lazy_ evaluation).
>>
>> For the uqs() thing, expanding calls