[ovirt-devel] [ovirt-users] Unremovable disks created through the API

Wed Mar 7 22:14:57 UTC 2018

On Wed, Mar 7, 2018 at 11:48 PM, Michal Skrivanek <
michal.skrivanek at redhat.com> wrote:

>
>
> On 07 Mar 2018, at 14:20, Arik Hadas <ahadas at redhat.com> wrote:
>
>
>
> On Wed, Mar 7, 2018 at 1:41 PM, Richard W.M. Jones <rjones at redhat.com>
> 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 xml: memory size, memory size, num of CPUs, name,.. ) and
>> > only things that depend on the content of the disks or things that
>> depend
>> > on installations during the conversion are unknown.
>> > But anyway, it is enough IMO to send the name, memory, CPU and size of
>> the
>> > disks to present something useful to the user and make the necessary
>> > validations at that point.
>>
>> Some of those things are known, but they didn't seem to me to be that
>> interesting for oVirt to know in advance.  In any case what's
>> precisely known before conversion is:
>>
>> (1) The 'source' struct and sub-structs:
>>
>> https://github.com/libguestfs/libguestfs/blob/ba53251ab912b8
>> bac9e00c1022adc6ba9bdf70a3/v2v/types.mli#L59
>>
>> (2) The 'overlay' struct (one per disk):
>>
>> https://github.com/libguestfs/libguestfs/blob/ba53251ab912b8
>> bac9e00c1022adc6ba9bdf70a3/v2v/types.mli#L175
>>
>> Note only virtual disk size is known, which is near to useless for
>> provisioning storage.
>>
>> (3) The 'target' struct (one per disk):
>>
>> https://github.com/libguestfs/libguestfs/blob/ba53251ab912b8
>> bac9e00c1022adc6ba9bdf70a3/v2v/types.mli#L191
>>
>> What's unknown are guest capabilities (hence nothing about what
>> devices should be presented to the guest), inspection data, target bus
>> mapping, real size of disks, etc.
>>
>>
> I see. I think it is sufficient - the information from the 'source' struct
> seems enough just to produce a representative VM entity in the database
> that would be reflected in the UI with status 'importing' and for general
> validations,
>
>
> For having an entity, yes. For meaningful validations, not really.
>

I was thinking mostly about validating the name and the amount of free
space in the target storage domain.
But in the future, when/if the imported VMs could be from different
architecture (PPC?) or different CPU type (q35?) we can also validate that
the target cluster is valid.

> It's not so interesting to see much in oVirt, at least not for the
> virt-v2v command line usage
>
>
Functionality-wise, I agree.
But in a serious management application you don't expect to see memory=0 or
memory=N/A when you open the general tab of the VM that is being imported.
If we can easily get the information from the 'source' struct, I think we
should.

> and the estimated size on the 'target' struct would be enough for storage
> validations and optionally for choosing the right target storage domain.
> The other things are relatively hidden in oVirt's UI and can be added at
> the last phase.
>
>
> What I do not like that much about is that you change the VM at the end
> substantially, and for the import duration it's locked anyway
> The name has a value, and progress, but again, only for a oVirt GUI user -
> and when you are driving the process from cmdline it's just not that
> important
>

Right, but I tend to think that it's better to generalize the process in a
way that the cmdline flow will make an extra step(s) rather than having
separate and different flows.

>
> It's not so difficult to do it like that "externally" - just blindly
> create a completely stub VM in your caller app(wrapper; another
> integration), and then replace it. We do not need to push that into v2v
> directly
>
>
It depends on the amount and quality of validations you want to make at the
beginning of the process and whether or not ovirt-engine should instruct
v2v where to upload the disks to (maybe there should be an option to upload
a disk without specifying the target storage domain so it will be selected
automatically).
v2v will anyway need to trigger a call to ovirt-engine in order to create
that context, that wrapper command. If the data we need at the beginning is
already available to v2v at that point, providing it to that call shouldn't
be that complex, right?

>
> BTW, that's how import from VMware/Xen currently works - we add a VM
> entity based on the domain XML we get from vCenter and at the last phase
> add the missing parts when getting the generated OVF from virt-v2v. So for
> instance, the VM would have no graphics device until that last phase.
>
>
>
>> Rich.
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>> virt-top is 'top' for virtual machines.  Tiny program with many
>> powerful monitoring features, net stats, disk stats, logging, etc.
>> http://people.redhat.com/~rjones/virt-top
>>
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20180308/beee8044/attachment.html>