- openstack-discuss - lists.openstack.org

[largescale-sig] Next meeting: Jan 11, 15utc
by Thierry Carrez 12 Jan '23

12 Jan '23

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

1 1

[neutron] PTG flavour: virtual or in person
by Rodolfo Alonso Hernandez 12 Jan '23

12 Jan '23

Hello Neutrinos: I'm reaching you today to ask you about the PTG. Please first read [1] to have a bit of context. Due to the requests from the contributors to bring back the in person events, there will be a PTG along with the OpenInfra Summit in Vancouver. The virtual PTGs will remain and the first one will be in March. My main questions here are: 1) What do you prefer: virtual or in-person? 2) For this year, will you attend the virtual PTG only? Or will you attend the Vancouver one too? In the second question I'm implying that the virtual ones are "mandatory". At least this year those events will be needed to define the roadmap of the next releases, same as the previous virtual PTGs we had (please don't forget to order your ticket [2]). Regards. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645… [2]https://openinfra-ptg.eventbrite.com

4 3

[cinder] Bug Report from 01-11-2023
by Sofia Enriquez 11 Jan '23

11 Jan '23

This is a bug report from 01-04-2022 to 01-11-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/2001619 "svf : if pool attribute is specified in volume type during retype along with --migration-policy defaults to cinder generic migration." Assigned to Sathyanarayana R. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[all][tc] Technical Committee next weekly meeting on 2023 Jan 11 at 1600 UTC
by Ghanshyam Mann 11 Jan '23

11 Jan '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Jan 11, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Jan 10 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[openstack-helm] Stability of Openstack Helm for large Ironic (baremetal) clouds with Openstack Yoga
by Farhad Sunavala 11 Jan '23

11 Jan '23

Hi, We're currently running Openstack services on baremetal.Time to upgrade has come and it is a nightmare.We are evaluating containerizing the services with Openstack Helm. Our cloud:We are essentially a large Openstack Ironic (Baremetal) cloud with 5000-8000 baremetal nodes in different DCs.We are thinking of upgrading from Queens to Yoga. Any feedback on stability of Openstack Helm for such installations? Any pointers on what to expect, gotchas, etc. Thanks,Fred..

2 1

nova api error
by Parsa Aminian 11 Jan '23

11 Jan '23

hello On nova api I have this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete and I have Unknown Error (HTTP 504) error on every nova request .

1 0

The OpenInfra Summit CFP is closing soon!
by Helena Spease 11 Jan '23

11 Jan '23

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is closing in just a few days[1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT. See what that is in your timezone [3] We are also now accepting submissions for Forum sessions [4]! Looking for other resources? Find information on registration, sponsorships, travel support and visa requests at https://openinfra.dev/summit/ <https://openinfra.dev/summit/vancouver-2023> If you have any questions feel free to reach out :) Cheers, Helena [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentations> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su… <https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su…> [4] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/>

3 4

Different between of the role of Nova-Conductor and Nova-Compute
by Huy Võ Lê 10 Jan '23

10 Jan '23

Hi, I have a question about Nova role - Assert: I don't understand about OPS/Redhat explaination. Because all of information said nova-conductor will help database-accessing for nova-compute, every chart/image showed, too. - Reallity: When I download OPS Nova source code looked into nova/compute/manager.py, I saw the many many block code that queries the data from the database (instance list) and updates the data (instance.save). So the assertion of the Openstack and Redhat development community is wrong or true???? Link 1: https://docs.openstack.org/nova/pike/install/get-started-compute.html Link 2: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/… Link n: ....

4 5

[neutron] Bug deputy 2-8 January
by Rodolfo Alonso Hernandez 10 Jan '23

10 Jan '23

Hello Neutrinos: This is the (short) bug list of the last week: * https://bugs.launchpad.net/neutron/+bug/2002316: "ha router - vxlan - incorrect ovs flow ?" Unassigned. Regards.

1 0

Accessing databases of one openstack component from another
by vincent lee 10 Jan '23

10 Jan '23

Hi all, I have a working OpenStack in the yoga version and am trying to customize the zun component. In terms of deployment, I am using Kolla-ansible to deploy the OpenStack. I am trying to access blazar databases from the zun container. However, I have no clue of how the actual flow goes. I hope to receive some directions or suggestions to get me started. Best, Vincent

2 1

[tc] Fwd: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Feb 8, 2023 2pm - 3pm (CST)
by Jeremy Stanley 10 Jan '23

10 Jan '23

Just a reminder that a couple of months ago we arranged a February meeting time between the OpenStack community and the OpenInfra Board of Directors, Wednesday 2023-02-08 at 20:00 UTC. Julia has graciously supplied a conference call connection for the hour (calendar invite attached). I've also added the connection info to the pad we've been using for planning this call: https://etherpad.opendev.org/p/2023-02-board-openstack-sync -- Jeremy Stanley ----- Forwarded message from Julia Kreger ----- Date: Wed, 16 Nov 2022 21:31:42 +0000 Subject: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Feb 8, 2023 2pm - 3pm (CST) (jeremy(a)openinfra.dev) OpenInfra Board sync with OpenStack TC Wednesday Feb 8, 2023 ⋅ 2pm – 3pm Central Time - Chicago Location https://us02web.zoom.us/j/87498907965?pwd=T0h3dDAwVHk1dTBqcVpxa202YmRPUT09 Greetings Directors & All, Meeting invite per informal discussion call on November 16th, for the next informal discussion. Note: This is being sent in advance of the new board being seated. We'll obviously need to update this invite once elections have completed. -Julia ────────── Julia Kreger is inviting you to a scheduled Zoom meeting. Join Zoom Meeting: https://us02web.zoom.us/j/87498907965?pwd=T0h3dDAwVHk1dTBqcVpxa202YmRPUT09 Meeting ID: 874 9890 7965 Passcode: 035164 ----- End forwarded message -----

1 0

[cinder] Unit test failures under Python 3.11 - mocks can no longer be provided as the specs for other Mocks
by Sofia Enriquez 10 Jan '23

10 Jan '23

Hi, Since python3.11 mocks can no longer be provided as the specs for other Mocks. As a result, an already-mocked object cannot be passed to mock.Mock(). This can uncover bugs in tests since these Mock-derived Mocks will always pass certain tests (e.g. isinstance) and built-in assert functions (e.g. assert_called_once_with) will unconditionally pass.[1] There's a bug report to track this issue in Cinder [2] but I think this may affect other projects too. I've reproduce the error and most drivers fail with: ``` unittest.mock.InvalidSpecError: Cannot spec a Mock object. [object=<Mock name='mock.client.HPE3ParClient' id='139657768087760'>] ``` Cheers, Sofia [1] https://github.com/python/cpython/issues/87644 [2] https://bugs.launchpad.net/cinder/+bug/2000436 -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

4 3

[Kolla] Transition Ussuri/Victoria to EOL
by Bartosz Bezak 09 Jan '23

09 Jan '23

Hello, As aggreed on IRC meeting, Kolla Ussuri and Victoria deliverables (Kolla, Kolla-Ansible, Kayobe) are going EOL. [1] Wallaby remains in extended maintenance. Xena, Yoga and Zed are our current stable releases. Ussuri and Victoria branches were in Extended Maintenance for a some time, Kolla community does not have resources to support those branches actively. Moreover Ussuri and Victoria were the last releases that support CentOS 8 which is also EOL. All changes to those branches have been abandoned. [1] https://review.opendev.org/c/openstack/releases/+/869569 Best regards, Bartosz Bezak

1 0

[Nova][Horizon]
by Nguyễn Hữu Khôi 09 Jan '23

09 Jan '23

Hello guys. Is there any way to assign AZ to a specified project? After searching, I cannot find any answer. Example. Sale project will only see Sale AZ to select. Tech project will only see Tech AZ to select Thank you. Regards Nguyen Huu Khoi

3 7

[all][gate][stable] Pinning tox<4 in stable branch testing
by Ghanshyam Mann 09 Jan '23

09 Jan '23

Hello Everyone, As you might know, tox4 broke almost all the projects tox.ini and so do master as well as stable branches gate. On the master, we need to fix it as we should use tox4 in testing. To fix the stable branches gate, either we need to backport all the fixes which include some more issues fixes[1] or we can pin the tox<4. We discussed it in today's TC meeting and it is better to keep testing the stable branch with the tox version that they were released with and not with the tox4. Even in future, there might be the cases where latest tox might introduce more incompatible changes. By considering all these factors, it is better to pin tox<4 for stable branches (<=stable/zed) testing. I have prepared the patch to pin it in the common job/template, feel free to comment with your feedback/opinion: - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849/3 also, tested with nova/cinder stable branches: - https://review.opendev.org/q/I0ca55abf9975c5a3f9713ac5dd5be39083e04554 - https://review.opendev.org/q/I300e7804a27d08ecd239d1a7faaf2aaf3e07b9ee You can also test it in your project stable branches in case any different syntax in tox.ini causing the tox upgrade to the latest. [1] https://github.com/tox-dev/tox/issues/2712 -gmann

4 7

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 09 Jan '23

09 Jan '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we continue working on planning for the OpenInfra Summit as well as Foundation-wide surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

[blazar] Next IRC meeting cancelled
by Pierre Riteau 09 Jan '23

09 Jan '23

Hello, I am unable to run the IRC meeting on Thursday January 12. I propose to cancel it. Best wishes, Pierre Riteau (priteau)

1 0

[ci][all]tox.tox_env.python.api.NoInterpreter - gate is blocked
by Balazs Gibizer 09 Jan '23

09 Jan '23

Hi, It seems that all the tox based jobs are blocked right now on master with the following error: tox.tox_env.python.api.NoInterpreter: could not find python interpreter matching any of the specs It is due to a recent bugfix in tox that uncovered another bug[1]. There is a fix proposed in tox [2]. [1]<https://github.com/tox-dev/tox/issues/2811> [2]<https://github.com/tox-dev/tox/pull/2828>

3 2

[openstack-ansible] git clone fatal: the remote end hung up unexpectedly
by Satish Patel 09 Jan '23

09 Jan '23

Folks, Trying to deploy an openstack-ansible Zed release but noticed strange behavior with git clone. failed: [localhost] (item={'name': 'galera_server', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-galera_server', 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-12-12'}) => {"ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": ["/usr/bin/git", "fetch", "--depth", "20", "--force", "origin", "+refs/heads/master:refs/remotes/origin/master"], "item": {"name": "galera_server", "scm": "git", "shallow_since": "2022-12-12", "src": "https://opendev.org/openstack/openstack-ansible-galera_server", "trackbranch": "master", "version": "master"}, "msg": "Failed to download remote objects and refs: fatal: error in object: unshallow e04aeacc58c196c4fb3d49116cb93fa74f7fba31\nfatal: the remote end hung up unexpectedly\n"} Full logs: https://paste.opendev.org/show/bUjuekKPzknE5IC8zbPa/

2 2

Re: add a new service to a pre-deployed openstack private cloud
by Oliver Weinmann 08 Jan '23

08 Jan '23

You don’t need to make any changes to your inventory files. Just keep using your initial inventory and you will be fine. > On 8. Jan 2023, at 09:19, A Monster <amonster369(a)gmail.com> wrote: > > Thank you for your quick response, > do I need to change the hosts in my inventory files and keep only the nodes on which these new services will be deployed on, or is it done automatically through the roles defined ? > > On Sun, 8 Jan 2023 at 09:15, Oliver Weinmann <oliver.weinmann(a)me.com <mailto:oliver.weinmann@me.com>> wrote: >> Hi, >> >> Sure. It is doable. Just make your changes to globals.yml, add the required config files and run e.g. for MAGNUM: >> >> kolla-ansible -i <inventory> deploy --tags common,horizon,magnum >> Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation >> docs.openstack.org >> >> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…>Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> docs.openstack.org <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> >> In that case deploy will not re-deploy your cluster, but pull in the needed containers for magnum and configure it. >> >>> On 8. Jan 2023, at 08:48, A Monster <amonster369(a)gmail.com <mailto:amonster369@gmail.com>> wrote: >>> >>> I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, >>> is this doable ? as I couldn't find anything in the kolla-ansible docs. >>

1 0

add a new service to a pre-deployed openstack private cloud
by A Monster 08 Jan '23

08 Jan '23

I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, is this doable ? as I couldn't find anything in the kolla-ansible docs.

2 1

Accessing databases of one OpenStack component from another
by vincent lee 08 Jan '23

08 Jan '23

Hi all, I have a working OpenStack in the yoga version and am trying to customize the zun component. In terms of deployment, I am using Kolla-ansible to deploy the OpenStack. I am trying to access blazar databases from the zun container. However, I have no clue of how the actual flow goes. I hope to receive some directions or suggestions to get me started. Best, Vincent

1 0

[openstack][cinder] Assign each storage backend to each AZ
by Nguyễn Hữu Khôi 08 Jan '23

08 Jan '23

Hello guys. I took time to search for this question but I can't find the answer. I have an Openstack private cloud and I use an AZ to a department. For example, AZ-IT for IT department AZ-Sale for Sale department... I will prepare 2 storage backends for each AZ. My goal is that when users launch an instance by choosing AZ then It will use only the backend for this AZ. Would Openstack support my goal? Thanks for reading my email. Nguyen Huu Khoi

4 9

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

07 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 07 Jan '23

07 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