Notes from today's meeting... Standing Topics - Gerrit review that need attention - OpenStack Train Upgrade Patches; Yong's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006838.h... - sanity - any reds since last call? - ISO 20191105: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006843.h... - Simplex Issue: 1851424 - didn't happen today, maybe fixed? - Storage Issue: 1851419 - didn't get this far today, failed on integ-apps apply fail - any unanswered calls for assistance on the mailing list - Sai Chandu: "Upload of application stx-openstack (1.0-17-centos-stable-latest) failed: Unsupported application version" - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.h... - Christopher said this doesn't look like a recent sanity issue - Yong said it could be a version mismatch - will show Sai Chandu how to confirm if this is it MS3 Blocking Issues - Intel K8S plugins for GPU and QAT - have not reached closure on design direction. Can we discuss and resolve here? (brucej) - (Ghada) The code merged does not align with the architectural direction. Unfortunately, this was not caught by the original code reviewers, but it was caught later by two TLs (Brent & Matt); both very familiar with this code area andthe architecture of StarlingX. Matt has proposed two options for a resolution: - (1) Revert the code and align with how labels were handled previously - (2) Inventory the devices and add semantic checks when the user is adding the labels - So we need the developer to proceed with implemeting one of these options. - Agreed with Ran that she will revert the code for now and work further on option 2 as a future enhancement. - VIM testing of the Train merge - who has these tests, who can run them (brucej for Yong) - per Bart - they're available to be run, with instructions - re: VIM test if any of the VIM API tests fail, the fix would *always* be done in the VIM - VIM test needs a particular lab setup - would take up to a day, there are instructions - how much OpenStack Regression did we run on Train? - to help us understand the risk of committing w/out running the VIM test suite - Ada to send the OpenStack Regression tests - Bart to review - Ghada asked about the VM connectivity issue - is it also seen in Train? - Yong wasn't sure if this had been seen in Train - we agreed to go ahead & commit Train then deal with whatever issues come up - some reviews to complete, per Yong's email Sanity and Regression Blockers - Need help with https://bugs.launchpad.net/starlingx/+bug/1851414 blocking regression testing (brucejj) - This is under investigation by the networking team - Huifeng as PL / Joseph as a developer - The follow-up action here is to add a VM connectivity test to sanity. This is basic functionality. This was raised before in the stx.2.0 timeframe. - Christopher confirmed that they are working on this - Need help with 1851419 and 1851424 found in Tuesday's Sanity run (brucej) -----Original Message----- From: Zvonar, Bill Sent: Tuesday, November 5, 2019 10:54 AM To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Community Call (Nov 6, 2019) Hi all, reminder of the Community call tomorrow. Please note that with the time change, this call moves to 3pm UTC - see [2] for the start time where you are. Feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Co... [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191106T1500