- openstack-discuss - lists.openstack.org

[i18n] i18n SIG PTG Schedule & Key Topics for Discussion
by Seongsoo Cho 24 Oct '24

24 Oct '24

Hi i18n SIG Team I’m pleased to announce the i18n SIG schedule for the upcoming PTG. Here are the details: Dates: • October 23rd: 13:00 - 15:00 UTC • October 24th: 13:00 - 15:00 UTC We encourage you to check the meeting minutes and contribute to the discussion by accessing the following Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-i18n Key Discussion Topics: 1. Weblate Migration: We will discuss the progress and steps needed for migrating to Weblate. 2. Enhancing Translation Engagement: We’ll focus on strategies to improve the engagement and translation rates for OpenStack projects. Potential ideas, such as incorporating LLM (Large Language Models), will also be explored. We look forward to your participation and contributions to these discussions. Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 2

[barbican][vault]
by Andy Speagle 24 Oct '24

24 Oct '24

Hey Folks, I'm having some trouble getting barbican to generate and/or store keys in our hashicorp vault in our charmed openstack environment. I have issues with both TPM and SSL related keys. I get extremely generic errors back that I can't seem to figure out how to troubleshoot: 'Traceback (most recent call last):\n File "/usr/lib/python3/dist- packages/nova/conductor/manager.py", line 688, in build_instances\n scheduler_utils.populate_retry(\n File "/usr/lib/python3/dist- packages/nova/scheduler/utils.py", line 998, in populate_retry\n raise exception.MaxRetriesExceeded(reason=msg)\nnova.exception.MaxRetriesExce eded: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance 0c50b2d7-8ac5-41a2-90ab-1e33f7aa1c22. Last exception: Key manager error: Internal Server Error: Secret creation failure seen - please contact site administrator.\n' I'm using barbican 14.0.2 in yoga/stable ... anyone have an ideas how to troubleshoot this? -- Andy Speagle

2 1

[cloudkitty] 2025.01 PTG summary
by Rafael Weingärtner 23 Oct '24

23 Oct '24

Dear all, The CloudKitty project had a great PTG meeting [1]. Thanks to the OpenInfra Foundation for holding it. Also, thanks to all who have dedicated precious time to attend. We started the meeting by revisiting the latest release and discussing the review format we have adopted in the past years. Looking at the result of our process, we decided to maintain it, as it seems to bring results, and concentrate our efforts on getting CloudKitty better and evolving over time. Furthermore, as the current CloudKitty team is a bit small, we have decided to focus on the following topics for the next cycle. - State of Elasticsearch - We want to make sure the CloudKitty CI tests Elasticsearch v8, driver was last tested on v6/7. - OpenSearch/Elasticsearch datastreams -- It looks like this feature is present in both OpenSearch and Elasticsearch. Therefore, we will make an effort to concentrate on these two drivers, instead of replicating their codebase, and separate between them just the differences. - Epoxy (2025.1) supported runtimes -- we will drop the unsupported Python releases/versions. - oslo.policy RBAC new defaults -- We will need to address these new supports in the upcoming release. - Horizon dashboard improvements -- Borrow ideas from Catnip? https://github.com/ObjectifLibre/catnip, and maybe discuss with other agents from the community. In summary that is the outcome of our small, but efficient PTG meeting. Let's keep improving and making CloudKitty better. If I missed something, please do not hesitate to reply back. Also, if somebody needs any help, you can always ping me :) See you guys. Have a nice week! [1] https://etherpad.opendev.org/p/oct2024-ptg-cloudkitty -- Rafael Weingärtner

1 0

Openstack haproxy customization
by Gaurav Sharma 23 Oct '24

23 Oct '24

I have deployed openstack multinode using kolla-ansible ,you know when we run deploy command then haproxy configuration generated by default, now i want to customize the by default configuration by custom file(if create). Please provide better steps to customize haproxy. i have tried many steps but did't get success, one thing i have docker not systemctl .

1 0

[ironic] Core team split into reviewers/approvers
by Jay Faulkner 23 Oct '24

23 Oct '24

OpenStack & Ironic community, Ironic has not added a core reviewer in years. We've had new contributors during this time, but none who has, as yet, risen to the level of being given core review access -- which reflects how steep the learning/responsibility curve is to being a core on an OpenStack project. I'd like to propose, on behalf of many Ironic cores and our PTL Riccardo, a new core review structure for Ironic projects. The goal being to provide an on-ramp for newer cores into the community. The existing ironic-core group will be removed and replaced with two new groups: - ironic-reviewers will contain contributors permitted to perform core reviews (+2/-2) against patches in ironic projects. This group will be initially populated with two new code reviewers (should they accept), CID and cardoe. - ironic-approvers will contain contributors permitted to both perform core reviews and workflow (+A) patchsets. This group will be initially populated with the existing membership of ironic-core. I hope that by providing a middle point on the route to being an approver, we'll be able to extend trust to new contributors more quickly and give them incentive to code review more often -- since their reviews will be able to have a positive impact on landing code more quickly. I've proposed a change here: https://review.opendev.org/c/openstack/project-config/+/931991which makes the first step in adjusting ACLs to split the groups. I've also as part of this change unified more ironic-related projects under the ironic core review banner after auditing those core groups and seeing some inactive contributors in them. Ironic cores have already discussed this privately, and we have a lazy consensus to perform this change. This email serves as both notice to the larger community and as a formal way to gain consensus. If there are any questions or concerns please let us know. Thanks, Jay Faulkner

8 12

[kolla-ansible][haproxy][2024.1] HAProxy template error
by Satish Patel 22 Oct '24

22 Oct '24

I am deploying kolla-ansible latest release 2024.1 on Ubuntu 22.04 and getting strange error at following task When I am running kolla-ansible -i multinode deploy TASK [include_role : glance] ***************************************************************************************************************************************************************** task path: /usr/local/share/kolla-ansible/ansible/site.yml:168 redirecting (type: modules) ansible.builtin.firewalld to ansible.posix.firewalld TASK [haproxy-config : Copying over glance haproxy config] *********************************************************************************************************************************** task path: /usr/local/share/kolla-ansible/ansible/roles/haproxy-config/tasks/main.yml:2 The full traceback is: Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/ansible/plugins/action/template.py", line 152, in run resultant = templar.do_template(template_data, preserve_trailing_newlines=True, escape_backslashes=False, overrides=overrides) File "/usr/local/lib/python3.10/dist-packages/ansible/template/__init__.py", line 1010, in do_template res = myenv.concat(rf) File "/usr/local/lib/python3.10/dist-packages/ansible/template/native_helpers.py", line 83, in ansible_concat return ''.join([to_text(v) for v in nodes]) File "/usr/local/lib/python3.10/dist-packages/ansible/template/native_helpers.py", line 83, in <listcomp> return ''.join([to_text(v) for v in nodes]) File "<template>", line 436, in root File "/usr/local/lib/python3.10/dist-packages/ansible/template/__init__.py", line 381, in call return super().call(obj, *args, **kwargs) File "/usr/local/lib/python3.10/dist-packages/jinja2/runtime.py", line 303, in call return __obj(*args, **kwargs) File "/usr/local/lib/python3.10/dist-packages/jinja2/runtime.py", line 768, in __call__ return self._invoke(arguments, autoescape) File "/usr/local/lib/python3.10/dist-packages/jinja2/runtime.py", line 782, in _invoke rv = self._func(*arguments) File "<template>", line 193, in macro File "/usr/local/lib/python3.10/dist-packages/ansible/template/__init__.py", line 295, in wrapper ret = func(*args, **kwargs) File "/usr/local/lib/python3.10/dist-packages/jinja2/filters.py", line 1030, in do_format return soft_str(value) % (kwargs or args) File "/usr/local/lib/python3.10/dist-packages/markupsafe/__init__.py", line 165, in __mod__ return self.__class__(super().__mod__(value)) File "/usr/local/lib/python3.10/dist-packages/markupsafe/__init__.py", line 370, in __str__ return str(self.escape(self.obj)) File "/usr/local/lib/python3.10/dist-packages/markupsafe/__init__.py", line 235, in escape rv = escape(s) File "/usr/local/lib/python3.10/dist-packages/markupsafe/__init__.py", line 45, in escape return Markup(_escape_inner(str(s))) SystemError: <built-in function _escape_inner> returned NULL without setting an exception failed: [os2-bos-ctrl01] (item={'key': 'glance-api', 'value': {'container_name': 'glance_api', 'group': 'glance-api', 'host_in_groups': True, 'enabled': True, 'image': ' registry.example.com/kolla/glance-api:2024.1-ubuntu-jammy', 'environment': {'http_proxy': '', 'https_proxy': '', 'no_proxy': 'localhost,127.0.0.1,10.0.52.11,10.0.52.10'}, 'privileged': False, 'volumes': ['/etc/kolla/glance-api/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'glance:/var/lib/glance/', '', 'kolla_logs:/var/log/kolla/', '', ''], 'dimensions': {}, 'healthcheck': {'interval': '30', 'retries': '3', 'start_period': '5', 'test': ['CMD-SHELL', 'healthcheck_curl http://10.0.52.11:9292'], 'timeout': '30'}, 'haproxy': {'glance_api': {'enabled': True, 'mode': 'http', 'external': False, 'port': '9292', 'frontend_http_extra': ['timeout client 6h'], 'backend_http_extra': ['timeout server 6h'], 'custom_member_list': ['server os2-bos-ctrl01 10.0.52.11:9292 check inter 2000 rise 2 fall 5', '']}, 'glance_api_external': {'enabled': True, 'mode': 'http', 'external': True, 'external_fqdn': 'openstack-bos-2.example.com', 'port': '9292', 'frontend_http_extra': ['timeout client 6h'], 'backend_http_extra': ['timeout server 6h'], 'custom_member_list': ['server os2-bos-ctrl01 10.0.52.11:9292 check inter 2000 rise 2 fall 5', '']}}}}) => { "ansible_loop_var": "item", "changed": false, "item": { "key": "glance-api", "value": { "container_name": "glance_api", "dimensions": {}, "enabled": true, "environment": { "http_proxy": "", "https_proxy": "", "no_proxy": "localhost,127.0.0.1,10.0.52.11,10.0.52.10" }, "group": "glance-api", "haproxy": { "glance_api": { "backend_http_extra": [ "timeout server 6h" ], "custom_member_list": [ "server os2-bos-ctrl01 10.0.52.11:9292 check inter 2000 rise 2 fall 5", "" ], "enabled": true, "external": false, "frontend_http_extra": [ "timeout client 6h" ], "mode": "http", "port": "9292" }, "glance_api_external": { "backend_http_extra": [ "timeout server 6h" ], "custom_member_list": [ "server os2-bos-ctrl01 10.0.52.11:9292 check inter 2000 rise 2 fall 5", "" ], "enabled": true, "external": true, "external_fqdn": "openstack-bos-2.example.com", "frontend_http_extra": [ "timeout client 6h" ], "mode": "http", "port": "9292" } }, "healthcheck": { "interval": "30", "retries": "3", "start_period": "5", "test": [ "CMD-SHELL", "healthcheck_curl http://10.0.52.11:9292" ], "timeout": "30" }, "host_in_groups": true, "image": " registry.example.com/kolla/glance-api:2024.1-ubuntu-jammy", "privileged": false, "volumes": [ "/etc/kolla/glance-api/:/var/lib/kolla/config_files/:ro", "/etc/localtime:/etc/localtime:ro", "/etc/timezone:/etc/timezone:ro", "glance:/var/lib/glance/", "", "kolla_logs:/var/log/kolla/", "", "" ] } }, "msg": "SystemError: <built-in function _escape_inner> returned NULL without setting an exception" }

1 1

[zaqar]Proposing Takashi Kajinami as Zaqar core member
by hao wang 22 Oct '24

22 Oct '24

Hello, everyone, I would like to propose Takashi Kajinami for the OpenStack Zaqar core member. Takashi has contributed to the Zaqar project since 2021 and has done a great job of improving this project. It is very important to Zaqar to keep it stable and reliable. I am so excited that we can have such a great contributor and I believe we can do more valuable work to the Zaqar project. Thank you for your contributions. Regards, Hao Wang -- Best Wishes For You!

1 0

[nova][ptg] Nova sessions on Wednesday
by Sylvain Bauza 22 Oct '24

22 Oct '24

Hi, Given most of the nova cores will attend the eventlet-removal session at 1300UTC, we'll defer the nova sessions to start at 1400UTC instead of 1300UTC. Please stay online in #openstack-nova IRC channel or please take a look at https://ptg.opendev.org/ptg.html to see the exact time when we spawn again the nova conversations. Thanks, -Sylvain (who just unbooked the austin room for Wed-B1)

1 0

[Horizon] Cancelling weekly meeting tomorrow
by Tatiana Ovchinnikova 22 Oct '24

22 Oct '24

Hello team, Since we have vPTG sessions, I'm cancelling our weekly meeting tomorrow. With kind regards, Tatiana

1 0

[dev][cinder] Bubbling up maintenance status on a volume from a third-party backend
by David Pineau 22 Oct '24

22 Oct '24

Hello Openstack and Cinder team, I'm currently working on the storage management layer of our company's Openstack platform. As we manage the storage ourselves, we may run background operations, which are akin to a maintenance, on individual volumes, or part of the infrastructure. As a bit of context, this infrastructure will be both exposed to external customers, as well as internal departments, and as such, we are looking for a refined user experience where an error is not a simple "an error occurred in service X", but something potentially actionable by whoever encounters it. At the moment in the Cinder documentation (and what I could find on the discuss archive), there seems to be no way for a Cinder Driver and its backing services to: - Tell Cinder that a specific Volume is undergoing a backend maintenance and should be considered unavailable - raise a relevant error to Cinder about ongoing Operations affecting a Volume within its backend, that cinder could properly react to As a first step, I wanted to check if you, the community, had ever considered this issue (or at least we consider it to be one). We'd be very happy if you had recipes or pieces of advice to share with us on how to handle this. If nothing is available or known, how could we help in bringing such an improvement to Cinder ? Kind regards, -- David Pineau (joa)

3 5