On Wed, Mar 7, 2018 at 11:48 PM, Michal Skrivanek <
michal.skriva...@redhat.com> wrote:
>
>
> On 07 Mar 2018, at 14:20, Arik Hadas wrote:
>
>
>
> On Wed, Mar 7, 2018 at 1:41 PM, Richard W.M. Jones
> wrote:
>
>> On Wed, Mar 07, 2018 at 01:26:39PM +0200, Arik Hadas wrote:
>> > Interesting, that co
On 07 Mar 2018, at 14:20, Arik Hadas wrote:
On Wed, Mar 7, 2018 at 1:41 PM, Richard W.M. Jones
wrote:
> On Wed, Mar 07, 2018 at 01:26:39PM +0200, Arik Hadas wrote:
> > Interesting, that contradicts my intuition - I would imagine that most of
> > the things are actually known (the things that
On Wed, Mar 7, 2018 at 3:37 PM, Richard W.M. Jones
wrote:
> On Wed, Mar 07, 2018 at 03:12:58PM +0200, Arik Hadas wrote:
> > If for some predefined period of time no new disk is added or an upload
> > doesn't make any progress (assuming the uploads are done sequentially),
> to
> > fail the import
On Wed, 7 Mar 2018 15:12:58 +0200
Arik Hadas wrote:
> On Wed, Mar 7, 2018 at 1:01 PM, Tomáš Golembiovský
> wrote:
>
> > Hi,
> >
> > this sounds like a good idea in general. Few interconnected questions
> > though...
> >
> > On Wed, 7 Mar 2018 10:42:31 +0200
> > Arik Hadas wrote:
> >
> > > IM
On Wed, Mar 07, 2018 at 03:12:58PM +0200, Arik Hadas wrote:
> If for some predefined period of time no new disk is added or an upload
> doesn't make any progress (assuming the uploads are done sequentially), to
> fail the import operation and that would roll back the resources (disks,
> VMs) that w
On Wed, Mar 7, 2018 at 1:41 PM, Richard W.M. Jones
wrote:
> On Wed, Mar 07, 2018 at 01:26:39PM +0200, Arik Hadas wrote:
> > Interesting, that contradicts my intuition - I would imagine that most of
> > the things are actually known (the things that appear in the top-level
> part
> > of the domain
On Wed, Mar 7, 2018 at 1:01 PM, Tomáš Golembiovský
wrote:
> Hi,
>
> this sounds like a good idea in general. Few interconnected questions
> though...
>
> On Wed, 7 Mar 2018 10:42:31 +0200
> Arik Hadas wrote:
>
> > IMHO, the process should be comprised of:
> > 1. virt-v2v calls an API with the (p
On Wed, Mar 07, 2018 at 01:26:39PM +0200, Arik Hadas wrote:
> Interesting, that contradicts my intuition - I would imagine that most of
> the things are actually known (the things that appear in the top-level part
> of the domain xml: memory size, memory size, num of CPUs, name,.. ) and
> only thin
On Wed, Mar 7, 2018 at 12:05 PM, Richard W.M. Jones
wrote:
> On Wed, Mar 07, 2018 at 10:42:31AM +0200, Arik Hadas wrote:
> > (Moving to devel-list)
> > BTW, I think that the import process should include a preliminary phase
> > where ovirt-engine is informed that the import process starts.
> >
>
Hi,
this sounds like a good idea in general. Few interconnected questions
though...
On Wed, 7 Mar 2018 10:42:31 +0200
Arik Hadas wrote:
> IMHO, the process should be comprised of:
> 1. virt-v2v calls an API with the (probably partial since the OS and other
> things are unknown at that point) OV
On Wed, Mar 07, 2018 at 10:42:31AM +0200, Arik Hadas wrote:
> (Moving to devel-list)
> BTW, I think that the import process should include a preliminary phase
> where ovirt-engine is informed that the import process starts.
>
> Currently, IIUC, the new process is designed to be:
> 1. virt-v2v uplo
On Tue, Mar 6, 2018 at 11:19 PM, Richard W.M. Jones
wrote:
> On Tue, Mar 06, 2018 at 11:14:40PM +0200, Arik Hadas wrote:
> > On Tue, Mar 6, 2018 at 9:18 PM, Richard W.M. Jones
> > wrote:
> >
> > >
> > > I've been playing with disk uploads through the API. As a result
> > > I now have lots of di
12 matches
Mail list logo