February 2022 - openstack-discuss

[TripleO] Gate blocker - centos-9 standalone and multinode
by Bhagyashri Shewale 27 Feb '22

27 Feb '22

Hi All, We have an issue affecting standalone and multinode centos-9 check/gate jobs due to tempest test failure. Details: https://bugs.launchpad.net/tripleo/+bug/1962298 We are currently deciding on the best course of action for unblocking this issue. We will post an update once the check/gate is clear. Until then, please hold on rechecking. Thanks and Regards Bhagyashri Shewale

2 1

[Manila] Manila Collaborative Review Session - Thursday, March 10th
by Liron Kuchlani 26 Feb '22

26 Feb '22

Hi all, We are planning a Manila collaborative review session on Thursday, March 10th, to walk through the following proposed feature: - Add S-RBAC tests for manila [1] The session will start at 14:30 UTC and continue through the first half of the weekly upstream manila community meeting as needed. We will use an etherpad [2] during the session to capture notes and discussions. Hope you can all join us, [1] https://review.opendev.org/c/openstack/manila-tempest-plugin/+/805938 [2] https://etherpad.opendev.org/p/Manila-S-RBAC-collaborative-review

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Brian Rosmaita 26 Feb '22

26 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. Note to reviewers: please concentrate on the below over the next week. 1. Complete transition to Alembic - https://blueprints.launchpad.net/cinder/+spec/complete-transition-to-alembic - this is essential technical debt elimination - has a Feature Freeze Exception 2. Reset State Robustification - https://blueprints.launchpad.net/cinder/+spec/reset-state-robustification - Tushar has been working patiently on this forever - not a destabilizing change - has a Feature Freeze Exception - let's prioritize getting the base patch reviewed and merged, and we can see how far we can work up the stack before 7 March. - https://review.opendev.org/c/openstack/cinder/+/773985/ Driver features 3. HPE Nimble driver rename - https://blueprints.launchpad.net/cinder/+spec/nimble-change-location - https://review.opendev.org/c/openstack/cinder/+/786054 - has one +2 - patch has passed third party CI configured with the old name *and* with the rename - has an FFE Hitachi VSP driver The below require this non-feature patch, which addresses followup issues - https://review.opendev.org/c/openstack/cinder/+/827259/ - has one +2 - doesn't need an FFE because it's a bugfix, but let's get it reviewed and merged! 4. Support AIX as host OS type for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-aix-os-type - https://review.opendev.org/c/openstack/cinder/+/828061 - has one +2 - has an FFE 5. Target Port Assignment for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-tgt-port-asgn - https://review.opendev.org/c/openstack/cinder/+/828060 - has one +2 - has an FFE Questionable: 1. The Return of Make Cinder Consistent and Secure RBAC Ready - https://blueprints.launchpad.net/cinder/+spec/s-rbac-ready-y - community goal - I will meet with the cinder Zed PTL to discuss what to do about this one (may give a FFE for just part) 2. Hitachi: Port Scheduler for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-port-scheduler - https://review.opendev.org/c/openstack/cinder/+/828696 - Code and tests look mostly fine, and CI is passing - some really minor issues and needs a release note - needs to be rebased on latest version of 828060 - not giving an auto-FFE because it hasn't had a +2 yet - must apply for an FFE 3. ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE

1 0

[Magnum] heat-container-agent not able to talk to keystone
by Satish Patel 26 Feb '22

26 Feb '22

Folks, I am trying to deploy k8s cluster using magnum on openstack and found cluster creation stuck during kube master heat deployment and when i look into logs i found following Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Source [heat] Unavailable. Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Source [heat] Unavailable. In my deployment it's a private cloud so all control plane components running on private address space and k8s cluster created their own private network which is not routable so the kube master node can't talk to keystone. I can't put my HAProxy on a public address. In that case what are the options I have? I am running OVN for networking deployed by kolla-ansible. ~S

1 0

[manila] Yoga FFE request
by Fernando Ferraz 26 Feb '22

26 Feb '22

Hi Team, I'd like to request a FFE for the following changes we have been working on for the Yoga cycle. They are all part of the effort to partially implement spec *Add spec for multiple subnet share servers* *[1]* in Manila.: 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 826462: Container: Multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/826462 825155: NetApp ONTAP: Add support to multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/825155 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 All changes were submitted in time and there has been significant progress in reviews until this point. [1] https://review.opendev.org/c/openstack/manila-specs/+/619925 Regards, Fernando

2 2

[manila] RC1 bugsquash next week, no weekly IRC meetings until 17th March 2022
by Goutham Pacha Ravi 25 Feb '22

25 Feb '22

Hello there zorillas, It's time again to gather and squash some bugs together! We're hosting a bugsquash week between 3rd March 2022 and 10th March 2022. We've a preliminary list of bugs scoped out [1]. We'd love for you to participate by claiming a bug or two to fix during the week and reviewing bug fixes. Some of these bug fixes are in-progress, and we'll be conducting collaborative reviews to merge them during the week. If you'd like to work on something, please add it to the list [1] We'll use meetpad [2] to hang out opportunistically during the week at different times to review code or brainstorm, please watch the chatter on OFTC's #openstack-manila. However, a few scheduled events: * We'll have a kick-off at 1500 UTC on 3rd March 2022 * A "almost there" check in on 8th March 2022 at 1600 UTC on 8th March 2022 * A collab-review for S-RBAC tempest tests [3] at 1430 UTC on 10th March 2022 * A wrap up for the bugsquash week at 1530 UTC on 10th March 2022 All these will occur in the meetpad room; and these times overlap with our weekly IRC meetings - so we'll skip those. If you have any topics to discuss, please call our attention on this mailing list or on OFTC's #openstack-manila. Thanks, and hope to see you there! Goutham [1] https://ethercalc.openstack.org/t727llczm00f [2] https://meetpad.opendev.org/ManilaYogaRC1Bugsquash [3] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027329…

1 0

[all][tc] What's happening in Technical Committee: summary 25th Feb, 21: Reading: 5 min
by Ghanshyam Mann 25 Feb '22

25 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 24th. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-24-15.00.log.html * Next week's meeting is on 4th March Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by 3rd March. 2. What we completed this week: ========================= * Zed cycle technical election[2] * Switch Keystone back to PTL model[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Eight open reviews for ongoing activities[5]. Zed cycle Leaderless projects ---------------------------------- As elections are closed, 17 projects are missing the nomination and out of those 11 have the late nomination. 6 projects are still seeking leaders. As the next step, TC will work on the assignment of leaders if we find any other steps on these leaderless projects[6]. Zed cycle testing runtime ------------------------------ I started the Zed cycle testing runtime, please check and give any objection if there is any[7] PTG Preparation -------------------- I have started the etherpad for TC PTG[8] preparation as well as for TC+Community Leaders sessions[9]. Also, doodle poll to select the slots[10] Testing and bumping the lower bounds in requirements.txt --------------------------------------------------------------------- Brian brought this topic while there was discussion on os-bricks bumping the minimum in requirements.rst[11]. As we do not test the lower bounds, we are not sure if existing lower bounds work or not. Telling anyone to reply on those is no guarantee that they will work or not. As TC, we agreed to give more clear direction on lower bounds and that is why we will discuss this topic in Zed PTG. Meanwhile, os-brick bumping the minimum is fine. Release identification and release name ----------------------------------------------- The proposal is under review and updates [12] Dropping tags framework ------------------------------ part1 of this is merged[13], part-2 of updating release script and other tags migration is under-progress. TC position on release cadence ------------------------------------- The proposal is under review and updates [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 ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [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] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027412… http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [3] https://review.opendev.org/c/openstack/governance/+/829037 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/zed-leaderless [7] https://review.opendev.org/c/openstack/governance/+/830454 [8] https://etherpad.opendev.org/p/tc-zed-ptg [9] https://etherpad.opendev.org/p/tc-ptl-interaction-zed [10] https://doodle.com/poll/gz4dy67vmew5wmn9 https://doodle.com/poll/dcer6i3wk2b8eim3 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027343… https://review.opendev.org/c/openstack/os-brick/+/828802 [12] https://review.opendev.org/c/openstack/governance/+/829563 [13] https://review.opendev.org/c/openstack/governance/+/822900 [14] https://review.opendev.org/c/openstack/governance/+/828777 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] https://review.opendev.org/c/openstack/governance/+/798540 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-4, Feb 28 - Mar 04
by Előd Illés 25 Feb '22

25 Feb '22

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Yogadeliverables can be proposed, well ahead of the final Yogarelease date. General Information ------------------- We are still finishing up processing a few release requests, but the Yogarelease requirements are now frozen. If new library releases are needed to fix release-critical bugs in Yoga, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in Yoga that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 24th, 2022this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/yogabranches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Yoga changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Yogacycle-highlights yet, you are already late to the party. Please see our email for details: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027361… Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022(R-3 week) Final RC deadline: March 24th, 2022(R-1 week) Final Yogarelease: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[all][elections][tc] Technical Committee Election Results
by Ghanshyam Mann 25 Feb '22

25 Feb '22

For 5 TC open seats, there were 5 candidates so no election was required. Please join me in congratulating the 5 newly elected members of the Technical Committee (TC). Amy Marrich (spotz) Arne Wiebalck (arnewiebalck) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you for another great round. -gmann, on behalf of the OpenStack Technical Election Officials

3 2

[all][elections][ptl] Project Team Lead Zed Election Conclusion and Results
by Ghanshyam Mann 24 Feb '22

24 Feb '22

Thank you to the all candidates who put their names forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Barbican : Douglas Mendizábal * Blazar : Pierre Riteau * Cinder : Rajat Dhasmana * Cloudkitty : Rafael Weingartner * Cyborg : Bailin Zhang * Designate : Michael Johnson * Ec2 Api : Andrey Pavlov * Glance : Abhishek Kekane * Horizon : Vishal Manchanda * Ironic : Iury Gregory Melo Ferreira * Keystone : Douglas Mendizábal * Kolla : Michal Nasiadka * Kuryr : Maysa de Macedo Souza * Manila : Carlos Silva * Neutron : Lajos Katona * Nova : Sylvain Bauza * Octavia : Gregory Thiemonge * OpenStack Helm : Gage Hugo * OpenStackAnsible : Dmitriy Rabotyagov * OpenStackSDK : Artem Goncharov * Puppet OpenStack : Takashi Kajinami * Quality Assurance : Martin Kopec * Rally : Andrey Kurilin * Release Management : Elod Illes * Requirements : Matthew Thode * Sahara : Fossen Qiu * Storlets : Takashi Kajinami * Swift : Tim Burke * Tacker : Yasufumi Ogawa * Telemetry : Matthias Runge * Tripleo : James Slagle * Vitrage : Eyal Bar-Ilan * Winstackers : Lucian Petrut For remaining projects (without PTL candaidates), TC will work on the appointment. Elections: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process -gmann, on behalf of the OpenStack Technical Election Officials

1 0