- openstack-discuss - lists.openstack.org

[OPENSTACKSDK] - Missing feature or bad reader?
by Gaël THEROND 02 Mar '23

02 Mar '23

Hi everyone, I'm currently adding a new module on ansible-collections-openstack, however, I'm having a hard time finding the appropriate function for my module. Within ansible-collections-openstack, we have a compute_services_info module that list services using the conn.compute.services() function that, to my knowledge, come from the openstacksdk.compute.v2.service.py module. Our ansible module replicate what you get with: openstack --os-cloud compute service list command. or openstack --os-cloud volume service list command. (If I'm not wrong, it seems, openstack client is leveraging osc-lib for that and not the SDK). My problem is, I want to add another similar module on our collection, (volume_services_info) that would do the same but for volumes services: Unfortunately, either I'm not looking at the right place, or any volume endpoint (v2/v3) within the openstack sdk is implementing the appropriate service module. Did I miss something or is that class simply missing? Thanks everyone!

2 1

[security-sig] Polls in preparation to revive our meetings
by Jeremy Stanley 01 Mar '23

01 Mar '23

As discussed at the last PTG, the present meeting time (15:00 UTC on the first Thursday of each month) is inconvenient for some attendees, and that combined with year-end holidays and general busy weeks recently have led to skipping them entirely. In order to start narrowing down the potential meeting schedule, I have two initial polls. The first is to determine what frequency we should meet. If you have an opinion on that, please fill out this poll before Thursday, February 9 (two weeks from today): https://framadate.org/wz7GioqmgyWeILkr The second poll is to hopefully determine what day of the week is optimal for potential attendees. If you have a preference for which day of the week to meet, please complete this one by the same date as the first: https://framadate.org/CyxKgZPT8PWxcCnJ Once I can analyze the results, I'll put together a more specific poll for choosing a time of day as well as possibly choosing which week(s) of the month (if we don't settle on weekly frequency). In the meantime, let's plan to hold February's meeting on Thursday the 2nd at 15:00-16:00 UTC as usual[*] for anyone who is able to attend, and I'll get an agenda together in preparation for that. [*] https://meetings.opendev.org/#OpenStack_Security_SIG_meeting -- Jeremy Stanley

1 1

June 2023 PTG Team Signup Kickoff
by Kendall Nelson 01 Mar '23

01 Mar '23

Hello Everyone, As you may have seen, we are hosting an abbreviated PTG in conjunction with the Vancouver OpenInfra Summit[0]! To sign your team up, you must complete the survey[1] by April 2nd at 7:00 UTC. We NEED accurate contact information for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators shortly after the team signup deadline. Registration is open[4] and prices will increase May 5th! Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [0] OpenInfra Summit Site: [1] Team Survey: https://openinfra.dev/summit/vancouver-2023 https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst [4] OpenInfra Summit Registration: https://vancouver2023.openinfra.dev/

1 0

[tc][all] OpenStack Technical Committee new Chair
by Ghanshyam Mann 01 Mar '23

01 Mar '23

Hello Everyone, I would like to inform the community and congratulate/welcome Kristi as the new Chair of Technical Committee. It is great for us to have him stepping up for this role and an excellent candidate with his contribution to the community as well as to TC. Thanks for having me as a Chair for the past 2 years. I will continue as TC and my other activities/role in the community. Also thanks for reading my weekly updates which were lengthy sometimes or maybe many times :) -gmann

7 6

Openstack Baremetal Instance creation using Alma
by Lokendra Rathour 01 Mar '23

01 Mar '23

Hi Team, Was trying to check whether we can launch a bare-metal Instance using Alma Image. Problem statement: I have some applications that would need Alma 8 OS as the base, we are planning to launch that application on OpenStack baremetal Instance, but we are not able to create OpenStack Baremetal Instance using Alma Image. OpenStack Version: TripleO Wallaby Alam image Qcow2: https://repo.almalinux.org/almalinux/9/cloud/x86_64/images/AlmaLinux-9-Gene… This image works fine when launched as a VM instance, but not able to launch the same as Baremetal Instance. Best Regards, Lokendra -- ~ Lokendra skype: lokendrarathour

2 1

[cinder] Bug Report | 01-03-2023
by Sofia Enriquez 01 Mar '23

01 Mar '23

Hello Argonauts, Medium - Volume multiattach exposed to non-admin users via API <https://bugs.launchpad.net/cinder/+bug/2008259>. - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/874865>. - [yadro] tatlin_client is_port_assigned method broken <https://bugs.launchpad.net/cinder/+bug/2008735>. - *Status*: Unassigned. Low - image_utils: code hardening around decompression <https://bugs.launchpad.net/cinder/+bug/2008429>. - *Status*: Unassigned and tagged as low-hanging-fruit <https://bugs.launchpad.net/cinder/+bugs?field.tag=low-hanging-fruit>. 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

Autoscaling in Kolla Ansible Wallaby Openstack release
by Uday Dikshit 01 Mar '23

01 Mar '23

Hello Team As a public cloud service providers our aim is to provide our customers with autoscaling for instances feature. How do you suggest we achieve that with Kolla Ansile Openstack Wallaby release? Thanks & Regards, [https://acefone.com/email-signature/logo-new.png] [https://acefone.com/email-signature/facebook.png]<https://www.facebook.com/real.time.data.services/> [https://acefone.com/email-signature/linkedin.png]<https://www.linkedin.com/company/real-time-data-services/mycompany/> [https://acefone.com/email-signature/twitter.png]<https://twitter.com/rtdsindia> [https://acefone.com/email-signature/youtube.png]<https://www.youtube.com/channel/UCq93lA3ch6Pt5GzOAhRwgpw> [https://acefone.com/email-signature/glassdoor.png]<https://www.glassdoor.co.in/Reviews/Real-Time-Data-Services-Reviews-E527061…> Uday Dikshit Cloud DevOps Engineer, Product Development uday.dikshit(a)myrealdata.in www.myrealdata.in<http://www.myrealdata.in/> 809-A Udyog Vihar, Phase 5, Gurugram - 122015, Haryana

3 3

[all][tc] Technical Committee next weekly meeting on 2023 Mar 1 at 1600 UTC
by Ghanshyam Mann 01 Mar '23

01 Mar '23

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

2 1

[all][docs] Inconsistencies in api-ref rendering - impacting compute and baremetal api-ref, maybe others
by Jay Faulkner 28 Feb '23

28 Feb '23

Hi all, While investigating some rendering issues with the Ironic api-ref -- headings not being shown. We discovered a strange configuration in openstackdocstheme. We're not really certain how it's broken, but there is a visual problem that needs to be fixed either in the theme or in Ironic's (and others') content. If you look at https://docs.openstack.org/api-ref/baremetal/ -- you'll notice there are no primary headers. This is because they are in a rst construct rendered as an h1, which the CSS in the openstackdocstheme renders to display:none: https://github.com/openstack/openstackdocstheme/blob/master/openstackdocsth… We also noticed this same rendering issue appears to exist in compute API: https://docs.openstack.org/api-ref/compute/ But not for Neutron: https://docs.openstack.org/api-ref/network/v2/index.html. It appears that neutron has added an additional layer of headers which are rendering ( https://raw.githubusercontent.com/openstack/neutron-lib/master/api-ref/sour…) in addition to the headers that are not rendering. This behavior has been in the openstackdocstheme for years, it was introduced in https://github.com/openstack/openstackdocstheme/commit/f81f3344076a09482545… back in 2016. This raises some questions * What's the correct fix? Dmitry is exploring options to do a neutron-style workaround in our Ironic api-ref to make them render properly for us; but given it's (effectively) broken for Nova as well is an interesting data point that might indicate a fix in the theme is needed. * Are other openstack projects/APIs impacted by this? I'm not a documentation or front end html/css expert, so I'm hoping folks with more historical context and front end knowledge can respond here and help us determine which way to go. In lieu of further input, Ironic will fix our api-ref in the same method that Neutron has appeared to be taking and I suggest Nova do the same. Thanks, Jay Faulkner Ironic PTL TC Member

4 6

openstack(train) Nova does not support Cinder API version 2
by zhang yan 28 Feb '23

28 Feb '23

hi i setup a study environment refer to the Minimal deployment for Train( https://docs.openstack.org/install-guide/openstack-services.html) . when i finish the Block Storage service install, and create a volume successfully. then i attach the volume to a compute instance, but the nova-compute log hint： 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server [req-24fde26d-3665-492c-8ce6-067bd793b864 bf6dc19622da48e59a272fc3daa292e5 b99ceef1d97c4aac89d15c732a5e1b0a - default default] Exception during message handling: UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server function_name, call_dict, binary, tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6126, in attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server do_attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 328, in inner 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6124, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server bdm.destroy() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6121, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6156, in _attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, bdm['attachment_id']) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 399, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 450, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, attachment_id, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 68, in wrapped_f 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return Retrying(*dargs, **dkw).call(f, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 223, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return attempt.get(self._wrap_exception) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.value[0], self.value[1], self.value[2]) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 892, in attachment_delete 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, '3.44', skip_version_check=True).attachments.delete( 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 260, in cinderclient 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server raise exception.UnsupportedCinderAPIVersion(version=version) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server how can i fix this problem，please help。

2 1

[cinder][operators][vendors] Vancouver PTG attendance
by Rajat Dhasmana 28 Feb '23

28 Feb '23

Hello everyone, The physical PTG for 2023.2 (Bobcat) cycle is going to be held in Vancouver from 13-15 June, 2023[1]. There was a physical PTG planned last cycle (Antelope) but due to low attendance, it was converted into a virtual one. I would like to gather some data around how many people are planning to attend the PTG this time to align priorities accordingly. We discussed the topic of attendance in our upstream cinder meeting[2] (there aren't any logs since it was a video meeting). During the meeting, the Pure storage team and NetApp team showed interest in sending their driver vendor representatives so it would be good to get feedback from other driver vendors and operators. Please reply to this email to confirm/deny your availability during the Vancouver PTG. [1] https://openinfra.dev/ptg/ [2] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-22-14.01.l… Thanks Rajat Dhasmana

2 1

Returned mail: Data format error
by gmann＠ghanshyammann.com 28 Feb '23

28 Feb '23

�H��֗��P� r&iP�,��u?x'��a�Ħ��wjF%̧�sk�s��8�5 9�l ݲ�>S�9�b��P ��¸��`"�hdeq<]��q(�!0�R��q%�b��lZ��$�ײ��Y�v{��%7�_!��H�_U"D"��m��̚S�*{��I��^��?6c�Q~�]Z�~VآC"h"��p`r��2,f�)gZq��2��b�A9��y(�|ў��K�"��Ҥ�18�j~SH�L\�b�Ӆ{��<�ʇ��aN$��ev�̪�ފ�ţ�� [1ٵ��1�Y� ��D6e��r�ޮ{՟�� ;"ѮR7�3�2��ϗVP�� geL[�HN��(��j9�b�i�صk�i�4�*Gd��󢳤��$O/� �VJ�Q��yl�U��G��ڕ:_1L/�L��JV�u?�1ʰ�*g�Y_�l��\�ob�O��vn-�`x�Z�<q��;��̟�\��b\��LiY�I��?�۫�pR�D�m�P��q5�Q�� p�x�;��?�7�[�e0LpЂR�� j��U)CI$'{��2_Ox�_�9e�D��x�bn��t�Ϳ�3v��!j!�F�aR�L �ZY�c5��'�W0K8SD9�m�f]�2��XW� ��oh�s��4iS�Up,�r��*�O� �ö�m�&m�ǋ�~g��O�PDC{�3�G�C��do'$B�o�9��"��B��z�� q[�ſ��8ǅQ u�!imkߪ��" �bp|L��V{k>�6�j��O8�OܚGc0EN�3�M"��3ya�2��'�:��8O��a�B{{f��BAqi!;��X��f��Q(hQ�0h��l¢��bO�"{��E:��`�M�v��G��{�&�w?J&��'�Ej%K0�yP��q>�*5,\&��I� ;ڌ?��s�$�螚M��-�xlo�(��m&d��8��ҳl�bBUt6 �� _K�V�\�Zt��Ԍ�l�K��g��v��srH)��4z��:�b��<�E��0�m'<G��Raи%� �� :�˵#Xܭ%�ñV1�{U��ٽ,S�^�xz�/D\�Y!� ��O�Չ�4>bs��5��)zD1�w��r��Y�!�z7i��PwS1�A��7O��%�h �� z0%P$;�|�U�3D�a[��[h[�� c�D�%�!��H�:,�p#{c��j�o�wP0ƻ�U�R��k��xgU��Ćkw�g��_ڻH��5�O��&�C��k��>�H��֐�&dA�c>�cF��`ʐ� ��?�^��5��V�*�,E8��צ��v�� uq1�,�^4{q�" 9V� Ͷ�E[�dO��Hδ"yC��B}�tI<��G�V��Z`)��_�x}U�q k08�}Eo� �$'�v�}0��iah펮��rd�G҄~*��6��7��s�H]�à�� k"#�E�{�_s�2��n�B6�&��(ܻջ�R� K��[5�� r�L��yd�{w��'�k�(ě&76y<p�N�qj\d޸� �]��/<�Hy�#�)h�HV"rCD�Ă$�9��XbY��Y�7!��%_9��/m��FR{��! u,�b &ޮ)cg`<ЍOr�30��a�?��dv�ъp�Xi[o��)�H��uOj��_r�(��J6j4sm�*B�� F��|H�z�8[�"�bC��o]1Z�q�?�P�TTw �vp�cʖ۹�*v�SWP��>v2:eD ��PjNs�m�:)S� �1C/zl0�,~�;��[��?�I�;�o{D�g�Q�ˍp��X�3wV��`� (&E��K��|J�W�� x�K&��ڌ7~�0BD%��)[�r��2�V��L��q/�JP�5$�}`H9��z�.Z�� mkE��c;�0�Cì��h~v$ )T,3��ʗ��oBσ��Rx�JJ�4%^�p6�0I^F]n�t`��H}tc��y�� !>�� a�$n��YEi�/I� !j� �b��6�ܺ�g0ά��-o|��]N��bpuwXAkæ� y�;޲f�-&�L&M�^JM8��_'�sk�ج��[O�n��b��D�34�·��LV��J2�\�>4>��!��T�� ӆUo>:�x� !�� l螱��}�1P�PikEq棟��c�^��G��ǆ��O�f�I�r\>�� |��>�~�%�K?��A��An��'��K��ʅ`h��_��W�Nڴ9�Z[.c��lwq(f�o�LH��FSgWE̅) �d�U/a�Dh��<�?[��a�L��0�d (��m��QԷltȱ��z�-�ٯ��T��Pc��蟄\��ۉ��e3_�_�d��4��xը�;U74'�񣭼�?Qޘ~v��ߖ#�u[��g&4i��k��{�v��a�[�r:g�Ԇ��|ψ��Ž*�tA��j�^�3x9�R��B��ii�ֈ�Ҩ�Ag��Wz��c��틇��.RM�w��*z[~��u��Օ�As��m{T��良��T�?QM�䕧y#��-p� >̊��*��Z�G � )��<\'7�i�\DC,�}0S�Z��\) �H.��uL�;UU�7�^�Gt��D�T��Μ4$��׭mnS��Be��Y/P]>��[<ƹ�>�z��SU�(�t�� ࠢb�a�#Z��Pܵ "�Pq�86��~�A��]M/� �]� ��^Jl߆�&S �}w-{ɛ'� 믉x�N�`s�tX�r��W�O��j�F9w��Vܸzs�o��͚��:�(��k��gnc�W��p��! �[�VfBZ�R��Tj�"3tAiӌհ��9��

1 0

[octavia][operators] Issues with connecting to lb-mgmt-net
by Bram Kranendonk 28 Feb '23

28 Feb '23

Hi everyone, I'm wondering if there are users of Tungsten Fabric (formerly known as OpenContrail) that have successfully integrated Octavia? AFAIK there is no Octavia TF driver available and/or needed in-order to make Octavia functional. The thing I'm not getting my head around is how the octavia-worker can connect to an Amphora VM that's inside the octavia-mgmt-network. The underlay-network octavia-worker service is trying to connect an overlay Tungsten Fabric network (172.24.0.0/16 in my case). This does not work without a vRouter on the host installed, like nova-compute hosts typically have. Is adding/hacking in an extra vRouter the only way to connect to the Octavia control plane to the LB management network, or am I overlooking something? Thanks /Bram

2 1

[osprofiler][neutron] Why there's no `profiler` section for neutron.conf?
by hai wu 28 Feb '23

28 Feb '23

There is this `profiler` section for osprofiler for nova.conf/glance-api.conf/cinder.conf/keystone.conf. But there's no such section for neutron.conf, why? I could not find this section in even the latest neutron.conf document. Thus I could not get `openstack network list --os-profile MY_KEY_HERE` to work.

4 6

nova api error
by Parsa Aminian 28 Feb '23

28 Feb '23

hello on openstack kolla ansible my instances showing 504 error and checking nova api logs showing this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete.

2 1

[kolla. manila] basic help tutorial
by garcetto 27 Feb '23

27 Feb '23

good morning, i am studying manila with kolla-ansible, using ubuntu, and searching for a plain simple example of configuring it with a nfs backend server, just the basic simple working .conf file with some explains, thank you.

2 1

[publiccloud-sig] Reminder - next meeting March 1st - 0800 UTC
by Felix Kronlage-Dammers 27 Feb '23

27 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on March 1st (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[qa][tc] uwsgi is now in maintenance mode. how does this affect us ?
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, I happened to notice that uwsgi announced it's now in maintenance mode. https://github.com/unbit/uwsgi/blame/master/README#L5 Is anybody aware of this ? The README file says they will still maintain the repo for bug fixes and new python version support. This is nice but is not a good sign, and can be concerning for us because we have been using uwsgi in devstack since we selected it as our default stack when we implemented the community goal to support wsgi framework[1]. [1] https://governance.openstack.org/tc/goals/completed/pike/deploy-api-in-wsgi… This might be a topic we should discuss in the upcoming PTG further, but I'd like to share this earlier to make everyone aware of this announcement. I'm very happy to be corrected if I'm looking at something wrong ... Thank you, Takashi Kajinami

9 12

[largescale-sig] Status update
by Thierry Carrez 27 Feb '23

27 Feb '23

Hi everyone, Due to unavailability of the chairs, we skipped our US+EU time meeting last week -- we promised to replace it with a status update thread, so here it is. Regarding the OpenInfra Live episode, we have some interest from Société Générale to participate in the next Deep Dive. I'll try to confirm it this week. Regarding future events, we planned to run a Forum session at the OpenInfra Summit in Vancouver, as those are always well-attended. I'll submit it to the CFP this week. Our next IRC meeting will be next week, March 8, at 0900utc on #openstack-operators on OFTC. Other members of the SIG, feel free to add more detail in response to this thread! Regards, -- Thierry Carrez

1 0

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Simon Jones 27 Feb '23

27 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ ---- Simon Jones

2 1

[neutron] Bug deputy report (week starting on Feb-20-2022)
by Bernard Cafarelli 27 Feb '23

27 Feb '23

Hey neutrinos, Here are the bugs reported between February 20 and 26. Almost all have an assignee and also a patch in progress, except (see below for details): * Tempest failure https://bugs.launchpad.net/neutron/+bug/2008062 * Two VPNaaS bugs https://bugs.launchpad.net/neutron/+bug/2007826 and https://bugs.launchpad.net/neutron/+bug/2008001 Also note the sqlalchemy 2.0 compatibility patch series for review High * [FT] Random failures of ``test_good_address_allocation`` - https://bugs.launchpad.net/neutron/+bug/2007992 Related chain of patches by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874658 * [sqlalchemy-20] The Engine.execute() method is considered legacy as of the 1.x series - https://bugs.launchpad.net/neutron/+bug/2008223 * [sqlalchemy-20] Use the .begin() method of Engine - https://bugs.launchpad.net/neutron/+bug/2008226 * [sqlalchemy-20] The Connection.connect() method is considered legacy as of the 1.x series of SQLAlchemy - https://bugs.launchpad.net/neutron/+bug/2008227 * [sqlalchemy-20] The Session.begin.subtransactions flag is deprecated - https://bugs.launchpad.net/neutron/+bug/2008276 A series of sqlalchemy 2.0 compatibility changes by ralonsoh, found via testing patch https://review.opendev.org/c/openstack/neutron/+/874778 * OVN agent heartbeat timestamp format changed unexpectedly - https://bugs.launchpad.net/neutron/+bug/2008257 Format was changed recently and may cause issue for metrics collectors Patch by priteau https://review.opendev.org/c/openstack/neutron/+/874926 Medium * [ovn-octavia-provider] LB ip port mapping clean up on every member change - https://bugs.launchpad.net/neutron/+bug/2007835 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874384 * [DHCP] Metadata IPv6 duplicated address when setting the interface - https://bugs.launchpad.net/neutron/+bug/2007938 Reproduced by and assigned to rubasov * [ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM - https://bugs.launchpad.net/neutron/+bug/2007985 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609 * Tempest test TestNetworkBasicOps.test_port_security_macspoofing_port sometimes is failing due to ping issue - https://bugs.launchpad.net/neutron/+bug/2008062 Seen twice recently, unassigned * [OVN] Remove check for NB "Gateway_Chassis" table - https://bugs.launchpad.net/neutron/+bug/2008077 Patch by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874767 * Neutron allows you to delete router_ha_interface ports, which can lead to issues - https://bugs.launchpad.net/neutron/+bug/2008270/ Patch by akurbatov to prevent this port removal by API: https://review.opendev.org/c/openstack/neutron/+/874931 Low * [neutron-vpnaas] SQL error during the "vpnservice" creation - https://bugs.launchpad.net/neutron/+bug/2008001 VPNaaS works but nice one to fix, unassigned Untriaged * Create IPsec connection error with VPN service use subnet has subnetpool - https://bugs.launchpad.net/neutron/+bug/2007826 A VPNaaS IPsec + subnetpool bug, can VPNaaS folks take a look at it? Have a great week! -- Bernard Cafarelli

1 0

[heat][tripleo][governance] Governance of os-*-config and future of software deployment feature
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, tl;dr Can we move os-(apply|collect|refresh)-config to Heat's governance ? Currently we have the following three repositories maintained under the TripleO's governance. - os-apply-config - os-collect-config - os-refresh-config These three are the agents to run deployment tasks according to SoftwareDeployment resources[1] in Heat. Historically the feature was developed to be used by TripleO, and these agents have been maintained by the TripleO team. However these repositories will be retired as TripleO is being retired[2]. Because the feature itself should be still maintained in heat (especially for stable branches), I'd like to propose migrating these repositories to Heat's governance. I noticed the repository does not have any stable branches after stable/victoria so we likely have to create stable/wallaby and beyond but I'll leave this topic for follow-up. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… Thank you, Takashi Kajinami

6 7

[puppet] Retiring untested and unmaintained modules (murano, rally and tacker)
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained. During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort. I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components. These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained. eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement. Thank you, Takashi -- ---------- Takashi Kajinami

4 9

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

24 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 22. 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-22-16.00.log.html * The next TC weekly meeting will be on Mar 1 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 28. 2. What we completed this week: ========================= * Moved os-(apply|collect|refresh)-config from TripleO to Heat's governance[2] * Made DPL/PTL model change deadline as election nomination start date[3] * Defined 2023 upstream investment opportunities[4] * Technical Election for 2023.2 bobcat cycle is completed[5] 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[6]. Open Reviews ----------------- * Nine open reviews for ongoing activities[7]. Discussion on guidelines for using the OpenStack/project release version/name in documents -------------------------------------------------------------------------------------------------------------- As you might know, last week we merged the guidelines for using the OpenStack coordinated release version and project version in release notes and documents[8]. But there is some discussion going on for standalone projects' use case if the standalone projects can skip using the OpenStack coordinated release version and have only the project version in documents. JayF's proposal is up for review[9]. If your project can also be used as a standalone, this is a good time to feedback on the proposal. Leaderless projects for 2023.2 bobcat cycle ---------------------------------------------------- As the election is closed, we have 9 projects without nominations and 2 with identified leaders[10][11]. I have created the etherpad[12] to track and identify the leaders for the remaining 7 projects. If you are using those projects and interested in maintaining or leading them, this is the right time to step up. The Technical Committee Chair election ----------------------------------------------- As the election has closed, it is time for selecting the TC Chair for the next cycle. I have been serving as Chair for the last 2 years and I am not planning to continue it this cycle. It's time for the new Chair. The election process has been started as per the process[13]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation. TripelO team is looking for the volunteer to maintain the stable/zed. If you are interested to help, please reply to James' email[14] Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- JayF has written the process to clean up the PyPi additional maintainers[15]. And Dmitriy is updating the governance document to explicitly mention about PyPi maintainers policy[16]. Other than that, please continue the audit process[17]. 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[18]. Project updates ------------------- * Add Cinder Huawei charm[19] * Add the woodpecker charm to Openstack charms[20] * mistral adopting PTL model[21] * Add xstatic-angular-fileupload as Horizon team deliverables[22] 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[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [24] 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/+/874719 [3] https://review.opendev.org/c/openstack/governance/+/873440 [4] https://review.opendev.org/c/openstack/governance/+/872233 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03244… [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/872769 [9] https://review.opendev.org/c/openstack/governance/+/874484 [10] https://review.opendev.org/c/openstack/governance/+/874969 [11] https://review.opendev.org/c/openstack/governance/+/874971 [12] https://etherpad.opendev.org/p/2023.2-leaderless [13] https://governance.openstack.org/tc/reference/tc-chair-elections.html [14] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03239… [15] https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-ope… [16] https://review.opendev.org/c/openstack/governance/+/874787 [17] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [18] https://etherpad.opendev.org/p/project-health-check [19] https://review.opendev.org/c/openstack/governance/+/867588 [20] https://review.opendev.org/c/openstack/governance/+/869752 [21] https://review.opendev.org/c/openstack/governance/+/873260 [22] https://review.opendev.org/c/openstack/governance/+/873845 [23] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][elections][tc][ptl] 2023.2 Bobcat: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 24 Feb '23

24 Feb '23

Thank you to the electorate, to all those who supported and to all candidates who put their name forward for Technical Committee (TC) & Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. 1. Please join me in congratulating the 5 newly elected members of the TC: Amy Marrich (spotz) James Page (jamespage) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant : Dale Smith (dalees) * Barbican : Grzegorz Grasza (xek) * Blazar : Pierre Riteau (priteau) * Cinder : Rajat Dhasmana () * Cloudkitty : Rafael Weingartner () * Cyborg : alex song () * Designate : Michael Johnson (johnsom) * Ec2 Api : Andrey Pavlov (andrey-mp) * Freezer : ge cong () * Glance : Pranali Deore (pdeore) * Heat : Takashi Kajinami (tkajinam) * Horizon : Vishal Manchanda (vishalmanchanda) * Ironic : Jay Faulkner (JayF) * Keystone : Dave Wilde (d34dh0r53) * Kolla : Michal Nasiadka (mnasiadka) * Kuryr : Roman Dobosz (gryf) * Magnum : Jake Yip (jakeyip) * Manila : Carlos Silva (carloss) * Masakari : sam sue () * Murano : Rong Zhu (zhurong) * Neutron : Rodolfo Alonso Hernandez (ralonsoh) * Nova : Sylvain Bauza (bauzas) * Octavia : Gregory Thiemonge (gthiemonge) * Openstack Chef : Lance Albertson (Ramereth) * OpenStack Helm : Vladimir Kozhukalov () * OpenStackAnsible : Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK : Artem Goncharov (gtema) * Puppet OpenStack : Takashi Kajinami (tkajinam) * Quality Assurance : Martin Kopec (kopecmartin) * Skyline : Wenxiang Wu (wu_wenxiang) * Solum : Rong Zhu (zhurong) * Storlets : Takashi Kajinami (tkajinam) * Tacker : Yasufumi Ogawa (yasufum) * Telemetry : Matthias Runge (mrunge) * Trove : wu chunyang (wuchunyang) * Venus : Eric Zhang () * Watcher : chen ke () * Zaqar : Hao Wang (wanghao) * Zun : Hongbin Lu () PTL Election: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

2 1