February 2021 - openstack-discuss

[PTLs][release] Wallaby Cycle Highlights
by Kendall Nelson 16 Mar '21

16 Mar '21

Hello Everyone! It's time to start thinking about calling out 'cycle-highlights' in your deliverables! I have no idea how we are here AGAIN ALREADY, alas, here we be. As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Stein[1], Train[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. *The deadline for cycle highlights is the end of the R-5 week [3] (next week) on March 12th.* How To Reminder: ------------------------- Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/highlights.html. Feel free to add me as a reviewer on your patches. Can't wait to see you all have accomplished this release! Thanks :) -Kendall Nelson (diablo_rojo) [1] https://releases.openstack.org/stein/highlights.html [2] https://releases.openstack.org/train/highlights.html [3] htt <https://releases.openstack.org/train/schedule.html#t-cycle-highlights> https://releases.openstack.org/wallaby/schedule.html <https://releases.openstack.org/ussuri/schedule.html>

2 6

[all][tc] Thoughts on Python 3.7 support
by Pierre Riteau 11 Mar '21

11 Mar '21

Hello, There have been many patches submitted to drop the Python 3.7 classifier from setup.cfg: https://review.opendev.org/q/%2522remove+py37%2522 The justification is that Wallaby tested runtimes only include 3.6 and 3.8. Most projects are merging these patches, but I've seen a couple of objections from ironic and horizon: - https://review.opendev.org/c/openstack/python-ironicclient/+/769044 - https://review.opendev.org/c/openstack/horizon/+/769237 What are the thoughts of the TC and of the overall community on this? Should we really drop these classifiers when there are no corresponding CI jobs, even though more Python versions may well be supported? Best wishes, Pierre Riteau (priteau)

9 13

[horizon][i18n][infra] Renaming Chinese locales in Django from zh-cn/zh-tw to zh-hans/zh-hant
by Akihiro Motoki 08 Mar '21

08 Mar '21

Hi, The horizon team is planning to switch Chinese language codes in Django codes from zh-cn/zh-tw to zh-hans/zh-hant. Django, a framework used in horizon, recommends to use them since more than 5 years ago [1][2]. This change touches Chinese locales in the dashbaord codes of horizon and its plugins only. It does not change Chinese locales in other translations like documentations and non-Django python codes. This is to minimize the impact to other translations and the translation platform. ### What are/are not changed in repositories * horizon and horizon plugins * locales in the dashboard codes are renamed from zh-cn/zh-tw to zh-hans/zh-hant * locales in doc/ and releasenotes/ are not changed * other repositories * no locale change happens NOTE: * This leads to a situation that we have two different locales in horizon and plugin repositories (zh-hans/hant in the code folders and zh-cn/tw in doc and releasenotes folders), but it affects only developers and does not affect horizon consumers (operators/users) and translators. * In addition, documentations are translated in OpenStack-wide (not only in horizon and plugins). By keeping locales in docs, locales in documentation translations will be consistent. ### Impact on Zanata In Zanata (the translation platform), zh-cn/zh-tw continue to be used, so no change is visible to translators. The infra job proposes zh-cn/zh-tw GUI translatoins as zh-hans/zh-hant translations to horizon and plugin repositories. NOTE: The alternative is to create the corresponding language teams (zh-hans/zh-hant) in Zanata, but it affects Chinese translators a lot. They need to join two language teams to translate horizon (zh-hans/zh-hant) and docs (zh-cn/zh-tw). It makes translator workflow complicated. The proposed way has no impact on translators and they can continue the current translation process and translate both horizon and docs under a single language code. ### Changes in the infra scripts Converting Chinese locales of dashboard translations from zh-cn/zh-tw to zh-hans/zh-hant is handled by the periodic translation job. propose_translation_update job is responsible for this. [propose_translation_update.sh] * Move zh-cn/zh-tw translations related to Django codes in horizon and its plugins from zanata to zh-hans/hant directory. * This should happen in the master branch (+ future stable branhces such as stable/wallaby). ### Additional Remarks I18n SIG respects all language team coordinators & members, and is looking forward to seeing discussions and/or active contributions from the language teams. Currently all language codes follow the ISO 639-1 standard (language codes with relevant country codes), but the change introduces new language code forms like zh-hans/zh-hant. This follows IETF BCP 47 which recommends a combination of language codes and ISO 15924 script code (four letters). We now have two different language codes in OpenStack world. This is just to minimize the impact on the existing translations. It is not ideal. We are open for further discussion on language codes and translation support. ### References [1] https://code.djangoproject.com/ticket/18419 [2] https://www.djbook.ru/rel1.7/releases/1.7.html#language-codes-zh-cn-zh-tw-a… Thanks, Akihiro Motoki (irc: amotoki)

1 1

Puppet openstack modules
by Bessghaier, Narjes 04 Mar '21

04 Mar '21

Dear OpenStack team, My name is Narjes and I'm a PhD student at the University of Montréal, Canada. My current work consists of analyzing code reviews on the puppet modules. I would like to precisely know what the ruby files are used for in the puppet modules. As mentioned in the official website, most of unit test are written in ruby. Are ruby files destined to carry out units tests or destined for production code. I appreciate your help, Thank you

3 4

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?
by Alex Schultz 03 Mar '21

03 Mar '21

On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz(a)redhat.com> wrote: > > On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos(a)gmail.com> wrote: > > The release page says Ocata is planned to go into extended maintenance mode > > on Aug 27 [1]. There really isn't much to this except it means we don't do > > releases for Ocata anymore [2]. There is a caveat that project teams that do > > not wish to maintain stable/ocata after this point can immediately end of > > life the branch for their project [3]. We can still run CI using tags, e.g. > > if keystone goes ocata-eol, devstack on stable/ocata can still continue to > > install from stable/ocata for nova and the ocata-eol tag for keystone. > > Having said that, if there is no undue burden on the project team keeping > > the lights on for stable/ocata, I would recommend not tagging the > > stable/ocata branch end of life at this point. > > > > So, questions that need answering are: > > > > 1. Should we cut a final release for projects with stable/ocata branches > > before going into extended maintenance mode? I tend to think "yes" to flush > > the queue of backports. In fact, [3] doesn't mention it, but the resolution > > said we'd tag the branch [4] to indicate it has entered the EM phase. > > > > 2. Are there any projects that would want to skip EM and go directly to EOL > > (yes this feels like a Monopoly question)? > > > > I believe TripleO would like to EOL instead of EM for Ocata as > indicated by the thead > http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.ht… > Bringing this backup to see what we need to do to get the stable/ocata branches ended for the TripleO projects. I'm bringing this up because we have https://review.openstack.org/#/c/647009/ which is for the upcoming rename but CI is broken and we have no interest in continue to keep the stable/ocata branches alive (or fix ci for them). Thanks, -Alex > Thanks, > -Alex > > > [1] https://releases.openstack.org/ > > [2] > > https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… > > [3] > > https://docs.openstack.org/project-team-guide/stable-branches.html#extended… > > [4] > > https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.… > > > > -- > > > > Thanks, > > > > Matt > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

5 11

[SIG][Containers][k8s] Merge? Retire?
by Kendall Nelson 02 Mar '21

02 Mar '21

Hello! As you might have noticed, we've been working on getting the sig governance site updated with current chairs, sig statuses. etc. Two SIGs that are in need of updates still. The k8s SIG's listed chairs have all moved on. The container SIG is still listed as forming. While not the exact same goal/topic, perhaps these can be merged? And if so, do we have any volunteers for chairs? The other option is to simply remove the Container SIG as its not completely formed at this point and retire the k8s SIG. Thoughts? Volunteers? -Kendall (diablo_rojo)

2 2

VIP switch causing connections that refuse to die
by Michal Arbet 02 Mar '21

02 Mar '21

Hi, I found that keepalived VIP switch cause TCP connections that refuse to die on host where VIP was before it was switched. I filled a bug here -> https://bugs.launchpad.net/kolla-ansible/+bug/1917068 Fixed here -> https://review.opendev.org/c/openstack/kolla-ansible/+/777772 Video presentation of bug here -> https://download.kevko.ultimum.cloud/video_debug.mp4 I was just curious and wanted to ask here in openstack-discuss : If someone already seen this issue in past ? If yes, do you tweak net.ipv4.tcp_retries2 kernel parameter ? If no, how did you solve this ? Thank you, Michal Arbet ( kevko )

4 5

[puppet-openstack] stop using the ${pyvers} variable
by Thomas Goirand 02 Mar '21

02 Mar '21

Hi, Using the ${pyvers} so we can switch be between Python versions made sense 1 or 2 years ago. However, I'm in the opinion that we should stop using that, and switch to using python3 everywhere directly whenever possible. Though Tobias seems to not agree (see [1]), so I'm raising the topic in the list so we can discuss this together. Your thoughts? Cheers, Thomas Goirand (zigo) [1] https://review.opendev.org/c/openstack/puppet-swift/+/777564

5 10

[TripleO] Moving stable/rocky for *-tripleo-* repos to End of Life OK?
by Marios Andreou 01 Mar '21

01 Mar '21

Hello all, it's been ~ 2 months now since my initial mail about $subject [1] and just under a month since my last bump on the thread [2] and I haven't heard any objections so far. So I think it's now appropriate to move forward with [3] which tags the latest commits to the stable/rocky branch of all tripleo-repos [4] as 'rock-eol' (except archived things like instack/tripleo-ui). Once it merges we will no longer be able to land anything into stable/rocky for all tripleo repos and the stable/rocky branch will be deleted. So, last chance! If you object please go and -1 the patch at [3] and/or reply here thanks, marios [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019338… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.… [3] https://review.opendev.org/c/openstack/releases/+/774244 [4] https://releases.openstack.org/teams/tripleo.html

2 4

Moving ara code review to GitHub
by David Moreau Simard 01 Mar '21

01 Mar '21

Hi openstack-discuss, long time no see o/ I've long dreaded doing this and sending this email out because I know how the community feels about proprietary platforms and I value the four opens that the OpenStack community has taught me so much about. I've recently reached out and asked if people would be more likely to contribute to ara if pull requests were possible [1] and had a number of potential contributors interested. Don't get me wrong: I still like OpenStack (have a cloud in my basement!) and personally prefer the Gerrit change workflow to the one on GitHub. However, I've come to the conclusion that my personal preferences should not be a barrier to contribution and so for the health and sustainability of the project I'll move the code review for ara to GitHub leveraging Ansible's Zuul deployment [2] for CI. The truth is that ara never had many contributors and the few that were interested were often discouraged by the process involved in signing up and sending a change through Gerrit. It broke my heart to see a pull request being automatically closed with a template by an OpenStack bot. It broke my heart to have to tell people that they must jump through several hoops to send a patch. I was forever grateful every single time that someone actually went through the process and managed to get a patch merged with or without my help. For more than five years already, I've done my best to salvage these contributions and ask for help but at the end of the day, most of the Ansible community projects are on GitHub and it has weighed down on me heavily to battle this inertia. Frankly, it has been exhausting and even depressing sometimes. I'm thankful for the OpenStack (and OpenDev) communities for hosting the project until now and hope to continue talking to you on freenode -- you can find me in #ara amongst many other channels. See you around ! [1]: https://github.com/ansible-community/ara/issues/205 [2]: https://dashboard.zuul.ansible.com/t/ansible/status David Moreau Simard dmsimard = [irc, github, twitter]

4 3