7:13 p.m.
On Mon, Nov 14, 2022 at 6:29 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote:
Hey Didi,
thanks for the recap.
I hope that soon I will have some free time and I can more actively involve in the next
months.
Thanks!
I would like to get some hints about the Ansible code. How do we test it ?
Do you refer to [1] (engine-initiated, mainly host-deploy) or [2]
(most of the rest)?
I do not think there is any "unit-testing" for any of them. Much of
the code there is
tested as part of [3] - host-deploy code is ran by all suites there,
HE-deploy by the
he-basic suite, and some of the other ansible code by the ansible
suite. [3] used to
run on our jenkins server, and so I could (and did) point people to
successful runs
there (e.g. if there was a question about content of some log file or
whatever), but
now we don't, anymore. It does still run routinely in systems internal
to Red Hat.
Anyone can run it manually - and if you try and run into problems,
please report :-).
Thanks and best regards,
[1]
https://github.com/oVirt/ovirt-engine/tree/master/packaging/ansible-runne...
[2] https://github.com/oVirt/ovirt-ansible-collection/
[3] https://github.com/oVirt/ovirt-system-tests/
Best Regards,
Strahil Nikolov
On Mon, Nov 14, 2022 at 9:14, Yedidyah Bar David
<didi(a)redhat.com> wrote:
Hi all,
Red Hat Virtualization (RHV) recently entered maintenance phase[1],
and the RHV development team is gradually shifting its efforts over to
other projects.
We are still around, subscribed to the mailing lists, answering
questions and help as needed.
There is a strong trend in the industry towards containers and
microservices, and Red Hat's part of that is OpenShift. People that
want to use OpenShift and still need virtualization, until they
transition their workloads to run in containers, would best be served
by using OpenShift Virtualization. Following this, if you are an oVirt
user, you might want to try OKD Virtualization [2], the Community
Distribution of Kubernetes that powers Red Hat OpenShift, and Forklift
[3], a migration tool that facilitates the transition of VM workloads
from oVirt to OKD Virtualization.
We worked hard over the last year or so on making sure the oVirt
project will be able to sustain development even without much
involvement from us - including moving most of the infrastructure from
private systems that were funded by/for oVirt/RHV, elsewhere - code
review from Gerrit to GitHub, and CI (Continuous Integration) from
jenkins to GitHub/Copr/CentOS CBS.
We see lots of activity in the community both trying and using oVirt,
and helping each other, which is great!
We also see some work done on basing oVirt on Rocky/Alma Linux, which
is also great! We’ll be happy to help with this, where our specific
expertise is needed.
Ultimately, the future of oVirt lies in the hands of the community. If
you, as a community member, use and like oVirt, and want to see it
thrive, now is the best time to help with this!
In particular, we welcome long-time, active members of this list to
join the list moderation team. If you want to help with this, please
contact me directly, or email ovirt-users at ovirt.org.
I am posting this message to both lists - users and devel, separately
- deliberately not cross-posting. If you are subscribed to both, and
feel like replying, please choose the list that best matches the
content of your reply. Thanks! :-)
Best regards,
[1] https://access.redhat.com/support/policy/updates/rhev
[2] https://docs.okd.io/latest/virt/about-virt.html
[3] https://www.konveyor.io/tools/forklift/
--
Didi
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-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/users@ovirt.org/message/HEKKBM6MZEK...
--
Didi