Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Status - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbr... - Selective Feature Updates - FPGA Integration - Need to reduce scope. - Don't expect Distributed Cloud orchestration code to make it for stx.4.0. - Will limit the scope to flashing images thru the config subsystem via the system cmds. - Also have a dependency on Intel's most recent OPAE/SDK being upstreamed. - Ceph Containerization - Update from Austin - Team addressing some issues currently , it should be ready before May 29th. - system host-swact for duplex . - system backup/restore feature for containerization ceph - Requesting code review feedback - https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+conta... - Feature Testing - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRyp... - Noteables: - Ceph Rook: Need to re-work the test-cases - B&R: Waiting for a number of bug fixes; currently B&R is not working - TSN: Started to look into the documentation and building the kernel. Working to get setup ready to start testing. - Regression Testing - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiH... - Test team has concerns about completing regression in time - Robot automation is not running in a fully automated fashion - They were run previously in a semi-automated fashion where the tester would setup what the test needed manually - This is becoming very time consuming for the new test team as they don't have this background information - Investigating test failures to determine what is wrong - Team is also looking at re-implementing some of the test-cases in - Still need to assess the full impact of this on the release time-frame - Automated pytest is starting - Bugs - Need to start focusing on bug resolution - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 - Current Count: 90 - Add as a PSA in the community meeting Maintenance Releases - stx.2.x - Nobody in the community came back with a response that they are using stx.2.0 and need a maintenance release. - Agreed not to proceed with any stx.2.x maintenance releases - stx.3.x - No specific demand from the community for stx.3.x maintenance release - Got a response from one user (Volker von Hoesslin) saying stx.3.0 is working fine for him. His interest was more in the upgrade to stx.4.0 - Agreed to wait for the upgrades enabling code (see below) before considering an stx.3 maintenance release - Forecast post-June -- Daet to be confirmed later based on upgrades plan stx.3 to stx.4 Upgrades - Question (Bruce): What is required for this? - There is code that will be required on the stx.3 side to enable upgrades from the stx.3 side to the stx.4 side - This code is not ready yet. There is no plan yet as to when this will code will be ready. - Team has been focusing on the framework and allowing a "null" upgrade from stx.4 to stx.4 - This is the current commitment for stx.4.0 - The framework code is currently going in stx master - After stx.4.0 (end of June), team will look at what portion of code is required to be ported to the stx.3 release - The stx.3 code can be included in a maintenance release OR a user can make it into a patch if they want to avoid a re-install to the stx.3 maintenance release.