January 2023 - openstack-discuss - lists.openstack.org

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

06 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 04. Most of the meeting discussions are summarized in this email. Meeting recordings are available @ https://www.youtube.com/watch?v=4vR7iStJZe0 and summary logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-04-16.00.log.html * The next TC weekly meeting will be on Jan 11 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 10. 2. What we completed this week: ========================= * Nothing specific for this week. 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[2]. Open Reviews ----------------- * Two open reviews for ongoing activities[3]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- Clarkb reported this last week and we had an initial discussion in the TC meeting. xstatic-font-awesome repo which is under the Horizon project has non-OpenStack core as maintainers in PyPI and recently a new maintainer is added[4] without going through or knowing by the OpenStack Horizon PTL. While checking other deliverables, I found there are other maintainers present in many of the deliverables. A few examples are https://pypi.org/project/murano/ https://pypi.org/project/glance/ To avoid two sets of maintainers for OpenStack deliverables (one OpenStack and one external), we should clean this up. 'openstackci' is maintainers on the PyPI side which can be kept for all the OpenStack deliverables. If any external maintainers want to maintain it external to OpenStack and OpenStack project is ok for that then we can discuss that option also. For example, xstatic-* repo can be a good example to handover to the external maintainer if the Horizon team agrees. We will discuss it in the next TC meeting also. Meanwhile, I will reach out to the Horizon team and find more about the xstatic-* repos. IMPORTANT: Tox 4 failure ------------------------------- As you might have seen the gate failure due to tox4 (even the latest release too), we discussed in TC meeting[5] and after testing[6] we pinned tox<4 for the stable branch. Pinning is done in the common job in openstack-zuul-jobs repo [7]. But there are some cases where this global pinning is not enough and the latest tox is installed by pip. For example, Brian reported one case[8]. In that case, you can explicitly pin tox in the tox.ini file otherwise global pinning should work fine. For the master, we need to fix the failure. Hoping we do not get more new failures on every new tox release (for example, the missing interpreter issue which is fixed by stephenfin today). Mistral release and more maintainers ------------------------------------------- Mistral gate is green and things are merging there[9] so I feel it is ready for release. But I have sent an email reply on ML[10] to know more about it from the Mistral team. Adjutant release and more maintainers ---------------------------------------------- Adjutant is in the Inactive project list. But I have seen Dale (PTL) has fixed the gate and merged the things[11]. I will ping Dale about the release status and accordingly we can decide on its status change if needed. Project updates ------------------- * Add Cinder Huawei charm[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://github.com/openstack/xstatic-font-awesome/pull/2 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031668… [6] https://review.opendev.org/q/topic:tox4-pin-testing [7] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849/4 [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031678… [9] https://review.opendev.org/q/project:openstack/mistral [10] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031687… [11] https://review.opendev.org/q/project:openstack/adjutant [12] https://review.opendev.org/c/openstack/governance/+/867588 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][mistral][release] Propose to deprecate Mistral
by Elõd Illés 06 Jan '23

06 Jan '23

Hi, Mistral projects are unfortunately not actively maintained and caused hard times in latest official series releases for release management team. Thus we discussed this and decided to propose to deprecate Mistral [1] to avoid broken releases and last minute debugging of gate issues (which usually fall to release management team), and remove mistral projects from 2023.1 Antelope release [2]. We would like to ask @TC to evaluate the situation and review our patches (deprecation [1] + removal from the official release [2]). Thanks in advance, Előd Illés irc: elodilles @ #openstack-release [1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://review.opendev.org/c/openstack/releases/+/865577

6 7

[release] Release countdown for week R-10, Jan 9 - 13
by Thierry Carrez 06 Jan '23

06 Jan '23

Development Focus ----------------- We are now past the antelope-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 9). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 16) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 16. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 2) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 16) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 9 (R-6 week) Client library freeze: February 16 (R-5 week) antelope-3 milestone: February 16 (R-5 week) Final 2023.1 Antelope release: March 22nd, 2023 -- Thierry Carrez (ttx)

1 0

[kolla] Propose Bartosz Bezak for core reviewer
by Michał Nasiadka 06 Jan '23

06 Jan '23

Hello Koalas, I’d like to propose Bartosz Bezak as a core reviewer for Kolla, Kolla-Ansible, Kayobe and ansible-collection-kolla. Bartosz has recently went through release preparations and release process itself for all mentioned repositories, has been a great deal of help in meeting the cycle trailing projects deadline. In addition to that, he’s been the main author of Ubuntu Jammy and EL9 (Rocky Linux 9 to be precise) support in Kayobe for Zed release, as well as fixing various bugs amongst all four repositories. Bartosz also brings OVN knowledge, which will make the review process for those patches better (and improve our overall review velocity, which hasn’t been great recently). Kind regards, Michal Nasiadka

6 6

Nova libvirt/kvm sound device
by Zakhar Kirpichenko 06 Jan '23

06 Jan '23

Hi! I'd like to have the following configuration added to every guest on a specific host managed by Nova and libvirt/kvm: <sound model='bla'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </sound> When I add the device manually to instance xml, it works as intended but the instance configuration gets overwritten on instance stop/start or hard reboot via Nova. What is the currently supported / proper way to add a virtual sound device without having to modify libvirt or Nova code? I would appreciate any advice. Best regards, Zakhar

2 2

[designate] Implemeting PTR record restrictions
by Thomas Goirand 06 Jan '23

06 Jan '23

Hi, We implemented this scenario for our public cloud: https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.htm… This is currently in production in beta-mode at Infomaniak's public cloud. We did that, because we want our customers to be able to set any domain name or PTR for the IPs they own. However, we discovered that there's no restriction on what zone customers can set. For example, if customer A owns the IP 203.0.113.9, customer B can do "openstack zone create 9.113.0.203.in-addr.arpa.", preventing customer A to set their PTR record. Is there currently a way to fix this? Or maybe a spec to implement the correct restrictions? What is the way to fix this problem in a public cloud env? Cheers, Thomas Goirand (zigo)

2 1

[designate] New project: designate-tlds
by Thomas Goirand 05 Jan '23

05 Jan '23

Hi, We wrote this: https://salsa.debian.org/openstack-team/services/designate-tlds The interesting code bits are in: https://salsa.debian.org/openstack-team/services/designate-tlds/-/blob/debi… What it does is download the TLD list from https://publicsuffix.org/list/public_suffix_list.dat using requests (with an optional proxy), compare it to the list of TLDs in Designate, and fix the difference. It's by default setup in a cron every week. Basically, it's just apt-get install designate-tlds, configure keystone_authtoken in /etc/designate-tlds/designate-tlds.conf and set dry_run=false, and you're done! Note I also wrote a patch for puppet-designate [1] to support it. Moving forward I see 2 solutions: 1- we continue to maintain this separately from Designate 2- our code gets integrated into Designate itself. Designate team: are you interested for option 2? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/puppet/puppet-module-designate/-/bl…

2 1

[nova][neutron][openstacksdk] Any API way to tell the difference for openstack ports created manually or automatically?
by hai wu 05 Jan '23

05 Jan '23

I could not find any API way to tell the difference between openstack ports created automatically when a new instance got created, and openstack ports manually created for port reservation purposes. There's 'preserve_on_delete' attribute in the openstack database for each vm instance, and if it is set to 'true', then the port was manually created, if not, then it was automatically created. But there's no API to retrieve this. Am I missing something? Hai

3 4

The Next OpenStack Release Name Is...
by Erin Disney 04 Jan '23

04 Jan '23

Hey everyone- Voting for the upcoming OpenStack B release name has ended and we have a winner... BOBCAT! Thanks to everyone who voted and helped us pick the next name. Thanks, Erin Erin Disney Event Marketing OpenInfra Foundation

1 0

[cinder][drivers] third-party CI for os-brick changes
by Brian Rosmaita 04 Jan '23

04 Jan '23

To all third-party CI maintainers, As you are aware, cinder third-party CI systems are required to run on all cinder changes. However, the os-brick library used in cinder CI testing is the latest appropriate *released* version of os-brick. Thus, it is possible for changes to be happening in os-brick development that might impact the functionality of your driver. If you aren't testing os-brick changes, you won't find out about these until *after* the next os-brick release, which is bad news all around. Therefore, at last week's cinder midcycle [0], the cinder project team agreed to require that cinder third-party CI systems run on all os-brick changes in addition to all cinder changes. This is a nice-to-have for the current (Zed) development cycle, but will be required in order for a driver to be considered 'supported' in the 2023.1 (Antelope) release [1]. If you have comments or concerns about this policy, please reply on the list to this email or put an item on the agenda [2] for the cinder weekly meeting. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_changes… [2] https://etherpad.opendev.org/p/cinder-zed-meetings

2 1