[tc][uc][all] Starting community-wide goals ideas for V series

Ghanshyam Mann gmann at ghanshyammann.com
Mon Jun 15 17:57:25 UTC 2020


Hello Everyone,

Sending the final updates on Victoria cycle goal selection(on top of email for easy read).

community-wide goals for Victoria cycle are finalized:
- https://governance.openstack.org/tc/goals/selected/victoria/index.html

Selected goals for Victoria cycle:
----------------------------------------
1. Switch legacy Zuul jobs to native
- https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-jobs.html

2. Migrate CI/CD jobs to new Ubuntu LTS Focal
- https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal.html

Please start planning to work on those goals if not yet done.

TC will be starting the W cycle goals process soon.

-gmann & njohnston


 ---- On Tue, 05 May 2020 13:03:59 -0500 Ghanshyam Mann <gmann at ghanshyammann.com> wrote ----
 >  ---- On Thu, 30 Apr 2020 06:20:29 -0500 Thomas Goirand <zigo at debian.org> wrote ----
 >  > On 2/5/20 7:39 PM, Ghanshyam Mann wrote:
 >  > > Hello everyone,
 >  > > 
 >  > > We are in R14 week of Ussuri cycle which means It's time to start the
 >  > > discussions about community-wide goals ideas for the V series.
 >  > > 
 >  > > Community-wide goals are important in term of solving and improving a technical
 >  > > area across OpenStack as a whole. It has lot more benefits to be considered from
 >  > > users as well from a developers perspective. See [1] for more details about
 >  > > community-wide goals and process.
 >  > > 
 >  > > We have the Zuulv3 migration goal already accepted and pre-selected for v cycle.
 >  > > If you are interested in proposing a goal, please write down the idea on this etherpad[2]
 >  > > - https://etherpad.openstack.org/p/YVR-v-series-goals 
 >  > > 
 >  > > Accordingly, we will start the separate ML discussion over each goal idea.
 >  > > 
 >  > > Also, you can refer to the backlogs of community-wide goals from this[3] and ussuri
 >  > > cycle goals[4].
 >  > > 
 >  > > NOTE: TC has defined the goal process schedule[5] to streamlined the process and
 >  > > ready with goals for projects to plan/implement at the start of the cycle. I am
 >  > > hoping to start that schedule for W cycle goals.
 >  > > 
 >  > > [1] https://governance.openstack.org/tc/goals/index.html
 >  > > [2] https://etherpad.openstack.org/p/YVR-v-series-goals
 >  > > [3] https://etherpad.openstack.org/p/community-goals
 >  > > [4] https://etherpad.openstack.org/p/PVG-u-series-goals
 >  > > [5] https://governance.openstack.org/tc/goals/#goal-selection-schedule
 >  > > 
 >  > > -gmann
 >  > 
 >  > I've added 3 major paint points to the etherpad which I think are very
 >  > important for operators:
 >  > 
 >  > 8. Get all services to systemd-notify
 >  > 
 >  > 9. Make it possible to reload service configurations dynamically without
 >  > restarting daemons
 >  > 
 >  > 10. All API to provide a /healthcheck URL (like the Keystone one...).
 >  > 
 >  > I don't have the time to implement all of this, but that's still super
 >  > useful things to have. Does anyone have the time to work on this?
 > 
 > #10 looks interacting to me and useful from the user's point of view. I can help with this. 
 > Key thing will be do we need more generic backends than file existence one, for example, DB checks
 > or service-based backends.
 > 
 > But we can discuss all those details in separate threads, thanks for bringing this. 
 > 
 > -gmann
 > 
 >  > 
 >  > Cheers,
 >  > 
 >  > Thomas Goirand (zigo)
 >  > 
 >  > 
 > 
 > 



More information about the openstack-discuss mailing list