February 2023 - openstack-discuss

[publiccloud-sig] Reminder - next meeting March 1st - 0800 UTC
by Felix Kronlage-Dammers 27 Feb '23

27 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on March 1st (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[qa][tc] uwsgi is now in maintenance mode. how does this affect us ?
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, I happened to notice that uwsgi announced it's now in maintenance mode. https://github.com/unbit/uwsgi/blame/master/README#L5 Is anybody aware of this ? The README file says they will still maintain the repo for bug fixes and new python version support. This is nice but is not a good sign, and can be concerning for us because we have been using uwsgi in devstack since we selected it as our default stack when we implemented the community goal to support wsgi framework[1]. [1] https://governance.openstack.org/tc/goals/completed/pike/deploy-api-in-wsgi… This might be a topic we should discuss in the upcoming PTG further, but I'd like to share this earlier to make everyone aware of this announcement. I'm very happy to be corrected if I'm looking at something wrong ... Thank you, Takashi Kajinami

9 12

[largescale-sig] Status update
by Thierry Carrez 27 Feb '23

27 Feb '23

Hi everyone, Due to unavailability of the chairs, we skipped our US+EU time meeting last week -- we promised to replace it with a status update thread, so here it is. Regarding the OpenInfra Live episode, we have some interest from Société Générale to participate in the next Deep Dive. I'll try to confirm it this week. Regarding future events, we planned to run a Forum session at the OpenInfra Summit in Vancouver, as those are always well-attended. I'll submit it to the CFP this week. Our next IRC meeting will be next week, March 8, at 0900utc on #openstack-operators on OFTC. Other members of the SIG, feel free to add more detail in response to this thread! Regards, -- Thierry Carrez

1 0

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Simon Jones 27 Feb '23

27 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ ---- Simon Jones

2 1

[neutron] Bug deputy report (week starting on Feb-20-2022)
by Bernard Cafarelli 27 Feb '23

27 Feb '23

Hey neutrinos, Here are the bugs reported between February 20 and 26. Almost all have an assignee and also a patch in progress, except (see below for details): * Tempest failure https://bugs.launchpad.net/neutron/+bug/2008062 * Two VPNaaS bugs https://bugs.launchpad.net/neutron/+bug/2007826 and https://bugs.launchpad.net/neutron/+bug/2008001 Also note the sqlalchemy 2.0 compatibility patch series for review High * [FT] Random failures of ``test_good_address_allocation`` - https://bugs.launchpad.net/neutron/+bug/2007992 Related chain of patches by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874658 * [sqlalchemy-20] The Engine.execute() method is considered legacy as of the 1.x series - https://bugs.launchpad.net/neutron/+bug/2008223 * [sqlalchemy-20] Use the .begin() method of Engine - https://bugs.launchpad.net/neutron/+bug/2008226 * [sqlalchemy-20] The Connection.connect() method is considered legacy as of the 1.x series of SQLAlchemy - https://bugs.launchpad.net/neutron/+bug/2008227 * [sqlalchemy-20] The Session.begin.subtransactions flag is deprecated - https://bugs.launchpad.net/neutron/+bug/2008276 A series of sqlalchemy 2.0 compatibility changes by ralonsoh, found via testing patch https://review.opendev.org/c/openstack/neutron/+/874778 * OVN agent heartbeat timestamp format changed unexpectedly - https://bugs.launchpad.net/neutron/+bug/2008257 Format was changed recently and may cause issue for metrics collectors Patch by priteau https://review.opendev.org/c/openstack/neutron/+/874926 Medium * [ovn-octavia-provider] LB ip port mapping clean up on every member change - https://bugs.launchpad.net/neutron/+bug/2007835 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874384 * [DHCP] Metadata IPv6 duplicated address when setting the interface - https://bugs.launchpad.net/neutron/+bug/2007938 Reproduced by and assigned to rubasov * [ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM - https://bugs.launchpad.net/neutron/+bug/2007985 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609 * Tempest test TestNetworkBasicOps.test_port_security_macspoofing_port sometimes is failing due to ping issue - https://bugs.launchpad.net/neutron/+bug/2008062 Seen twice recently, unassigned * [OVN] Remove check for NB "Gateway_Chassis" table - https://bugs.launchpad.net/neutron/+bug/2008077 Patch by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874767 * Neutron allows you to delete router_ha_interface ports, which can lead to issues - https://bugs.launchpad.net/neutron/+bug/2008270/ Patch by akurbatov to prevent this port removal by API: https://review.opendev.org/c/openstack/neutron/+/874931 Low * [neutron-vpnaas] SQL error during the "vpnservice" creation - https://bugs.launchpad.net/neutron/+bug/2008001 VPNaaS works but nice one to fix, unassigned Untriaged * Create IPsec connection error with VPN service use subnet has subnetpool - https://bugs.launchpad.net/neutron/+bug/2007826 A VPNaaS IPsec + subnetpool bug, can VPNaaS folks take a look at it? Have a great week! -- Bernard Cafarelli

1 0

[heat][tripleo][governance] Governance of os-*-config and future of software deployment feature
by Takashi Kajinami 26 Feb '23

26 Feb '23

Hello, tl;dr Can we move os-(apply|collect|refresh)-config to Heat's governance ? Currently we have the following three repositories maintained under the TripleO's governance. - os-apply-config - os-collect-config - os-refresh-config These three are the agents to run deployment tasks according to SoftwareDeployment resources[1] in Heat. Historically the feature was developed to be used by TripleO, and these agents have been maintained by the TripleO team. However these repositories will be retired as TripleO is being retired[2]. Because the feature itself should be still maintained in heat (especially for stable branches), I'd like to propose migrating these repositories to Heat's governance. I noticed the repository does not have any stable branches after stable/victoria so we likely have to create stable/wallaby and beyond but I'll leave this topic for follow-up. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… Thank you, Takashi Kajinami

6 7

[puppet] Retiring untested and unmaintained modules (murano, rally and tacker)
by Takashi Kajinami 26 Feb '23

26 Feb '23

Hello, In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained. During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort. I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components. These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained. eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement. Thank you, Takashi -- ---------- Takashi Kajinami

4 9

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

24 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 22. 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-22-16.00.log.html * The next TC weekly meeting will be on Mar 1 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 28. 2. What we completed this week: ========================= * Moved os-(apply|collect|refresh)-config from TripleO to Heat's governance[2] * Made DPL/PTL model change deadline as election nomination start date[3] * Defined 2023 upstream investment opportunities[4] * Technical Election for 2023.2 bobcat cycle is completed[5] 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[6]. Open Reviews ----------------- * Nine open reviews for ongoing activities[7]. Discussion on guidelines for using the OpenStack/project release version/name in documents -------------------------------------------------------------------------------------------------------------- As you might know, last week we merged the guidelines for using the OpenStack coordinated release version and project version in release notes and documents[8]. But there is some discussion going on for standalone projects' use case if the standalone projects can skip using the OpenStack coordinated release version and have only the project version in documents. JayF's proposal is up for review[9]. If your project can also be used as a standalone, this is a good time to feedback on the proposal. Leaderless projects for 2023.2 bobcat cycle ---------------------------------------------------- As the election is closed, we have 9 projects without nominations and 2 with identified leaders[10][11]. I have created the etherpad[12] to track and identify the leaders for the remaining 7 projects. If you are using those projects and interested in maintaining or leading them, this is the right time to step up. The Technical Committee Chair election ----------------------------------------------- As the election has closed, it is time for selecting the TC Chair for the next cycle. I have been serving as Chair for the last 2 years and I am not planning to continue it this cycle. It's time for the new Chair. The election process has been started as per the process[13]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation. TripelO team is looking for the volunteer to maintain the stable/zed. If you are interested to help, please reply to James' email[14] Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- JayF has written the process to clean up the PyPi additional maintainers[15]. And Dmitriy is updating the governance document to explicitly mention about PyPi maintainers policy[16]. Other than that, please continue the audit process[17]. 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[18]. Project updates ------------------- * Add Cinder Huawei charm[19] * Add the woodpecker charm to Openstack charms[20] * mistral adopting PTL model[21] * Add xstatic-angular-fileupload as Horizon team deliverables[22] 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[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [24] 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/+/874719 [3] https://review.opendev.org/c/openstack/governance/+/873440 [4] https://review.opendev.org/c/openstack/governance/+/872233 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03244… [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/872769 [9] https://review.opendev.org/c/openstack/governance/+/874484 [10] https://review.opendev.org/c/openstack/governance/+/874969 [11] https://review.opendev.org/c/openstack/governance/+/874971 [12] https://etherpad.opendev.org/p/2023.2-leaderless [13] https://governance.openstack.org/tc/reference/tc-chair-elections.html [14] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03239… [15] https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-ope… [16] https://review.opendev.org/c/openstack/governance/+/874787 [17] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [18] https://etherpad.opendev.org/p/project-health-check [19] https://review.opendev.org/c/openstack/governance/+/867588 [20] https://review.opendev.org/c/openstack/governance/+/869752 [21] https://review.opendev.org/c/openstack/governance/+/873260 [22] https://review.opendev.org/c/openstack/governance/+/873845 [23] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][elections][tc][ptl] 2023.2 Bobcat: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 24 Feb '23

24 Feb '23

Thank you to the electorate, to all those who supported and to all candidates who put their name forward for Technical Committee (TC) & 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. 1. Please join me in congratulating the 5 newly elected members of the TC: Amy Marrich (spotz) James Page (jamespage) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant : Dale Smith (dalees) * Barbican : Grzegorz Grasza (xek) * Blazar : Pierre Riteau (priteau) * Cinder : Rajat Dhasmana () * Cloudkitty : Rafael Weingartner () * Cyborg : alex song () * Designate : Michael Johnson (johnsom) * Ec2 Api : Andrey Pavlov (andrey-mp) * Freezer : ge cong () * Glance : Pranali Deore (pdeore) * Heat : Takashi Kajinami (tkajinam) * Horizon : Vishal Manchanda (vishalmanchanda) * Ironic : Jay Faulkner (JayF) * Keystone : Dave Wilde (d34dh0r53) * Kolla : Michal Nasiadka (mnasiadka) * Kuryr : Roman Dobosz (gryf) * Magnum : Jake Yip (jakeyip) * Manila : Carlos Silva (carloss) * Masakari : sam sue () * Murano : Rong Zhu (zhurong) * Neutron : Rodolfo Alonso Hernandez (ralonsoh) * Nova : Sylvain Bauza (bauzas) * Octavia : Gregory Thiemonge (gthiemonge) * Openstack Chef : Lance Albertson (Ramereth) * OpenStack Helm : Vladimir Kozhukalov () * OpenStackAnsible : Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK : Artem Goncharov (gtema) * Puppet OpenStack : Takashi Kajinami (tkajinam) * Quality Assurance : Martin Kopec (kopecmartin) * Skyline : Wenxiang Wu (wu_wenxiang) * Solum : Rong Zhu (zhurong) * Storlets : Takashi Kajinami (tkajinam) * Tacker : Yasufumi Ogawa (yasufum) * Telemetry : Matthias Runge (mrunge) * Trove : wu chunyang (wuchunyang) * Venus : Eric Zhang () * Watcher : chen ke () * Zaqar : Hao Wang (wanghao) * Zun : Hongbin Lu () PTL Election: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. 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 to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

2 1

[requirement] RFE for multiple python-*clients
by Elõd Illés 24 Feb '23

24 Feb '23

Hi, this is kind of a late, formal bulk request of Requirements Freeze Exception for the following deliverables. Neither of them introduces big changes, rather some tox related gate fix and other minimal changes: * python-muranoclient * python-solumclient * python-heatclient * python-swiftclient * python-keystoneclient * python-saharaclient * python-freezerclient * python-monascaclient The exception is the following deliverable as this has many changes, features, bugfixes in its release: * python-openstackclient Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0