February 2023 - openstack-discuss

[cinder] festival of feature reviews 17th February 2023
by Rajat Dhasmana 16 Feb '23

16 Feb '23

Hello Argonauts, We will be having our monthly festival of reviews tomorrow i.e. 17th February (Friday) from 1400-1600 UTC. This time we are planning to review features instead of XS patches since we have feature freeze this week. Following are some additional details: Date: 17th February, 2023 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! Thanks Rajat Dhasmana

1 0

[horizon][kolla] xstatic libraries and setuptools 67.3.1
by Michał Nasiadka 16 Feb '23

16 Feb '23

Hello, Recently setuptools 67.3.1 has been released, and it broke Kolla Horizon container builds. It seems that xstatic libraries rely on setuptools importing pkg_resources during build, which does not work in latest setuptools [1]. I raised a horizon bug #2007574 (https://bugs.launchpad.net/horizon/+bug/2007574) Raising awareness on the ML, because maybe that affects more projects than only Horizon. We’ve pinned to 67.2.0 in Kolla for now (in master and stable/zed, because earlier branches have a pin from u-c) [1]: https://github.com/pypa/setuptools/issues/3824 Michal Nasiadka

1 0

overcloud node import shows node already registered for a new baremetal box | ironic | wallaby
by Swogat Pradhan 16 Feb '23

16 Feb '23

Hi, I have 2 separate baremetal boxes, 1 is dell and the other is of lenovo make. I have created 2 separate instanenv.json files for both of them, and tried importing. the dell box was imported earlier and is now part of the cloud and now when i am trying to import the lenovo box it gives me the <uuid of dell> is alredy registered. I am not sure why this is coming when they both have separate ip addresses and even mac. json files: (undercloud) [stack@hkg2director ~]$ cat dcn01/hci3.json { "nodes": [ { "name": "HCI3", "pm_type": "ipmi", "ports": [ { "address": "90:B1:1C:4F:CA:3B", "physical_network": "ctlplane" } ], "cpu": "24", "memory": "114688", "disk": "2602", "arch": "x86_64", "pm_user": "root", "pm_password": "password", "pm_addr": "172.25.180.57", "_comment": "HCI 3" } ] } (undercloud) [stack@hkg2director ~]$ cat dcn02/ceph3.json { "nodes": [ { "name": "ceph3", "pm_type": "ipmi", "ports": [ { "address": "38:68:DD:8D:9E:4A", "physical_network": "ctlplane" } ], "cpu": "48", "memory": "65536", "disk": "558", "arch": "x86_64", "pm_user": "root", "pm_password": "password", "pm_addr": "10.11.11.12", "_comment": "ceph 3" } ] } With regards, Swogat Pradhan

1 0

[Magnum]enable cluster user trust
by Nguyễn Hữu Khôi 16 Feb '23

16 Feb '23

Hello guys. I am going to use Magnum for production but I see that https://nvd.nist.gov/vuln/detail/CVE-2016-7404 if I want to use cinder for k8s cluster. Is there any way to fix or minimize this problem? Thanks. Nguyen Huu Khoi

2 3

ceph power outage cause filesystem error on vms
by Satish Patel 16 Feb '23

16 Feb '23

Folks, I am running a small 3 node compute/controller with 3 node ceph storage in my lab. Yesterday, because of a power outage all my nodes went down. After reboot of all nodes ceph seems to show good health and no error (in ceph -s). When I started using the existing VM I noticed the following errors. Seems like data loss. This is a lab machine and has zero activity on vms but still loses data and the file system corrupt. Is this normal ? I am not using eraser coding, does that help in this matter? blk_update_request: I/O error, dev sda, sector 233000 op 0x1: (WRITE) flags 0x800 phys_seg 8 prio class 0 find attached screenshot.

1 0

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 16 Feb '23

16 Feb '23

Developers, The TC Election Campaigning Period has now started [1]. Although there are no polls that need to be held [2], during the next couple days, you are all encouraged to ask the candidates questions about their platforms [3], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. TC Candidates, Each of you has posted a platform [3], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. Ian Y. Choi (ianychoi) On behalf of all the Election Officials [1] https://governance.openstack.org/election/ [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03224… [3] https://opendev.org/openstack/election/src/branch/master/candidates/bobcat/…

1 0

OpenInfra Live - Feb. 16 at 9 a.m. CT / 15:00 UTC
by Kristin Barrientos 15 Feb '23

15 Feb '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community. Episode: VGPU Management by OpenStack Nova and Cyborg Members of the OpenStack community will introduce how Cyborg, an OpenStack project, aims to provide a general-purpose management framework for acceleration resources such as GPU, FPGA, NVMe SSDs, and SmartNIC. Date and time: February 16, 2023, at 9 a.m. CT (15:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=WUdkS9558p8 LinkedIn: https://www.linkedin.com/events/7026620675729608704/ Facebook: https://www.facebook.com/events/677204717420396 WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Alex Song, Brin Zhang, Dmitriy Rabotyagov, and Jimmy McArthur Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

The OpenInfra Summit Schedule is Live!
by Helena Spease 15 Feb '23

15 Feb '23

Hello everyone, I am really excited to let you know the Schedule [1] for the OpenInfra Summit 2023 is available! The schedule features keynotes and sessions from users like Bloomberg, LINE, Alibaba Cloud, Samsung and Volvo. The event will be held June 13-15, 2023, at the Vancouver Convention Centre overlooking Vancouver Harbor. Other notable speakers include Ant Group, the Australian Research Data Commons (ARDC), China Mobile, SAP, and Viettel, the largest public and private cloud infrastructure provider in Vietnam. Check out these OpenStack sessions you can expect at the OpenInfra Summit! LINE's 6 years journey to 4 million cores Deploying and managing baremetal Kubernetes with Ironic OpenStack as a Sandwich - Running Kubernetes below and above the IaaS layer. A beginner's journey of operating production-level Private Cloud using OpenStack and managed Kubernetes. Setting Up an OpenStack Development Environment The OpenInfra Summit [2] will be a limited-capacity, sellout event. Early bird sales for the OpenInfra Summit end February 15, 2023 at 11:59 PM PT. Register now [3] to save on your ticket and join us in Vancouver, June 13-15, 2023! The price increase will also apply to contributor discount codes, so if you received a contributor discount code last week, be sure to use it before February 15! Looking for other resources for the OpenInfra Summit? Sponsorship, Travel Support, visa requests, info on the PTG at the OpenInfra Summit, and Forum session details can be found at openinfra.dev/summit <http://openinfra.dev/summit>! Cheers, Helena [1] http://openinfra.dev/summit-schedule <http://openinfra.dev/summit-schedule> [2] http://openinfra.dev/summit <http://openinfra.dev/summit> [3] https://openinfra.dev/summit/registration <https://openinfra.dev/summit/registration> Cheers, Helena Cheers, Helena helena(a)openinfra.dev Marketing & Community Associate The OpenInfra Foundation

1 1

[ironic][OpenStackSDK][horizon][QA] cycle-with-intermediary deliverables without any release
by Elõd Illés 15 Feb '23

15 Feb '23

Hi, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the 2023.1 Antelope cycle: [ironic*] bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch [OpenStackSDK] python-openstackclient [horizon] horizon [Quality Assurance] patrole tempest Those should be released ASAP, and in all cases before March 2nd, so that we have a release to include in the final 2023.1 Antelope release. Előd Illés irc: elodilles

1 0

hw:mem_page_size Works on Flavors, hw_mem_page_size Doesn't Works on Image
by Lazuardi Nasution 15 Feb '23

15 Feb '23

Hi, There is a weird situation if it is not a bug. Hugepage instance launching is working if I put hw:mem_page_size on the used flavor. But, when I try the same launching configuration and change hw:mem_page_size on used flavor to hw_mem_page_size on used image, it cannot work as expected. It seems that this issue is like on https://bugzilla.redhat.com/show_bug.cgi?id=1791132, but it still happens on Zed. Is this an old bug? Should I submit a bug report for this? Best regards.

3 6

[election][cloudkitty] PTL candidacy for Bobcat
by Rafael Weingärtner 15 Feb '23

15 Feb '23

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the Bobcat release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/873902 -- Rafael Weingärtner

1 0

[cinder] Bug Report from 02-15-2023
by Sofia Enriquez 15 Feb '23

15 Feb '23

This is a bug report from 02-08-2023 to 02-15-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/os-brick/+bug/2006960 "Failure to mount volumes with LUN ID > 255." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2007275 "Error created new rsc_name in linstor driver." Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/2007139 "NFS Encryption Clone operation is broken." Fix proposed to master. - https://bugs.launchpad.net/cinder-tempest-plugin/+bug/2006594 " Inaccurate docstring test_boot_cloned_encrypted_volume." Unassigned. Wrong - https://bugs.launchpad.net/keystone/+bug/2006631 "Service token does not work if user auth is token based." 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

[election][tc] Candidacy for the TC
by James Page 15 Feb '23

15 Feb '23

Hi All, I'd like to announce my candidacy for the Technical Committee. For those of you who do not know me, I've been involved with OpenStack from the very early days of the project. I've attended many OpenStack summits and Project Teams Gatherings over the years and have been privileged to help the project grow from its small beginnings to the established cloud platform that it has now become. I was the main driver behind migration of the OpenStack Charms to its current home as an official OpenStack project which I then led for many cycles as PTL and I remain an active core developer on this project. I also work as part of the team responsible for the packaging and distribution of OpenStack as part of Ubuntu. I've spent time in the past contributing to oslo.messaging (ZeroMQ prototyping) and contributing minor fixes across other OpenStack projects through my work in Ubuntu. More recently I’ve been involved in the design of enabling support for the current and next generation of hardware offload enabled network cards in OVN and OpenStack and I'm currently working on there-design of the OpenStack Charms deployment approach. I have not served on the TC before but I believe I can bring a valuable technical voice from an OpenStack distribution and deployment tooling perspective. For the majority of operators this will be their primary route for adoption of OpenStack as a cloud platform. As a member of the TC I would look for opportunities to enable better collaboration between deployment projects and core projects to ensure that OpenStack becomes easier to consume. Thank you for taking the time to consider my candidacy for this role. Regards James Page (irc:jamespage) Principal Software Engineer Canonical

1 0

[all][elections][ptl][tc] Combined PTL/TC 2023.2 cycle Election Nominations Last Days
by Tony Breeds 15 Feb '23

15 Feb '23

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 15, 2023 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2023-02-01 23:45:00 UTC Nominations end @ 2023-02-15 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 21:19:30 Nominations progress : 93.65% --------------------------------------------------- Projects : 48 Projects with candidates : 33 ( 68.75%) Projects with election : 0 ( 0.00%) --------------------------------------------------- TC Seats : 5 TC Candidates : 4 --------------------------------------------------- Need election : 0 () Need appointment : 15 (Adjutant Barbican Cloudkitty Keystone Monasca OpenStackSDK OpenStack_Charms Rally Sahara Senlin Storlets Swift Tripleo Vitrage Winstackers) =================================================== Stats gathered @ 2023-02-15 02:25:30 UTC This means that with approximately 2 days left, 15 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… Yours Tony.

1 0

[election][ptl][Barbican] Candidiacy for 2023.2
by Grzegorz Grasza 15 Feb '23

15 Feb '23

Hi all, I would like to announce my candidacy to be the Barbican PTL for the next Bobcat cycle. I've been the Barbican PTL since the Antelope cycle and I would like to continue to contribute in this role. In the upcoming Bobcat cycle, I'd like to focus on Barbican maintanance and stability. Thank you for considering my candidacy, Grzegorz Grasza (xek)

2 1

[election][ptl][puppet] Candidacy for 2023.2 Bobcat
by Takashi Kajinami 15 Feb '23

15 Feb '23

Hello, I'd like to announce my candidacy for the PTL role in Puppet OpenStack, to continue my PTL role for the Bobcat cycle. For the recent few cycles we have successfully updated our modules to keep them up-to-date with the OpenStack projects and underlying operating systems (such as CentOS Stream 9 or Ubuntu 22.04). I expect the next cycle would be a stable one compared to the past cycles because of no major changes we are aware of now, and I'd like to focus more on items to make our future maintenance easier * Adapt to updates in each component * Review status of our modules and remove unmaintained ones or implementations Thank you for your consideration. Thank you, Takashi Kajinami (irc: tkajinam)

1 0

[election][ptl][heat] Candidacy for 2023.2 Bobcat
by Takashi Kajinami 15 Feb '23

15 Feb '23

Hello, I'd like to announce my candidacy for Heat PTL during the Bobcat cycle. I've been contributing to the project for several cycles and one of the core reviewers in the project. My contribution has been focusing on keeping our CI green so that we can merge new changes such as bug fixes or new features. For this cycle I'd like to propose a few items as focus items. * Keep CI green This is our top priority. Keeping CI healthy is very important so that we can operate the project properly. * Adapt to changes in the other projects Because heat relies on the other projects such as Nova to create resources, it's important to adapt to the changes in underlying components (eg. API microversions). * Migration to OpenStack SDK This is currently important work so that some other projects such as Neutron can complete migration from own client libraries. We already have some patches proposed by Neutron cores (Thank you !) and reviewing and merging these patches would be prioritized for the next cycle. Thank you for your consideration ! Thank you, Takashi Kajinami (irc: tkajinam)

1 0

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

15 Feb '23

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

1 1

[election][tc] TC Candidacy for Bobcat
by Slawek Kaplonski 15 Feb '23

15 Feb '23

Hi Stackers, I want to propose my candidacy to the Technical Committee.I have been working on OpenStack for many years. I am a member of the Neutron drivers team and a core reviewer in the Neutron project. I was also the Neutron PTL in the past.One year ago, I became a member of the Technical Committee and I want to continue working for the OpenStack community in the upcoming year. During this year in the TC, I have been working on improving the stability of our CI jobs and various aspects of the infra resources usage, like monitoring and optimizing the number of "rechecks", especially "bare" rechecks done without giving any reason. I have also been working on the definition of the "emerging" and inactive projects and on improving how we monitor activity in the OpenStack projects. Thank you for considering my candidacy for the Technical Committee. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

OpenInfra Summit Forum Selection Committee Call for Volunteers
by Kendall Nelson 14 Feb '23

14 Feb '23

Hello Everyone! The Forum at the OpenInfra Summit Vancouver is coming up! We would love 1 volunteer from OpenStack for the Forum Selection Committee. Ideally, the volunteer would: - already be serving in some capacity in a governance role for your project - not be planning to submit to the Forum CFP or be willing to abstain from voting on your proposals For information on the OpenInfra Summit in Vancouver: https://openinfra.dev/summit/vancouver-2023/ For more information on the Forum, please see: https://openinfra.dev/summit/vancouver-2023/forum/ Please reach out to me, knelson@open <http://goog_1840023357/>infra.dev, or reply on this thread if you're interested. Volunteers should respond on or before March 5th, 2023 @ 7:00 UTC. This role does not require you to travel to the OpenInfra Summit, but can get you a discounted ticket if you choose to volunteer and then attend (we would love to have you there!). Thanks! Kendall Nelson

2 2

Virtual PTG March 2023 Team Signup Deadline - LAST CALL!
by Kendall Nelson 14 Feb '23

14 Feb '23

Hello Everyone, This is your last call to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, March 27th to Friday, March 31st 2023! NOTE: Since we have had the feedback that the Europe+Africa/Americas timeslot is overbooked, we will be extending it beyond the ‘normal’ size of 4 hour blocks to 5 hour blocks. If you haven't already done so and your team is interested in participating, please complete the survey[1] by February 19th, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] PTG Registration: https://openinfra-ptg.eventbrite.com

2 2

[election][tc] TC Candidacy for Bobcat
by Nikolla, Kristi 14 Feb '23

14 Feb '23

Hi all, I am announcing my candidacy to continue working on the OpenStack Technical Committee for another year[1][2]. I'm a software engineer at the MOC Alliance[0], an initiative from major universities in the Boston area to create and operate public and open clouds. I've been involved with OpenStack for the past 8 years as a user, operator, developer, and community member. I have also served as the PTL of Keystone[3][4]. I am passionate about open source, governance, and keeping the community healthy and I believe I bring a different perspective to the Technical Committee thanks to working for academia. My focus in the previous term as well as in the coming one will continue to be in facilitating discussions, whether they are internal to a team, between project teams, or between OpenStack and other projects. In pursuit of that goal, I ran unsuccessfully for chair of the Technical Committee, which I plan to do so again this cycle If I am re-elected. I also assisted in running the Antelope cycle elections and I plan on continuing to assist with them. Please allow me once again the honor of representing you, and the opportunity to continue contributing to the community that I owe so much to and want to see grow and succeed. Thank you for your time and consideration, Kristi Nikolla (he/him) [0]. https://massopen.cloud [1]. https://opendev.org/openstack/election/raw/branch/master/candidates/victori… [2]. https://opendev.org/openstack/election/raw/branch/master/candidates/zed/TC/… [3]. https://opendev.org/openstack/election/raw/branch/master/candidates/victori… [4]. https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby…

1 0

[ironic] the confuse of user data and too long time of clean
by 韩光宇 14 Feb '23

14 Feb '23

Hello, I'm using ironic to deploy baremetal node. Now I have two puzzles. 1. The node has been in the "clean wait" stage for more than 3 hours I saw that node was used "erase_devices_metadata" clean step, and It is very different from the description in the document[1] " it has the advantage of a reasonably quick runtime (seconds to minutes)" Attachment “ramdisk_ironic-python-agent.log” is the log of ironic-python-agent in ramdisk. Does anyone know why this is? ```shell # openstack baremetal node show $NODE_UUID -f value -c driver_internal_info {'agent_erase_devices_iterations': 1, 'agent_erase_devices_zeroize': True, 'agent_continue_if_ata_erase_failed': False, 'agent_enable_ata_secure_erase': True, 'disk_erasure_concurrency': 1, 'agent_erase_skip_read_only': False, 'last_power_state_change': '2023-02-14T12:50:40.718177', 'clean_steps': [{'step': 'erase_devices_metadata', 'priority': 99, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'erase_devices', 'priority': 10, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}], 'agent_version': '9.2.1.dev4', 'agent_last_heartbeat': '2023-02-14T13:49:18.272802', 'hardware_manager_version': {'generic_hardware_manager': '1.1'}, 'agent_cached_clean_steps_refreshed': '2023-02-14 12:55:07.250187', 'agent_secret_token': '******', 'agent_url': 'https://192.168.3.62:9999', 'agent_verify_ca': '/var/lib/ironic/certificates/f982467d-57bc-497d-9905-6594e5d03ca9.crt', 'agent_cached_clean_steps': {'deploy': [{'step': 'erase_devices', 'priority': 10, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'erase_devices_metadata', 'priority': 99, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'erase_devices_express', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'erase_pstore', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'burnin_cpu', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'burnin_disk', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'burnin_memory', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}, {'step': 'burnin_network', 'priority': 0, 'interface': 'deploy', 'reboot_requested': False, 'abortable': True}], 'raid': [{'step': 'delete_configuration', 'priority': 0, 'interface': 'raid', 'reboot_requested': False, 'abortable': True}, {'step': 'create_configuration', 'priority': 0, 'interface': 'raid', 'reboot_requested': False, 'abortable': True}]}, 'clean_step_index': 1} ``` 2. Could I can directly use `openstack server create --user-data ./my-user-date.txt` for baremetal node? or baremetal node requires configdrive? Is there any special configuration required in the user image? such as ““datasource_list of cloud-init” Any kind of pointers are greatly appreciated, sincere thanks [1]: https://docs.openstack.org/ironic/latest/admin/cleaning.html#storage-cleani…

2 1

[election][ptl][qa] Candidacy for 2023.2 Bobcat
by Martin Kopec 14 Feb '23

14 Feb '23

Hi everyone, I would like to propose my candidacy and continue serving as Quality Assurance PTL in the Bobcat cycle. I have been serving as PTL of QA for the last 4 cycles during which we have done a ton of work. I would like to thank all the contributors, core reviewers, and anyone involved in any QA project, maintaining the projects would simply not be possible without you. Finding and guiding new contributors will remain one of my biggest priorities as that is very important in order to keep up in the long term. Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[ironic] Is there a ramdisk image of aarch64 architecture available for download
by 韩光宇 14 Feb '23

14 Feb '23

Hello, I saw that we can get ramdisk image from tarballs.openstack.org[1] in ironic doc[2]. I would like to ask whether all the above are of amd64 architecture. Where can I download the ramdisk image of aarch64 architecture？ When I built aarch64 image locally, It's always failed. ```shell # export ARCH=aarch64 # ironic-python-agent-builder fedora ... mount: /tmp/tmp.1yEQhatS1X/mnt: wrong fs type, bad option, bad superblock on /dev/mapper/loop0p5, missing codepage or helper program, or other error. # ironic-python-agent-builder centos ... 2023-02-12 14:15:02.361 | dib-run-parts Running /tmp/in_target.d/pre-install.d/01-00-centos-python3 2023-02-12 14:15:05.204 | CentOS Linux 8 - AppStream 17 B/s | 38 B 00:02 2023-02-12 14:15:05.209 | Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist # ironic-python-agent-builder ubuntu ... 2023-02-12 14:15:31.623 | Fetching Base Image 2023-02-12 14:15:31.657 | % Total % Received % Xferd Average Speed Time Time Time Current 2023-02-12 14:15:31.657 | Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 2023-02-12 14:15:32.388 | Server copy has not changed. Using locally cached https://cloud-images.ubuntu.com/focal/current/SHA256SUMS 2023-02-12 14:15:32.422 | % Total % Received % Xferd Average Speed Time Time Time Current 2023-02-12 14:15:32.422 | Dload Upload Total Spent Left Speed 100 286 100 286 0 0 418 0 --:--:-- --:--:-- --:--:-- 418 2023-02-12 14:15:33.110 | Server returned an unexpected response code. [404] ``` [1]: https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/ [2]: https://docs.openstack.org/ironic/latest/install/deploy-ramdisk.html

5 5

Issues with virsh XML changing disk type after Nova live migration
by Budden, Robert M. (GSFC-606.2)[InuTeq, LLC] 14 Feb '23

14 Feb '23

Hello Community, We’ve hit a rather pesky bug that I’m hoping someone else has seen before. We have an issue with Nova where a set of Cinder backed VMs are having their XML definitions modified after a live migration. Specifically, the destination host ends up having the disk type changed from ‘qcow2’ to ‘raw’. This ends up with the VM becoming unbootable upon the next hard reboot (or nova stop/start is issued). The required fix ATM is for us to destroy the VM and recreate from the persistent Cinder volume. Clearly this isn’t a maintainable solution as we rely on live migration for patching infrastructure. Any thoughts, ideas, would be most welcome. Gory details are below. Here’s the key details we have: * Nova boot an instance from the existing volume works as expected. * After live migration the ‘type’ field in the virsh XML is changed from ‘qcow2’ -> ‘raw’ and we get a ‘No bootable device’ from the VM (rightly so) * After reverting this field automatically (scripted solution), a ‘nova stop’ followed by a ‘nova start’ yet again rewrites the XML with the bad type=’raw’. * It should be noted that before a live migration is performed ‘nova stop/start’ functions as expected, no XML changes are written to the virsh definition. * Injecting additional logs into the python on these two hosts I’ve narrowed it down to ‘bdm_info.connection_info’ on the destination end is choosing the ‘raw’ parameter somehow (I’ve only got so far through the code at this time). The etree.XMLParser of the source hypervisors XML definition is properly parsing out ‘qcow2’ type. Some background info: * We’re currently running the Wallaby release with the latest patches. * Hybrid OS (Stream8 /Rocky 8) on underlying hardware with the majority of the Control Plane Stream aside from our Neutron Network Nodes. Computes are roughly split 50/50 Stream/Rocky. * The Cinder volumes that experience this were copied in from a previous OpenStack cloud (Pike/Queens) on the backend. I.e. NetApp snapmirror, new bootable Cinder volume created on the backend, and an internal NetApp operation for a zero copy operation over the backing Cinder file. * Other Cinder volumes that don’t exhibit this to mostly be in ‘raw’ format already (we haven’t vetted every single bootable Cinder volume yet). * We’ve noticed these Cinder volumes lack some metadata fields that other Cinder volumes create by Glance have (more details below). Ideas we’ve tried: * Adjusting settings on both computes for ‘use_cow_images’ and ‘force_raw_images’ seem to have zero effect. * Manually setting the Cinder metadata parameters to no avail (i.e. openstack volume set --image-property disk_format=qcow2). Thanks! -Robert

3 5

[TripleO] Integrating external Graylog with openstack TripleO wallaby
by Kushagra Gupta 14 Feb '23

14 Feb '23

Hi Team, We have a tripleO environment. Our tripleO environment consists of 2 compute nodes, 3 controller nodes, and 1 undercloud node. TripleO Release: Wallaby We want to integrate the Graylog server with the tripleO openstack. Does tripleO support this integration? If so, could anyone please share some sources from where we can do the same? Thanks and Regards, Kushagra Gupta DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

1 0

[election][ptl][Kuryr] Candidacy for 2023.2 Bobcat
by Roman Dobosz 14 Feb '23

14 Feb '23

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next Bobcat cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. I'm also the PTL since Antelope cycle. In the upcoming Bobcat cycle, I'd like to focus on Kuryr maintanance, stability and compatibility with upcoming Kubernetes release. Thanks, Roman Dobosz (gryf)

1 0

Replaying pcap captured network traffic into OpenStack Victoria
by Felipe Mogollon 14 Feb '23

14 Feb '23

Hello, I have an OpenStack Victoria with a controller+network+compute node plus a compute node. Both nodes are working fine and I have no problem with network traffic. If I try to replay some previously captured traffic from a tcpdump pcap file no traffic at all comes through qrouters. I have tried replaying network traffic from external machine to OpenStack and from OpenStack to external and internal machines and I have the same negative results in all cases. When I replay traffic from an external computer to an instance insde OpenStack I noticed that incoming packets go to the external interface of the qrouter but don't go passthrough to the internal interface from the qrouter. I have tried replaying traffic with scapy and tcpreplay and I get the same results in both cases. Any ideas? Thanks -- <https://www.vicomtech.org> Juan Felipe Mogollón Rodríguez Researcher | Investigador fmogollon(a)vicomtech.org +[34] 943 30 92 30 Digital Media <https://www.linkedin.com/company/vicomtech> <https://www.youtube.com/user/VICOMTech> <https://twitter.com/@Vicomtech> member of: <https://graphicsvision.ai/> La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado. The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

1 0

[election][ptl][Octavia] Candidacy for 2023.2 Bobcat
by Gregory Thiemonge 14 Feb '23

14 Feb '23

Hi, I would like to announce my candidacy for Octavia PTL for the Bobcat release. I have been PTL since the Xena cycle and I want to continue to contribute to this role. For the Bobcat release I would like to focus on important internal tasks, such as completing the SQLAlchemy 2 migration and moving from python-neutronclient to openstacksdk. I would like also to improve the amphorav2 driver by analyzing and optimizing the SQL queries (we know we're doing many DB calls). Thanks for your consideration, Gregory Thiemonge (gthiemonge)

1 0

Live migration to host with advanced cpu results in instance inheriting incorrect cpu_model, even when overridden in nova.conf
by Andy Speagle 14 Feb '23

14 Feb '23

Hey Folks, We have a number of nodes in our openstack cluster who have the same family CPU (IvyBridge-IBRS) ... and one advanced CPU (Broadwell-IBRS). We have set the cpu_mode to custom and overridden the cpu_model to IvyBridge-IBRS so that all of the hosts would be compatible. This seems to work for instances started on the advanced host... we can live migrate off of the host. But... when we live migrate instances TO the advanced host... they seem to inherit the wrong CPU type. Example: If I live migrated onto the advanced host and then try to live migrate off of it... nova-compute logs on the older host throw: Error: Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. And the output clearly shows that it thinks it was launched on the Broadwell CPU: Instance launched has CPU info: {"arch": "x86_64", "model": "Broadwell- IBRS", "vendor": "Intel" ... With that instance on the advanced host, if I restart it... magically it comes up with the correct cpu_model and can be live migrated off... We're running ussuri ... does anyone know if this is known behavior? Could I have a misconfiguration somewhere? Thanks. -- Andy Speagle

1 0

[election][tc] TC candidacy for 2023
by Brian Rosmaita 14 Feb '23

14 Feb '23

Hello OpenStack Community, I am declaring my candidacy for a second term on the Technical Committee. I've been working on OpenStack since Folsom and currently serve as a core reviewer for the Glance and Cinder projects. In the past, I've been PTL of Glance and Cinder, and I am just now completing my first term on the Technical Committee. As I said last time, I don't have an agenda other than to represent active technical contributors to OpenStack and to participate in the TC in a manner consistent with its charter. Additionally, during my first term, I have been working with the OpenStack i18n SIG to refresh the translations infrastructure, and I would like to continue that work into the Bobcat development cycle. Thank you for considering my candidacy for the OpenStack Technical Committee. - Brian Rosmaita (rosmaita)

1 0

[publiccloud-sig] Reminder - next meeting Feb 15th - 0800 UTC
by Felix Kronlage-Dammers 14 Feb '23

14 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on February 15th (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[election][ptl][openstack-ansible] Candidacy for 2023.2 Bobcat
by Dmitriy Rabotyagov 13 Feb '23

13 Feb '23

Hello everyone! I would like to announce my candidacy for the role of PTL of OpenStack-Ansible during the Bobcat/2023.2 cycle. I have been serving as the OpenStack PTL for quite a while now so with announcing my candidacy I also want to encourage other active contributors to participate in elections for keeping a healthy community and plurality of opinions in the project leadership. For the next cycle I would like to focus project development on: * Implementing SLURP upgrades both in terms of CI testing and upgrade script adjustment * Continue integration and improvement of PKI role with services * Keep up with latest supported versions of infrastructure software, like MariaDB, RabbitMQ and Ansible * Have progress on better functional testing of different scenarios for roles * Improve timing for our releases by decreasing the gap between OpenStack coordinated release and OSA trailing one. Thank you for your consideration!

1 0

[election][ptl][manila] Candidacy for 2023.2 Bobcat
by Carlos Silva 13 Feb '23

13 Feb '23

Hello everyone! I would like to announce my candidacy for the role of PTL of Manila during the Bobcat/2023.2 cycle. I have been serving as the Manila PTL for 2 cycles in a row and I would like to continue serving as PTL to this amazing community. During the last two cycles we have been focusing on closing the feature gap between the core of Manila and OpenStack Client, SDK and Manila UI, as well as engaging and encouraging contributor participation through mentoring and promoting collaborative activities, focusing on tech debt, and enhancing the tests coverage for various areas of Manila. We have also been putting efforts on making sure that relevant new features, fixes and enhancements are landing every single release. For the next cycle I would like to continue the great work we have been doing so far, but also have some focus on: * Continue encouraging active maintainers to actively do reviews so we can enhance our review bandwidth; mentor people to become core reviewers, as well as promote and participate in mentoring opportunities such as Outreachy, GHC and so on. * Continue to promote events like hackathons or bug squashes that will not only help us to achieve our goals such as enhancing our functional tests coverage and reduce the bug stats, but will also strengthen the community and get contributors to collaborate and create great learning opportunities. * Continue past cycles efforts to collaboratively cover the lack of documentation we have on third party CI setups for Manila, helping potential new vendors to quickly set up their CI systems. * Pursue the remaining changes keeping us from starting the deprecation of manilaclient in favor of the OpenStack client. Thank you for your consideration! Carlos da Silva IRC: carloss

1 0

[openstack-helm] switching to using service's user for requests
by Mohammed Naser 13 Feb '23

13 Feb '23

Hi team, I'm wondering if it makes sense for us to make a change in all of OpenStack Helm's code in order to make it use the service user for all requests. For example, right now, we are using the placement user in the `[placement]` section in Neutron, or the Neutron user in the `[neutron]` section in Nova. However, all of these users have the same exact role and permissions, so I believe it would help a lot in locking down services (let's say placement gets compromised, you can lock it's user only). I also think it will significantly simplify all of our code for endpoints for the different services, since we'll just be re-using the same credentials. Let me know what everyone thinks. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2

[election][ptl][designate] Candidacy for 2023.2 Bobcat
by Michael Johnson 13 Feb '23

13 Feb '23

Hello OpenStack community, I would like to announce my candidacy for PTL of Designate for the Bobcat cycle. I would like to continue to support the Designate team for the Bobcat release. For the Antelope release, we have continued our code stability work and focused development on a major new feature "Shared Zones". Looking forward to the Bobcat development cycle I expect to see a lot of work around updating for SQLAlchemy 2.x and introducing the "catalog zones" feature. Thank you for your support and your consideration for Bobcat, Michael Johnson (johnsom)

1 0

[cinder] Review Priorities R-5 (17th Feb, 2023)
by Rajat Dhasmana 13 Feb '23

13 Feb '23

Hello Argonauts, We've multiple deadlines this week (R-5 - 17th Feb, 2023) hence I would like to focus the team's review bandwidth towards the important reviews. 1) Cinderclient: 4 patches, 1 approved, 3 have +2s Important reviews: https://etherpad.opendev.org/p/cinderclient-antelope-release 2) python-brick-cinderclient-ext: 1 patch with +2 https://review.opendev.org/c/openstack/python-brick-cinderclient-ext/+/8735… 3) Feature Freeze: 12 features, 2 merged, 10 need reviews https://etherpad.opendev.org/p/cinder-antelope-features 4) Requirements Freeze: 4 patches but 2 potential ones https://review.opendev.org/q/(project:openstack/cinder+OR+project:openstack… Kindly focus on the above changes as they need to be merged this week for making into 2023.1 (Antelope) release. Thanks Rajat Dhasmana

1 0

[skyline] Is there a billing module available to integrate with Skyline?
by Roger Rivera 13 Feb '23

13 Feb '23

Hello, Skyline seems like an awesome contribution. We noticed there are price references on the video presentation of the Skyline dashboard. Does anybody know if there is an existing billing module that integrates with Skyline to add this functionality as seen in the bottom part of the screenshot? Any guidance to make this would be highly appreciated. Thank you -- *Roger Rivera*

3 2

[election][ptl][neutron] Candidacy for 2023.2 Bobcat
by Rodolfo Alonso Hernandez 13 Feb '23

13 Feb '23

Hello all: I would like to announce my candidacy for the role of PTL of Neutron for the Bobcat/2023.2 cycle. Let me introduce myself first. I started contributing to OpenStack in Liberty release (2015). I've contributed to several projects, mainly Neutron, neutron-lib, os-ken and os-vif, in addition to Nova and devstack. During the last two years I've been focused on the ML2/OVN integration, QoS and Placement related features and helping on the Neutron CI improvement and stabilization. For this new release, those are the main goals I would like to focus on: * Continue with the improvement of CI stability. This has been a very high time consuming task for the Neutron community, but the improvements can be seen in the number of rechecks and CI time used by Neutron. We must continue with this effort during the next release. * Keep working on the smart NIC / hardware offload testing. This is something I personally started during the last cycle but with little success, but we should continue with this effort. * Keep working on the approved (or active) specs with active developments: ** Metadata rate limit (LP#1989199) ** Expose backend hints in the port API, hint ovs-tx-steering (LP#1990842) ** ML2/OVN IPv6 Distributed routing (LP#1998609) ** Active-active L3 Gateway with Multihoming (LP#2002687) ** Configurable Security Group rules added by default to the new Security Groups (LP#1983053) Apart from those main goals, we should always keep an eye on: * The SQLAlchemy 2.0 migration and any possible issue detected. During the last two releases we found and solved several issues related to the migration to SQLAlchemy 2.0. We need to keep watching for new possible issues. * The Neutron's stadium ecosystem is alive and healthy: this is a permanent goal in any release. The Neutron ecosystem is wide and diverse and it is maintained with few resources. We should focus on those active projects and communities that support their respective repositories. * Still closing (or surpassing) the ML2/OVS - ML2/OVN feature gap. * The spec tracking and review, in order to continue adding new functionalities. Thank you in advance. Rodolfo Alonso Hernandez (ralonsoh, ralonsoh(a)redhat.com) Link: https://review.opendev.org/c/openstack/election/+/873508

1 0

[election][ptl][nova][placement] Candidacy for 2023.2 Bobcat
by Sylvain Bauza 13 Feb '23

13 Feb '23

Hey Nova and Placement folks, Despite me saying that Antelope would have been my last cycle as PTL, I have to fight the evidence : our project needs more contributors and we're struggled by our current dynamics. That's why I'm hereby proposing to act as PTL for this Bobcat release. When looking at the mirror, we tried a couple of things te lower the entry barrier in order to contribute to the Nova/Placement community : - we had a productive meet-and-greet session at the Berlin summit - we introduced a Review-Priority Gerrit label for identifying upstream interest - people volunteered for upstream bug triage on a weekly basis - we tried to minimize merge conflicts by ordering API changes Those different efforts worked pretty well for helping the Nova project to get more hands willing to solve problems, but it didn't helped that far the reviewing dynamics. Yes, we not only need contributors that contribute but we also need contributors that review what others contribute. During this Bobcat cycle, I'll propose a couple of incentives in that direction. This release is also special because it will be our first 'not-SLURP' [1] one. As a PTL, I'll take an attention to track all the developments so we can identify the necessary knobs in order to make this 'skipped' release a painless experience for our operators. Last but certainly not the least, the recent weeks showed us how fragile we are when our Zuul gate gets cold. I'll continue to propose help, support and visibility for our beloved firefighters that dig into those problems, including the stable branches which are crucial for many consumers of those branches. Anyway, nothing can happen magically, we need hands. Thanks, -Sylvain [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

1 0

[neutron] Bug Deputy Report February 6 - 12
by Elvira Garcia Ruiz 13 Feb '23

13 Feb '23

Hi! Here you have the Neutron bug report from February 6th to 12th: Critical --------- - https://bugs.launchpad.net/neutron/+bug/2004656 - "rpc_workers" config variable needs to be registered in stadium projects Fix proposed https://review.opendev.org/c/openstack/neutron/+/872644 Assigned to ralonsoh High ------ - https://bugs.launchpad.net/neutron/+bug/2006112 - [OVN] Error during execution of "add_vnic_type_and_pb_capabilities_to_lsp" Fix proposed: https://bugs.launchpad.net/neutron/+bug/2006112 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006603 - [FT] Test "OVSInterfaceEventTestCase.test_port_creation_and_deletion" randomly failing Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873118 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006612 - [FT] Test "TestOVNNeutronAgent.test_ovs_and_ovs_events" failing randomly Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873126 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006734 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873296 - https://bugs.launchpad.net/neutron/+bug/2006735 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873247 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006264 - [CI] tox-py311 job timing out some times Unassigned https://bugs.launchpad.net/neutron/+bug/2006953 - [stable/wallaby] test_established_tcp_session_after_re_attachinging_sg is unstable on ML2/OVS iptables_hybrid job Unassigned - https://bugs.launchpad.net/neutron/+bug/2006683 - fwaas scenario job fails randomly Unassigned Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2004581 - Neutron API query error, implicit cast does not exist in postgresql Fix proposed: https://review.opendev.org/c/openstack/neutron/+/872745 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006496 - [L3-HA] "max_l3_agents_per_router" not honored when the redundancy is reduced Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873107 Assigned to ralonsoh https://bugs.launchpad.net/neutron/+bug/2006949 - SLAAC and stateless DHCP are not working with stateless SG Assigned to Ihar Low ----- https://bugs.launchpad.net/neutron/+bug/2006122 - ExternalGatewayForFloatingIPNotFound returns misleading http status code Fix proposed: https://review.opendev.org/c/openstack/neutron-lib/+/872748 Assigned to Felix Huettner Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2006145 - BGP Speaker peer sessions down when rabbitmq offline I looked for the l3 bgp lieutenants for better triaging but I was not able to find them online. Kind regards, Elvira

1 0

[kolla]RabbitMQ HA policies define
by Satish Patel 13 Feb '23

13 Feb '23

Folks, I have deployed 3 node kolla controllers and notice rabbitMQ doesn't have any HA policy for queues. when i rebooted one of the nodes and found some messages got lost. Any reason kolla doesn't use HA policies by default? If i want to add policies then where should i specify them or any doc you can point me to define policies.

4 11

[trove] Larger than max_request_body_size
by Jorge Visentini 13 Feb '23

13 Feb '23

Hi all. I'm noob in Openstack, so I'm testing/studying the features. At the moment I am testing the Trove but I can't start a database instance... This error appears for me. 2023-02-10 18:07:19.888 1651 ERROR trove.taskmanager.models [-] Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 *Request is too large. Larger than max_request_body_size (114688). * (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 844, in _create_server_volume server = self._create_server( File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 999, in _create_server server = self.nova_client.servers.create( File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 1562, in create return self._boot(response_key, *boot_args, **boot_kwargs) File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 887, in _boot return self._create('/servers', body, response_key, File "/usr/lib/python3.9/site-packages/novaclient/base.py", line 363, in _create resp, body = self.api.client.post(url, body=body) File "/usr/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 401, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python3.9/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) : novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). 2023-02-10 18:07:19.913 1651 ERROR oslo_messaging.rpc.server [-] Exception during message handling: trove.common.exception.TroveError: Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 Request is too large. Larger than max_request_body_size (114688). Can you help me? I don't know where I change this parameter... Have a good weekend for us! -- Att, Jorge Visentini +55 55 98432-9868

2 1

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

11 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 8. 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-08-16.00.log.html * The next TC weekly meeting will be on Feb 15 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 14. 2. What we completed this week: ========================= * Defined 2023.2 cycle testing runtime[2] I have pushed the job template change which needs to wait until 2023.1 release[3] 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[4]. Open Reviews ----------------- * Six open reviews for ongoing activities[5]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the sync-up call with Board members on Feb 8[6]. We continued the discussion from the previous meeting on below two topics: 1. Renovate translation SIG i18 Brian gave the updates on this and weblate license is purchased. There is a discussion going on about hosting the service. Another thing pending on this is to find the maintainer to help in weblate hosting and translation work. Brian will discuss it with Ian and Seongsoo about it. 2. Less Diversity (of organization contributing to OpenStack) This was continued to know if there is any actual progress to solve this problem. We always discuss spreading the word about benefits to the community and hope more companies will come forward for help. We are still facing less diversity from organizations involved in upstream activities. Many projects are/will face a single company maintaining them and will end up on retirement if that company changes their plan. TripelO is a recent example of it. Proposal was to Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation ------------------------------------------------------------------------------------------------------------------------- As discussed in the last vPTG, there was some confusion about using the OpenStack release name or version and project version in release notes and documentation. Slawek proposed guidelines about it[7] which is up fore review. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[8] to define the 2023 calendar year which is nothing but continuing last year's opportunities. Please let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [9]. There is a discussion also going on in ML[10]. JayF is working on an email template which can be used to communicate to additional developers to transfer the ownership to 'openstackci' account and remove them from the maintainer's list. 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[11]. Project updates ------------------- * Add Cinder Huawei charm[12] * Add the woodpecker charm to Openstack charms[13] * Retire xstatic-font-awesome[14] * mistral adopting PTL model[15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 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/+/872232 [3] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873051 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/2023-02-board-openstack-sync [7] https://review.opendev.org/c/openstack/governance/+/872769 [8] https://review.opendev.org/c/openstack/governance/+/872233 [9] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [10] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [11] https://etherpad.opendev.org/p/project-health-check [12] https://review.opendev.org/c/openstack/governance/+/867588 [13] https://review.opendev.org/c/openstack/governance/+/869752 [14] https://review.opendev.org/c/openstack/governance/+/872837 [15] https://review.opendev.org/c/openstack/governance/+/873260 [16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Trove configuration - Larger than max_request_body_size
by Jorge Visentini 11 Feb '23

11 Feb '23

Hi all. I'm noob in Openstack, so I'm testing/studying the features. At the moment I am testing the Trove but I can't start a database instance... This error appears for me. 2023-02-10 18:07:19.888 1651 ERROR trove.taskmanager.models [-] Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 *Request is too large. Larger than max_request_body_size (114688). * (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 844, in _create_server_volume server = self._create_server( File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 999, in _create_server server = self.nova_client.servers.create( File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 1562, in create return self._boot(response_key, *boot_args, **boot_kwargs) File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 887, in _boot return self._create('/servers', body, response_key, File "/usr/lib/python3.9/site-packages/novaclient/base.py", line 363, in _create resp, body = self.api.client.post(url, body=body) File "/usr/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 401, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python3.9/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) : novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). 2023-02-10 18:07:19.913 1651 ERROR oslo_messaging.rpc.server [-] Exception during message handling: trove.common.exception.TroveError: Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 Request is too large. Larger than max_request_body_size (114688). Can you help me? I don't know where I change this parameter... Have a good weekend for us! -- Att, Jorge Visentini +55 55 98432-9868

1 0

[neutron][releases] Issue with neutron-tempest-plugin in T, U and V
by Rodolfo Alonso Hernandez 11 Feb '23

11 Feb '23

Hello: I've started to see an error in the neutron-tempest-plugin job executions, in T, U and V. The hash used for these versions is the same [1]. This has been marked as the last version of this project in these releases. However I found [2] today. The library "guestmount" seems to be not present in Ubuntu 20.04 and we need to install it. That was done in [3] and is present in newer releases. My question here is: how do I push a patch for these versions (tag=1.6.0) and release a 2nd "last" version (if possible)? Thanks in advance. U and V last release: https://review.opendev.org/c/openstack/releases/+/864342 T last release: da9745f8b12dcb7e6f52d9ee868bc402cb44055e [1]https://paste.opendev.org/show/bkKq38Moq2qBXwpr4vSv/ [2]https://bugs.launchpad.net/neutron/+bug/2006763 [3]https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195

3 5

[election][ptl][tacker] PTL Candidacy for 2023.2 (Bobcat)
by Yasufumi Ogawa 10 Feb '23

10 Feb '23

Hi, I'd like to propose my candidacy for Tacker PTL for Bobcat cycle. I have been a Tacker's PTL since Victoria and mainly contributed to provide the latest features of ETSI-NVF standard features to enable operators to deploy their services. As Tacker team, we have focused on introducing container management support while revising the standard features to follow the latest API specifications. Our interest has been shifting to more practical usecases such as providing 5GC services with VRAN features on Tacker and OpenStack. I'd like to make a progress for expanding these usecases required by operators in the next cycle. Regards, Yasufumi (yasufum)

1 0

[heat][release] Proposing to EOL Train, Ussuri and Victoria
by Brendan Shephard 10 Feb '23

10 Feb '23

Hi folks, We’re looking to move Train, Ussuri and Victoria branches to EOL for Heat projects. Just reaching out to see if there are any objections, if I don’t hear anything back I’ll move forward with that this week. Cheers, Brendan Shephard Senior Software Engineer Red Hat Australia

2 3

[release] Release countdown for week R-5, Feb 13-17
by Thierry Carrez 10 Feb '23

10 Feb '23

Development Focus ----------------- We are getting close to the end of the 2023.1 Antelope cycle! Next week on February 16 is the Antelope-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.2 Bobcat cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 16. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 16 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights, ahead of the deadline on February 23. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Early bird deadline for OpenInfra Summit registration: February 15 Antelope-3 milestone (feature freeze): February 16 (R-5 week) Cycle Highlights Due: February 23 (R-4 week) RC1 deadline: March 2 (R-3 week) Final RC deadline: March 16 (R-1 week) Final 2023.1 Antelope release: March 22 Virtual PTG: March 27-31 -- Thierry Carrez (ttx)

1 0