On Mon, Apr 6, 2020 at 9:48 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno dom 5 apr 2020 alle ore 19:32 Strahil Nikolov <hunter86_bg@yahoo.com> ha scritto:

Hey Sandro,

Can you clarify which CPUs will not be supported  in 4.4 ?

I can give the list of supported CPU according to ovirt-engine code:

select fn_db_add_config_value('ServerCPUList',
'1:Intel Nehalem Family:vmx,nx,model_Nehalem:Nehalem:x86_64; '
|| '2:Secure Intel Nehalem Family:vmx,spec_ctrl,ssbd,md_clear,model_Nehalem:Nehalem,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '3:Intel Westmere Family:aes,vmx,nx,model_Westmere:Westmere:x86_64; '
|| '4:Secure Intel Westmere Family:aes,vmx,spec_ctrl,ssbd,md_clear,model_Westmere:Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '5:Intel SandyBridge Family:vmx,nx,model_SandyBridge:SandyBridge:x86_64; '
|| '6:Secure Intel SandyBridge Family:vmx,spec_ctrl,ssbd,md_clear,model_SandyBridge:SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '7:Intel IvyBridge Family:vmx,nx,model_IvyBridge:IvyBridge:x86_64; '
|| '8:Secure Intel IvyBridge Family:vmx,spec_ctrl,ssbd,md_clear,model_IvyBridge:IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '9:Intel Haswell Family:vmx,nx,model_Haswell:Haswell:x86_64; '
|| '10:Secure Intel Haswell Family:vmx,spec_ctrl,ssbd,md_clear,model_Haswell:Haswell,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '11:Intel Broadwell Family:vmx,nx,model_Broadwell:Broadwell:x86_64; '
|| '12:Secure Intel Broadwell Family:vmx,spec_ctrl,ssbd,md_clear,model_Broadwell:Broadwell,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '13:Intel Skylake Client Family:vmx,nx,model_Skylake-Client:Skylake-Client:x86_64; '
|| '14:Secure Intel Skylake Client Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Client:Skylake-Client,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '15:Intel Skylake Server Family:vmx,nx,model_Skylake-Server:Skylake-Server:x86_64; '
|| '16:Secure Intel Skylake Server Family:vmx,spec_ctrl,ssbd,md_clear,model_Skylake-Server:Skylake-Server,+spec-ctrl,+ssbd,+md-clear:x86_64; '
|| '17:Intel Cascadelake Server Family:vmx,model_Cascadelake-Server:Cascadelake-Server,-hle,-rtm,+arch-capabilities:x86_64; '
|| '18:Secure Intel Cascadelake Server Family:vmx,md-clear,mds-no,model_Cascadelake-Server:Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities:x86_64; '
|| '1:AMD Opteron G4:svm,nx,model_Opteron_G4:Opteron_G4:x86_64; '
|| '2:AMD Opteron G5:svm,nx,model_Opteron_G5:Opteron_G5:x86_64; '
|| '3:AMD EPYC:svm,nx,model_EPYC:EPYC:x86_64; '
|| '4:Secure AMD EPYC:svm,nx,ibpb,ssbd,model_EPYC:EPYC,+ibpb,+virt-ssbd:x86_64; '
|| '1:IBM POWER8:powernv,model_POWER8:POWER8:ppc64; '
|| '2:IBM POWER9:powernv,model_POWER9:POWER9:ppc64; '
|| '1:IBM z114, z196:sie,model_z196-base:z196-base:s390x; '
|| '2:IBM zBC12, zEC12:sie,model_zEC12-base:zEC12-base:s390x; '
|| '3:IBM z13s, z13:sie,model_z13-base:z13-base:s390x; '
|| '4:IBM z14:sie,model_z14-base:z14-base:s390x;',
'4.4');

 
Also, does oVirt 4.4 support teaming or it is still staying with bonding. Network Manager was mentioned, but it's not very clear.

+Dominik Holler can you please reply to this?
 

oVirt stays with bonding.
Reasons why oVirt should support teaming are gathered in
Bug 1351510 - [RFE] Support using Team devices instead of bond devices
https://bugzilla.redhat.com/show_bug.cgi?id=1351510

 
What is the version of gluster bundled  with 4.4 ?

Latest Gluster 7 shipped by CentOS Storage SIG, right now it is 7.4 (https://docs.gluster.org/en/latest/release-notes/7.4/)

 

Best Regards,
Strahil Nikolov



--