June 2022 - openstack-discuss - lists.openstack.org

[tc] August 2022 OpenInfra Board Sync
by Jeremy Stanley 12 Aug '22

12 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-08-board-openstack-sync I've also created a Framadate poll has in order to identify a few preferred dates and times. Responses must be submitted by Friday, 2022-07-15, in order to provide the board members with time to pick from the available options. The poll can be found here: https://framadate.org/atdFRM8YeUtauSgC Feel free to reply here on the mailing list, or you can reach out to me directly by E-mail or as fungi in the #openstack-tc IRC channel, with any questions you may have. -- Jeremy Stanley

1 3

Need help on rabbitmq
by AJ_ sunny 10 Aug '22

10 Aug '22

Hi team I am using kolla-ansible based openstack infra and getting below error in logs seems frequent rabbitmq disconnections <0.5023.16> closing AMQP connection <0.5023.16> (10.80.0.13:40356 -> 10.80.0.13:5672 - mod_wsgi:19:d3196668-57e5-46dc-8b69-78d73b5873a0): missed heartbeats from client, timeout: 60s AMQP server on 10.80.0.13:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer Is this bug or any resolution for fixing this issue? Thanks Arihant Jain

4 4

[nova] Review guide for PCI tracking for Placement patches
by Balazs Gibizer 10 Aug '22

10 Aug '22

Hi Nova, The first batch of patches are up for review for the PCI tracking for Placement feature. These mostly covers two aspects of the spec[1]: 1) renaming [pci]passthrough_whitelist to [pci]device_spec 2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement This covers the first 4 sub chapters of Proposed Change chapter of the spec[1] up until "PCI alias configuration". I noted intentional deviations from the spec in the spec review [2] and I will push a follow up to the spec at some point fixing those. I tried to do it in small steps hence the long list of commits[3]: #2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement 5827d56310 Stop if tracking is disable after it was enabled before a4b5788858 Support [pci]device_spec reconfiguration 10642c787a Reject devname based device_spec config b0ad05fb69 Ignore PCI devs with physical_network tag f5a34ee441 Reject mixed VF rc and trait config c60b26014f Reject PCI dependent device config 5cf7325221 Extend device_spec with resource_class and traits eff0df6a98 Basics for PCI Placement reporting #1) renaming [pci]passthrough_whitelist to [pci]device_spec adfe34080a Rename whitelist in tests ea955a0c15 Rename exception.PciConfigInvalidWhitelist to PciConfigInvalidSpec 55770e4c14 Rename [pci]passthrough_whitelist to device_spec There is a side track branching out from "adfe34080a Rename whitelist in tests" to clean up the device spec handling[4]: 514500b5a4 Move __str__ to the PciAddressSpec base class 3a6198c8fb Fix type annotation of pci.Whitelist class f70adbb613 Remove unused PF checking from get_function_by_ifname b7eef53b1d Clean up mapping input to address spec types 93bbd67101 Poison /sys access via various calls in test 467ef91a86 Remove dead code from PhysicalPciAddress 233212d30f Fix PciAddressSpec descendants to call super.__init__ ad5bd46f46 Unparent PciDeviceSpec from PciAddressSpec cef0d2de4c Extra tests for remote managed dev spec 2fa2825afb Add more test coverage for devname base dev spec adfe34080a Rename whitelist in tests This is not a mandatory part of the feature but I think they improve the code in hand and even fixing some small bugs. I will continue with adding allocation healing for existing PCI allocations. Any feedback is highly appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-dev… [2] https://review.opendev.org/c/openstack/nova-specs/+/791047 [3] https://review.opendev.org/q/topic:bp/pci-device-tracking-in-placement [4] https://review.opendev.org/q/topic:bp/pci-device-spec-cleanup

1 2

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 05 Aug '22

05 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[all][stable] Propose to EOL Pike series
by Előd Illés 29 Jul '22

29 Jul '22

Hi, It seems that time has come to (mass)transition Pike to End of Life due to lack of maintainers (and backports + reviews; see the list of recent changes [1]). Some core projects have made this step already. Others are still open but not really maintained, which can be seen by the number of daily periodic stable job failures on pike branch, which is around 40 for several months now. (By the way, periodic stable job failures number is constantly high [2], due to some projects which seem to be abandoned completely (murano, *-powervm), but that is another story). Please let me know what do you think, or indicate if any of the projects wants to keep its pike branch open / in Extended Maintenance. [1] https://review.opendev.org/q/branch:stable/pike [2] http://lists.openstack.org/pipermail/openstack-stable-maint/2022-May/thread… Thanks, Előd

1 1

[vdi][daas][ops] What are your solutions to VDI/DaaS on OpenStack?
by Radosław Piliszek 20 Jul '22

20 Jul '22

Hello Fellow OpenStackers, I am wondering if and how OpenStackers are approaching the subject of VDI (Virtual Desktop Infrastructure), also nowadays commonly called DaaS (Desktop as a Service) offering. To be more specific, I am looking forward to a solution covering both Linux and Windows desktops, pre-OS screen access optional, well-integrated (i.e., having automation) with OpenStack Nova, preferably also with Cinder and Glance, optionally with Keystone (apart from self-auth of course!) and Heat, 3D acceleration optional (most of the desktops here don't need it), nice to have read-only sharing of screen. A search brought me to vdi-broker [1] [2] with Guacamole. [3] But the vdi-broker seems dead with no documentation whatsoever. I know Guacamole but normally it offers only static definition of connections to existing machines (VNC or RDP). Looking forward to hearing (reading :D ) your experience with VDI/DaaS on an OpenStack cloud offering. I am also open to collaboration should any of you share the same interest. We can have a relevant SIG created if that is the case. PS: Sadly, I am not able to attend the Berlin summit due to other commitments, so can't ask in person. ;-( [1] https://github.com/cloudbase/vdi-broker [2] https://www.openstack.org/videos/boston-2017/virtual-desktop-infrastructure… [3] https://guacamole.apache.org/ Kind regards, -yoctozepto

7 14

Upgrading to a more recent version of jsonschema
by Thomas Goirand 19 Jul '22

19 Jul '22

Hi, A few DDs are pushing me to upgrade jsonschema in Debian Unstable. However, OpenStack global requirements are still stuck at 3.2.0. Is there any reason for it, or should we attempt to upgrade to 4.6.0? I'd really appreciate if someone (else than me) was driving this... Cheers, Thomas Goirand (zigo)

6 18

Propose to add Tobias Urdin as Tooz core reviewer
by Herve Beraud 16 Jul '22

16 Jul '22

Hello everybody, It is my pleasure to propose Tobias Urdin (tobias-urdin) as a new member of the Tooz project core team. During the last months Tobias has been a significant contributor to the Tooz project. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

2 2

Propose to add Takashi Kajinami as Oslo core reviewer
by Herve Beraud 16 Jul '22

16 Jul '22

Hello everybody, It is my pleasure to propose Takashi Kajinami (tkajinam) as a new member of the oslo core team. During the last months Takashi has been a significant contributor to the oslo projects. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

4 4

[adjutant][tc][all] Call for volunteers to be a PTL and maintainers
by Slawek Kaplonski 15 Jul '22

15 Jul '22

Hi, After last PTL elections [1] Adjutant project don't have any PTL. It also didn't had PTL in the Yoga cycle already. So this is call for maintainters for Adjutant. If You are using it or interested in it, and if You are willing to help maintaining this project, please contact TC members through this mailing list or directly on the #openstack-tc channel @OFTC. We can talk possibilities to make someone a PTL of the project or going with this project to the Distributed Project Leadership [2] model. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [2] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… -- Slawek Kaplonski Principal Software Engineer Red Hat

4 8