- openstack-discuss - lists.openstack.org

[kolla] where to find docker compose files
by garcetto 16 Jan '23

16 Jan '23

good afternoon, where can i find docker compose files for quay,io docker images used in kolla-ansible? need to undestand how are build, thank you.

2 1

Cinder LVM backend shows 100% space usage
by A Monster 16 Jan '23

16 Jan '23

I deployed openstack using kolla ansible using LVM as a backend, but after using it for a while, I ended up creating multiple volume with different sizes, but now I can no longer create new volumes, after checking lvs I found out that the thin pool created by cinder displays a 100% space usage of 20TB , but the size used by the volumes created is less than 1TB. how can I fix this isse?

1 0

Re: [Heat][OpenStack-I18n] Need help in making sense of a message in Heat
by Ian Y. Choi 16 Jan '23

16 Jan '23

(Adding openstack-discuss mailing list and adding "[Heat]" on the subject) Hi, It would be so great if OpenStack Heat users or developers can help Juliette's question on i18n thread! Thank you all, /Ian On Fri, Jan 13, 2023 at 11:39 PM Juliette Tux <juliette.tux(a)gmail.com> wrote: > > Hello, > Could anybody kindly elaborate on the meaning of a condition in a message: > > "The flag which represents condition of reserved resources of the > lease. If it is true, the amount of reserved resources is less than > the request or reserved resources were changed." > > The obscure part for me is "less than the request or reserved > resources were changed." > > Context: heat/engine/resources/openstack/blazar/lease.py:233 > > TY! > > -- > С уважением, Дронова Юлия > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org

3 2

[neutron] Bug Deputy Report January 9 - 15
by Lucas Alvares Gomes 16 Jan '23

16 Jan '23

Hi, This is the Neutron bug report from January 9th to 15th. *Critical:* * https://bugs.launchpad.net/neutron/+bug/2002800 - "Allow multiple IPv6 ports on router from same network on ml2/ovs+vxlan+dvr" - Assigned to: Fernando Royo *High:* * https://bugs.launchpad.net/neutron/+bug/2002417 - "DVR+HA routers all answering to ping on private interface" - Assigned to: Arnaud Morin *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2002577 - "The neutron-keepalived-state-change.log log is not rotated and grows without bound until disk is full" - Unassigned *Low:* * https://bugs.launchpad.net/neutron/+bug/2002839 - "Remove compatibility with OVN<20.09" - Unassigned *RFE / Wishlist:* * https://bugs.launchpad.net/neutron/+bug/2002687 - "[RFE] Active-active L3 Gateway with Multihoming" - Assigned to: Dmitrii Shcherbakov Cheers, Lucas

1 0

[skyline][i18n] Questions on more language translation support
by Ian Y. Choi 15 Jan '23

15 Jan '23

Hi Skyline team and I18n contributors, First, Skyline team, thank you for considering skyline with i18n! As Seongsoo started to talk via skyline IRC channel [1], I see that there are some needs for more language support for the Skyline project. Let me elaborate through the following questions as current I18n SIG lead: 1. Skyline team: While I believe you are welcome to contribute to other languages by adding per-language json files like [2], is it okay to contribute Korean language through Korea User Group members? Me and/or Seongsoo would like to happily step up as reviewers to guarantee sufficient language quality. 2. Any translation interests from other I18n language teams? Feel free to tell me or reply to this thread. 3. While number 1 would be a short-term approach to add Korean language support, to support more international languages, I want to suggest integrating with react-intl if skyline is using react (from my brief investigation, it is yes through [3]), since react-intl support to convert json <-> pot which functionality was previously used by tripleo-ui for i18n support [4]. Although I18n SIG is trying to migrate from Zanata to Weblate, a new translation platform [5], pot support would be essential for standardizing i18n and the translation process. With many thanks, /Ian [1] https://meetings.opendev.org/irclogs/%23openstack-skyline/%23openstack-skyl… [2] https://github.com/openstack/skyline-console/tree/master/src/locales [3] https://opendev.org/openstack/skyline-console/src/branch/master/package.jso… [4] https://opendev.org/openstack/tripleo-ui/src/commit/d1baef537f0746efceacfdd… [5] https://lists.openstack.org/pipermail/openstack-i18n/2022-October/003559.ht…

2 1

[kolla] [cinder] cinder.exception.NoValidBackend
by A Monster 15 Jan '23

15 Jan '23

I deployed openstack yoga using kolla ansible, and used LVM as a backend for cinder storage service, after the deployment everything was working fine, but after a month, I could no longer create a volume as I get an error message > schedule allocate volume:Could not find any available weighted backend. > and the cinder_scheduler log shows the following error message > ERROR cinder.scheduler.flows.create_volume > [req-2290223d-8f96-48d7-8680-959c5932d5be 3b4bd66ca3b04ab587a9a64a9e6966bc > ec29bdcd73064dfb8186f413537327eb - - -] Failed to run task > cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: > No valid backend was found. No weighed backends available: > cinder.exception.NoValidBackend: No valid backend was found. No weighed > backends available > the storage server doesn't show any apparent errors, any ideas of how can I fix this?

2 1

[Openstack Tacker] - Issue while creating NS
by Lokendra Rathour 15 Jan '23

15 Jan '23

Hi Team, Was trying to create NS using the document : https://docs.openstack.org/tacker/yoga/user/nsd_usage_guide.html But getting an error, the bug has been opened, requesting your kind assistance. https://bugs.launchpad.net/tacker/+bug/1999502 thanks once again. -- ~ Lokendra skype: lokendrarathour

2 1

Destroy a specific service from an openstack kolla deployment
by A Monster 15 Jan '23

15 Jan '23

Is it possible to remove a specific service from openstack, using > > kolla-ansible destroy -i multinode --tag service destroys all service and doesn't take into consideration the tag parameter.

1 0

Minimum Number Of Nodes for Deployment
by Nazmul Haque (N&C, SIL) 14 Jan '23

14 Jan '23

Hi, We are exploring various open source cloud platform. We are currently running Nutanix for our private cloud infrastructure. We would like to explore Openstack. Currently we have two clusters , one with 5 nodes and another with 3 nodes. In order to deploy two Openstack clusters what is the minimum number of nodes required for a private cloud infrastructure ensuring high availability and data integrity in mind. I will pursue the COA course however I want to have some background from industry experts since I am under the impression that Openstack deployment would require a lot of nodes for initial deployment which would be very expensive. Regards, Md Nazmul Haque Disclaimer: This e-mail, including any attachment with it may contain privileged, proprietary & confidential information and is intended solely for the addressee. If you are not the intended recipient of this e-mail, please notify us immediately and destroy this email without taking any copies or showing it to anyone. Unauthorized use of this e-mail is prohibited. SQUARE will not take any responsibility for misdirection, corruption or unauthorized use of e-mail communications, or for any damage that may be caused as a result of transmitting or receiving an e-mail communication. Caution: Do not click links or open attachments unless you recognize the sender and know the content is safe.

1 0

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

13 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 11. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html * The next TC weekly meeting will be on Jan 18 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 17. 2. What we completed this week: ========================= * Nothing specific for this week. 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[2]. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The horizon team discussed the 'xstatic-font-awesome' repo PyPi maintainer topic[4] in the weekly meetings[5], As the next step, they will be discussing it with PyPi non-OpenStack maintainers for the possible option to do the maintenance in a single place (either in OpenStack or outside of OpenStack). TC continued the discussion for all other repo/developers' PyPi maintainer cleanup. knikolla will be automating to get the list of deliverables that need PyPi maintainer's cleanup and after that TC will reach out to the respective project PTL to do the audit if we can cleanup those directly or need some more discussion with external maintainers (like 'xstatic-font-awesome' case) if there is any. We will continue this topic discussion in TC next weekly meeting also. Project updates ------------------- * Add Cinder Huawei charm[6] * Add the woodpecker charm to Openstack charms[7] Less Active/Inactive projects: ~~~~~~~~~~~~~~~~~~~~~~ * Zaqar status Zaqar gate is broken due to the MongoDB package not being present in Ubuntu 22.04 which is used for testing in 2023.1 cycle. Zaqar's team knows about the issue and discusses the same[8]. The TC is discussing and reaching out to the PTL about it. The release team is waiting to get a clear situation on the activeness/gate fix of this project so that they can decide on its release for 2023.1 cycle. It is also proposed to be marked as Inactive[9]. TC will continue the discussion with the Zaqar team and take the next action soon. * Mistral status: The Mistral team is actively merging the gate fixes[10], python-mistralclient gate is facing more issue which is being looked at by the Mistral team. The release team is trying the beta release patches for mistral deliverables[11][12] * Adjutant Status The Adjutant gate is green and its beta release is done[13][14]. With that, Dale proposed to remove this project from the Inactive project list[15] which has a positive response from the TC review. Thanks, Dale to make this project active again. 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://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://github.com/openstack/xstatic-font-awesome/pull/2 [5] https://meetings.opendev.org/meetings/horizon/2023/horizon.2023-01-11-15.00… [6] https://review.opendev.org/c/openstack/governance/+/867588 [7] https://review.opendev.org/c/openstack/governance/+/869752 [8] https://review.opendev.org/c/openstack/zaqar/+/857924/comments/a0d5d45e_300… [9] https://review.opendev.org/c/openstack/governance/+/870098 [10] https://review.opendev.org/q/project:openstack/mistral [11] https://review.opendev.org/c/openstack/releases/+/869470 [12] https://review.opendev.org/c/openstack/releases/+/869448 [13] https://review.opendev.org/c/openstack/releases/+/869449 [14] https://review.opendev.org/c/openstack/releases/+/869471 [15] https://review.opendev.org/c/openstack/governance/+/869665 [16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 13 Jan '23

13 Jan '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[horizon]
by Nguyễn Hữu Khôi 12 Jan '23

12 Jan '23

Hello guys. I use Openstack Xena which deployed by Kolla Ansible.My problem is when I launch instance from Horizon, Port selection won't show as below pictures: [image: image.png] [image: image.png] I try to change browser but this problem still persists Any suggestions for me? Thank you. Regards. Nguyen Huu Khoi

2 2

RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml | Openstack wallaby | tripleo | centos 8 stream
by Swogat Pradhan 12 Jan '23

12 Jan '23

Hi, INFO: Openstack wallaby on centos 8 stream I am trying to deploy a DCN and during the ceph deploy command i am getting the following error: (undercloud) [stack@hkg2director dcn01]$ openstack overcloud ceph deploy dcn01_overcloud-baremetal-deployed.yaml --stack dcn01 --config initial-ceph.conf --output deployed_ceph.yaml --container-image-prepare containers-prepare-parameter.yaml --network-data custom_network_data.yaml --cluster dcn01 --roles-data dcn01_roles.yaml -vvv The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 241, in get_deployed_roles_to_hosts UnboundLocalError: local variable 'matching_hosts' referenced before assignment During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 102, in <module> File "<stdin>", line 94, in _ansiballz_main File "<stdin>", line 40, in invoke_module File "/usr/lib64/python3.6/runpy.py", line 205, in run_module return _run_module_code(code, init_globals, run_name, mod_spec) File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code mod_name, mod_spec, pkg_name, script_name) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 500, in <module> File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 471, in main File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 246, in get_deployed_roles_to_hosts RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml 2023-01-13 01:27:15.811878 | 48d539a1-1679-ea57-d54d-000000000013 | FATAL | Create Ceph spec based on baremetal_deployed_path and tripleo_roles | undercloud | error={ "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 241, in get_deployed_roles_to_hosts\nUnboundLocalError: local variable 'matching_hosts' referenced before assignment\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 500, in <module>\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 471, in main\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 246, in get_deployed_roles_to_hosts\nRuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1 } (undercloud) [stack@hkg2director dcn01]$ cat /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml parameter_defaults: DeployedServerPortMap: dcn01-hci-0-ctlplane: fixed_ips: - ip_address: 172.25.221.96 dcn01-hci-1-ctlplane: fixed_ips: - ip_address: 172.25.221.90 dcn01-hci-2-ctlplane: fixed_ips: - ip_address: 172.25.221.106 HCICount: 3 HCIHostnameFormat: '%stackname%-hci-%index%' HostnameMap: dcn01-hci-0: dcn01-hci-0 dcn01-hci-1: dcn01-hci-1 dcn01-hci-2: dcn01-hci-2 NodePortMap: dcn01-hci-0: ctlplane: ip_address: 172.25.221.96 ...> Can someone please tell me what could be the issue here?? Am I missing something? With regards, Swogat Pradhan

1 1

[ironic] Bugfix branches being EOL'd first week of Jan, 2023
by Jay Faulkner 12 Jan '23

12 Jan '23

OpenStack Community and Operators, As documented in https://specs.openstack.org/openstack/ironic-specs/specs/approved/new-relea…, Ironic performs bugfix releases in the middle of a cycle to permit downstream packagers to more rapidly deliver features to standalone Ironic users. However, we've neglected as a project to cleanup or EOL any of these branches -- until now. Please take notice that during the first week in January, we will be EOL-ing all old, unsupported Ironic bugfix branches. This will be handled similarly to an EOL of a stable branch; we will create a tag -- e.g. for bugfix/x.y branch, we would tag bugfix-x.y-eol -- then remove the branch. These branches have been out of support for months and should not be in use in your Ironic clusters. If you are using any branches slated for retirement, please immediately upgrade to a supported Ironic version. A full listing of projects and branches impacted: ironic branches being retired bugfix/15.1 bugfix/15.2 bugfix/16.1 bugfix/16.2 bugfix/18.0 bugfix/20.0 ironic-python-agent branches being retired bugfix/6.2 bugfix/6.3 bugfix/6.5 bugfix/6.6 bugfix/8.0 bugfix/8.4 ironic-inspector branches being retired bugfix/10.2 bugfix/10.3 bugfix/10.5 bugfix/10.10 Thank you, Jay Faulkner Ironic PTL

1 4

[ironic] Moving Aija to core-emeritus
by Jay Faulkner 12 Jan '23

12 Jan '23

Hi all, As many of you may already know, Aija is no longer actively working on OpenStack. She informed many Ironic cores over email of this last week. I asked her if she expected to contribute on her own time and she said no. In order to ensure we keep core reviewer lists up to date, I suggest we move Aija to core-emeritus status, removing core permissions from gerrit. If she decides to begin working on OpenStack again in the future, we'd obviously quickly return core permissions. What do you think? -- Jay Faulkner Ironic PTL TC Member P.S. A huge thanks to Aija for her hard work on the sushy project and the Dell driver in Ironic.

6 6

Overriding tox's install_command won't work for non-service projects
by Stephen Finucane 12 Jan '23

12 Jan '23

Another tox 4 PSA. It turns out the tox 3 was not using the command in '[tox] install_command' when installing the package under test. tox 4 does, which means overriding '[tox] install_command' to include a constraints file (-c) will prevent you installing any requirement that is listed in the upper-constraints file, even if said requirement is the thing you're currently working on. This applies to all libraries (e.g. oslo.db, python-cinderclient) but not the services (cinder, nova) since those aren't included in upper-constraints. The "correct" way to respect upper-constraints is to provide them in 'deps' alongside the requirements file(s), e.g. [testenv] deps = -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt This will cause tox to install all of the package's dependencies first *with* constraints before installing the package itself *without constraints*. There is a bug report open against pip to change this behaviour [1], but it's been sat there for over two years with no activity so I wouldn't rely on this. Stephen [1] https://github.com/pypa/pip/issues/7839

2 3

Issue resizing volumes attached to running volume backed instances
by Jérôme BECOT 12 Jan '23

12 Jan '23

Hello Openstack, We have Ussuri deployed on a few clouds, and they're all plugged to PureStorage Arrays. We allow users to only use volumes for their servers. It means that each server disk is a LUN attached over ISCSI (with multipath) on the compute node hosting the server. Everything works quite fine, but we have a weird issue when extending volumes attached to running instances. The guests notice the new disk size .. of the last extent. Say I have a server with a 10gb disk. I add 5gb. On the guest, still 10gb. I add another 5gb, and on the guest I get 15, and so on. I've turned the debug mode on and I could see no error in the log. Looking closer at the log I could catch the culprit: 2022-12-08 17:35:13.998 46195 DEBUG os_brick.initiator.linuxscsi [] Starting size: *76235669504* 2022-12-08 17:35:14.028 46195 DEBUG os_brick.initiator.linuxscsi [] volume size after scsi device rescan *80530636800* extend_volume 2022-12-08 17:35:14.035 46195 DEBUG os_brick.initiator.linuxscsi [] Volume device info = {'device': '/dev/disk/by-path/ip-1...1:3260-iscsi-iqn.2010-06.com.purestorage:flasharray.x-lun-10', 'host': '5', 'channel': '0', 'id': '0', 'lun': '10'} extend_volume 2022-12-08 17:35:14.348 46195 INFO os_brick.initiator.linuxscsi [] Find Multipath device file for volume WWN 3624... 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] Checking to see if /dev/disk/by-id/dm-uuid-mpath-3624.. exists yet. wait_for_path 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] /dev/disk/by-id/dm-uuid-mpath-3624... has shown up. wait_for_path 2022-12-08 17:35:14.382 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *current size 76235669504* 2022-12-08 17:35:14.412 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *new size 76235669504* 2022-12-08 17:35:14.413 46195 DEBUG oslo_concurrency.lockutils [] Lock "extend_volume" released by "os_brick.initiator.connectors.iscsi.ISCSIConnector.extend_volume" :: held 2.062s inner 2022-12-08 17:35:14.459 46195 DEBUG os_brick.initiator.connectors.iscsi [] <== extend_volume: return (2217ms) *76235669504* trace_logging_wrapper 2022-12-08 17:35:14.461 46195 DEBUG nova.virt.libvirt.volume.iscsi [] Extend iSCSI Volume /dev/dm-28; new_size=*76235669504* extend_volume 2022-12-08 17:35:14.462 46195 DEBUG nova.virt.libvirt.driver [] Resizing target device /dev/dm-28 to *76235669504* _resize_attached_volume The logs clearly shows that the rescan confirm the new size but when interrogating multipath, it does not. But requesting multipath few seconds after on the command line shows the new size as well. It explains the behaviour. I'm running Ubuntu 18.04 with multipath 0.7.4-2ubuntu3.2. The os-brick code for multipath is far more basic than the one in master branch. Maybe the multipath version installed is too recent for os-brick. Thanks for the help Jerome

2 2

[CI][Tempest] Broken tempest-full-multinode-py3 job
by Lukas Piwowarski 12 Jan '23

12 Jan '23

Hi, I've got stuck trying to figure out why one of our tempest jobs is failing. I will be grateful for any kind of input regarding potential solutions. I did a little investigation of the failing job (tempest-multinode-full-py3 [1][2]) and this is what I found: - The failure is mostly caused by scenario tests. There was one occurrence of failure outside of the scenario tests ( test_create_servers_on_different_hosts_with_list_of_servers) - The failure is always connected to the creation of a VM. The reasons for the failure differ but most of the time it looks like the VM gets created but tempest is not able to access it ("Authentication (publickey) failed.") or the created instance can not be found ("Instance f4e582fe-52e6-40e3-b366-2b11ed589089 could not be found.") - The failure is not connected to one specific test. I am wondering why only the multinode job is failing as in other jobs the scenario tests are passing fine. Thanks for any kind of help Lukáš Piwowarsk [1] https://ca077a96786c794b51b6-8aab0ff599dd9fcfda722d0dee6871dd.ssl.cf5.rackc… [2] https://review.opendev.org/c/openstack/tempest/+/866692

1 0

[openstack][nova][kvm] numa
by Ignazio Cassano 11 Jan '23

11 Jan '23

Hello All, I would like to know if with numa in kvm hypervisor I must disable merge across nodes ? If yes, is there any metadata to do it ? Ignazio

2 2

[largescale-sig] Next meeting: Jan 11, 15utc
by Thierry Carrez 11 Jan '23

11 Jan '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230111T15 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[neutron] PTG flavour: virtual or in person
by Rodolfo Alonso Hernandez 11 Jan '23

11 Jan '23

Hello Neutrinos: I'm reaching you today to ask you about the PTG. Please first read [1] to have a bit of context. Due to the requests from the contributors to bring back the in person events, there will be a PTG along with the OpenInfra Summit in Vancouver. The virtual PTGs will remain and the first one will be in March. My main questions here are: 1) What do you prefer: virtual or in-person? 2) For this year, will you attend the virtual PTG only? Or will you attend the Vancouver one too? In the second question I'm implying that the virtual ones are "mandatory". At least this year those events will be needed to define the roadmap of the next releases, same as the previous virtual PTGs we had (please don't forget to order your ticket [2]). Regards. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645… [2]https://openinfra-ptg.eventbrite.com

4 3

[cinder] Bug Report from 01-11-2023
by Sofia Enriquez 11 Jan '23

11 Jan '23

This is a bug report from 01-04-2022 to 01-11-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/2001619 "svf : if pool attribute is specified in volume type during retype along with --migration-policy defaults to cinder generic migration." Assigned to Sathyanarayana R. 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

[all][tc] Technical Committee next weekly meeting on 2023 Jan 11 at 1600 UTC
by Ghanshyam Mann 10 Jan '23

10 Jan '23

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

1 1

[openstack-helm] Stability of Openstack Helm for large Ironic (baremetal) clouds with Openstack Yoga
by Farhad Sunavala 10 Jan '23

10 Jan '23

Hi, We're currently running Openstack services on baremetal.Time to upgrade has come and it is a nightmare.We are evaluating containerizing the services with Openstack Helm. Our cloud:We are essentially a large Openstack Ironic (Baremetal) cloud with 5000-8000 baremetal nodes in different DCs.We are thinking of upgrading from Queens to Yoga. Any feedback on stability of Openstack Helm for such installations? Any pointers on what to expect, gotchas, etc. Thanks,Fred..

2 1

nova api error
by Parsa Aminian 10 Jan '23

10 Jan '23

hello On nova api I have this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete and I have Unknown Error (HTTP 504) error on every nova request .

1 0

The OpenInfra Summit CFP is closing soon!
by Helena Spease 10 Jan '23

10 Jan '23

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is closing in just a few days[1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT. See what that is in your timezone [3] We are also now accepting submissions for Forum sessions [4]! Looking for other resources? Find information on registration, sponsorships, travel support and visa requests at https://openinfra.dev/summit/ <https://openinfra.dev/summit/vancouver-2023> If you have any questions feel free to reach out :) Cheers, Helena [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentations> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su… <https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Su…> [4] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/>

3 4

Different between of the role of Nova-Conductor and Nova-Compute
by Huy Võ Lê 10 Jan '23

10 Jan '23

Hi, I have a question about Nova role - Assert: I don't understand about OPS/Redhat explaination. Because all of information said nova-conductor will help database-accessing for nova-compute, every chart/image showed, too. - Reallity: When I download OPS Nova source code looked into nova/compute/manager.py, I saw the many many block code that queries the data from the database (instance list) and updates the data (instance.save). So the assertion of the Openstack and Redhat development community is wrong or true???? Link 1: https://docs.openstack.org/nova/pike/install/get-started-compute.html Link 2: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/… Link n: ....

4 5

[neutron] Bug deputy 2-8 January
by Rodolfo Alonso Hernandez 10 Jan '23

10 Jan '23

Hello Neutrinos: This is the (short) bug list of the last week: * https://bugs.launchpad.net/neutron/+bug/2002316: "ha router - vxlan - incorrect ovs flow ?" Unassigned. Regards.

1 0

Accessing databases of one openstack component from another
by vincent lee 10 Jan '23

10 Jan '23

Hi all, I have a working OpenStack in the yoga version and am trying to customize the zun component. In terms of deployment, I am using Kolla-ansible to deploy the OpenStack. I am trying to access blazar databases from the zun container. However, I have no clue of how the actual flow goes. I hope to receive some directions or suggestions to get me started. Best, Vincent

2 1

[tc] Fwd: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Feb 8, 2023 2pm - 3pm (CST)
by Jeremy Stanley 09 Jan '23

09 Jan '23

Just a reminder that a couple of months ago we arranged a February meeting time between the OpenStack community and the OpenInfra Board of Directors, Wednesday 2023-02-08 at 20:00 UTC. Julia has graciously supplied a conference call connection for the hour (calendar invite attached). I've also added the connection info to the pad we've been using for planning this call: https://etherpad.opendev.org/p/2023-02-board-openstack-sync -- Jeremy Stanley ----- Forwarded message from Julia Kreger ----- Date: Wed, 16 Nov 2022 21:31:42 +0000 Subject: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Feb 8, 2023 2pm - 3pm (CST) (jeremy(a)openinfra.dev) OpenInfra Board sync with OpenStack TC Wednesday Feb 8, 2023 ⋅ 2pm – 3pm Central Time - Chicago Location https://us02web.zoom.us/j/87498907965?pwd=T0h3dDAwVHk1dTBqcVpxa202YmRPUT09 Greetings Directors & All, Meeting invite per informal discussion call on November 16th, for the next informal discussion. Note: This is being sent in advance of the new board being seated. We'll obviously need to update this invite once elections have completed. -Julia ────────── Julia Kreger is inviting you to a scheduled Zoom meeting. Join Zoom Meeting: https://us02web.zoom.us/j/87498907965?pwd=T0h3dDAwVHk1dTBqcVpxa202YmRPUT09 Meeting ID: 874 9890 7965 Passcode: 035164 ----- End forwarded message -----

1 0

[cinder] Unit test failures under Python 3.11 - mocks can no longer be provided as the specs for other Mocks
by Sofia Enriquez 09 Jan '23

09 Jan '23

Hi, Since python3.11 mocks can no longer be provided as the specs for other Mocks. As a result, an already-mocked object cannot be passed to mock.Mock(). This can uncover bugs in tests since these Mock-derived Mocks will always pass certain tests (e.g. isinstance) and built-in assert functions (e.g. assert_called_once_with) will unconditionally pass.[1] There's a bug report to track this issue in Cinder [2] but I think this may affect other projects too. I've reproduce the error and most drivers fail with: ``` unittest.mock.InvalidSpecError: Cannot spec a Mock object. [object=<Mock name='mock.client.HPE3ParClient' id='139657768087760'>] ``` Cheers, Sofia [1] https://github.com/python/cpython/issues/87644 [2] https://bugs.launchpad.net/cinder/+bug/2000436 -- 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>

4 3

[Kolla] Transition Ussuri/Victoria to EOL
by Bartosz Bezak 09 Jan '23

09 Jan '23

Hello, As aggreed on IRC meeting, Kolla Ussuri and Victoria deliverables (Kolla, Kolla-Ansible, Kayobe) are going EOL. [1] Wallaby remains in extended maintenance. Xena, Yoga and Zed are our current stable releases. Ussuri and Victoria branches were in Extended Maintenance for a some time, Kolla community does not have resources to support those branches actively. Moreover Ussuri and Victoria were the last releases that support CentOS 8 which is also EOL. All changes to those branches have been abandoned. [1] https://review.opendev.org/c/openstack/releases/+/869569 Best regards, Bartosz Bezak

1 0

[Nova][Horizon]
by Nguyễn Hữu Khôi 09 Jan '23

09 Jan '23

Hello guys. Is there any way to assign AZ to a specified project? After searching, I cannot find any answer. Example. Sale project will only see Sale AZ to select. Tech project will only see Tech AZ to select Thank you. Regards Nguyen Huu Khoi

3 7

[all][gate][stable] Pinning tox<4 in stable branch testing
by Ghanshyam Mann 09 Jan '23

09 Jan '23

Hello Everyone, As you might know, tox4 broke almost all the projects tox.ini and so do master as well as stable branches gate. On the master, we need to fix it as we should use tox4 in testing. To fix the stable branches gate, either we need to backport all the fixes which include some more issues fixes[1] or we can pin the tox<4. We discussed it in today's TC meeting and it is better to keep testing the stable branch with the tox version that they were released with and not with the tox4. Even in future, there might be the cases where latest tox might introduce more incompatible changes. By considering all these factors, it is better to pin tox<4 for stable branches (<=stable/zed) testing. I have prepared the patch to pin it in the common job/template, feel free to comment with your feedback/opinion: - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849/3 also, tested with nova/cinder stable branches: - https://review.opendev.org/q/I0ca55abf9975c5a3f9713ac5dd5be39083e04554 - https://review.opendev.org/q/I300e7804a27d08ecd239d1a7faaf2aaf3e07b9ee You can also test it in your project stable branches in case any different syntax in tox.ini causing the tox upgrade to the latest. [1] https://github.com/tox-dev/tox/issues/2712 -gmann

4 7

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 09 Jan '23

09 Jan '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we continue working on planning for the OpenInfra Summit as well as Foundation-wide surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0

[blazar] Next IRC meeting cancelled
by Pierre Riteau 09 Jan '23

09 Jan '23

Hello, I am unable to run the IRC meeting on Thursday January 12. I propose to cancel it. Best wishes, Pierre Riteau (priteau)

1 0

[ci][all]tox.tox_env.python.api.NoInterpreter - gate is blocked
by Balazs Gibizer 09 Jan '23

09 Jan '23

Hi, It seems that all the tox based jobs are blocked right now on master with the following error: tox.tox_env.python.api.NoInterpreter: could not find python interpreter matching any of the specs It is due to a recent bugfix in tox that uncovered another bug[1]. There is a fix proposed in tox [2]. [1]<https://github.com/tox-dev/tox/issues/2811> [2]<https://github.com/tox-dev/tox/pull/2828>

3 2

[openstack-ansible] git clone fatal: the remote end hung up unexpectedly
by Satish Patel 08 Jan '23

08 Jan '23

Folks, Trying to deploy an openstack-ansible Zed release but noticed strange behavior with git clone. failed: [localhost] (item={'name': 'galera_server', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-galera_server', 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-12-12'}) => {"ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": ["/usr/bin/git", "fetch", "--depth", "20", "--force", "origin", "+refs/heads/master:refs/remotes/origin/master"], "item": {"name": "galera_server", "scm": "git", "shallow_since": "2022-12-12", "src": "https://opendev.org/openstack/openstack-ansible-galera_server", "trackbranch": "master", "version": "master"}, "msg": "Failed to download remote objects and refs: fatal: error in object: unshallow e04aeacc58c196c4fb3d49116cb93fa74f7fba31\nfatal: the remote end hung up unexpectedly\n"} Full logs: https://paste.opendev.org/show/bUjuekKPzknE5IC8zbPa/

2 2

Re: add a new service to a pre-deployed openstack private cloud
by Oliver Weinmann 08 Jan '23

08 Jan '23

You don’t need to make any changes to your inventory files. Just keep using your initial inventory and you will be fine. > On 8. Jan 2023, at 09:19, A Monster <amonster369(a)gmail.com> wrote: > > Thank you for your quick response, > do I need to change the hosts in my inventory files and keep only the nodes on which these new services will be deployed on, or is it done automatically through the roles defined ? > > On Sun, 8 Jan 2023 at 09:15, Oliver Weinmann <oliver.weinmann(a)me.com <mailto:oliver.weinmann@me.com>> wrote: >> Hi, >> >> Sure. It is doable. Just make your changes to globals.yml, add the required config files and run e.g. for MAGNUM: >> >> kolla-ansible -i <inventory> deploy --tags common,horizon,magnum >> Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation >> docs.openstack.org >> >> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…>Magnum - Container cluster service — kolla-ansible 15.1.0.dev19 documentation <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> docs.openstack.org <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> <https://docs.openstack.org/kolla-ansible/latest/reference/containers/magnum…> >> >> In that case deploy will not re-deploy your cluster, but pull in the needed containers for magnum and configure it. >> >>> On 8. Jan 2023, at 08:48, A Monster <amonster369(a)gmail.com <mailto:amonster369@gmail.com>> wrote: >>> >>> I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, >>> is this doable ? as I couldn't find anything in the kolla-ansible docs. >>

1 0

add a new service to a pre-deployed openstack private cloud
by A Monster 08 Jan '23

08 Jan '23

I've done an openstack deployment using kolla ansible, and after deploying I want to add new services but without having to redo the deployment from scratch in order to keep both the configuration and the data already in use, is this doable ? as I couldn't find anything in the kolla-ansible docs.

2 1

Accessing databases of one OpenStack component from another
by vincent lee 07 Jan '23

07 Jan '23

Hi all, I have a working OpenStack in the yoga version and am trying to customize the zun component. In terms of deployment, I am using Kolla-ansible to deploy the OpenStack. I am trying to access blazar databases from the zun container. However, I have no clue of how the actual flow goes. I hope to receive some directions or suggestions to get me started. Best, Vincent

1 0

[openstack][cinder] Assign each storage backend to each AZ
by Nguyễn Hữu Khôi 07 Jan '23

07 Jan '23

Hello guys. I took time to search for this question but I can't find the answer. I have an Openstack private cloud and I use an AZ to a department. For example, AZ-IT for IT department AZ-Sale for Sale department... I will prepare 2 storage backends for each AZ. My goal is that when users launch an instance by choosing AZ then It will use only the backend for this AZ. Would Openstack support my goal? Thanks for reading my email. Nguyen Huu Khoi

4 9

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

06 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 04. Most of the meeting discussions are summarized in this email. Meeting recordings are available @ https://www.youtube.com/watch?v=4vR7iStJZe0 and summary logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-04-16.00.log.html * The next TC weekly meeting will be on Jan 11 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 10. 2. What we completed this week: ========================= * Nothing specific for this week. 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[2]. Open Reviews ----------------- * Two open reviews for ongoing activities[3]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- Clarkb reported this last week and we had an initial discussion in the TC meeting. xstatic-font-awesome repo which is under the Horizon project has non-OpenStack core as maintainers in PyPI and recently a new maintainer is added[4] without going through or knowing by the OpenStack Horizon PTL. While checking other deliverables, I found there are other maintainers present in many of the deliverables. A few examples are https://pypi.org/project/murano/ https://pypi.org/project/glance/ To avoid two sets of maintainers for OpenStack deliverables (one OpenStack and one external), we should clean this up. 'openstackci' is maintainers on the PyPI side which can be kept for all the OpenStack deliverables. If any external maintainers want to maintain it external to OpenStack and OpenStack project is ok for that then we can discuss that option also. For example, xstatic-* repo can be a good example to handover to the external maintainer if the Horizon team agrees. We will discuss it in the next TC meeting also. Meanwhile, I will reach out to the Horizon team and find more about the xstatic-* repos. IMPORTANT: Tox 4 failure ------------------------------- As you might have seen the gate failure due to tox4 (even the latest release too), we discussed in TC meeting[5] and after testing[6] we pinned tox<4 for the stable branch. Pinning is done in the common job in openstack-zuul-jobs repo [7]. But there are some cases where this global pinning is not enough and the latest tox is installed by pip. For example, Brian reported one case[8]. In that case, you can explicitly pin tox in the tox.ini file otherwise global pinning should work fine. For the master, we need to fix the failure. Hoping we do not get more new failures on every new tox release (for example, the missing interpreter issue which is fixed by stephenfin today). Mistral release and more maintainers ------------------------------------------- Mistral gate is green and things are merging there[9] so I feel it is ready for release. But I have sent an email reply on ML[10] to know more about it from the Mistral team. Adjutant release and more maintainers ---------------------------------------------- Adjutant is in the Inactive project list. But I have seen Dale (PTL) has fixed the gate and merged the things[11]. I will ping Dale about the release status and accordingly we can decide on its status change if needed. Project updates ------------------- * Add Cinder Huawei charm[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://github.com/openstack/xstatic-font-awesome/pull/2 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031668… [6] https://review.opendev.org/q/topic:tox4-pin-testing [7] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/867849/4 [8] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031678… [9] https://review.opendev.org/q/project:openstack/mistral [10] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031687… [11] https://review.opendev.org/q/project:openstack/adjutant [12] https://review.opendev.org/c/openstack/governance/+/867588 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][mistral][release] Propose to deprecate Mistral
by Elõd Illés 06 Jan '23

06 Jan '23

Hi, Mistral projects are unfortunately not actively maintained and caused hard times in latest official series releases for release management team. Thus we discussed this and decided to propose to deprecate Mistral [1] to avoid broken releases and last minute debugging of gate issues (which usually fall to release management team), and remove mistral projects from 2023.1 Antelope release [2]. We would like to ask @TC to evaluate the situation and review our patches (deprecation [1] + removal from the official release [2]). Thanks in advance, Előd Illés irc: elodilles @ #openstack-release [1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://review.opendev.org/c/openstack/releases/+/865577

6 7

[release] Release countdown for week R-10, Jan 9 - 13
by Thierry Carrez 06 Jan '23

06 Jan '23

Development Focus ----------------- We are now past the antelope-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 9). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 16) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 16. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 2) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 16) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 9 (R-6 week) Client library freeze: February 16 (R-5 week) antelope-3 milestone: February 16 (R-5 week) Final 2023.1 Antelope release: March 22nd, 2023 -- Thierry Carrez (ttx)

1 0

[kolla] Propose Bartosz Bezak for core reviewer
by Michał Nasiadka 06 Jan '23

06 Jan '23

Hello Koalas, I’d like to propose Bartosz Bezak as a core reviewer for Kolla, Kolla-Ansible, Kayobe and ansible-collection-kolla. Bartosz has recently went through release preparations and release process itself for all mentioned repositories, has been a great deal of help in meeting the cycle trailing projects deadline. In addition to that, he’s been the main author of Ubuntu Jammy and EL9 (Rocky Linux 9 to be precise) support in Kayobe for Zed release, as well as fixing various bugs amongst all four repositories. Bartosz also brings OVN knowledge, which will make the review process for those patches better (and improve our overall review velocity, which hasn’t been great recently). Kind regards, Michal Nasiadka

6 6

Nova libvirt/kvm sound device
by Zakhar Kirpichenko 06 Jan '23

06 Jan '23

Hi! I'd like to have the following configuration added to every guest on a specific host managed by Nova and libvirt/kvm: <sound model='bla'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </sound> When I add the device manually to instance xml, it works as intended but the instance configuration gets overwritten on instance stop/start or hard reboot via Nova. What is the currently supported / proper way to add a virtual sound device without having to modify libvirt or Nova code? I would appreciate any advice. Best regards, Zakhar

2 2

[designate] Implemeting PTR record restrictions
by Thomas Goirand 05 Jan '23

05 Jan '23

Hi, We implemented this scenario for our public cloud: https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.htm… This is currently in production in beta-mode at Infomaniak's public cloud. We did that, because we want our customers to be able to set any domain name or PTR for the IPs they own. However, we discovered that there's no restriction on what zone customers can set. For example, if customer A owns the IP 203.0.113.9, customer B can do "openstack zone create 9.113.0.203.in-addr.arpa.", preventing customer A to set their PTR record. Is there currently a way to fix this? Or maybe a spec to implement the correct restrictions? What is the way to fix this problem in a public cloud env? Cheers, Thomas Goirand (zigo)

2 1

[designate] New project: designate-tlds
by Thomas Goirand 05 Jan '23

05 Jan '23

Hi, We wrote this: https://salsa.debian.org/openstack-team/services/designate-tlds The interesting code bits are in: https://salsa.debian.org/openstack-team/services/designate-tlds/-/blob/debi… What it does is download the TLD list from https://publicsuffix.org/list/public_suffix_list.dat using requests (with an optional proxy), compare it to the list of TLDs in Designate, and fix the difference. It's by default setup in a cron every week. Basically, it's just apt-get install designate-tlds, configure keystone_authtoken in /etc/designate-tlds/designate-tlds.conf and set dry_run=false, and you're done! Note I also wrote a patch for puppet-designate [1] to support it. Moving forward I see 2 solutions: 1- we continue to maintain this separately from Designate 2- our code gets integrated into Designate itself. Designate team: are you interested for option 2? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/puppet/puppet-module-designate/-/bl…

2 1

[nova][neutron][openstacksdk] Any API way to tell the difference for openstack ports created manually or automatically?
by hai wu 05 Jan '23

05 Jan '23

I could not find any API way to tell the difference between openstack ports created automatically when a new instance got created, and openstack ports manually created for port reservation purposes. There's 'preserve_on_delete' attribute in the openstack database for each vm instance, and if it is set to 'true', then the port was manually created, if not, then it was automatically created. But there's no API to retrieve this. Am I missing something? Hai

3 4