April 2023 - openstack-discuss - lists.openstack.org

[kolla][kolla-ansible] Kolla-Ansible mirror update and kolla images
by Nguyễn Hữu Khôi 18 Apr '23

18 Apr '23

Hello. I have a question. I use kolla-ansible 13.0.0 and kolla 13.0.0 images then I upgrade kolla-ansible to 13.8.0. I will use kolla 13.8.0 to build new images? Thank you. Regards Nguyen Huu Khoi

3 4

[neutron] Bug deputy April 10-16th
by Rodolfo Alonso Hernandez 18 Apr '23

18 Apr '23

Hello Neutrinos: This is the bug list from the last week: High: * https://bugs.launchpad.net/neutron/+bug/2015847: Functional job db missconfiguration. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2016142: [sqlalchemy-20] Error in "get_ports_on_host_by_subnet" execution. Fixed. * https://bugs.launchpad.net/neutron/+bug/2016266: [Secure RBAC] Get availability zone API should be available for READER role. Assigned to Slawek. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/880461 Medium: * https://bugs.launchpad.net/neutron/+bug/2016198: [L3][HA] race condition between first two router creations when tenant has no HA network. Related to https://bugs.launchpad.net/neutron/+bug/2016197. Not assigned. Low: * https://bugs.launchpad.net/neutron/+bug/2015844: Remove netifaces dependency from neutron. To be discussed during the Neutron meeting. * https://bugs.launchpad.net/neutron/+bug/1988039: ovs idl not monitor tables after reconnect. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/857010 * https://bugs.launchpad.net/neutron/+bug/2016413: api-ref: missing documentation for subnet-onboard. Not assigned. Whislist: * https://bugs.launchpad.net/neutron/+bug/2016158: [OVN] How to deal with SB "Chassis"/"Chassis_Private" duplicated registers. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2016197: [Open Discussion] neutron can create port from network which has no subnet. Not assigned (maybe it won’t be necessary). Regards.

1 0

[zun][zun_api][blazar][config][yoga][kolla-ansible] Adding more configuration to config file
by James Leong 18 Apr '23

18 Apr '23

Hi all, I am playing around with Zun. I have used kolla-ansible as a deployment tool for deploying the yoga version of OpenStack. I am trying to add an option to the configuration file. However, those added options are not recognized by OpenStack when being called. For instance, Zun.conf, I am adding a new database (blazar) information to it so I can access blazar information in the zun service. Would that be possible to allow the zun_api container to access the blazar database? Thanks for your help, James

3 2

Re: [all][stable][ptl] Propose to EOL Rocky series
by Elõd Illés 17 Apr '23

17 Apr '23

Hi, thanks for all the feedbacks from teams so far! @Zigo: Extended Maintenance process was created just for the same situation: to give space to interested parties to cooperate and keep things maintained even when stable releases are over their 'supported' lifetime. So it's good to see that there is interest in it! Unfortunately, with very old branches we've reached the state where gates can't be maintained and without a functional gate it's not safe to merge patches (yes, even security fixes) and they are just using resources (CI & maintainers' time). When gate is broken in such extent, then i think the community have to accept that it is not possible to merge patches confidently and needs to EOL that release. (Yes, it means that some vendors still have to do it for their own sake, testing it by their own, etc). Keeping things open in such state gives the false signal to vendors that 'it is maintained' however this is done without fully testing the changes. Another aspect is that code cannot be cleaned up until those old branches are still present (CI jobs, project configurations, etc) which gives pain for developers. So, however some vendors would appreciate probably to keep things open forever, for the community this is not beneficial and doable I think. Seeing that teams want to EOL their old branches is a proof that this is needed (unfortunately). Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release ________________________________ From: Thomas Goirand <thomas(a)goirand.fr> Sent: Saturday, January 28, 2023 2:25 PM Cc: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: Re: [all][stable][ptl] Propose to EOL Rocky series Hi, I understand the gate is broken, however, Rocky is in Debian LTS, and I would like to keep the possibility to merge patches, even with the gate tests disabled. CVE-2022-47951 is an example why this is important... Thomas Goirand (zigo) On Jan 28, 2023 11:54, Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: > > Masakari is happy to EOL Rocky too. > > Radek > -yoctozepto > > On Fri, 27 Jan 2023 at 20:59, Jay Faulkner <jay(a)gr-oss.io> wrote: > > > > Thanks for doing all this cleanup work Elod. Ironic is OK with retirements of these shared resources up to Train. > > > > - > > Jay Faulkner > > > > On Fri, Jan 27, 2023 at 10:12 AM Elõd Illés <elod.illes(a)est.tech> wrote: > >> > >> Hi, > >> > >> Similarly like the Queens branch EOL proposal [1] I would like to propose > >> to transition every project's stable/rocky to End of Life: > >> > >> - gates are mostly broken > >> - minimal number of activity can be seen on this branch > >> - some core projects already transitioned their stable/rocky to EOL > >> recently (like ironic, neutron, nova) > >> - gate job definitions are still using the old, legacy zuul syntax > >> - gate jobs are based on Ubuntu Xenial, which is also beyond its public > >> maintenance window date and hard to maintain > >> > >> Based on the above, if there won't be any project who wants to keep open > >> their stable/rocky, then I'll start the process of EOL'ing Rocky stable > >> series as a whole. If anyone has any objection then please respond to > >> this mail. > >> > >> Thanks, > >> > >> Előd Illés > >> irc: elodilles @ #openstack-stable / #openstack-release > >> > >> [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-October/031030… > >> >

3 4

[Neutron] Future of TripleO OVN migration in-tree code
by Jakub Libosvar 17 Apr '23

17 Apr '23

Hello Neutrinos and others, as this has been brought up several times through some conversation channels with no consensus, I wanted to start a discussion and possibly find a consensus about the code for migrating an OpenStack from OVS mechanism driver to OVN [1]. The code leverages TripleO to install and to configure OVN services, however the TripleO project is no longer maintained after Zed release [2]. This brings up the question what to do with the migration tooling that relies on TripleO. Shall we remove the code completely or is there anybody who would be interested in maintaining that code and implement support for other installers? Thanks Kuba [1] https://opendev.org/openstack/neutron/src/branch/master/tools/ovn_migration… [2] https://review.opendev.org/c/openstack/governance/+/878799

2 2

[kolla] Reducing ceilometer, gnocchi, aodh time interval
by Modyngs 17 Apr '23

17 Apr '23

Dear lists, Hi I have recently noticed of this link to customize configurations to be overridden [Thanks to michal nasiadka]: https://docs.openstack.org/kolla-ansible/latest/admin/advanced-configuratio… but i have some doubts in regards! The docs says /etc/kolla/ config/<< service name >>/<< config file >> (Ex. /etc/kolla/config/nova/nova-scheduler.conf) let's say i want to change interval to 30sec (* 'interval: 30'*) in *'/etc/kolla/ceilometer-central/polling.yaml'* file: as i understood, i need to create a file in *'/etc/kolla/config/ceilometer-central/polling.yaml'* and copy all the contents of * '/etc/kolla/ceilometer-central/polling.yaml'* into it ( *or just the change?*) and then change just the *interval from 300 to 30 .* Am I doing Right? ( because there was no [DEFAULT] section available in the polling.yaml file ....) After doing the same for all the desired files, then i need to do prechecks and deploy? kolla-ansible -i /etc/kolla/all-in-one prechecks kolla-ansible -i /etc/kolla/all-in-one deploy Thanks

1 0

[largescale-sig] Next meeting: April 19, 15utc
by Thierry Carrez 17 Apr '23

17 Apr '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC, our EU+US-friendly time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230322T14 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[tc] Technical Committee next weekly meeting on 2023 April 18 at 1800 UTC
by Nikolla, Kristi 17 Apr '23

17 Apr '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday (April 18) at 1800 UTC on #openstack-tc on OFTC IRC Items can be proposed by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Unless there are last minute additions (for which I will send a follow-up email) the agenda will be: • Roll call • Follow up on past action items • gmann respond to Sahara PTL volunteer to propose a patch to governance, and explain the outcome of today's discussion • jamespage to write email about Winstackers removal • Gate health check • 2023.2 cycle Leaderless projects • https://etherpad.opendev.org/p/2023.2-leaderless • Broken docs due to inconsistent release naming • Recurring tasks check • Bare 'recheck' state • https://etherpad.opendev.org/p/recheck-weekly-summary • Open Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

Installation
by BEDDA Fadhel 15 Apr '23

15 Apr '23

Bonjour, Ou je peux trouver pour tester openstack sur Ubuntu 22.04 Cordialement

3 2

[tc][all] What's happening in the Technical Committee - 2023 April 14
by Nikolla, Kristi 14 Apr '23

14 Apr '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on April 11 on the #openstack-tc channel on OFTC IRC. The next weekly meeting will happen on April 18th. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Final call for Winstackers (and Windows Support) ------------------------------------------------ Cloudbase Solutions are no longer in a position to maintain support for running OpenStack on Windows and have also ceased operation of their 3rd party CI for the windows support across a number of OpenStack projects. This is the final call for any maintainers to step forward for maintaining Winstackers if this feature is important to them in OpenStack[0][1]. If there is no response by June 2023, we will discuss the retirement of this project. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033342.h… [1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033273.h… Final call for Vitrage maintainers ---------------------------------- This is the final call for maintainers. If anyone is using or interested in this project, this is the right time to step up. If there is no response by the end of April 2023, we will discuss the retirement of this project.[0] [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033348.h… Patrole retirement ------------------ As notified on the mailing list yesterday[0] and by a patch proposed to the governance repo[1], the Patrole project is being retired. The project is inactive, and there was no interest from prospective maintainers. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033346.h… [1]. https://review.opendev.org/c/openstack/governance/+/880014 Gate status ----------- Every week we have a look at the overall status of the "gate". In the last meeting the status was reported and not super healthy[0]. * The U-C bump broke Glance's functional test and there is a desire to put Glance's functional tests behind the U-C gate so that future breakages are caught before they happen. * It was also reported that we were seeing some guest kernel crashes on volume tests. These may be related to nested virtualization. [0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-11-17.59.log.html#… Changes ======= * Merged * Add ovn-bgp-agent to Neutron governed projects (project-update) | https://review.opendev.org/c/openstack/governance/+/879455 * Add xstatic-angular-fileupload as Horizon team deliverables (project-update) | https://review.opendev.org/c/openstack/governance/+/873845 * Retire puppet-tacker - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/875295 * New Open * Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/879847 * Retire patrole (project-update) | https://review.opendev.org/c/openstack/governance/+/880014 * Correct the old deprecated policies removal timeline for SLURP release (formal-vote) | https://review.opendev.org/c/openstack/governance/+/880238 * Add missing governance-sigs repo in technical-committee-repos.yaml (project-update) | https://review.opendev.org/c/openstack/governance/+/880237 * Retire puppet-rally - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/880018 * All Open * https://review.opendev.org/q/project:openstack/governance+status:open 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 an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0