ovirt rest api: how to get wwnn and wwnp of fiber channel of the KVM host managed by Ovirt manager using rest api
by Vivek Basappa
Hello, I am new to Ovirt , trying to dig through documentation, I am working on
integrating Hitachi SAN storage with Ovirt manager. working on Hitachi SAN storage
integration, I am trying to get WWNN and WWNP port details of the KVM Host using REST API.
but I am unable to find any documentations in REST API about that. I could see that
information in Ovirt Admin UI. how can I get this information trough REST API
any help is appreciated
4 years, 11 months
ansible-based host-deploy
by Yedidyah Bar David
Hi all,
I saw that recently some patches for $subject were merged to the
engine. Is ovirt-host-deploy now fully replaced? Would you like to
push a patch to the engine that removes the dependency on it? If not,
what's the status?
Thanks and best regards,
--
Didi
4 years, 11 months
ovirt rest api: how to get wwnn and wwnp of fiber channel of the KVM host managed by Ovirt manager using rest api
by Vivek Basappa
Hello, I am new to Ovirt , trying to dig through documentation, I am working on
integrating Hitachi SAN storage with Ovirt manager. working on Hitachi SAN storage
integration, I am trying to get WWNN and WWNP port details of the KVM Host using REST API.
but I am unable to find any documentations in REST API about that. I could see that
information in Ovirt Admin UI. how can I get this information trough REST API
any help is appreciated
4 years, 11 months
Engine builds are not passed to change queue for 4 days
by Martin Perina
Hi Nir,
I've just found out that your patch https://gerrit.ovirt.org/105020 broke
build-artifacts stage for engine, so no engine build can be passed to
change queue.
Here is the error:
*18:15:11* git ls-files | tar --files-from /proc/self/fd/0 -czf
"ovirt-engine-4.4.0_master.tar.gz" ovirt-engine.spec*18:15:11* tar:
.gitignore: Cannot stat: No such file or directory*18:15:11* tar:
Exiting with failure status due to previous errors
Could you fix asap?
Thanks,
Martin
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
4 years, 11 months
ovirt-engine - check-patch and build-artifacts diverged
by Sandro Bonazzola
Hi,
just noticed that over time check-patch and build-artifacts script diverged
significantly.
Due to this, check-patch passed on fc30 but failed after merge on
build-artifacts.
I'm fixing the immediate failure but a deeper review from java developers
would be helpful.
Thanks,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.*
4 years, 11 months
Change queue failing for 4 days
by Tal Nisan
Nir / Didi, it seems related to the gitignore patch you did in the make
script:
[2019-12-08T05:22:45.783Z] git ls-files | tar --files-from /proc/self/fd/0
-czf "ovirt-engine-4.4.0_master.tar.gz" ovirt-engine.spec
[2019-12-08T05:22:45.783Z] tar: .gitignore: Cannot stat: No such file or
directory
[2019-12-08T05:22:54.107Z] tar: Exiting with failure status due to previous
errors
[2019-12-08T05:22:54.107Z] make: *** [Makefile:361: dist] Error 2
https://jenkins.ovirt.org/job/ovirt-engine_standard-on-merge/337/consoleText
4 years, 11 months
Re: Ovirt and ZFS
by Fabio Zaltron
Any?
Zaltron Fabio
Via Rovigana, 34/A
35043 Monselice (PD)
E-mail: fz(a)corelink.it<mailto:fz@corelink.it>
Tel: (+39) 0429 1702612
Mob: (+39) 349 1048723
Web: www.corelink.it<http://www.corelink.it>
[LOGO SMALL]
Ai sensi del Regolamento (UE) 2016/679 relativo alla protezione delle persone fisiche con riguardo al trattamento dei dati personali, nonch? alla libera circolazione di tali dati (Regolamento generale sulla protezione dei dati) si avverte che le informazioni contenute in questo messaggio sono strettamente riservate ed esclusivamente indirizzate al destinatario indicato (oppure alla persona responsabile di rimettere il messaggio al destinatario), tenendo presente che qualsiasi uso, riproduzione o divulgazione di questo messaggio ? vietata. Nel caso in cui aveste ricevuto questo messaggio di posta per errore, vogliate avvertire il mittente al pi? presto a mezzo posta elettronica e subito dopo distruggerlo.
4 years, 11 months