[Starlingx-discuss] Minutes: StarlingX Release Meeting - May 28/2020

Khalil, Ghada Ghada.Khalil at windriver.com
Sat May 30 00:53:50 UTC 2020


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

stx.4.0
- Feature Status:  https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 
- Openstack Rebase to Ussuri (from community call)
      - As per Yong, testing complete and patches are up for review. Finishing off additional testing recommended by Frank
      - Concerns raised that there are stability issues with the openstack application apply/recovery & IPv6 in stx master right now and putting a major change in can cause even more issues.
      - Yong indicated an extra week is needed (Jun 5)
- Ceph Containerization (from community call)
      - As per Austin, the team is finishing up testing -- especially around backup & restore (some issues encountered and help requested)
      - More time needed. Agreed on an extra week (Jun 5)
      - Based on further discussion in the release meeting, there is concern about the impact of this large feature coming in that late in the release cycle. Also there have been changes in test resources which will impact feature testing. 
      - Given that there is no current user =explicitly waiting for this, we agreed as a community to defer to stx.5.0.
- Support for IPv6 pxeboot
      - Marked as Out. No response from the developer.
- Fault Containerization
      - Container team proposed to defer to stx.5.0. New team ramping up and making progress, but container team agreed that there is no need to rush.
- Features expected to finish shortly
      - FPGA  (note: Distributed Cloud Orchestration is defered to stx.5.0)
      - Decoupling container apps
- Features to checkpoint next week
      - Kubernetes Component Upversion - helm v3
      - Openstack Rebase to Ussuri
      - B&R
      - System Upgrades
      - Flock Versioning
- Prep / Ongoing Items -- no need to track these explicitly
      - Python3 - core reviewers to evaluate impact/risk on a per commit basis
      - Unit Tests - can continue / no functional impact
      - Bandit / Coverity - can continue / no functional impact
      - Regression Automation- can continue / no functional impact
- Complete / Dev Complete Features
      - Kata Containers
      - Active Directory Integration for K8s APIs
      - TSN support in kata container
      - Cert Manager Integration
      - OS Rebase to CentOS 8 - Kernel / Module Upgrade
      - Upversion Openstack services used by flock components on host
      - Kubernetes Upgrade Support
      - Redfish virtual media support
      - Layered Build



More information about the Starlingx-discuss mailing list