[Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020
Hi All: Thanks join the call. MoM for 2/19 meeting: - Prb update (JITStack-Wesley) --- build time any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.h... , currently no feedback from build team. - CentOS8 upgrade (Austin/Shuicheng) - incremental upgrade on master : * mock support (old gcc and new gcc ) , no solution yet. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007769.h... * new gcc will cause el7 rpm conflict or build failure. * std kernel build status update (kernel 4.18.0-80.11.2 on master env (gcc 4.8 +python2) do some minor changes , this kernel 4.18.0-80.11.2 built by gcc 4.8 , kernel can be built successfully AR: summary the changes and send to mail list. * rt kernel build status (kernel 4.18.0-147.3.1.rt24.96) , * 3.10 patch rebase , config update are remaining * python3 enable on master ? which is the preferred repo to upgrade to python3 besides NFV start this task now. * Ussuri host openstack (oslo , keystone , barbican , horizon and openstack client ) upgrade ? plan openstack client containerization no resource assign , some early study have been done by Stephan, timeline for Ussuri official release on CentOS8 should be risk . *the target , plan and goal on stx 4.0 feature ? target : end of March to finish kernel(std and rt) upgrade depends on centos8 rpms readiness (openstack), the minimum target is kernel upgrade . - any new stx.4.0 feature depends on kernel 4.18 ? - when will involve test team - how about centos8 branch ? shall we continue if we fully switch to incremental upgrade. keep centos8 branch, and do test on some user space rpms upgrade. - Vista Creek (FPGA card) support tarball/srpm issue need to be fixed by intel us team OPAE iavf and i40e driver . new driver integrated into stx. ---done . SRIOV device plugin --- no feedback yet . https://github.com/intel/sriov-network-device-plugin/pull/196 - Open Thanks. BR Austin Sun.
Hi all, Here is my AR for a quick update for the 4.18 std kernel with gcc-4.8.5. Meta patch for spec: Customize-4.18-kernel-with-centos-7-build-environmen.patch Source code patch: Fix-compile-error-with-gcc-4.8.5.patch Also CONFIG_KASAN=n is added to tis_extra config file, due to gcc-4.8.5 doesn't support -fsanitize=kernel-address. "BUILDSTDERR: scripts/Makefile.kasan:17: Cannot use CONFIG_KASAN: -fsanitize=kernel-address is not supported by compiler" Please notice it is tested with 4.18.0-80 kernel. And patch is expected to be updated with more test and 4.18.0-147 kernel. Best Regards Shuicheng -----Original Message----- From: Sun, Austin <austin.sun@intel.com> Sent: Wednesday, February 19, 2020 11:16 PM To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020 Hi All: Thanks join the call. MoM for 2/19 meeting: - Prb update (JITStack-Wesley) --- build time any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.h... , currently no feedback from build team. - CentOS8 upgrade (Austin/Shuicheng) - incremental upgrade on master : * mock support (old gcc and new gcc ) , no solution yet. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007769.h... * new gcc will cause el7 rpm conflict or build failure. * std kernel build status update (kernel 4.18.0-80.11.2 on master env (gcc 4.8 +python2) do some minor changes , this kernel 4.18.0-80.11.2 built by gcc 4.8 , kernel can be built successfully AR: summary the changes and send to mail list. * rt kernel build status (kernel 4.18.0-147.3.1.rt24.96) , * 3.10 patch rebase , config update are remaining * python3 enable on master ? which is the preferred repo to upgrade to python3 besides NFV start this task now. * Ussuri host openstack (oslo , keystone , barbican , horizon and openstack client ) upgrade ? plan openstack client containerization no resource assign , some early study have been done by Stephan, timeline for Ussuri official release on CentOS8 should be risk . *the target , plan and goal on stx 4.0 feature ? target : end of March to finish kernel(std and rt) upgrade depends on centos8 rpms readiness (openstack), the minimum target is kernel upgrade . - any new stx.4.0 feature depends on kernel 4.18 ? - when will involve test team - how about centos8 branch ? shall we continue if we fully switch to incremental upgrade. keep centos8 branch, and do test on some user space rpms upgrade. - Vista Creek (FPGA card) support tarball/srpm issue need to be fixed by intel us team OPAE iavf and i40e driver . new driver integrated into stx. ---done . SRIOV device plugin --- no feedback yet . https://github.com/intel/sriov-network-device-plugin/pull/196 - Open Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (2)
-
Lin, Shuicheng
-
Sun, Austin