- openstack-discuss - lists.openstack.org

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 10 Mar '23

10 Mar '23

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Have a nice weekend!

1 0

[barbican] Canceling weekly meeting (March 14th) + PTG discussion topics
by Grzegorz Grasza 10 Mar '23

10 Mar '23

Hi all, I'm on PTO next week, so I'm canceling the weekly meeting. We have just one last meeting before the Virtual PTG, so I booked a time slot for us on Tuesday, March 28th at 13:00 UTC. Please add topics you would like to discuss to the etherpad: https://etherpad.opendev.org/p/march2023-ptg-barbican If there are more things to discuss, I'll book another time slot later in the week. Thanks, / Greg

1 0

[all] broken pepe8 jobs caused by bandit 1.7.5
by Takashi Kajinami 10 Mar '23

10 Mar '23

fyi; It seems the new release of bandit (1.7.5) just came out and this introduces a new lint rule to require defining the timeout parameter for all "requests" calls. https://github.com/PyCQA/bandit/commit/5ff73ff8ff956df7d63fde49c3bd671db8e8… This is currently affecting heat and quick search shows some of the other projects contain some code not compliant with this rule(barbican, ceilometer, cinder, glance, manila, nova, ...). Also, it seems we do not pin bandit by u-c for some reason this likely affects all stable branches. Actually I first noticed this when I tried to backport one fix to 2023.1 branch of heat... Thank you, Takashi

2 2

[neutron][ovn] domain-search dhcp option per network/subnet level
by Михаил 10 Mar '23

10 Mar '23

Greetings to all! In my openstack setup (vanilla ubuntu 22.04 Zed release + OVN networking ) I try to find a way to setup a scheme where my instances should get dhcp search domain option on network/subnet level. For example - when I create network/subnet, I want to tell neutron, that all created ports in that network/subnet must receive my dhcp search-domain option Any help advices will appreciated. Thank you! -- Best regards, Mikhail.

2 2

[manila] Share configuration with cinder as a backend
by Jan Wasilewski 09 Mar '23

09 Mar '23

Hi, I am looking for instructions on how to configure a Manila service with Cinder as a backend. I have gone through the https://github.com/openstack/manila/blob/master/doc/source/configuration/sh… page, and I am wondering if someone has a link to a preconfigured "golden image" that can be used as a service_image. Additionally, I am wondering if this configuration can be used with driver_handles_share_servers=True (generally, I see that both options are supported here), but are there any specific limitations? I have already configured other backends (standalone ZFS, NFS, and Huawei driver), but I would like to test share snapshot retrieval using Cinder as a backend. Unfortunately, as I see, Cinder is not as straightforward as other backends(or no one is using it), which is why I am asking for some hints. Thanks in advance /Jan

2 1

[barbican] Canceling weekly meeting (March 14th) + PTG discussion topics
by Grzegorz Grasza 09 Mar '23

09 Mar '23

Hi all, I'm on PTO next week, so I'm canceling the weekly meeting. We have just one last meeting before the Virtual PTG, so I booked a time slot for us on Tuesday, March 28th at 13:00 UTC. Please add topics you would like to discuss to the etherpad: https://etherpad.opendev.org/p/march2023-ptg-barbican If there are more things to discuss, I'll book another time slot later in the week. Thanks, / Greg

1 0

[neutron][largescale-sig] agent_down_time and report_interval
by Arnaud Morin 09 Mar '23

09 Mar '23

Hello neutron and large-scalers, Is there any recommendation on tuning the neutron report_interval (agent) and agent_down_time (server) to "optimize" the communication between agents and servers without putting to much heavy duty on both rabbit and database? We are currently facing some scaling issue regarding this, and we found out that, at least, CERN did some tweak about this ([1] and [2]) Is there anyone else with specific configuration on that part? I have the feeling that this could be increased (so report will happen less often). One obvious side effect of this is the fact that the server will take more time to see a down agent, is there any other side effect that could happen? Is it something we can eventually add in our large-scale documentation ([3])? Cheers, [1] https://youtu.be/5WL47L1P5kE?t=1173 [2] https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c0… [3] https://docs.openstack.org/large-scale/journey/configure/index.html

2 2

Re: [cinder] Error when creating backups from iscsi volume
by Gorka Eguileor 09 Mar '23

09 Mar '23

On 06/03, Rishat Azizov wrote: > Hi, > > It works with smaller volumes. > > multipath.conf attached to thist email. > > Cinder version - 18.2.0 Wallaby Hi, After giving it some thought I think I may know what is going on. If you have DEBUG logs enabled in cinder-backup when it fails, how many calls do you see in the cinder-backup to "multipath -f" from os-brick, only one or do you see more? Cheers, Gorka. > > пн, 6 мар. 2023 г. в 17:35, Gorka Eguileor <geguileo(a)redhat.com>: > > > On 16/02, Rishat Azizov wrote: > > > Hello! > > > > > > We have an error with creating backups from iscsi volume. Usually, this > > > happens with large backups over 100GB. > > > > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > [req-f6619913-6f96-4226-8d75-2da3fca722f1 > > 23de1b92e7674cf59486f07ac75b886b > > > a7585b47d1f143e9839c49b4e3bbe1b4 - - -] Exception during message > > handling: > > > oslo_concurrency.processutils.ProcessExecutionError: Unexpected error > > while > > > running command. > > > Command: multipath -f 3624a93705842cfae35d7483200015ec6 > > > Exit code: 1 > > > Stdout: '' > > > Stderr: 'Feb 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a > > > multipath device\n' > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Traceback > > > (most recent call last): > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line > > 165, > > > in _process_incoming > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server res = > > > self.dispatcher.dispatch(message) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line > > > 309, in dispatch > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > self._do_dispatch(endpoint, method, ctxt, args) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line > > > 229, in _do_dispatch > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = > > > func(ctxt, **new_args) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/cinder/utils.py", line 890, in wrapper > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > func(self, *args, **kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 410, in > > > create_backup > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > volume_utils.update_backup_error(backup, str(err)) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in > > > __exit__ > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > self.force_reraise() > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in > > > force_reraise > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise > > > self.value > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 399, in > > > create_backup > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server updates > > = > > > self._run_backup(context, backup, volume) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 493, in > > > _run_backup > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > ignore_errors=True) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 1066, > > in > > > _detach_device > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > force=force, ignore_errors=ignore_errors) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 141, in > > > trace_logging_wrapper > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > f(*args, **kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line > > 360, > > > in inner > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > f(*args, **kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > > > "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", > > > line 880, in disconnect_volume > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > is_disconnect_call=True) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > > > "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", > > > line 942, in _cleanup_connection > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > self._linuxscsi.flush_multipath_device(multipath_name) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/os_brick/initiator/linuxscsi.py", line > > > 382, in flush_multipath_device > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > root_helper=self._root_helper) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/os_brick/executor.py", line 52, in > > > _execute > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = > > > self.__execute(*args, **kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/os_brick/privileged/rootwrap.py", line > > > 172, in execute > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > execute_root(*cmd, **kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_privsep/priv_context.py", line > > 247, > > > in _wrap > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return > > > self.channel.remote_call(name, args, kwargs) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File > > > "/usr/lib/python3.6/site-packages/oslo_privsep/daemon.py", line 224, in > > > remote_call > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise > > > exc_type(*result[2]) > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > oslo_concurrency.processutils.ProcessExecutionError: Unexpected error > > while > > > running command. > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Command: > > > multipath -f 3624a93705842cfae35d7483200015ec6 > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Exit code: 1 > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stdout: '' > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stderr: 'Feb > > > 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a multipath > > device\n' > > > 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server > > > > > > Could you please help with this error? > > > > Hi, > > > > Does it work for smaller volumes or does it also fail? > > > > What are your defaults in your /etc/multipath.conf file? > > > > What Cinder release are you using? > > > > Cheers, > > Gorka. > > > > > defaults { > user_friendly_names no > find_multipaths yes > enable_foreign "^$" > } > > blacklist_exceptions { > property "(SCSI_IDENT_|ID_WWN)" > } > > blacklist { > } > > devices { > device { > vendor "PURE" > product "FlashArray" > fast_io_fail_tmo 10 > path_grouping_policy "group_by_prio" > failback "immediate" > prio "alua" > hardware_handler "1 alua" > max_sectors_kb 4096 > } > }

1 0

OpenInfra Live March 9, 2023, at 9 a.m. CT
by Kristin Barrientos 09 Mar '23

09 Mar '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by OpenMetal Episode: Examination of Cost Differences b/w Private Cloud and Hyperscalers Todd Robinson, president of OpenMetal, will be discussing the examination of cost differences between private cloud and hyperscalers. Date and time: March 9, 2023, at 9 a.m. CT (15:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=6GCGhuRpPqM LinkedIn: https://www.linkedin.com/events/7038909988492242944/comments/ WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Todd Robinson Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[Magnum] Magnum service status in Openstack Antelope
by A Tom 08 Mar '23

08 Mar '23

Hi, Will magnum be supported in Antelope and further releases of Openstack? I was looking for some informations about this and I’m quite confused, because here I don’t see Magnum service: https://releases.openstack.org/antelope/index.html and here Magnum is mentioned: https://docs.openstack.org/2023.1.antelope/projects.html Which version of kubernetes is supported in Zed, and which (if) will be in Antelope? Because there’s no such information in compatibility matrix: https://wiki.openstack.org/wiki/Magnum Best regards, Adam Tomas

3 2