search for: l384

Displaying 5 results from an estimated 5 matches for "l384".

Did you mean: 384
2020 Jan 10
1
Operator precedence of =, <- and ?
...mentation? Or is the documentation ?correct?, and there?s a bug in the parser (in some versions of R)? [1] < https://stackoverflow.com/questions/1741820/51564252#comment105506343_51564252 > [2] < https://github.com/wch/r-source/blob/386c3a93cbcaf95017fa6ae52453530fb95149f4/src/main/gram.y#L384-L390 > -- Konrad Rudolph [[alternative HTML version deleted]]
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 Sep 26
0
Re: OpenStack output workflow
...isting behaviour. The issue of cleaning up disks in general is a hard one to solve. With the OpenStack backend we try our best as long as virt-v2v exits on a normal failure path: https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L370-L384 However there are always going to be cases where that is not possible (eg. virt-v2v segfaults or is kill -9'd or whatever), and in that case I envisaged for OpenStack some sort of external garbage collector. To this end, disks which have not been finalized are given a special description so i...
2018 Sep 26
2
Re: OpenStack output workflow
[Adding Tomas Golembiovsky] On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > Rather than jumping to a solution, can you explain what the problem > is that you're trying to solve? > > You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc. > Well, that's mainly IMS related challenges. We're working on
2018 Sep 26
3
Re: OpenStack output workflow
...ue of cleaning up disks in general is a hard one to solve. > > With the OpenStack backend we try our best as long as virt-v2v > exits on a normal failure path: > > > https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L370-L384 > > However there are always going to be cases where that is not possible > (eg. virt-v2v segfaults or is kill -9'd or whatever), and in that case > I envisaged for OpenStack some sort of external garbage collector. To > this end, disks which have not been finalized are given a...