September 2020 - openstack-discuss

[cinder] this week's meeting in video+IRC
by Brian Rosmaita 28 Sep '20

28 Sep '20

I forgot to mention at last week's Cinder meeting that the meeting for Wednesday 30 September, being the last meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. Here's a quick reminder of the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. connection info: https://bluejeans.com/3228528973 cheers, brian

1 0

[election][designate] PTL candidacy for Wallaby
by Michael Johnson 28 Sep '20

28 Sep '20

My fellow OpenStack community, I would like to announce my candidacy for PTL of Designate for the Wallaby cycle. As you probably know I have been the Octavia PTL five times since the Pike release. I will continue to be involved in the Octavia project, but it is time for a change! I feel that allowing for leadership change on projects is healthy and gives others the opportunity to lead. In my downstream day job I am becoming more involved in supporting Designate as part of our OpenStack offering. This means I will be contributing more to Designate and supporting the Designate community. One of my Designate goals for the Wallaby release will be expanding the documentation available. For example, I would like to create some user cookbooks, similar to those in the Octavia documentation, that would guide users through scenarios using Designate. I am also excited to see a proposed patch for DNS “views” in Designate, so I will be supporting that development effort in any way I can help. Thank you for your support and your consideration for Wallaby, Michael Johnson (johnsom)

1 0

[tc] weekly update
by Mohammed Naser 28 Sep '20

28 Sep '20

Hi everyone,Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 - Retire openstack/os-loganalyze https://review.opendev.org/753834 - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Reorder repos alphabetically https://review.opendev.org/754097 - Add Ironic charms to OpenStack charms https://review.opendev.org/754099 - Define TC-approved release in a resolution https://review.opendev.org/752256 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg - PTG Registration: https://october2020ptg.eventbrite.com Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

TC Candidacy for Wallaby
by Amy Marrich 28 Sep '20

28 Sep '20

Hey all, I am declaring my candidacy for the Technical Committee. I have served in various leadership positions within the community over the years and feel I have developed a well rounded view of what goes on within OpenStack from the project level up to the OSF Board level. I feel I can represent all members of the community from the folks running small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributers from those just starting out to those who have been here from the beginning. While I'm admittedly not a developer by profession, I have code and documentation contributions in multiple projects which I think is important in seeing the big picture as to how pieces fit together in the larger OpenStack codebase. Thanks, Amy Marrich (spotz)

1 0

[neutron] Bug deputy report for week of September 21st
by Brian Haley 28 Sep '20

28 Sep '20

Hi, I was Neutron bug deputy last week. Below is a short summary about the 21 (!) reported bugs. -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896603 - ovn-octavia-provider: Cannot create listener due to alowed_cidrs validation - https://review.opendev.org/#/c/753302/ * https://bugs.launchpad.net/bugs/1896678 - [OVN Octavia Provider] test_port_forwarding failing in gate - https://review.opendev.org/#/c/753419/ * https://bugs.launchpad.net/neutron/+bug/1896766 - OVN jobs failing due to failed OVS compilation - https://review.opendev.org/#/c/751882/ * https://bugs.launchpad.net/neutron/+bug/1897326 - scenario test test_floating_ip_update is failing often on Ubuntu 20.04 - Possibly related to https://bugs.launchpad.net/neutron/+bug/1896735 - Slawek took ownership High bugs --------- * https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1896506 - keepalived_use_no_track default=True breaks bionic deploys - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896677 - [OVN Octavia Provider] OVN provider fails creating pool without subnet ID - Assigned to haleyb * https://bugs.launchpad.net/neutron/+bug/1896735 - Scenario tests from neutron_tempest_plugin.scenario.test_port_forwardings.PortForwardingTestJSON failing due to ssh failure - https://review.opendev.org/#/c/753552/ proposed * https://bugs.launchpad.net/neutron/+bug/1896827 - port update api should not lose foreign external_ids - https://review.opendev.org/#/c/753833/ proposed * https://bugs.launchpad.net/neutron/+bug/1896945 - dnsmasq >= 2.81 not responding to DHCP requests with current q-dhcp configs - Looks similar to https://bugs.launchpad.net/neutron/+bug/1876094 but that fix is merged - Needs owner * https://bugs.launchpad.net/neutron/+bug/1897095 - [OVN] ARP/MAC handling for routers connected to external network is scaling poorly - https://review.opendev.org/#/c/752678/ proposed Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1896470 - OVN migration infrared plugin does not remove ML2OVS-specific templates - https://review.opendev.org/#/c/752918/ proposed * https://bugs.launchpad.net/neutron/+bug/1896587 - iptables firewall driver don't drops invalid packets which match some SG rule - Fix for https://bugs.launchpad.net/neutron/+bug/1460741 moved this iptables chain lower, so more investigation required. * https://bugs.launchpad.net/tempest/+bug/1896592 - [neutron-tempest-plugin] test_dhcpv6_stateless_* clashing when creating a IPv6 subnet - Actually a bug in the tempest repo, added component - Fixed in neutron-tempest-plugin with https://review.opendev.org/#/c/560465/ - Marked Incomplete by Rodolfo as he noticed server issues (500's) in the logs * https://bugs.launchpad.net/neutron/+bug/1896733 - [FT] Error while executing "remove_nodes_from_host" method - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896850 - dhcp release fails when client_id is specified - https://review.opendev.org/#/c/753865/ proposed * https://bugs.launchpad.net/neutron/+bug/1896933 - Exception when plugin creates a network without specifying the MTU - https://review.opendev.org/#/c/753717/ proposed Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1896588 - [Security Groups] When using neutron CLI, if non-existing project is given when listing the SGs, a default SG is created - Rodolfo working on it * https://bugs.launchpad.net/neutron/+bug/1897100 - Improve port listing command - https://review.opendev.org/#/c/754117/ proposed * https://bugs.launchpad.net/neutron/+bug/1897423 - [L3] Let agent extension do delete router first - https://review.opendev.org/#/c/736258/ proposed * https://bugs.launchpad.net/neutron/+bug/1895876 - When accounts.yaml is used neutron_tempest_plugin fails with "Invalid input for tenant_id. Reason: 'None' is not a valid string." - https://review.opendev.org/754782 proposed Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896920 - Unnecessary error log when checking if a device is ready - https://review.opendev.org/#/c/754005/ proposed Further triage required ----------------------- * None

1 0

[requirements][election] PTL candidacy for Wallaby
by Matthew Thode 28 Sep '20

28 Sep '20

I would like to announce my candidacy for PTL of the Requirements project for the Wallaby cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like botocore). 3. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. Json libs are on the short list this go around. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

1 0

[blazar][election] PTL candidacy for Wallaby
by Pierre Riteau 28 Sep '20

28 Sep '20

Hi, I would like to self-nominate for the role of PTL of Blazar for the Wallaby release cycle. I have been PTL since the Stein cycle and I am willing to continue. Unfortunately, Blazar has been suffering from low participation in the project. I will keep engaging with current users and potential new ones, in order to get more contributors involved in the project. Thank you for your support, Pierre Riteau (priteau)

1 0

[election][barbican] Add Douglas Mendizábal candidacy for Barbican PTL
by Douglas Mendizabal 28 Sep '20

28 Sep '20

Hello OpenStack, I would like to nominate myself for Barbican PTL. [1] My focus for the new cycle will be to continue the maintenance and development of the project. We will continue to improve usability as well as continue to enable cross-project encryption features. We hope to deliver our first microversion revision early in the Wallaby cycle, so tha we can finally release the Secret Consumers feature. Thanks, Douglas Mendizábal [1] https://review.opendev.org/#/c/754735/

1 0

[election][magnum] Add strigazi candidancy for magnum
by Spyros Trigazis 28 Sep '20

28 Sep '20

Hello stackers, I would like to nominate [0] myself for Magnum PTL. In the recent releases the focus of the team was around our kubernetes driver. I would like to continue that direction for wallaby while trying to improve cloud administrators' management. More specifically: * simplifying addon deployment for our kubernetes driver (the current proposal relies on helm3) * allow control plane resizing * optionally run the clusters' control plane on the cloud operators' tenant * investigate addon upgrades The goal of the project is clearly to be very lean and rely as much as possible on the dependent communities like: kubernetes, containerd, calico, helm and so on. Thank you for considering me, Spyros Trigazis [0] https://review.opendev.org/754727

1 0

[release] Release countdown for week R-2 Sept 28 - Oct 2
by Sean McGinnis 28 Sep '20

28 Sep '20

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the victoria deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- If you have deliverables on a cycle-with-rc model but haven't had a RC1 released yet, please check the proposed RC1 releases at [1]. Without a clear answer, the release management team will be approving those on Monday morning! [1] https://review.opendev.org/#/q/topic:victoria-rc1+status:open Early in the week, the release team will be proposing stable/victoria branch creation for all deliverables that have not branched yet, using the latest available victoria release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/victoria branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/victoria branch before releasing out of the stable/victoria branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for wallaby development, though the focus should still be on finishing up victoria until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final victoria release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the victoria version of your project. Upcoming Deadlines & Dates -------------------------- Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[elections][placement][blazar] Placement PTL Non-candidacy: Stepping down
by Tetsuro Nakamura 28 Sep '20

28 Sep '20

Hello everyone, Due to my current responsibilities, I'm not able to keep up with my duties either as a Placement PTL, core reviewer, or as a Blazar core reviewer in Wallaby cycle. Thank you so much to everyone that has supported. I won't be able to checking ML or IRC, but I'll still be checking my emails. Please ping me via email if you need help. Thanks. - Tetsuro -- Tetsuro Nakamura <tetsuro.nakamura.bc(a)hco.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan

4 3

[Kuryr] Proposing Roman Dobosz for kuryr-kubernetes core
by Michał Dulko 28 Sep '20

28 Sep '20

Hello, I'd like to propose Roman for the core reviewer role in kuryr- kubernetes. Roman was leading several successful development activities during Train and Ussuri cycles: * Switch to use openstacksdk as our OpenStack API client. * Support for IPv6. * Moving VIF data from pod annotations to a KuryrPort CR. He also demonstrated code reviewing skills of an experienced Python developer. In the absence of objections, I'll proceed with adding Roman to the core team next week. Thanks, Michał

5 5

Re: [openstack-ansible] OpenStack Ansible deployment fails, due to lxc containers not having network connection
by Oliver Wenz 28 Sep '20

28 Sep '20

> I would recommend always building an All-In-One deployment in a virtual > machine > so that you have a reference to compare against when moving away from > the 'stock config'. > Documentation for the AIO can be found here > https://docs.openstack.org/openstack-ansible/ussuri/user/aio/quickstart.html I gradually decreased the complexity of my test system towards the 'stock config' to find out what caused the error but it kept showing up. Finally, it vanished when I rebooted the server and my original configuration also completed successfully afterwards. 🤦‍♂️ Thank you for your help and the insights to OSA! Kind regards, Oliver

1 0

[ptl][election][mistral] PTL candidacy
by Renat Akhmerov 28 Sep '20

28 Sep '20

Hi, I'm Renat Akhmerov. I'd like to announce my PTL candidacy for Mistral in Wallaby cycle. In Victoria, we made a huge change related to how we manage actions in Mistral. Previously, all actions were stored in the database and when any Mistral subsystem needed to get info about an action (action definition) it sent a query to DB. So, there wasn't any abstraction responsible for action management. This approach is not flexible and makes refactoring incredibly hard. It also means that it's nearly impossible to deliver actions to the system or alter them in runtime w/o having to reboot a cluster node. In Victoria we introduced the new abstraction called Action Provider. Action providers are fully responsible for delivering actions to Mistral. It is possible to. register many providers in the entry point "mistral.action.providers" in setup.cfg of any Python project (installed within the same Python env as Mistral) and Mistral will be using them all to find actions. So action management is now decoupled from the rest of the system and it's now possible to move away from storing action definitions only in the DB. It's fully up to a particular action provider implentation. Actions can even be dynamically generated, for example, as wrappers around a subset of operating system commands. Another option is. requesting info about actions via some communication protocols like HTTP, AMQP etc. There's still work to polish this all and document properly but the main infrastructure is already available and everyone can implement their own action providers. For W cycle I'd like to proceed with improving Mistral usability (toolset for developing Mistral actions, docs etc.) and address several known scalability issues. As always, anyone is very welcome to join our project. It's a lot of fun to work on it. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.opendev.org/#/c/754646/ Cheers Renat Akhmerov @Nokia

1 0

[tripleo][ci] proposing Yatin as tripleo-ci core
by Wesley Hayutin 28 Sep '20

28 Sep '20

Greetings, I really thought someone else had already sent this out. However I don't see it so here we go. I'd like to propose Yatin Karel as tripleo-ci core. You know you want to say +2 :)

19 18

[adjutant][election] PTL candidacy for Wallaby
by Adrian Turjak 27 Sep '20

27 Sep '20

Hello All, I'm submitting myself as the PTL for Adjutant during the W cycle. The focus is as always to continue maintaining the project to ensure it is operating as expected and as bug free as possible. Wallaby will mostly be about cleaning up some internal systems, and minor features to help with custom plugin support. The hope is to also clean up policy/role in this release, and include some elements of that into the plugin layer, and to start working on more useful user management features. Depending on time and resources, we may start work on async worker support to allow some parts of tasks to be processed asynchronously. Cheers, Adrian Turjak

1 0

[all][elections][ptl][tc] Combined PTL/TC Nominations ending soon
by Jeremy Stanley 27 Sep '20

27 Sep '20

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 23:12:19 Nominations progress : 71.90% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 18 ( 32.73%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 37 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Ec2_Api Freezer Horizon Ironic Karbor Magnum Manila Masakari Mistral Monasca Murano Octavia OpenStack_Charms OpenStack_Helm Oslo Packaging_Rpm Placement Qinling Quality_Assurance Rally Requirements Searchlight Senlin Solum Storlets Tacker Telemetry Trove Watcher Zun) =================================================== Stats gathered @ 2020-09-28 00:32:41 UTC This means that with approximately 2 days left, 37 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 1

[election][tacker] PTL candidacy for Wallaby
by Yasufumi Ogawa 27 Sep '20

27 Sep '20

Hi, I'd like to propose my candidacy for Tacker PTL in Wallaby cycle. In Victoria release, we have released great features required for the latest ETSI NFV standard and made several improvements for Tacker as and as planed in the last vPTG. We also fix issues for migrating to python3 and Ubuntu focal. As a PTL, I've led the team by proposing not only new features, but also things for driving the team such as documentation or bug tracking. It was something hard, but is running well. In Wallaby cycle, I would like to continue to make Tacker be more useful product from not only telco, but also all users interested in NFV. I believe Tacker will be a good reference implementation for NFV standard. We have planed to make Tacker more feasible not only for VM environment, but also container to meet requirements from industries. - Introduce the latest container technology with ETSI NFV standard. - Reinforce test environment for keeping the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. - Revise wiki and documentation for covering users more. Regards, Yasufumi Ogawa

1 0

[election][heat] PTL candidacy for Wallaby
by Rico Lin 27 Sep '20

27 Sep '20

Hi all, I would like to announce my candidacy for Heat PTL for Wallaby cycle. Over the past couple of cycles, we running Heat dynamically according to requirements. We never stop encouraging people to join us and provide consistent reviews or fixes as much as we can based on priorities. And if those priorities not working for you, that means you must join the community to help. I believe the goals for the next cycle should be community CI stability, cross-project/community scenario tests to ensure what we deliver to users will get higher quality, also to get rid of legacy mode and move everything to convergence mode, and finally container-native support to make sure we provide usable Orchestration services for the container environment. I believe in new features, so we will try to encourage more features and review them as many as possible, but will not plan for team feature goals unless we can trigger more discussion and hands-on.Thank you for taking my self-nomination into consideration. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

API short reponse time between the S version and the U version
by Zhi CZ Chang 26 Sep '20

26 Sep '20

1 0

[election][swift] PTL candidacy for Wallaby
by Tim Burke 26 Sep '20

26 Sep '20

I'd like to announce my candidacy for Swift PTL for the Wallaby cycle. This past year, Swift celebrated ten years running in production. Much has changed in that time: new features have been developed and polished, versions of Python have come and gone, and clusters have grown to staggering capacities. However, our commitment to operational excellence remains the same. Recently (particularly in the last several months), I've noticed our contributors increasingly have an operator's mindset. We look for more and better ways to measure Swift. We seek to reduce client impacts from config reloads and upgrades. We take greater ownership over the health and performance of our clusters. To a large extent, we're all operators now. The benefits have been enormous. We've improved performance; we've upgraded without disrupting any client requests; we've migrated clusters to Python 3 to position them well for the next ten years. Through it all, clients put ever more data into Swift. The increases in demand bring almost incomprehensible scales. We now see individual clusters sustaining tens of thousands of requests every second. We see containers with a billion objects. We see expansions that are as large as many whole clusters were just a few years ago. This is our next great challenge: how do we move away from a world where expansions are a rarity that may require a bit of a scramble and into a world of constant expansion? How can we effectively manage clusters with thousands of nodes? How do we shift from thinking in terms of petabytes to exabytes? I can't wait to see how we rise to meet this challenge. Tim Burke

1 0

The question about OpenStack instance fail to boot after unexpected compute node shutdown
by Yule Sun 26 Sep '20

26 Sep '20

I saw your message on the website http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005635.ht… . And i have been troubled by the same problem for a long time . I tried to change the parameters resume_guests_state_on_host_boot=True and instance_usage_audit=True in the nova.conf ,but it didn't work . I wonder if you have solved this problem, looking forward your reply, Thank you and best regards. And my instance error looks like this . [cid:e8770762-d2b2-4630-9ce6-4d357dc92cee]

2 1

[election][zaqar] PTL candidacy for Wallaby
by hao wang 26 Sep '20

26 Sep '20

Hi, I want to propose my candidacy and continue serving as Zaqar PTL in the Wallaby cycle. For the Victoria release, the Zaqar team continues to keep the Zaqar stable and reliable, and also some great works have been done. We designed and implemented the Encrypted message in the queue to enhance the security of Zaqar. We also fixed some bugs to meet the python3 requirements. In the Wallaby cycle, I would like to continue serving this project and bring more contributors and the user requires. There are some major works I want to do in W cycle: 1.Finish the Topic resource work, to support all backends. 2.Consider to support more backends that have widely used. 3.Continue to support more security algorithms for encrypted messages. 4.Implement some new requirements from users. 5.keep Zaqar more reliable as usual. Thanks to everyone to support my work and keep contributing to Zaqar. I will do my best in the new cycle.

1 0

[openstack-ansible][election] Candidacy
by Dmitriy Rabotyagov 25 Sep '20

25 Sep '20

Hey everyone! This cycle I've decided to take part in elections and run for PTL of the OpenStack-Ansible project. I feel that OSA nowadays is a solid and stable project, and we're doing a great job to get all features in time and deploy only modern software with our deployments, as well as providing deployers with a high range of different supported options and flexibility. It's rather important to keep up with the progress. And there are main things I'd love to focus on during the upcoming release: # Integration tests coverage for all roles Despite migrating tests for most of the projects to the integrated repo, we still have several projects not covered with proper testing (like Zun). I also would love to pay attention to passing appropriate tempest scenarios for all projects instead of running some default ones. # Cleaning up bugtracker I think one of our highest priorities should be project stability. And taking care of bugs might help us heavily with that. We haven't been paying enough attention to our Launchpad for a while and I think we should change that by cleaning up stale bugs, so we could focus on real ones. Returning bug triage to the meeting might be also an efficient way to handle them. # Roles cleanup We have a lot of things left in code, like workarounds for upgrades, upstream bugs, support for obsolete operating systems, etc. Removal/replacement of deprecated OpenStack options should be also included. # Usage of the new pip resolver Our venv build process relies on provided constraints heavily, which isn't valid in case of the new pip resolver usage, so we will need to make appropriate adjustments into the process to keep the ability to define specific package requirements and use modern pip. Thank you for taking into consideration my nomination.

1 0

Re: [magnum][infra] Can We Delete the OpenDev Fedora Atomic Images Mirror
by feilong＠catalyst.net.nz 25 Sep '20

25 Sep '20

1 0