[Starlingx-discuss] Minutes: StarlingX Release Meeting - Mar 12/2020

Khalil, Ghada Ghada.Khalil at windriver.com
Mon Mar 16 17:04:14 UTC 2020


Agenda/Minutes are posted at:
https://etherpad.openstack.org/p/stx-releases  

stx.4.0
- Milestone-2 is planned for March 27
- Milestone-2 Criteria
          - Spec freeze; no new specs accepted for the release. The focus is on closing current specs
          - Feature plans defined and feature development well underway
                    - See Feature Plans google sheet: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 
                    - See Feature Notes for a subset of features below
          - Release test plan defined - including test automation deliverables
                    - There is risk regarding test in Intel due to hardware availability. Current target date is middle of April.
                    - Server dates are committed, but still working on switching and other infrastructure
                    - Servers can be utilized to setup a virtual environment to start

- Features Awaiting Confirmation / Updates:
          - Python2>>3 Migration - Ongoing?
                    - There are no python3 packages for everything we need.
                    - This is Partial at best, but would likely be considered out
                    - As of now, there is no python3 environment on the host yet. This would be the absolute first required step to move 
                    - Action: Bruce to follow up with Austin.
                    - Don: We have a couple of modules/daemons that should be straightforward to move to python3.
                                - I would start with tsconfig, creating and installing both a python2-tsconfig and a python3-tsconfig. This module is mostly constants, shared amongst STX services, along with a config file parser, and would be needed by most STX python services.
                                - Simple daemons like utilities/logmgmt and update/patch-alarm are probably good choices for early conversion, although patch-alarm would have a dependency on FM.

          - Upversion Openstack to Ussuris release
                    - From Yong (3/16): For Containerized OpenStack Services upgrading to "U", it's started and made good progress in past 2 weeks, so it will be a GO for stx.4.0.

          - Upversion Openstack services used by flock components on host
                    - From Yong (3/16): For 3 OpenStack services (keystone, horizon and barbican) on platform, we have no way to upgrade it to "U" because of the dependencies on CentOS 8 user space packages, which we decided 2 weeks ago in the meet-up  not to upgrade in stx.4.0. The alternative could be we upgrade to "Train" from the current "Stein". I will send a mail to the mailing-list to ask if everybody thinks it's valuable and worthy for stx.4.0.

          - Distributed Cloud - openstack
                    - This is Out. Resources are focused on upgrades

          - Containerize Openstack clients
                    - As per Bruce, TBD. Still need to look at resourcing

          - System Upgrade support
                    - Actively being worked. Consider as In w/ Risk.
                    - Currently working on spec and will update merge/feature test dates 

          - IPv6 support for PXE boot network
                    - Appears that 99cloud prime is starting to investigate. Questions posted to mailing list.

          - Regression Test Automation
                    - This is an ongoing initiative. WR is planning to contribute some additional test-cases. These TCs can be run by anyone in the open once they setup the required env.

          - Performance Test Automation
                    -  Best effort for Intel, but should be considered out due to focus on other release test activities.

          - Code Scans using Bandit & Coverity
                    - This has been transitioned to the Intel Bangalore team. At a minimum, would like to get initial results for review/analysis.
                    - Timeline is TBD




More information about the Starlingx-discuss mailing list