April 2022 - openstack-discuss - lists.openstack.org

[all][tc] Change OpenStack release naming policy proposal
by Slawek Kaplonski 04 Jun '22

04 Jun '22

Hi, During the last PTG in April 2022 in the TC meeting we were discussing our release naming policy [1]. It seems that choosing appropriate name for every releases is very hard and time consuming. There is many factors which needs to be taken into consideration there like legal but also meaning of the chosen name in many different languages. Finally we decided that now, after Zed release, when we will go all round through alphabet it is very good time to change this policy and use only numeric version with "year"."release in the year". It is proposed in [2]. This is also good timing for such change because in the same release we are going to start our "Tick Tock" release cadence which means that every Tick release will be release with .1 (like 2023.1, 2024.1, etc.) and every Tock release will be one with .2 (2023.2, 2024.2, etc.). [1] https://etherpad.opendev.org/p/tc-zed-ptg#L265[1] [2] https://review.opendev.org/c/openstack/governance/+/839897[2] -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://etherpad.opendev.org/p/tc-zed-ptg#L265 [2] https://review.opendev.org/c/openstack/governance/+/839897

16 42

[Neutron][neutron-vpnaas] proposing Mohammed Naser for neutron-vpnaas core reviewer
by Lajos Katona 13 May '22

13 May '22

Hi, I would like to propose Mohammed Naser (mnaser) as a core reviewer to neutron-vpnaas. He and his company uses neutron-vpnaas in production and volunteered to help in the maintenance of it. You can vote/feedback in this email thread. If there is no objection by 6th of May, we will add Mohammed to the core list. Thanks Lajos

6 6

[all][tc][policy][heat][cinder] Continuing the RBAC PTG discussion + policy pop-up meeting new time
by Ghanshyam Mann 11 May '22

11 May '22

Hello Everyone, As we said in PTG about continuing the RBAC discussion on open questions (currently from Heat and Cinder), we are scheduling the call on April 26 Tuesday from 14:30-15:00 UTC. And we will use the same time for the policy-popup team meeting every alternate Tuesday to answer RBAC queries from any projects. Meeting Details: - https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… Agenda (you can add for this or coming meetings) - https://etherpad.opendev.org/p/rbac-zed-ptg#L97 -gmann

1 2

[TripleO] Tear down of Train centOS 7 check jobs and integration line
by Ronelle Landy 09 May '22

09 May '22

Hello All, We have been running check/gate testing and integration lines for the Train release on both CentOS7 and CentOS 8. Following the work on CentOS 9 and the longevity of the Train release, we proposed removing the CentOS 7 Train jobs and building/testing changes to this release on CentOS 8 only. We floated this proposal with some interested parties and received no objections so we are beginning work on this tear down. We anticipate that removing the CentOS 7 jobs will allow patches to merge quicker and will free up resources for future work. Please respond if you have any questions or concerns. Thanks, Ronelle (for the TripleO CI team)

2 2

[manila] Zed cycle bug squash
by Carlos Silva 06 May '22

06 May '22

Greetings Zorillas and interested stackers! As mentioned in the previous weekly meetings, we will soon be meeting for the first bugsquash of the Zed release! The event will be held from May 2nd to May 6th, providing an extended contribution window. May 2nd 15:00 - 16:00 UTC - Kick off May 5th 15:00 - 16:00 UTC - Mid term checkpoint (we won't have our regular Manila meeting on this day) May 6th 15:00 - 15:30 UTC - Wrap Up We will use a meetpad for these meetings [1]. The main idea of this event is to go over the list of stale bugs and act on them, either seeing if they are incomplete or invalid at this point or working on them. The stale bugs list will be available on [2]. [1] https://meetpad.opendev.org/ManilaZed1Bugsquash [2] https://ethercalc.openstack.org/1nesczgjufb9 See you next week! Thank you, carloss

1 1

[all][tc][Release Management] Improvements in project governance
by Slawek Kaplonski 05 May '22

05 May '22

Hi, During the Zed PTG sessions in the TC room we were discussing some ideas how we can improve project governance. One of the topics was related to the projects which don't really have any changes in the cycle. Currently we are forcing to do new release of basically the same code when it comes to the end of the cycle. Can/Should we maybe change that and e.g. instead of forcing new release use last released version of the of the repo for new release too? If yes, should we then automatically propose change of the release model to the "independent" maybe? What would be the best way how Release Management team can maybe notify TC about such less active projects which don't needs any new release in the cycle? That could be one of the potential conditions to check project's health by the TC team. Another question is related to the projects which aren't really active and are broken during the final release time. We had such problem in the last cycle, see [1] for details. Should we still force pushing fixes for them to be able to release or maybe should we consider deprecation of such projects and not to release it at all? [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027864.ht… -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027864.ht…

4 4

[api=sig][i18n][infra][tc] Cleaning up more defunct mailing lists
by Jeremy Stanley 04 May '22

04 May '22

A quick audit of the mailing lists we host at lists.openstack.org turned up the following 11 which have had no new posts for at least three years now: * openstack-api-consumers * openstack-de * openstack-el * openstack-i18n-fr * openstack-ir * openstack-personas * openstack-ru * openstack-sos * openstack-tw * openstack-vi * third-party-announce I'd like to clean them up by removing their list configurations, but leaving any public archives intact. Are there any objections? Should any of the above have future messages redirected to a different list (though since they haven't had any for years, that's probably unnecessary)? -- Jeremy Stanley

5 8

question -dashboard horizon
by mahdi n 04 May '22

04 May '22

I login-ed in horizon but in page project http://ip:8000/project show error that : You are not authorized to access this page please login screenshot how to solve this?

4 4

[all][tc] What's happening in Technical Committee: summary April 29th, 22: Reading: 5 min
by Ghanshyam Mann 30 Apr '22

30 Apr '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on April 28. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-04-21-15.00.html * Next TC weekly meeting will be on May 5 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by May 4. We will cover CFN and tick-tock release notes topic there and if time permits then cover any othe topic. 2. What we completed this week: ========================= * Resolution to drop the lower constraints maintenance[2] * Remove TC Liaisons framework[3] * Retired openstack-helm-docs[4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], we have started the many items. Open Reviews ----------------- * Seven open reviews for ongoing activities[6]. Change OpenStack release naming policy proposal ----------------------------------------------------------- We discussed it it PTG, TC decided to drop the name from release name process and keping the numbers. Slaweq proposed it on gerrit[7] and on ML[8]. Discussion is in progress as there are some objection from foundation marketting team. Migration from old ELK service to new Dashboard ----------------------------------------------------------- You might have seen that Daniel email about the new dashboard[9] and login information, we encourage community members to use it and provide feedback if any. Dainel also investigation about the e-r instance. Consistent and Secure Default RBAC ------------------------------------------- We discussed about the heat mostly in Tuesday call but could not get any consensus. Notes are in etherpad[10] and will continue the discussion on Tuesday 3rd May 14:00 UTC [11], FIPs community-wide goal ------------------------------- Ade has proposed the new milestone for this goal work, please review those and give feedback if any[12]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's situation again on ML and hope Braden will be ready with their company side permission[14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * Add the cinder-three-par charm to Openstack charms[16] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/838004 [3] https://review.opendev.org/c/openstack/governance/+/837891 [4] https://review.opendev.org/c/openstack/governance/+/839100 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://review.opendev.org/c/openstack/governance/+/839897 [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028354.ht… [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028346.ht… [10] https://etherpad.opendev.org/p/rbac-zed-ptg#L103 [11] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… [12] https://review.opendev.org/c/openstack/governance/+/838601 [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] https://review.opendev.org/c/openstack/governance/+/837781 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[dev][infra][tact-sig] Retiring the status.openstack.org server
by Jeremy Stanley 30 Apr '22

30 Apr '22

With the recent retirement of the Elastic-Recheck and OpenStack-Health services, as well as Zuul long ago growing its own status dashboard, the only other thing still being served from the status.openstack.org site is a very broken and empty ReviewDay interface. I'm planning to take status.openstack.org offline at the end of this month (late next week), so wanted to give everyone a heads up that anything still served from that site right now (basically just a link to the Zuul status page for our openstack tenant) will be going away. If you want the Zuul status page for openstack, the proper URL is https://zuul.opendev.org/t/openstack/status or you can just go to the root of the site and click the "status" link in the openstack tenant row. (There's also a white-label zuul.openstack.org site but that's primarily maintained in order to avoid breaking old tools people may have hard-coded to use it.) -- Jeremy Stanley

1 1