Jump to: navigation, search

Difference between revisions of "StarlingX/Project Priorities"

(Project Priorities)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=== Project Priorities ===
 
=== Project Priorities ===
 +
 +
[https://etherpad.openstack.org/p/stx-2019.03-priorities This Etherpad] is the working document for updating this list for the next 6 months.
  
 
The following is an ordered list of our priorities from highest to lowest for the next six months.
 
The following is an ordered list of our priorities from highest to lowest for the next six months.
  
# Build stability & mirror cache / improvements
+
# Build stability & mirror cache / improvements.  Owner: Build sub-project
# Basic processes & infrastructure  e.g. CI/CD, Test/Validation, Releases, Dev, Bug handling, Security, Devstack, Zuul tests, unit tests, etc….
+
# Basic processes & infrastructure  Owner: Docs & Infra sub-project
# Documentation  e.g. project map, how to contribute, how to build/install, how to run, how to debug, ….
+
# Documentation  Owner: Docs & Infra sub-project
# Distro management - build, updates, automation, etc... How do we manage the package content? When / how do we upgrade to newer versions, newer versions of CentOS?
+
# Distro management.  Owners: Distro OpenStack subproject and Distro Non-OpenStack subproject
 +
## No OpenStack updates planned for 2018Rocky/Stein in 2019.
 +
## CentOS 7.5 update for Q4 2018 (October release)
 
## We will continually update components for CVE's.
 
## We will continually update components for CVE's.
## We want to keep as current (as possible) on key components (kernel, qemu/libvirt, etc...).  Is it time to move to CentOS 7.5?  To newer versions of qemu/libvirt?  Need the list of things to update (drivers, etc..).  Bruce to spin up a new sub-projects for CentOS 7.5 and qemu updates
+
## Ceph & qemu/libvirt to update to tip asap
# Patch backlog analysis and plan to address / close forks
+
# Patch backlog analysis and plan to address / close forks.  Owner Distro sub-projects
## Including how many patches per repo - some have very few, can we move to SRPM patches instead of repos?
+
# Disposition of StarlingX staging - find a long term home for those repos.  Owner Dean
# Disposition of StarlingX staging - find a long term home for those repos.   
+
# Project decoupling - make the services more self contained. Owner stx-* services sub-projects (the Flock)
## Long term we want to move away from needing them, but there will always be a set of patches to carry
+
# KPI establishment, test automation and on-going improvements.  Owner Test
## We need a plan for handling our kingbird repo since it's not really kingbird.  WR to create new repos that can hopefully be accepted
+
# Reduce patch backlog - openstack and non-openstack.  Owner Distro sub-projects
# Project decoupling - make the services more self contained
+
# Containerized OpenStack services support.  Owner Container subproject
# KPI establishment, test automation and on-going improvements
+
# Distributed Cloud (owner stx-dcloud)
# Reduce patch backlog - openstack and non-openstack
+
# Python 3 readiness.  Owner Distro-subprojects
# Python 3 readiness - new code is python3, repo by repo / file by file work neededzuul check jobs needed
+
# Package system independence Owner Non OpenStack Distro team (will need stx-update support)
# Container support
+
# Operating System independence Owner Non OpenStak Distro team
## Kubernetes integration
+
# Networking features Owner Networking sub-project
## Containerized OpenStack services
+
# Intel-specific features: SGX, EPID, integrations with Intel platforms and software Owner TBD
## Support for containerized workloads
 
# StarlingX Edge initiatives
 
## Beginnings of support for managing distributed Edge nodes, work being done by Greg in Edge working group
 
# Telemetry enhancements (collectd and gnocchi integration)
 
# PTP (Precision Time Protocol) support
 
# Networking features (containerized VNFs, ONAP integration, TSN (Time Senstive Networking), …)
 
# Intel-specific features: SGX, EPID, integrations with Intel platforms and software
 
# Package system independence
 
# Operating System independence
 

Latest revision as of 16:18, 18 October 2018

Project Priorities

This Etherpad is the working document for updating this list for the next 6 months.

The following is an ordered list of our priorities from highest to lowest for the next six months.

  1. Build stability & mirror cache / improvements. Owner: Build sub-project
  2. Basic processes & infrastructure Owner: Docs & Infra sub-project
  3. Documentation Owner: Docs & Infra sub-project
  4. Distro management. Owners: Distro OpenStack subproject and Distro Non-OpenStack subproject
    1. No OpenStack updates planned for 2018. Rocky/Stein in 2019.
    2. CentOS 7.5 update for Q4 2018 (October release)
    3. We will continually update components for CVE's.
    4. Ceph & qemu/libvirt to update to tip asap
  5. Patch backlog analysis and plan to address / close forks. Owner Distro sub-projects
  6. Disposition of StarlingX staging - find a long term home for those repos. Owner Dean
  7. Project decoupling - make the services more self contained. Owner stx-* services sub-projects (the Flock)
  8. KPI establishment, test automation and on-going improvements. Owner Test
  9. Reduce patch backlog - openstack and non-openstack. Owner Distro sub-projects
  10. Containerized OpenStack services support. Owner Container subproject
  11. Distributed Cloud (owner stx-dcloud)
  12. Python 3 readiness. Owner Distro-subprojects
  13. Package system independence Owner Non OpenStack Distro team (will need stx-update support)
  14. Operating System independence Owner Non OpenStak Distro team
  15. Networking features Owner Networking sub-project
  16. Intel-specific features: SGX, EPID, integrations with Intel platforms and software Owner TBD