2:03 p.m.
On Thu, Jun 25, 2020 at 11:17 AM Ales Musil <amusil(a)redhat.com> wrote:
On Thu, Jun 25, 2020 at 11:13 AM Ales Musil <amusil(a)redhat.com> wrote:
>
>
> On Thu, Jun 25, 2020 at 11:03 AM Prajith Kesava Prasad <
> pkesavap(a)redhat.com> wrote:
>
>>
>>
>> On Thu, Jun 25, 2020 at 2:26 PM Ales Musil <amusil(a)redhat.com> wrote:
>>
>>>
>>>
>>> On Thu, Jun 25, 2020 at 10:46 AM Prajith Kesava Prasad <
>>> pkesavap(a)redhat.com> wrote:
>>>
>>>> Hey Everyone,
>>>>
>>>
>>> Hi,
>>>
>>
>> Thank you for a quick response :-)
>>
>>>
>>> what I'm trying to achieve here is to get the list of network
>>>> interfaces attached to each host,
>>>> and then further get the ipv4Address from the corresponding attached
>>>> logical network (as seen in the in the column in the image below).
>>>>
>>>> So i tried to get the list of interfaces of current host by
>>>> getVds().getInterfaces() and it is returning an empty list
>>>> of List<VdsNetworkInterface>.
>>>> even though its showing in the UI.
>>>>
>>>
>>> So the first thing is where are you trying to get this list? In which
>>> part of the code?
>>>
>>
>> in class :- InstallVdsInternalCommand.java
>>
>
Prajith, you cannot access VdsInterfaces in InstallVdsInternal, because
they are not yet know. First the host needs to finish installation (ansible
playbook), then we need to establish connection from engine to host, then
we need to execute setupNetworks and only afterwards when host is activated
and host monitoring started we fetch all network interfaces from the host
and store them to database.
What's the usecase? Why do you need to know host interface during host
installation/reinstallation?
>>>
>>>>
>>>> Could you tell me if I'm missing something?
>>>>
>>>
>>> The interfaces are not populated and you would need an extra database
>>> call in order to get them properly.
>>>
>>
>> i assumed since getVds() could be called here, further methods in VDS
>> could be called without a DB call.
>>
>
> Unfortunately not. Because Vds is huge not everything is filled with a
> single DB call. You will need something like getVdsInterfacesByNetworkId
> from InterfaceDao.
>
Correction: Something like GetVdsInterfacesByVdsIdQuery.
>
>
>>
>>>
>>>> FYI:- (I'm ran vdsm-cliend Host getCapablities and
>>>> getNetworkCapablities and it was returning correctly.)
>>>>
>>>
That's exactly the calls which are executed from engine during
host
monitoring
>>>> Regards,
>>>> Prajith.
>>>>
>>>>
>>> Hopefully this helps.
>>>
>>> Regards,
>>> Ales
>>>
>>>
>>>>
>>>> [image: image.png]
>>>> _______________________________________________
>>>> Devel mailing list -- devel(a)ovirt.org
>>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3LXPIMKJICG...
>>>>
>>>
>>>
>>> --
>>>
>>> Ales Musil
>>>
>>> Software Engineer - RHV Network
>>>
>>> Red Hat EMEA <https://www.redhat.com>
>>>
>>> amusil(a)redhat.com IM: amusil
>>> <https://red.ht/sig>
>>>
>>
>
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amusil(a)redhat.com IM: amusil
> <https://red.ht/sig>
>
--
Ales Musil
Software Engineer - RHV Network
Red Hat EMEA <https://www.redhat.com>
amusil(a)redhat.com IM: amusil
<https://red.ht/sig>
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/OAYTFQGQ2OB...
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
