September 2021 - openstack-discuss

OVS_AFXDP for production
by Satish Patel 18 Sep '21

18 Sep '21

Folks, I’m running some high performance workload on SRIOV and planning to move from SRIOV to DPDK but recently Hearing a lots about AFDXP data path and just wanted to check with expert, is this ready for production? How good it is to compare with DPDK? Sent from my iPhone

1 0

[Interop] New meeting time
by Arkady Kanevsky 17 Sep '21

17 Sep '21

The interop WG changed its weekly meeting time to Thursday 16:00pm UTC. The Google meet and etherpad stay the same. See https://wiki.openstack.org/wiki/Governance/InteropWG#Meetings Thanks, Arkady -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

1 0

[all][tc][goals] Project Specific PTL and Contributor Documentation: Week R-20 Update
by Ghanshyam Mann 17 Sep '21

17 Sep '21

Hello Everyone, As you know, we did not select any community-wide goal for Xena cycle and in PTG, TC decided to spend more time on the previous cycle pending community-wide goal work[1] One of the previous cycle (Ussuri) goals is 'Project Specific PTL and Contributor Documentation' which still not completed by many projects. - https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-c… I am starting the work to finish this goal which is pretty straight forwards and sending the updates in this ML thread. Please review the patches and merge them or push the patches for your project's repo if not yet done. Gerrit Topic: https://review.opendev.org/q/topic:%22project-ptl-and-contrib-docs%22+(stat… Tracking: https://storyboard.openstack.org/#!/story/2007236 Progress Summary: =============== * Projects completed: 32 * Projects for which patches are up and required to merge those: 10 * Projects for which patches are not yet up: 12 [1] https://etherpad.opendev.org/p/tc-xena-tracker (Item#2) -gmann

2 2

[all][tc] What's happening in Technical Committee: summary 17th Sept, 21: Reading: 5 min
by Ghanshyam Mann 17 Sep '21

17 Sep '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Sept 16th Thursday. * Most of the meeting discussions are summarized in the below sections (Completed or in-progress activities section). To know more details, you can check the complete logs @ https://meetings.opendev.org/meetings/tc/2021/tc.2021-09-16-15.00.log.html * We will have next week's meeting on Sept 23rd, Thursday 15:00 UTC on IRC, feel free the topic in agenda [1] by Sept 22nd. 2. What we completed this week: ========================= * PTLs for all the six leaderless projects are now assigned and merged[2] * Added openstack-loadbalancer charm and interfaces[3] * TC chair and vice-chair for Yoga cycle are selected. I will continue as chair[3] and yoctozepto as vice-chair[4]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[6] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Three open reviews for ongoing activities[7]. TC tags analysis ------------------- * As discussed in the last PTG, TC is working on an analysis of the usefulness of the Tags framework[8] or what all tags can be cleaned up. * It seems no response yet on email from yoctozepto[9], if you are an operator, please respond to the email and based on the feedback we will continue the discussion in PTG. Collecting Pain points from projects/SIGs/pop-up ----------------------------------------------------------- * No updates on this, we will continue discussing it in PTG[10], join us if you are interested to help/discuss this topic. Project updates ------------------- * Add the cinder-netapp charm to Openstack charms[11] * Retiring js-openstack-lib [12] * Retire puppet-freezer[13] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [14]. * Current status: "Secure RBAC" is selected for Yoga cycle[15]. PTG planning ---------------- * We are collecting the PTG topics in etherpad[16], feel free to add any topic you would like to discuss. * We discussed the live stream of one of the TC PTG sessions like we did last time. Once we will have more topics in etherpad then we can select the appropriate one. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[17], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 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 UTC [19] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [20] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/yoga-leaderless [3] https://review.opendev.org/c/openstack/governance/+/807837 [4] https://review.opendev.org/c/openstack/governance/+/807163 [5] https://review.opendev.org/c/openstack/governance/+/807178 [6] https://etherpad.opendev.org/p/tc-xena-tracker [7] https://review.opendev.org/q/project:openstack/governance+status:open [8] https://governance.openstack.org/tc/reference/tags/index.html [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-September/02480… [10] https://etherpad.opendev.org/p/pain-point-elimination [11] https://review.opendev.org/c/openstack/governance/+/809011 [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] https://review.opendev.org/c/openstack/governance/+/807163 [14] https://etherpad.opendev.org/p/y-series-goals [15] https://review.opendev.org/c/openstack/governance/+/803783 [16] https://etherpad.opendev.org/p/tc-yoga-ptg [17] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [20] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[release][PTL] broken gates and stuck releases
by Herve Beraud 17 Sep '21

17 Sep '21

Hello PTLs, For your information our gates are currently broken so we are not able to merge patches and so to release deliverables. indeed openstack/release rely on openstack/governance to validate releases. The governance repo relies on pybot2 which is no longer maintained and became not installable a few hours ago. That broke the release gate and led us to a catch-22 situation where we are not able to release the governance repo to fix our repo. Our current solution is to pull openstack/governance from git source instead of from pypi. By doing that we will pull the fixed version from opendev git and we will unblock our gates. In this way, we will be able to restart to merge patches and release deliverables. We currently wait for some feedback from the infra team to help us to force merging the needed fixes by using their gerrit super admin rights, hence, bypassing the catch-22 situation. This situation highlighted the cross dependency between these two repos (governance and releases) and I don't think that this is something healthy. I propose to keep pulling the governance repo from git source even after we will fix the catch-22 situation. Any opinions? Thanks for your understanding, we will inform you when we will have updates. https://opendev.org/openstack/governance/commit/9128e502253db9aac346ce25726… https://review.opendev.org/c/openstack/releases/+/809626 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

3 3

Delete Volume on Instance Delete
by Derek O keeffe 17 Sep '21

17 Sep '21

Hi all, I was able to set "Create new volume" to no by default on the launch instance page by adding the following to /etc/openstack-dashboard/local_settings.py LAUNCH_INSTANCE_DEFAULTS ={ 'create_volume': False,} Is there anyway I can set "Delete Volume on Instance Delete" to yes by default should someone select to create a new volume when launching an instance. I tried the following but no luck LAUNCH_INSTANCE_DEFAULTS ={ 'create_volume': False, 'delete_on_termination': True} Thanks for any help/info in advance. Regards,Derek

2 2

How to resume/abort a migration in error state
by Yingji Sun 17 Sep '21

17 Sep '21

Buddies, I am in openstack train and I have some failure live-migration cases that leave some migration states to error. These failure cases may block the following migration request in “queued” state. Is it possible that I force to complete the failure cases ? live_migrate_force_complete only works for a “running”migration and live_migrate_abort works only for “running/queued/preparing”migration. Any suggestion would be appreciated. Yingji.

1 0

[neutron] Drivers meeting - Friday 17.09.2021 - cancelled
by Lajos Katona 16 Sep '21

16 Sep '21

Hi, Due to lack of topics for Today's Drivers meeting, let's cancel the meeting. Lajos (lajoskatona)

1 0

Autoscaling based on requests
by open infra 16 Sep '21

16 Sep '21

Hi, I have a requirement to allocate a server(VM) for each user request and make this automatic. Is it possible with Openstack autoscale? Scaling should not be done based on either cpu or memory usage as only one user is supposed to access a single VM. Regards, Danishka

1 0

[blazar] Third-party resource type plugins
by Jason Anderson 16 Sep '21

16 Sep '21

Hi all, I’ve just submitted a spec for making resources in Blazar follow a more explicit plugin architecture: https://review.opendev.org/c/openstack/blazar-specs/+/809485 The intent is to allow out-of-tree resource types, to allow deployers/operators to define their own abstractions. This could support some pretty wide-ranging implementations, like reserving bandwidth allocations on switches or perhaps access to other controlled/limited resources. I hope that this change will also enable Blazar to be adopted by a wider set of users and use cases. Please, have a look—it is currently proposed under Xena because there is not yet a Yoga spec section in blazar-specs. Cheers, /Jason

1 0