[ovirt-users] Single node hyper converged deployment best practices.

[Gilboa Davara]

Hello all,

> On Mon, May 11, 2020 at 7:10 PM Sandro Bonazzola  wrote:
 > Can you please detail what you're trying to achieve? sort of
hyperconverged deployment based on NFS instead of GlusterFS?
> If so, no, it's not officially supported.

Long story short: I've got a number of oVirt setups, a couple of "big"
GlusterFS based multi-node clusters (used for production) and a couple
of small single node ones (via localhost NFS) that are used to backup,
staging, testing, etc.

As I'm planning a (slow...) upgrade path to 4.4, what is the supported
/ best practice method to install oVirt on a single node? single-node
GlusterFS, localhost NFS or local file system (which I never tried for
no good reason)? Which tends to perform better?
I must admit that even with 20-30 active VMs (and a lot of IO), thus
far, localhost NFS served me (very) well.
BTW, per oVirt documentation [1], these no much information about the
preferred method.

[1] https://www.ovirt.org/documentation/admin-guide/chap-Storage.html

Thanks,
Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZQ2WYYA4KTYMSPB57JINROIEV4XWIE55/

[ovirt-users] Re: [Feedback needed] oVirt 4.4.0 Test week

[Gilboa Davara]

On Mon, May 11, 2020 at 7:10 PM Sandro Bonazzola  wrote:
>>
>> Hello,
>>
>> 1. Can I later upgrade 4.4RC to 4.4GA?
>
>
> It will require some additional steps but yes, it's supposed to be upgradable 
> from RC to GA.
> Actually, if no critical bug is found during this test week, RC can be 
> promoted to GA.

Thanks!

> Can you please detail what you're trying to achieve? sort of hyperconverged 
> deployment based on NFS instead of GlusterFS?
> If so, no, it's not officially supported.

Thanks. I have a followup question, but I'll move it to another thread.

- Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/3MW5WZCBVLB5D4G25ZIPHEAMOINMOFLQ/

[ovirt-users] Re: Can't add freshly installed node.. host has no default route

[Dominik Holler]

On Mon, May 11, 2020 at 12:31 PM Giorgio Biacchi 
wrote:

> Hi list,
> I've spent a couple of days trying to understand why this was happening...
>
> For the installation I have a well tested installation server with a
> custom kickstart file to setup ssh keys and custom hooks for infiniband
> and I'm installing Ovirt Node 4.3.9 via pxe, this is particularly useful
> when I have to install a bunch of blades at once.. In the past I had no
> issues and all was working like a charm until now when some hardware
> failed and I had to replace it.
>
> As expected I have no issues in the node installation process.. the
> troubles begins when I try to add the node, installation fails and in
> the UI I have an exclamation mark with the message "Host has no default
> route." but I can ping and do ssh to the host from the manager.. the
> problem is somewhere else in the communication between the engine and
> vdsmd preventing the engine to refresh the host capabilities.
>
> So from the engine I tried:
>
> [root@manager ~]# openssl s_client -connect 172.20.22.78:54321
> CONNECTED(0003)
> ---
> Certificate chain
>   0 s:/CN=cn128.lagrange.di.unimi.it/O=VDSM Certificate
> i:/CN=VDSM Certificate Authority
>   1 s:/CN=VDSM Certificate Authority
> i:/CN=VDSM Certificate Authority
> ---
>
> The host has still the self signed vdsm certificate.. and on the host in
> vdsm.log I find:
>
> 2020-05-11 09:52:25,433+ ERROR (Reactor thread)
> [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError,
> address: :::159.149.129.220 (sslutils:264)
>
> So I tried to enroll the certificate from the UI and from the events tab
> I sow the enrolling was successful but:
>
> [root@manager ~]# openssl s_client -connect 172.20.22.78:54321
>
> 140084336994192:error:140790E5:SSL routines:ssl23_write:ssl handshake
> failure:s23_lib.c:177:
> CONNECTED(0003)
> ---
> no peer certificate available
> ---
>
> there's still some issue with the certificates.. so on the host again:
>
> [root@cn128 vdsm]# find /etc/pki/vdsm/ -type f -cmin -10| xargs ls -l
> -rw---. 1 root kvm  1424 May 11 09:56 /etc/pki/vdsm/certs/cacert.pem
> -rw---. 1 root kvm  5108 May 11 09:57 /etc/pki/vdsm/certs/vdsmcert.pem
> -r--r-. 1 root kvm  1704 May 11 09:56 /etc/pki/vdsm/keys/vdsmkey.pem
> -rw-r--r--. 1 root root 1424 May 11 09:57
> /etc/pki/vdsm/libvirt-spice/ca-cert.pem
> -rw-r--r--. 1 root root 5108 May 11 09:57
> /etc/pki/vdsm/libvirt-spice/server-cert.pem
> -r--r-. 1 root root 1704 May 11 09:56
> /etc/pki/vdsm/libvirt-spice/server-key.pem
>
> It seems that cacert.pem and vdsmcert.pem have wrong permissions.. let's
> try to fix it..
>
> [root@cn128 vdsm]# chown 36:36 /etc/pki/vdsm/certs/cacert.pem
> /etc/pki/vdsm/certs/vdsmcert.pem
>
> And now:
>
> [root@manager ~]# openssl s_client -connect 172.20.22.78:54321| less
> CONNECTED(0003)
> ---
> Certificate chain
>   0 s:/O=lagrange.di.unimi.it/CN=172.20.22.78
> i:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941
>   1 s:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941
> i:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941
> ---
>
> Now I can finally refresh the host capabilities and setup the host
> networks..
>
> In attachment all the relevant logs, I don't know if I've found some
> bug.. this is the first time i had so many troubles adding a new host..
> so I decided to share my experience with the list..
>
>
Thanks for raising this.

On adding the host there is an error about  vdsm-hook-nestedvt which I
cannot interprete, maybe someone else can do.
In vdsm.log I noticed a strange behavior of setupNetworks, can you please
share the corresponding supervdsm.log, too?



> Cheers
> --
> gb
>
> PGP Key: http://pgp.mit.edu/
> Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/6JTU3HB4WCI27WSLGEOSLMPYFU22EX5H/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/LK47PGCYENSDO6LV7VRFPRO6UJEH2ASH/

[ovirt-users] Re: [ovirt-devel] oVirt and Fedora

[Michal Skrivanek]

> On 11 May 2020, at 14:49, Neal Gompa  wrote:
> 
> On Mon, May 11, 2020 at 8:32 AM Nir Soffer  wrote:
>> 
>> On Mon, May 11, 2020 at 2:24 PM Neal Gompa  wrote:
>>> 
>>> As far as the oVirt software keeping up with Fedora, the main problem here 
>>> has always been that people aren't integrating their software into the 
>>> distribution itself.

it was never a good fit for oVirt to be part of other distributions. We had 
individual packages part of Fedora in history, but there are things which are 
hard to accept (like automatically enabling of installed services, UIDs), and 
overall it’s just too complex, we’re rather a distribution than a simple app on 
top of base OS.

>>> That's how everything can get tested together. And this comes back to the 
>>> old bug about fixing vdsm so that it doesn't use /rhev, but instead 
>>> something FHS-compliant (RHBZ#1369102). Once that is resolved, pretty much 
>>> the entire stack can go into Fedora. And then you benefit from the Fedora 
>>> community being able to use, test, and contribute to the oVirt project. As 
>>> it stands, why would anyone do this for you when you don't even run on the 
>>> cutting edge platform that feeds into Red Hat Enterprise Linux?
>> 
>> This was actually fixed a long time ago. With this commit:
>> https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a09d
>> 
>> You can configure a compatible vdsm that does not use /rhev.
>> 
>> Of course it is not backward compatible, for this we need much more
>> work to support live migration
>> between old and new vdsm using different data-center configurations.
>> 
> 
> It'd probably be simpler to just *change* it to an FHS-compatible path
> going forward with EL8 and Fedora and set up a migration path there,
> but it's a bit late for that... :(

It wouldn’t. We always support live migration across several versions (now it’s 
4.2-4.4) and it needs to stay the same or youo have to go with arcane code to 
mangle it back and forth which gets a bit ugly when you consider 
suspend/resume, snapshots, etc

> 
> 
> -- 
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/SBAZ2F3FCOVGHRL7UNYTBLRX63BSBTCC/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SNM3D2ZBFXUQOA5PGU6FTLZOFYLJGM3V/

[ovirt-users] Re: [Feedback needed] oVirt 4.4.0 Test week

[Gianluca Cecchi]

On Mon, May 11, 2020 at 4:38 PM Joop  wrote:

> On 8-5-2020 13:23, Sandro Bonazzola wrote:
> > Hi,
> > oVirt team is planning to release oVirt 4.4.0 Ga in the next couple of
> > weeks.
> >
> I followed the same procedure as for the beta releases and have come
> across a new problem.
> Following the HCI setup using cockit in step 3 of deplying the VM
> ansible reports an error about missing /etc/pki/CA/cacert.pem which
> indeed does not exist.
> Can't find where this is supposed to come from and before creating my
> own and trying the install again I would like to know if I'm doing
> something wrong.
> In essence I installed Centos-8.1 from the link provided in the email.
>
> Regards,
>
> Joop
>
>
I have had a similar behaviour in one of my tests, but I have not
identified the reason.
I re-executed the deployment, after cleaning disks, apparently with same
parameters and all went good in the second attempt and the /etc/pki/CA/
structure had been created.
Unfortunately I scratched the first install to deploy over, but if you have
yet your files you can compare contents of messages and / or send to
developers, to compare what ewxpected by ansible and what happened actually.
The stage where it is created is around the end of prepare VM stage when
libvirtd is started on host.

For a successful configuration you would have this line in messages of host

May  8 16:44:50 novirt2 platform-python[27382]: ansible-command Invoked
with _raw_params=virsh -r net-dhcp-leases default | grep -i
00:16:3e:79:dc:d0 | awk '{ print $5 }' | cut -f1 -d'/' _uses_shell=True
warn=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None
executable=None creates=None removes=None stdin=None

with the temporary ip assigned to the local vm few lines under it

and around 10 minutes later you will have:

May  8 16:55:11 novirt2 ansible-async_wrapper.py[28148]: 28149 still
running (86225)
May  8 16:55:11 novirt2 python3[53024]: ansible-file Invoked with
dest=/etc/pki/libvirt/private state=directory owner=vdsm group=kv
m path=/etc/pki/libvirt/private recurse=False force=False follow=True
modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%
m%d%H%M.%S _original_basename=None _diff_peek=None src=None
modification_time=None access_time=None mode=None seuser=None serole=No
ne selevel=None setype=None attributes=None content=NOT_LOGGING_PARAMETER
backup=None remote_src=None regexp=None delimiter=None di
rectory_mode=None unsafe_writes=None
May  8 16:55:15 novirt2 python3[53956]: ansible-file Invoked with
dest=/etc/pki/libvirt/../CA state=directory owner=vdsm group=kvm
path=/etc/pki/libvirt/../CA recurse=False force=False follow=True
modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S
_original_basename=None _diff_peek=None src=None modification_time=None
access_time=None mode=None seuser=None serole=None selevel=None setype=None
attributes=None content=NOT_LOGGING_PARAMETER backup=None remote_src=None
regexp=None delimiter=None directory_mode=None unsafe_writes=None
May  8 16:55:16 novirt2 ansible-async_wrapper.py[28148]: 28149 still
running (86220)
May  8 16:55:17 novirt2 platform-python[54420]: ansible-ovirt_host_info
Invoked with pattern=name=novirt2.example.net auth={'token':
'Q56I1YcOPmPxQAPlXbNaB5hmXl8LcCWtSnGsrG3lTRIzo__crr_2RSKNo0e6C4TvmanadThlCCxSv5IhxOr5Ow',
'url': 'https://novengine2.example.net/ovirt-engine/api', 'ca_file': None,
'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False,
'headers': None} fetch_nested=False nested_attributes=[] all_content=False
cluster_version=None

In my failed run these latest lines were missing, but I didn't dig into
why... and then libvirtd was unable to start again because of the missing
CA

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/NELL3ZI74MFAOM4U42QGPNPJZAMSCRD2/

[ovirt-users] Re: [Feedback needed] oVirt 4.4.0 Test week

[Joop]

On 8-5-2020 13:23, Sandro Bonazzola wrote:
> Hi,
> oVirt team is planning to release oVirt 4.4.0 Ga in the next couple of
> weeks.
>
I followed the same procedure as for the beta releases and have come
across a new problem.
Following the HCI setup using cockit in step 3 of deplying the VM
ansible reports an error about missing /etc/pki/CA/cacert.pem which
indeed does not exist.
Can't find where this is supposed to come from and before creating my
own and trying the install again I would like to know if I'm doing
something wrong.
In essence I installed Centos-8.1 from the link provided in the email.

Regards,

Joop
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Q4L6L62UEKW2SHE522FJMSBYYPPDGDUV/

[ovirt-users] oVirt engine / node & snmp

[Andrei Verovski]

Hi,

oVirt node seems to run snmp by defeult, “service snmpd status” returns some 
data.
I’m going to connect all servers to LibreNMS, and it requires custom snmp 
options.
What options I should keep in oVirt node default nsmp.conf? Or I may just fully 
overwrite this file with my own?

Please note my oVirt node installed manually on CentOS, I don’t use node DVD 
image from oVirt project.


with best regards
Thanks in advance.
Andrei
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BBMLCEMMOKAO3DULZWVQ5VQGC7GPUDEC/

[ovirt-users] Re: [ovirt-devel] Re: oVirt and Fedora

[Neal Gompa]

On Mon, May 11, 2020 at 8:32 AM Nir Soffer  wrote:
>
> On Mon, May 11, 2020 at 2:24 PM Neal Gompa  wrote:
> >
> > As far as the oVirt software keeping up with Fedora, the main problem here 
> > has always been that people aren't integrating their software into the 
> > distribution itself. That's how everything can get tested together. And 
> > this comes back to the old bug about fixing vdsm so that it doesn't use 
> > /rhev, but instead something FHS-compliant (RHBZ#1369102). Once that is 
> > resolved, pretty much the entire stack can go into Fedora. And then you 
> > benefit from the Fedora community being able to use, test, and contribute 
> > to the oVirt project. As it stands, why would anyone do this for you when 
> > you don't even run on the cutting edge platform that feeds into Red Hat 
> > Enterprise Linux?
>
> This was actually fixed a long time ago. With this commit:
> https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a09d
>
> You can configure a compatible vdsm that does not use /rhev.
>
> Of course it is not backward compatible, for this we need much more
> work to support live migration
> between old and new vdsm using different data-center configurations.
>

It'd probably be simpler to just *change* it to an FHS-compatible path
going forward with EL8 and Fedora and set up a migration path there,
but it's a bit late for that... :(


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/SBAZ2F3FCOVGHRL7UNYTBLRX63BSBTCC/

[ovirt-users] Re: [ovirt-devel] Re: oVirt and Fedora

[Nir Soffer]

On Mon, May 11, 2020 at 2:24 PM Neal Gompa  wrote:
>
> On Mon, May 11, 2020 at 2:16 AM Sandro Bonazzola  wrote:
>>
>> If you have followed the oVirt project for a few releases you already know 
>> oVirt has struggled to keep the pace with the fast innovation cycles Fedora 
>> Project is following.
>>
>> Back in September 2019 CentOS project launched CentOS Stream as a rolling 
>> preview of future RHEL kernels and features, providing an upstream 
>> development platform for ecosystem developers that sits between Fedora and 
>> RHEL.
>>
>> Since then the oVirt project tried to keep the software working on Fedora, 
>> CenOS Stream, and RHEL/CentOS but it became quickly evident the project 
>> lacked resources to keep the project running on three platforms. Further, 
>> our user surveys show that oVirt users strongly prefer using oVirt on CentOS 
>> and RHEL.
>>
>> With the upcoming end of life of Fedora 30 the oVirt project has decided to 
>> stop trying to keep the pace with this amazing platform, focusing on 
>> stabilizing the software codebase on RHEL / CentOS Linux. By focusing our 
>> resources and community efforts on RHEL/CentOS Linux and Centos Stream, we 
>> can provide better support for those platforms and use more time for moving 
>> oVirt forward.
>>
>
> This is a humongous mistake. Almost everything with virtualization and 
> storage starts in Fedora. And there are some configurations that will not be 
> possible in CentOS Stream because of the nature of it.
>
> As far as the oVirt software keeping up with Fedora, the main problem here 
> has always been that people aren't integrating their software into the 
> distribution itself. That's how everything can get tested together. And this 
> comes back to the old bug about fixing vdsm so that it doesn't use /rhev, but 
> instead something FHS-compliant (RHBZ#1369102). Once that is resolved, pretty 
> much the entire stack can go into Fedora. And then you benefit from the 
> Fedora community being able to use, test, and contribute to the oVirt 
> project. As it stands, why would anyone do this for you when you don't even 
> run on the cutting edge platform that feeds into Red Hat Enterprise Linux?

This was actually fixed a long time ago. With this commit:
https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a09d

You can configure a compatible vdsm that does not use /rhev.

Of course it is not backward compatible, for this we need much more
work to support live migration
between old and new vdsm using different data-center configurations.

> It also seems like the oVirt folks are not learning from the mistakes of the 
> RDO project. They gave up on Fedora several years ago, and wound up spending 
> close to two years playing catchup on Python 3, DNF, modularity, 
> virtualization packaging changes, storage APIs, and everything else all at 
> once. They ground to a halt. They paid a price for not keeping up. And their 
> excuse of unaligned lifecycles stopped being true more than two years ago, 
> when OpenStack's release cycles aligned on Fedora's again. They also proved 
> that Fedora's "churn" wasn't the problem because when push comes to shove, 
> they were able to do something based on Fedora 28 (knowing it was the base 
> for RHEL 8).
>
> CentOS Stream is worthless in most respects because you aren't really testing 
> or integrating anything new most of the time, you're just making new releases 
> of your software on a stale platform. Again, the purpose of CentOS Stream is 
> to provide a window into the RHEL stream development, which by the nature of 
> things isn't very useful for future-proofing.
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/JM5UNXG6YI7R23NUR5LLW3TV3KDMPU2A/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/M47LI42YTFRCMNW5YTYVAYBXO277JXCN/

[ovirt-users] Re: [ovirt-devel] oVirt and Fedora

[Neal Gompa]

On Mon, May 11, 2020 at 2:16 AM Sandro Bonazzola 
wrote:

> If you have followed the oVirt project for a few releases you already know
> oVirt has struggled to keep the pace with the fast innovation cycles Fedora
> Project is following.
>
> Back in September 2019 CentOS project launched CentOS Stream as a rolling
> preview of future RHEL kernels and features, providing an upstream
> development platform for ecosystem developers that sits between Fedora and
> RHEL.
>
> Since then the oVirt project tried to keep the software working on Fedora,
> CenOS Stream, and RHEL/CentOS but it became quickly evident the project
> lacked resources to keep the project running on three platforms. Further,
> our user surveys show that oVirt users strongly prefer using oVirt on
> CentOS and RHEL.
>
> With the upcoming end of life of Fedora 30 the oVirt project has decided
> to stop trying to keep the pace with this amazing platform, focusing on
> stabilizing the software codebase on RHEL / CentOS Linux. By focusing our
> resources and community efforts on RHEL/CentOS Linux and Centos Stream, we
> can provide better support for those platforms and use more time for moving
> oVirt forward.
>
>
This is a *humongous* mistake. Almost *everything* with virtualization and
storage *starts* in Fedora. And there are some configurations that will
*not* be possible in CentOS Stream because of the nature of it.

As far as the oVirt software keeping up with Fedora, the main problem here
has always been that people aren't integrating their software into the
distribution itself. That's how everything can get tested together. And
this comes back to the old bug about fixing vdsm so that it doesn't use
/rhev, but instead something FHS-compliant (RHBZ#1369102
). Once that is resolved, pretty much
the entire stack can go into Fedora. And then you benefit from the Fedora
community being able to use, test, and contribute to the oVirt project. As
it stands, why would anyone do this for you when you don't even run on the
cutting edge platform that feeds into Red Hat Enterprise Linux?

It also seems like the oVirt folks are not learning from the mistakes of
the RDO project. They gave up on Fedora several years ago, and wound up
spending close to two years playing catchup on Python 3, DNF, modularity,
virtualization packaging changes, storage APIs, and everything else all at
once. They ground to a *halt.* They paid a price for not keeping up. And
their excuse of unaligned lifecycles stopped being true more than two years
ago, when OpenStack's release cycles aligned on Fedora's again. They also
proved that Fedora's "churn" wasn't the problem because when push comes to
shove, they were able to do something based on Fedora 28 (knowing it was
the base for RHEL 8).

CentOS Stream is worthless in most respects because you aren't really
testing or integrating anything new most of the time, you're just making
new releases of your software on a stale platform. Again, the purpose of
CentOS Stream is to provide a window into the RHEL stream development,
which by the nature of things isn't very useful for future-proofing.


-- 
真実はいつも一つ！/ Always, there's only one truth!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/JM5UNXG6YI7R23NUR5LLW3TV3KDMPU2A/

[ovirt-users] Re: [Feedback needed] oVirt 4.4.0 Test week

[Gilboa Davara]

On Fri, May 8, 2020 at 2:28 PM Sandro Bonazzola  wrote:
>
> Hi,
> oVirt team is planning to release oVirt 4.4.0 Ga in the next couple of weeks.
> oVirt 4.4.0 release candidate was released yesterday and we'd like to gather 
> as much feedback as possible.
> Please join us testing this release candidate next week, starting Sunday May 
> 10th 2020 till Friday May 15th 2020!
> We are going to coordinate the testing effort with a public Trello board at 
> https://trello.com/b/5ZNJgPC3/ovirt-440-test-day
> You'll find instructions on how to use the board there.
> For joining the board you can use this link: 
> https://trello.com/invite/b/5ZNJgPC3/f1b1826ee4902f348c44607765a15099/ovirt-440-test-day
>
> If you have not an environment dedicated to testing, remember you can set up 
> a few VMs and test the deployment with nested virtualization using your 
> production environment creating a virtual test environment. In this case 
> please be careful avoiding touching the production environment from the 
> testing one.
>
> The oVirt team will monitor the Trello board, the #ovirt IRC channel on 
> irc.oftc.net server and the users@ovirt.org mailing list to assist with the 
> testing and debugging issues.
> Basic instructions for setting up a minimal system are available in release 
> candidate announce at: 
> https://lists.ovirt.org/archives/list/annou...@ovirt.org/message/3QORBKVKTALNJ5SMJHEDO4QJ5YUCULTT/attachment/3/attachment.html
> Release notes for this release candidate are available here: 
> https://ovirt.org/release/4.4.0/
>
> Thanks

Hello,

1. Can I later upgrade 4.4RC to 4.4GA?
2. I plan to deploy yet-another-single-host setup (via NFS), is it
officially supported by 4.4 RC?

- Gilboa
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/U3W74GRRT7Q2SVSQAVTAS77SJXRDDI5J/

[ovirt-users] Re: Ubuntu 18.04 and 16.04 cloud images hang at boot up

[Jp]

Worked for me.

Thx Florian!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/JYC3LC2EBXRM7ONGZWKJJE5OVOR6T36F/

[ovirt-users] Unable to connect to cockpit

[Parth Dhanjal]

Hey!

I have a remote machine on which I have installed RHVH4.4
I'm unable to access the cockpit-plugin.
journalctl -u cockpit returns this error

cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received.


Screenshot while trying to reach cockpit through the browser attached.

Is anyone else facing this issue as well?
And does anyone has a solution/workaround to this?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/POYO4WEFLTSHLMDZ5WNQGAJ3SE245I3S/

[ovirt-users] Re: [ovirt-devel] oVirt and Fedora

[Nir Soffer]

On Mon, May 11, 2020 at 10:01 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 11 mag 2020 alle ore 08:50 Nir Soffer 
> ha scritto:
>
>> On Mon, May 11, 2020 at 9:16 AM Sandro Bonazzola 
>> wrote:
>>
>>> If you have followed the oVirt project for a few releases you already
>>> know oVirt has struggled to keep the pace with the fast innovation cycles
>>> Fedora Project is following.
>>>
>>> Back in September 2019 CentOS project launched CentOS Stream as a
>>> rolling preview of future RHEL kernels and features, providing an upstream
>>> development platform for ecosystem developers that sits between Fedora and
>>> RHEL.
>>>
>>> Since then the oVirt project tried to keep the software working on
>>> Fedora, CenOS Stream, and RHEL/CentOS but it became quickly evident the
>>> project lacked resources to keep the project running on three platforms.
>>> Further, our user surveys show that oVirt users strongly prefer using oVirt
>>> on CentOS and RHEL.
>>>
>>> With the upcoming end of life of Fedora 30 the oVirt project has decided
>>> to stop trying to keep the pace with this amazing platform, focusing on
>>> stabilizing the software codebase on RHEL / CentOS Linux. By focusing our
>>> resources and community efforts on RHEL/CentOS Linux and Centos Stream, we
>>> can provide better support for those platforms and use more time for moving
>>> oVirt forward.
>>>
>>
>> Where was this discussed?
>>
>> There is nothing about this in de...@ovirt.org or any other public
>> mailing list.
>>
>> I think this is a big mistake. It will mainly harm development since
>> Fedora is the only platform where
>> we can test early upstream changes, many months (and sometimes years)
>> before the packages reach
>> RHEL/CentOS.
>>
>> Nir
>>
>
> It has been discussed within team leads meeting and made clear by replies
> we keep giving when someone ask about Fedora.
> See "[ovirt-users] install oVirt on Fedora31", "[ovirt-users] oVirt orb
> python3/fedora 31 support".
>
> This doesn't mean that individual developers can try to get their packages
> working on Fedora or test their code on Fedora.
> This means that we are not committed to keep trying to support Fedora as a
> project.
>

Again, there was no discussion about this in public, but we can start the
discussion here.

The result of such a change is that soon there will be no way to install
vdsm on Fedora,
because we need only one maintainer that does not care about Fedora.

Then we cannot test vdsm with upstream libvirt and qemu, which will harm
our ability to develop
features like incremental backup, which was developed in the last year on
Fedora, using upstream
libvirt and qemu or upstream patches.

Another example, if you want to test sanlock fixes that will be available
in RHEL 8.3, the only way
to do this now is on Fedora - the fixes are available in updates-testing.
So we can make sure our
code is compatible with new sanlock now, or wait until 8.3 is out and find
about regressions
very late before the release.

This is a common trend  in the last 6.5 years - oVirt is not tested on
Fedora (e.g. no ovirt
systems on Fedora), leading to late detection of issues, and regressions in
new versions
in RHEL/CentOS.

What we should do instead is focus on Fedora support and testing early
upstream packages.

Currently oVirt is tested on CentOS 8.1, which is irrelevant to oVirt 4.4.
What we really need
is to test on RHEL 8.2 nightly builds, but this is not available to the
public and cannot be
used by an upstream project. But Fedora 32 is available and includes all
the packages
needed for valuable testing, so this should be our main platform for
testing.

CentOS stream could be a good solution for testing, if we could get the
advanced virt module
*before* the module is released in RHEL. Otherwise we test on old version
and we don't detect
issues in time.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/7VNRYA4773D7APLDO74DL22YBT4H5G65/

[ovirt-users] Re: [ovirt-devel] oVirt and Fedora

[Nir Soffer]

On Mon, May 11, 2020 at 9:16 AM Sandro Bonazzola 
wrote:

> If you have followed the oVirt project for a few releases you already know
> oVirt has struggled to keep the pace with the fast innovation cycles Fedora
> Project is following.
>
> Back in September 2019 CentOS project launched CentOS Stream as a rolling
> preview of future RHEL kernels and features, providing an upstream
> development platform for ecosystem developers that sits between Fedora and
> RHEL.
>
> Since then the oVirt project tried to keep the software working on Fedora,
> CenOS Stream, and RHEL/CentOS but it became quickly evident the project
> lacked resources to keep the project running on three platforms. Further,
> our user surveys show that oVirt users strongly prefer using oVirt on
> CentOS and RHEL.
>
> With the upcoming end of life of Fedora 30 the oVirt project has decided
> to stop trying to keep the pace with this amazing platform, focusing on
> stabilizing the software codebase on RHEL / CentOS Linux. By focusing our
> resources and community efforts on RHEL/CentOS Linux and Centos Stream, we
> can provide better support for those platforms and use more time for moving
> oVirt forward.
>

Where was this discussed?

There is nothing about this in de...@ovirt.org or any other public mailing
list.

I think this is a big mistake. It will mainly harm development since Fedora
is the only platform where
we can test early upstream changes, many months (and sometimes years)
before the packages reach
RHEL/CentOS.

Nir
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6CP7NPGHRFBULBWLD67HNHQWY4WEMZER/