February 2023 - openstack-discuss

[all][tc] What's happening in Technical Committee: summary 2023 Feb 17: Reading: 5 min
by Ghanshyam Mann 18 Feb '23

18 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 15. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-15-16.00.log.html * The next TC weekly meeting will be on Feb 22 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 21. 2. What we completed this week: ========================= * Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation[2] * Retire repo from the Governance repo - Retire xstatic-font-awesome[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Seven open reviews for ongoing activities[5]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation[6]. TripelO release model is a little different where they do have stable branches till stable/wallaby and after that, it was an independent release. But in the independent release model also, stable/zed branch was cut. With the TripleO deprecation, the team can maintain only till stable/wallaby. This makes the situation a little difficult where we do not have the best possible way to deprecate/retire stable/zed. TC discussed it but could not find any suitable options other than maintaining the stable/zed also. James will be checking this option with TripleO team and updating the ML thread. Election updates -------------------- Technical election nomination for the next cycle has been closed[7]. Even though there is no poll required in PTL as well as in TC elections, the TC campaigning is going on[8] where you can ask question to the TC candidates. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[9] to define the 2023 calendar year, which is continuing last year's opportunities. Please let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [10]. There is a discussion also going on in ML[11]. JayF is working on an email template which can be used to communicate to additional developers to transfer the ownership to 'openstackci' account and remove them from the maintainer's list. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[12]. Project updates ------------------- * Add Cinder Huawei charm[13] * Add the woodpecker charm to Openstack charms[14] * Retire xstatic-font-awesome[15] * mistral adopting PTL model[16] * Add xstatic-angular-fileupload as Horizon team deliverables[17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/872769 [3] https://review.opendev.org/c/openstack/governance/+/872837 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… [7] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [9] https://review.opendev.org/c/openstack/governance/+/872233 [10] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [11] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [12] https://etherpad.opendev.org/p/project-health-check [13] https://review.opendev.org/c/openstack/governance/+/867588 [14] https://review.opendev.org/c/openstack/governance/+/869752 [15] https://review.opendev.org/c/openstack/governance/+/872837 [16] https://review.opendev.org/c/openstack/governance/+/873260 [17] https://review.opendev.org/c/openstack/governance/+/873845 [18] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Ceph outage cause filesystem error on VM
by Satish Patel 18 Feb '23

18 Feb '23

Folks, I am running a small 3 node compute/controller with 3 node ceph storage in my lab. Yesterday, because of a power outage all my nodes went down. After reboot of all nodes ceph seems to show good health and no error (in ceph -s). When I started using the existing VM I noticed the following errors. Seems like data loss. This is a lab machine and has zero activity on vms but still loses data and the file system corrupt. Is this normal ? I am not using eraser coding, does that help in this matter? blk_update_request: I/O error, dev sda, sector 233000 op 0x1: (WRITE) flags 0x800 phys_seg 8 prio class 0

5 14

Fedora 37 image for Openstack Magnum
by sri ramu 18 Feb '23

18 Feb '23

Hi Team, I am testing the Openstack magnum ussuri version. However, to launch a magnum K8s cluster I am using Fedora32 as the backend image . As everyone is aware this fedora32 image has no support. So I have planned to deploy with fedora37 but their Heat agent was not running properly. Need your help to run the heat agent in fedora37. Regards, Sriramu Desing

2 1

[manila] Feature freeze exceptions
by Carlos Silva 18 Feb '23

18 Feb '23

Hello, Zorillas and interested stackers! As discussed in yesterday's Manila weekly meeting, some features we are targeting for Antelope will need some extra time to be merged due to a shortage of reviewers we had in the cycle. These changes have been under review and we believe they are close to being merged. The changes we will need more time to merge are: *Metadata for share network subnets:* Reviews ongoing [1]. Change was proposed in time during the cycle, has received a couple of reviews and authors have been responsive. There is also a small third party driver modification being proposed alongside [2]. Both seem close to being merged. Client change did not make it to the release and will be merged earlier in the next cycle. *NetApp ONTAP REST API transition:* NetApp contributors are pursuing an implementation that will allow them to transition from ZAPI to REST [3]. This is a huge change as they need to rewrite things to be compatible with their ONTAP REST API. The changes have been proposed in time, authors have been providing test results and reviewers have been providing feedback. We had a collaborative review earlier this week where they walked us through the changes [4]. We are extending the feature freeze deadline until next Thursday (Feb 23rd) for these changes. [1] https://review.opendev.org/c/openstack/manila/+/869707/ [2] https://review.opendev.org/c/openstack/manila/+/869708/ [3] https://etherpad.opendev.org/p/collab-review-manila-netapp-rest-api [4] https://www.youtube.com/watch?v=zCOm_g7HGWU Regards, carloss

1 0

[keystone] Feature freeze exceptions
by Hiromu Asahina 17 Feb '23

17 Feb '23

Hi All, As discussed in the reviewathon today, due to the shortage of review bandwidth, we are planning to extend the feature freeze for the changes related to mTLS OAuth2.0. Current feature freeze date (for keystone): 17 February 2023 New feature freeze date (for keystone): 24 February 2023 Kindly let me know if there are any objections to the above proposal else the changes related to topic:bp/support-oauth2-mtls [1] are eligible for the feature freeze exception of 1 week. [1] https://review.opendev.org/q/topic:bp%252Fsupport-oauth2-mtls Thanks, Hiromu Asahina

1 0

[release] Release countdown for week R-4, Feb 20-24
by Elõd Illés 17 Feb '23

17 Feb '23

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 2023.1 Antelope deliverables can be proposed, well ahead of the final 2023.1 Antelope release date. General Information ------------------- We are still finishing up processing a few release requests, but the 2023.1 Antelope release requirements are now frozen. If new library releases are needed to fix release-critical bugs in 2023.1 Antelope, 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 2023.1 Antelope 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 2nd, 2023 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/2023.1 branches 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 2023.1 Antelope changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed 2023.1 Antelope cycle-highlights yet, then you are encouraged to do so as deadline is February 23rd, 2023. A separate email will be sent early next week. Upcoming Deadlines & Dates -------------------------- Cycle Highlights Due: February 23rd, 2023 (R-4 week) RC1 deadline: March 2nd, 2023 (R-3 week) Final RC deadline: March 16th, 2023 (R-1 week) Final 2023.1 Antelope release: March 22nd, 2023 2023.2 Bobcat Virtual PTG: March 27-31, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[elections][Cinder] PTL Candidacy for 2023.2 (Bobcat)
by Rajat Dhasmana 17 Feb '23

17 Feb '23

Hi All, I would like to nominate myself to be Cinder PTL during the 2023.2 (Bobcat) cycle. I have been serving as the PTL for the last two cycles i.e. Zed and 2023.1 (Antelope) and there were a lot of key areas which we were able to improve as follows: ** Review bandwidth and quality:* Cinder's policy of "Do reviews to get reviews" has helped improve the review bandwidth and we have seen more participation and activity in code reviews. We have also added efficient review guidelines[1] to help new contributors onboard to the review process quickly and help them do quality reviews. ** cinderclient to openstackclient migration:* We are working towards reducing the parity between cinderclient and openstackclient and the effort can be tracked with this topic[2]. Currently we have proposed all the commands that were missing in openstackclient. ** Third party CI to report on os-brick changes: *The third party vendor CI's used to report only on cinder gate and not on os-brick gate which means their driver wasn't tested with the connector and they could only see issues when the os-brick release happens. Unfortunately, the driver merge deadline is milestone-2 and os-brick (non-client library) release is 1 week before feature freeze so it doesn't give enough time for driver maintainers to fix the issues. Reporting the CI on os-brick gate helps identify issues earlier and fix them timely. ** Security Vulnerabilities:* We went through the open security issues in Zed and triaged their priority and importance. A new security issue was reported in 2023.1 regarding VMDK file format for which a CVE has been filed, CVE-2022-47951 [3]. We have addressed the issue and releases were done for the actively maintained stable branches i.e. Zed[1], Yoga[2] and Xena[3]. Apart from that, we were able to handle deadlines better by managing and prioritizing work based on the milestones. Following are the plans for the 2023.2 cycle: * our first target will be to move away from adding additional commands to cinderclient and only rely on openstackclient for the CLI interface. Also we will explore openstacksdk to add support for cinder commands so we can break the dependency on the python bindings that exist in cinderclient. * Another thing to address is adding the service role after the keystone implements it[7]. * Third party drivers are the core of cinder that allows cinder to what the end users desire i.e. to interface between users and storage backends. We will focus to improve the experience of driver vendors to implement new drivers by improving our driver documentation and test stability by doing a 3rd party CI compliance check. We have been making progress in this area but more efforts are required that we will target for the next cycle. Finally will try to continue all the good things we have started that keeps the project healthy and active and also address new gaps discovered along the way. [1] https://docs.openstack.org/cinder/latest/contributor/gerrit.html#efficient-… [2] https://review.opendev.org/q/topic:add-missing-cinderclient-commands [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47951 [4] https://pypi.org/project/cinder/21.1.0 [5] https://pypi.org/project/cinder/20.1.0 [6] https://pypi.org/project/cinder/19.2.0 [7] https://review.opendev.org/c/openstack/keystone/+/863420 - Rajat Dhasmana

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 17 Feb '23

17 Feb '23

Hello Neutrinos: Due to the lack of agenda [1], today's drivers meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

Answer questions about 'OpenInfra Live - VGPU Management by OpenStack Nova and Cyborg'
by Alex Song (宋文平) 17 Feb '23

17 Feb '23

Hi everyone, The Episode of VGPU Management by OpenStack Nova and Cyborg has completed. Below is the answer of questions: Q:Does Cyborg do the MIG configuration or is that done manually outside OpenStack? A: We can configure MIG by cyborg-api, we list the MIG split combinations on the page for user to set. Cyborg-agent only need configure the driver of nvidia_mig_driver. In the driver, we automatic discover the vgpu_types and PCI addresses and set default vgpu_types. Q:Do l get it right that we need at least Ussuri on the hosts for Nova ? A: Yeah, from Ussuri we complete the interaction with Nova and Cyborg. If you use old Nova version, you can cherry pick the Cyborg part code. Q:does cyborg also help with SRIOV netork with MIG and passthrough hosts? A: Firstly, Cyborg has supported manage SmartNIC SRIOV network. Secondly, MIG and vGPU only support passthrough hosts in OpenStack nowadays, GPUDirect need RDMA communication. Thanks, Alex

1 0

[election][keystone] PTL candidacy for 2023.2 (Bobcat)
by Dave Wilde 16 Feb '23

16 Feb '23

Hello, I would like to nominate myself to be Keystone PTL for the 2023.2 (Bobcat) cycle. This will be my second cycle serving as PTL and I am looking forward to continuing the progress that we're making in Keystone. Some of the highlights of the last cycle that I would like to continue and build upon are: *Reviewathons*: We have been holding weekly reviewathons that I feel have been quite successful. We meet on Fridays (ping me if you'd like an invite) in an informal hour long GMeet room and either go down the list of pending reviews or if there is a specific topic/feature we might focus on that. The reviewathons have helped in significantly reducing our backlog of easily merged, maintenance type patches and have given us a very good opportunity to discuss in detail a very complicated feature. I would like to continue the reviewathons and extend an invitation to anyone who would like to join. *Weekly Meetings*: The weekly meetings are happening regularly and are fostering good discussion and information sharing. The weekly meetings are currently scheduled for Tuesdays at 15:00 UTC but I am always open to changing the day and time if it will garner more participation. *Bug Cleanup*: Keystone proper has over two hundred bugs and the other Identity projects probably contribute another one hundred, this is too many. I have been slowly going through and trying to close out old and irrelevant bugs as well as triage those that need fixing (my apologies for the emails about bugs that are years old :). I would like to continue this work and get our bug backlog into a manageable state. I've enjoyed my first cycle as PTL and with your continued support am looking forward to another cycle. Thanks for your consideration. /Dave

2 1