December 2023 - openstack-discuss

[Reminder] OpenInfra Live: PTG Recap, Dec 7 at 15 UTC
by Kristin Barrientos 06 Dec '23

06 Dec '23

Hi Everyone, Tune in this week for another episode of OpenInfra Live, brought to you by the OpenStack and StarlingX community! Episode: Join us for a Project Teams Gathering (PTG) recap! Project leaders from Ironic, Technical Committee, Nova, Sunbeam, Manila, Cinder, StarlingX and Neutron will provide recaps from discussions held during the PTG. Date and time: Thursday, Dec 7, 15 UTC YouTube: https://www.youtube.com/live/thidlQGX29M?feature=shared LinkedIn: https://www.linkedin.com/events/7132754094531747840/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Kendall Nelson, Jay Faulkner, Sylvain Bauza, James Page, Carlos da Silva, Rajat Dhasmana, Steve Geary and Brian Haley Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[keystone] Weekly meeting canceled
by Dave Wilde 06 Dec '23

06 Dec '23

Hello, Unfortunately I have a meeting conflict today and need to cancel the weekly meeting. Please let me know if there is anything y'all need. Thank you! /Dave

2 1

[cinder] 2024.1 (Caracal) R-17 virtual mid cycle (6 Dec, 2023)
by Rajat Dhasmana 06 Dec '23

06 Dec '23

Hello Argonauts, We will be conducting the first midcycle of 2024.1 (Caracal) on 6th December, 2023. Following are the details: Date: 6th December, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/auq-jiem-zxy Etherpad: https://etherpad.opendev.org/p/cinder-caracal-midcycles We have 2 weeks so please add your topics timely. Thanks Rajat Dhasmana

1 1

[oslo] the eventlet story
by Herve Beraud 06 Dec '23

06 Dec '23

Hello Osloers, Just a heads up to you about the eventlet topic. If it is not already the case, I'd recommend that you keep an eye on the current discussions [1][2] about this topic. Indeed it could impact the Oslo world sooner than expected. Obviously I invite you to join the discussions and share your thoughts there [2]. Thanks [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://review.opendev.org/c/openstack/governance/+/902585 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

how to remove volume from postgress in OpenStack
by kjme001＠gmail.com 06 Dec '23

06 Dec '23

Hello, I need to remove a volume from a postgress database on OpenStack. I found instructions on how to do it on mysql database: https://cloud.garr.it/support/kb/openstack/forceDeleteVolume/ but I don't know how to do it on a postgress database, could someone give me a hint? Greetings

1 0

[tc] Winter Holiday Meeting Schedule
by Jay Faulkner 06 Dec '23

06 Dec '23

Hi all, Due to the numerous TC members on PTO during the end of the year holidays, the TC is cancelling our meetings for December 26, 2023 and January 2, 2024. As always, the TC can be reached in #openstack-tc on OFTC or via the mailing list regardless of if we have a meeting. Thanks! Jay Faulkner OpenStack TC Chair

1 0

[cinder][nova][glance][ironic] restricting image metadata values to 255 chars
by Jorge Merlino 06 Dec '23

06 Dec '23

Hello stackers, It has come to our attention recently that nova, cinder, and glance treat image properties differently. This came up in a discussion on a patch to extend the allowable length of image metadata values in cinder [0]. Briefly: - glance allows image property values to be unrestricted in the schema, but effectively limited to 65535 bytes by the database. - cinder restricts the length of an image property value to 255 chars (by request schema) if you try to update the volume_image_properties on a volume, but if you create a volume from an image, cinder happily copies over all the image properties from glance, giving them an effective limit of 65535 bytes. - nova mostly truncates image properties values to 255 chars (it's a bit more complicated, but we can consider that to be nova's behavior for the purposes of this discussion). (We're not sure what ironic does, but they're in the subject line as a consumer of images and volumes.) Note that we're talking about metadata *values* here; the metadata keys are already restricted by charset to basically US-ASCII and 255 length. Values are allowed to be unicode. The point of this email is that it would be good for the services to be consistent about image metadata values. Thus, we propose that all services should restrict image metadata values to 255 unicode characters. (Which is sort of happening already, but not consistently.) The further point of this email is to find out what the impact of this restriction would be on current users. So please respond if you have a use case that would be affected by this change, and could not be addressed by, for example, instead of having one enormous value for a single key, the metadata was broken into a number of key/value pairs that would satisfy the 255 char restriction. Thanks for your attention to this! [0] https://review.opendev.org/c/openstack/cinder/+/868485

2 2

[nova] Spec review day is TOMORROW
by Sylvain Bauza 06 Dec '23

06 Dec '23

Hi folks, We'll run our second spec review day tomorrow. Please make sure that your specs are online and in a reviewable state if you want us to look at them. Please also check your Gerrit emails or be around on IRC in case we have any questions. Cores, you know your duty. Thanks, -Sylvain

1 0

[Neutron] - Getting bridge_name of the port from Java sdk
by Mahudeeswaran Palanisamy 05 Dec '23

05 Dec '23

Hi All, Looks like as part of the below commit, bridge_name info has been removed from port binding vif_details dictionary. Is there any way that we can get the bridge_name info of a port? As far as checked we can get this info by checking if port UUID is part of the “ports” array in “sudo ovs-vsctl list br” output. But there is no equivalent way to get from Java SDK. https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e49f099f… Thanks, Mahudees

3 6

[neutron] Bug Deputy Report November 27 - December 3
by Nurmatov Mamatisa 05 Dec '23

05 Dec '23

Hi, Below is the week summary of bug deputy report for last week. 1 rfe was proposed. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2044896 - [metadata_rate_limiting] options are absent from sample config files - Fix released: https://review.opendev.org/c/openstack/neutron/+/902013 - Assigned to Takashi Kajinami - https://bugs.launchpad.net/neutron/+bug/2045270 - [xena/yoga/zed] devstack-tobiko-neutron job broken - In progress - Assigned to Eduardo Olivares - https://bugs.launchpad.net/neutron/+bug/2045415 - ovn-octavia-provider lacks a sync script like Neutron - Unassigned Medium ------ https://bugs.launchpad.net/neutron/+bug/2045237 - [bulk] there is no clean operation if bulk create ports fails - Unassigned RFE --- - https://bugs.launchpad.net/neutron/+bug/2045058 - [RFE] Use call_monitor_timeout of oslo.messaging RPCClient instead of custom backoff mechanism and hardcoded timeouts - Triaged - Unassigned Best regards, isabek

1 0