January 2022 - openstack-discuss - lists.openstack.org

Can neutron-fwaas project be revived?
by Dazhong Qin (秦海中)-云数据中心集团 17 Jan '22

17 Jan '22

Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

4 10

[neutron] Bug Deputy Report January 10 - 107
by Jakub Libosvar 17 Jan '22

17 Jan '22

Hi, I was bug deputy last week, there are no bugs that require immediate attention. Here is the week summary Critical -------- - [tempest ] neutron-tempest-plugin-dynamic jobs are failing - https://bugs.launchpad.net/neutron/+bug/1957453 - Unassigned - As per Lajos it's fixed in os-ken - https://review.opendev.org/q/58a39392397cd01e174c4736fa31a9a5617f1ff0 High ---- - Functional tests for HA routers fails due to router transitioned to FAULT state - https://bugs.launchpad.net/neutron/+bug/1956958 - Assigned to Slawek - [FT] Test "test_port_dhcp_options" failing - https://bugs.launchpad.net/neutron/+bug/1956965 - Unassigned - Regular user can remove qos from a port despite the policy - https://bugs.launchpad.net/neutron/+bug/1957175 - Assigned to Yatin - OVS: except MappingNotFound instead of KeyError - https://bugs.launchpad.net/neutron/+bug/1957931 - Unassigned - Patch: https://review.opendev.org/c/openstack/neutron/+/824727 - test_network_basic_ops failing on centos-8-stream job - https://bugs.launchpad.net/neutron/+bug/1957941 - Unassigned - fixed in packaging but needs repo update Medium ------ - Wrong ACTIVE status of subports attached to a trunk whose parent is DOWN - https://bugs.launchpad.net/neutron/+bug/1957161 - patch: https://review.opendev.org/c/openstack/neutron/+/824378 - Assigned to Luis - NAT reflection with OVN on xena not working - https://bugs.launchpad.net/neutron/+bug/1957185 - Unassigned - DVR Router Update Error - https://bugs.launchpad.net/neutron/+bug/1957189 - Unassigned - qrouter ns leak while last service port delete because of router gw port - https://bugs.launchpad.net/neutron/+bug/1957794 - Assigned to Krzysztof - Patch: https://review.opendev.org/c/openstack/neutron/+/824008 - ha backup router ipv6 accept_ra broken - https://bugs.launchpad.net/neutron/+bug/1958149 - Unassigned Low --- - Neutron l3 agent keeps restarting (Ubuntu) - https://bugs.launchpad.net/neutron/+bug/1958128 - Unassigned - Related to fwaas and docs Needs more info --------------- - Incorrect openstack xena neutron install repo in documentation - https://bugs.launchpad.net/neutron/+bug/1956847 - Unassigned - Requires input from the reporter

1 0

[magnum] New meeting Wednesday Jan 19 09:00 AM UTC 2022 #openstack-containers
by Spyros Trigazis 17 Jan '22

17 Jan '22

Hello all, Let's restart the magnum team weekly meetings. The next meeting will happen on Wed Jan 19 09:00: AM UTC 2022 https://www.timeanddate.com/worldclock/converter.html?iso=20220119T090000&p… We can keep track of the meeting agenda in: https://etherpad.opendev.org/p/magnum-weekly-meeting Cheers, Spyros

1 0

[kolla-ansible] Gather facts strange error
by Satish Patel 17 Jan '22

17 Jan '22

Folks, I have a working cluster but today when I ran the following command I got very nasty error like the following. Even 192.168.75.144 is function node but giving super log error output that i can't copy paste here. $ sudo kolla-ansible -i /etc/kolla/multinode deploy -t nova-cell --limit 192.168.75.144 ... .... ....... PLAY [Gather facts for all hosts] ******************************************************************************************************************************************************************** TASK [Gather facts] ********************************************************************************************************************************************************************************** ok: [192.168.75.144] TASK [Group hosts to determine when using --limit] *************************************************************************************************************************************************** ok: [192.168.75.144] PLAY [Gather facts for all hosts (if using --limit)] ************************************************************************************************************************************************* TASK [Gather facts] ********************************************************************************************************************************************************************************** skipping: [192.168.75.144] => (item=192.168.75.144) ok: [192.168.75.144 -> 192.168.75.145] => (item=192.168.75.145) ok: [192.168.75.144 -> 192.168.75.146] => (item=192.168.75.146) failed: [192.168.75.144 -> 192.168.75.178] (item=192.168.75.178) => {"ansible_loop_var": "item", "item": "192.168.75.178", "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.75.178 port 22: No route to host", "unreachable": true} ok: [192.168.75.144 -> 192.168.75.179] => (item=192.168.75.179) failed: [192.168.75.144 -> 192.168.75.180] (item=192.168.75.180) => {"ansible_loop_var": "item", "item": "192.168.75.180", "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.75.180 port 22: No route to host", "unreachable": true} ok: [192.168.75.144 -> 192.168.75.181] => (item=192.168.75.181) ok: [192.168.75.144 -> 192.168.75.147] => (item=192.168.75.147) ok: [192.168.75.144 -> localhost] => (item=localhost) fatal: [192.168.75.144 -> {{ item }}]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"ansible_loop_var": "item", "changed": false, "item": "192.168.75.144", "skip_reason": "Conditional result was False", "skipped": true}, {"ansible_facts": {"ansible_all_ipv4_addresses": ["192.168.75.145"], "ansible_all_ipv6_addresses": ["fe80::3eec:efff:fe1f:1776", "fe80::f802:e3ff:fe71:e58c"], "ansible_apparmor": {"status": "disabled"}, "ansible_architecture": "x86_64", "ansible_bios_date": "02/27/2020", "ansible_bios_version": "3.3", "ansible_br_ex": {"active": false, "device": "br-ex", "features": {"esp_hw_offload": "off [fixed]", "esp_tx_csum_hw_offload": "off [fixed]", "fcoe_mtu": "off [fixed]", "generic_receive_offload": "on", "generic_segmentation_offload": "on", "highdma": "on", "hw_tc_offload": "off [fixed]", "l2_fwd_offload": "off [fixed]", "large_receive_offload": "off [fixed]", "loopback": "off [fixed]", "netns_local": "off [fixed]", "ntuple_filters": "off [fixed]", "receive_hashing": "off [fixed]", "rx_all": "off [fixed]", "rx_checksumming": "off [fixed]", "rx_fcs": "off [fixed]", "rx_gro_hw": "off [fixed]", "rx_gro_list": "off", "rx_udp_tunnel_port_offload": "off [fixed]", "rx_vlan_filter": "off [fixed]", "rx_vlan_offload": "off [fixed]", "rx_vlan_stag_filter": "off [fixed]", "rx_vlan_stag_hw_parse": "off [fixed]", "scatter_gather": "on", "tcp_segmentation_offload": "on", "tls_hw_record": "off [fixed]", "tls_hw_rx_offload": "off [fixed]", .... .... END PLAY RECAP ******************************************************************************************************************************************************************************************* 192.168.75.144 : ok=2 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0 Command failed ansible-playbook -i /etc/kolla/multinode -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla --tags nova-cell --limit 192.168.75.144 -e kolla_action=deploy /usr/local/share/kolla-ansible/ansible/site.yml

3 2

[TripleO] Gate blocker - tripleo-ci-centos-9-content-provider
by Ronelle Landy 16 Jan '22

16 Jan '22

Hello All, We have gate/check blocker which started late on Friday - and still seems to be hitting jobs in check and gate: 2022-01-16 02:53:58.796730 | primary | Error: 2022-01-16 02:53:58.796795 | primary | Problem: cannot install the best update candidate for package gcc-11.2.1-6.1.el9.x86_64 2022-01-16 02:53:58.796813 | primary | - nothing provides libgomp = 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 2022-01-16 02:53:58.796828 | primary | - nothing provides libgcc >= 11.2.1-7.4.el9 needed by gcc-11.2.1-7.4.el9.x86_64 2022-01-16 02:53:58.796904 | primary | (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) https://composes.stream.centos.org/production/latest-CentOS-Stream/compose/… does show libgomp-11.2.1-7.4.el9.x86_64.rpm <https://composes.stream.centos.org/production/latest-CentOS-Stream/compose/…> 2022-01-11 11:59 283K but http://mirror.iad3.inmotion.opendev.org/centos-stream/9-stream/BaseOS/x86_6… (for example) does not. It looks like the mirrors do not have this latest content. The failure is logged at: https://bugs.launchpad.net/tripleo/+bug/1957950. We will respond to this posting once the failure has been cleared. Thank you.

3 4

[ops][kolla][kolla-ansible][neutron] Xena upgrade connectivity issues
by Alexandros Soumplis 15 Jan '22

15 Jan '22

Hello all, I am doing an upgrade with kolla ansible from Wallaby to Xena, using source containers on ubuntu and openvswitch. After the upgrade, there is no connectivity from the VMs to the network (both provider networks and self-service) and also neutron services (dhcp, l3-agent, metadata) do not work. For the VMs I had no errors related, while for neutron services, probably due to lack of connectivity a continuous flapping of virtual routers and dhcp agents. I have downgraded neutron_openvswitch_agent, openvswitch_vswitchd and openvswitch_db to wallaby again and it everything works. I suspect there is something related to the flows created from the neutron agent but was not able to identify anything specific. Any help to debug this and identify the root cause is greatly appreciated. Thank you! a.

1 0

[all][tc] What's happening in Technical Committee: summary 14th Jan, 21: Reading: 5 min
by Ghanshyam Mann 14 Jan '22

14 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.log.html * Next week's meeting is on 20th Jan Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 19th Jan. 2. What we completed this week: ========================= * Added the cinder-solidfire charm to Openstack charms[2] * Added the cinder-nimblestorage charm to Openstack charms[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 6 open reviews for ongoing activities[5]. Z release cycle name ------------------------- Z release cycle naming process is started[6]. Nomination to collect the name are now open, feel free to propose it on wiki page[7]. TC vote on gender-neutral language change in bylaws 's TC section ------------------------------------------------------------------------------- In this week meeting, TC voted in favor of gender-neutral language change in bylaws 's TC section. They are officially approved and votes are recorded in meeting logs[8]. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[9]. SIG i18n status check -------------------------- Ian (SIG chair) is now back and fixed the IN translation issue also. So we are good here, but if you would like to help in i18n SIG, feel free to reachout to Ian. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[10] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[11]. No other updates from TC on this and we will set up a separate call to continue the discussion. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[12]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[13]. Project updates ------------------- * masakari Transfer PTL role to suzhengwei[14] * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [15] 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 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Welcome back from the holidays and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/823805 [3] https://review.opendev.org/c/openstack/governance/+/824585 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026620.… [7] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [8] https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.log.html#… [9] https://review.opendev.org/c/openstack/governance/+/822900 [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [14] https://review.opendev.org/c/openstack/governance/+/824509 [15] https://review.opendev.org/c/openstack/governance/+/798540 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all] Proposed Z cycle schedule
by Előd Illés 14 Jan '22

14 Jan '22

Hi, As we are beyond Yoga milestone 2 it's time to start planning the next, 'Z' cycle and its release schedule, so I've prepared a draft. (Since we don't have the name yet [1] I used the *codename* Zen in the patch, that will be updated whenever the official release name is announced) The patch: https://review.opendev.org/c/openstack/releases/+/824489 (Or see the current patch set's generated schedule page [2] for easier overview.) Feel free to review it and comment on the patch if there is something that should be considered for the schedule. Thanks in advance! [1] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [2] https://1b3db30de08d0b6cba67-15d40643a81384357fc5a6da097a7ab7.ssl.cf5.rackc… Előd Illés irc: elodilles

1 0

[security-sig] Log4j vulnerabilities and OpenStack
by Jeremy Stanley 13 Jan '22

13 Jan '22

Unless you were living under a rock during most of December, you've almost certainly seen the press surrounding the various security vulnerabilities discovered in the Apache Log4j Java library. As everyone reading this list hopefully knows, OpenStack is primarily written in Python, so has little use for Java libraries in the first place, but that hasn't stopped users from asking our VMT members if OpenStack is affected. While OpenStack doesn't require any Java components, I'm aware of one Neutron driver (networking-odl) which relies on an affected third-party service: https://access.redhat.com/solutions/6586821 Additionally, "storm" component of SUSE OpenStack seems to be impacted: https://www.suse.com/c/suse-statement-on-log4j-log4shell-cve-2021-44228-vul… As does an Elasticsearch component in Sovereign Cloud Stack: https://scs.community/security/2021/12/13/advisory-log4j/ Users should, obviously, rely on their distribution vendors/suppliers to notify them of available updates for these. Is anyone aware of other, similar situations where OpenStack is commonly installed alongside Java software using Log4j in vulnerable ways? -- Jeremy Stanley

4 17

[neutron] Drivers meeting agenda - 14.01.2022.
by Lajos Katona 13 Jan '22

13 Jan '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. The only topic for tomorrow: * Can neutron-fwaas project be revived? (mail thread: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026413… ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[openstack][stein][cinder] capacity filter is not working
by Ignazio Cassano 13 Jan '22

13 Jan '22

Hello, I am using openstack stein on centos 7 with netapp ontap driver. Seems capacity filter is not working and volumes are always creed on the first share where less space is available. My configuration is posted here: enabled_backends = nfsgold1, nfsgold2 [nfsgold1] nas_secure_file_operations = false nas_secure_file_permissions = false volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver netapp_storage_family = ontap_cluster netapp_storage_protocol = nfs netapp_vserver = svm-tstcinder2-cl1 netapp_server_hostname = faspod2.csi.it netapp_server_port = 80 netapp_login = apimanager netapp_password = password nfs_shares_config = /etc/cinder/nfsgold1_shares volume_backend_name = nfsgold #nfs_mount_options = lookupcache=pos nfs_mount_options = lookupcache=pos [nfsgold2] nas_secure_file_operations = false nas_secure_file_permissions = false volume_driver = cinder.volume.drivers.netapp.common.NetAppDriver netapp_storage_family = ontap_cluster netapp_storage_protocol = nfs netapp_vserver = svm-tstcinder2-cl2 netapp_server_hostname = faspod2.csi.it netapp_server_port = 80 netapp_login = apimanager netapp_password = password nfs_shares_config = /etc/cinder/nfsgold2_shares volume_backend_name = nfsgold #nfs_mount_options = lookupcache=pos nfs_mount_options = lookupcache=pos Volumes are created always on nfsgold1 also if has less space available of nfsgold2 share Thanks Ignazio

2 7

[swift] EC2 Credentials Returns 403 when Signature v4 Used
by tolga＠etom.com.tr 13 Jan '22

13 Jan '22

2 1

[Triple0]
by Lokendra Rathour 13 Jan '22

13 Jan '22

Hi Team, I was trying to deploy Triple0 Train using containers. After around 30+ min of overcloud running it gett below error: The error was: "keystoneauth1.exceptions.http.Unauthorized: The password is expired and needs to be changed for user: 765d7c43b3d54b289c9fa9e1dae15112. (HTTP 401) (Request-ID: req-f1344091-4f81-44c2-8ec6-e2daffbf998c) 2022-01-09 23:10:39.354147 | 525400bb-6dc5-c157-232d-000000003de1 | FATAL | As" I tried checking the Horizon, where is see that it is asking me to change the password immediately with the same message and a similar observation is seen with overcloud file. Please advice why this deployment is getting failed -- ~ Lokendra

3 4

[masakari] Transferring PTL role to suzhengwei
by Radosław Piliszek 13 Jan '22

13 Jan '22

Dears, Due to a shift in my priorities and being unable to dedicate enough time, I am transferring the Masakari PTL role to suzhengwei. The governance patch is already proposed. [1] suzhengwei has been lately the main contributor to the Masakari project, working on the major features that were introduced in the last few cycles. I have already obtained his approval by mail. Do note his contributions so far were using a different mail address (sugar-2008(a)163.com) but I have been asked to use the Inspur one (CC'ed) as it is currently preferred. [1] https://review.opendev.org/c/openstack/governance/+/824509 -yoctozepto

1 0

[nova] iothread support with Libvirt
by Eric K. Miller 13 Jan '22

13 Jan '22

Hi, I haven't found anything that indicates Nova supports adding iothreads parameters to the Libvirt XML file. I had asked various performance related questions a couple years back, including asking if iothreads were available, but I didn't get any response (so assumed the answer was no). So I'm just checking again to see if this has been a consideration to help improve a VM's storage performance - specifically with extremely high-speed storage in the host. Or is there a way to add iothread-related parameters without Nova being involved (such as modifying a template)? Thanks! Eric

4 13

Monitoring in Openstack Dashboard
by Karera Tony 13 Jan '22

13 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Monitoring in the Dashboard. Kindly advise If I could be missing something. Regards Regards Tony Karera

1 0

[all][tc] Technical Committee next weekly meeting on Jan 13th at 1500 UTC
by Ghanshyam Mann 12 Jan '22

12 Jan '22

Hello Everyone, Below is the agenda for Tomorrow's TC IRC meeting schedule at 1500 UTC. Amy will chair tomorrow's meeting. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting == Agenda for tomorrow's TC meeting == * Roll call * Follow up on past action items * TC vote on gender-neutral language bylaws change. ** https://lists.openinfra.dev/pipermail/foundation/2021-October/003016.html ** Need TC official approval for section Appendix 4, "OpenStack Technical Committee Member Policy". In the first paragraph it changes "his or her" to "their". * Gate health check ** Fixing Zuul config error in OpenStack *** https://etherpad.opendev.org/p/zuul-config-error-openstack * Progress checks on Yoga Tracker ** https://etherpad.opendev.org/p/tc-yoga-tracker ** Z Release Cycle Name ** It is needed for Release Management team to this week's task "Plan the next release cycle schedule" (elodilles) * SIG i18n status check ** Xena translation missing *** http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026244… ** Translation bug *** https://review.opendev.org/c/openstack/contributor-guide/+/821371 * Adjutant need PTLs and maintainers ** http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

Question about smartphone-based HPC system.
by Daehyun Lim 12 Jan '22

12 Jan '22

Dear, My name is Ray from South Korea. My company and I are very interested in Smartphone-based High Performance Computing system. Currently, my company is looking for research about how to build operating system (we called it 'Middleware system) that connects between each smartphone and the central system. We will running AP farm (easy to understand, imagine factory gathering huge amounts of smartphones - attached picture) and a network mining system that allows connecting only smartphones. Our current one of the issues is that how to build middleware system - allocate jobs to each smartphones, validate etc. And I'm curious how much realistic Flops from smartphones. While I was researching related information in Google, I saw Opnestack website. I'm curious that is possible Openstack can be implemented in the smartphone based HPC system. As you know, more than 100 million of phones are abandoned and unused every year. Therefore, I think if we can use these smartphones in new computing power, it will be great business in terms of save the resouces, low electricity and recycle. If you provide some advice about smartphone-based HPC system, I will grateful to you. Thank you. Best regards, Ray. [image: Mining.jpg] [image: photo_2020-01-29_14-38-17.jpg] [image: photo_2019-10-08_14-30-11.jpg] -- Telegram account : Raylim1217 Skype account : live:a43fdbe9bdd9a9c8 Zoom : 263-976-5455 Phone : +821092013947

2 1

[cinder] removing block-box code
by Brian Rosmaita 12 Jan '22

12 Jan '22

Hello Argonauts and other interested parties, As you may be aware, the cinder code repository contains files under contrib/block-box whose README file has included a note [0] since 20 January 2020 indicating that block-box is not supported. This note serves notice that we will be removing the code during the Yoga development cycle. I trust that this will be uncontroversial. If you have any objections, please raise them now, either here on the ML or on the patch removing the code: https://review.opendev.org/c/openstack/cinder/+/824472 cheers, brian [0] https://opendev.org/openstack/cinder/commit/a4d8f761639d63172814a593a32da41…

1 0

[tripleo]Making CentOS Stream 9 jobs voting and remove cs8 jobs
by Chandan Kumar 12 Jan '22

12 Jan '22

Hello, By the start of the year 2022, we have added CentOS Stream 9 tripleo non-voting jobs in the check pipeline. Now these jobs seem to be healthy. The TripleO CI team has put a lot of effort into adding these jobs. Now it's time to make them voting. Below is the status of each job: * content provider and Standalone Jobs https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-content-prov… * Standalone Sc1 to 4 https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario001-… * Standalone sc7, Sc10 and Sc12 https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario007-… * Multinode and undercloud jobs https://zuul.openstack.org/builds?job_name=ripleo-ci-centos-9-containers-mu… Here are the plans for moving forward with Master release: * Merge https://review.opendev.org/q/hashtag:%22c9voting%22+(status:open%20OR%20sta… patches to make the above jobs voting and gating. - It means tripleo patches might be seeing a lot of cs8 and cs9 jobs running on the patch and blocking it. * We will keep both cs8 and cs9 jobs running for 1 or 2 weeks. - Note: It might increase the load on infra. * After 2 weeks, we will start removing cs8 jobs from the check and gate jobs. * RDO third party c8 jobs will be still running against tripleo patches until CS9 OVB jobs are proven stable in check. Thank you and please reach out to us for any concerns or queries. With Regards, Chandan Kumar

1 0

[cinder] Bug deputy report for week of 01-12-2022
by Sofia Enriquez 12 Jan '22

12 Jan '22

This is a bug report from 01-05-2021 to 01-12-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1956887 "LVM backed ISCSI device not reporting the same size to nova." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1957073 "rbd: snapshot can't be deleted/unmanaged if its source volume is deleted from backend." Assigned to Takashi Kajinami. Incomplete - https://bugs.launchpad.net/cinder/+bug/1956601"Cinder doc is not reproducible." Unassigned. 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

[TripleO] Douglas Viroel for tripleo-ci core
by Marios Andreou 12 Jan '22

12 Jan '22

Hello TripleO ( & happy new year :) \o/ ) I'd like to propose Douglas Viroel [1] for core on the tripleo-ci repos (openstack/tripleo-ci, openstack/tripleo-quickstart-extras, openstack/tripleo-quickstart, openstack/tripleo-repos). Doug joined the team last year and besides his code contributions he has also been consistently providing many very useful and thoughtful code reviews. I think he will be an excellent addition to the ci core team. As is customary, let's leave this thread open for a week and if there are no objections or other concerns then we add Doug to the core group next week. thanks, marios [1] https://review.opendev.org/q/owner:viroel%2540gmail.com

11 15

[openstack-helm] No meeting tomorrow
by Gage Hugo 10 Jan '22

10 Jan '22

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is canceled. Our next meeting will be Jan 18th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[Deploy] Can three all-in-one nodes form a OpenStack cluster?
by 韩光宇 10 Jan '22

10 Jan '22

Dear all, I am deploing OpenStack Victoria. Can I make a cluster with three all-in-one nodes? Will this have any problems or points to be aware of? Sorry to bother, Thank you very much. Han Guangyu.

3 4

Monasca in kolla-ansible
by Karera Tony 10 Jan '22

10 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Logging in the Dashn=board. Kindly advise If I could be missing something. Regards Tony Karera

2 2

[nova][requirements] fasteners===0.16.3 held back by nova
by Matthew Thode 10 Jan '22

10 Jan '22

This one is simple, and iirc is blocked on upstream fixing something (but cannot find the reference). fasteners===0.16.3 https://review.opendev.org/823470 and https://review.opendev.org/804246 both test this change. -- Matthew Thode

4 4

[glance] Does glance not support using local filesystem storage in a cluster
by 韩光宇 10 Jan '22

10 Jan '22

Deal all, Sorry that maybe I ask a stupid question. But I'm really confused with it and didn't find discuss in glance document(https://docs.openstack.org/glance/latest/). I have a OpenStack Victoria cluster with three all-in-one node in centos8. I implemented it with reference to https://docs.openstack.org/ha-guide/. So this cluster use Pacemaker, HAproxy and Galera. "To implement high availability, run an instance of the database on each controller node and use Galera Cluster to provide replication between them." I found that I will encounter an error If I configure Glance backend to use local storage driver to store image files on the local disk. If I upload a image, this image only will be storaged in one node. But the database only storage the file path of image such as "/v2/images/aa3cbee0-717f-4699-8cca-61243302d693/file", don't have the host information. The database data is same in three node. If I upload a image in node1, image only is storaged in node1. The database of three node stores the local filesystem path of image. And If The create Instance task is assigned to node2, It will find image in node2, but image can't be found in node2. So we get the "Image has no associated data" error. So I want to ask: 1. Wheter glance does not support using local filesystem storage in a cluster? 2. If 1 was right, why do we do this design instead of storing information about the host on which images is located, as nova does with instance. I would appreciate any kind of guidance or help. Thank you, Han Guangyu

5 7

Huge Fake tap device creating on some Compute node || Open vSwitch
by Md. Hejbul Tawhid MUNNA 09 Jan '22

09 Jan '22

1 0

[kolla] Updating libvirt container images without VM downtime
by J-P Methot 09 Jan '22

09 Jan '22

Hi, I'm looking for validation regarding the way Kolla and containers work in regard to upgrading the libvirt containers. Essentially, when you upgrade the libvirt container to a new container image, the container needs to be restarted, thus creating downtime for the VMs. There is no way to avoid this downtime, unless you migrate the VMs to another node and then move them back once the container has restarted, right? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4

Logging (Monasca) not in Dashboard
by Karera Tony 08 Jan '22

08 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Logging in the Dashn=board. Kindly advise If I could be missing something. Regards Tony Karera

1 0

[release] Release countdown for week R-11, Jan 10-14
by Előd Illés 07 Jan '22

07 Jan '22

Development Focus ----------------- We are now past the Yoga-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 17th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 24th, 2022. 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 10th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases beforeMarch 25th, 2022 (Final RC deadline) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yogafinalrelease: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[TripleO] Overcloud deployment failing with Network Seggregation
by Anirudh Gupta 07 Jan '22

07 Jan '22

Hi Team, I am trying to deploy an Openstack Train using TripleO having 3 Controllers and 1 Compute. Without Network Isolation, I have deployed it successfully. Now, I am trying to segregate my network traffic using multiple-nics-vlan configuration generated via the below command /tools/process-templates.py -o ~/openstack-tripleo-heat-templates-rendered -n /home/stack/network_data.yaml -r /home/stack/templates/roles_data.yaml The command used for deploying the overcloud is openstack overcloud deploy --templates \ *-n /home/stack/templates/network_data.yaml \* -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ *...* *-e /home/stack/templates/environments/network-isolation.yaml \-e /home/stack/templates/environments/network-environment.yaml \* *...* It is failing just after the ovs bridge gets created and external nic vlan is attached to the bridge. [image: MicrosoftTeams-image (1).png] MAC Address of br-ex is same as the MAC of the interface specified in file network/config/multiple-nics-vlan/controller.yaml For testing, If I assign an IP address to that interface, it is reachable to GW. But, in case IP is assigned to VLAN 418 and it is added in the br-ex, Gateway remains unreachable. Please suggest

1 0

[neutron] Drivers meeting - Friday 7.1.2022 - cancelled
by Lajos Katona 06 Jan '22

06 Jan '22

Hi Neutron Drivers! Tomorrow we have not enough drivers to vote (see previous mail from mlavalle: [0]), so let's cancel tomorrow's meeting, and meet a week later: January 14th. [0]: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026549.… See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[all][Neutron][devstack] Deprecate lib/neutron
by Lajos Katona 06 Jan '22

06 Jan '22

Hi, In devstack we have two more or less overlapping lib for deploying Neutron: lib/neutron and lib/neutron-legacy. lib/neutron-legacy was recently "undeprecated" (see [0]), and Openstack CI mostly (fully?) uses it. To avoid double maintenance, and confusion in settings we would like to deprecate lib/neutron, for recent discussions see [1] and [2]. The plan is to keep lib/neutron for 2 cycles (that will be AA or the release after Z) and delete lib/neutron then, and rename lib/neutron-legacy to lib/neutron. As You can see from the discussions below there are questions like how to name the processes, log-files etc..., as lib/neutron-legacy uses q-* and lib/neutron uses neutron-* names. The best would be to keep both in the long term (we love q-* as historical tradition, but neutron-* looks like so fresh and modern;)) If you have any thoughts suggestions or questions please answer to this mail or comment on the deprecation patch: [3] [0]: https://review.opendev.org/c/openstack/devstack/+/704829 [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-01-04… [2]: https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2022-0… [3]: https://review.opendev.org/c/openstack/devstack/+/823653

1 0

[neutron] Dadfailed of ipv6 metadata IP in qdhcp namespace and disappearing dhcp namespaces
by Kamil Madáč 06 Jan '22

06 Jan '22

Hello, In our small cloud environment, we started to see weird behavior during last 2 months. Dhcp namespaces started to disappear randomly, which caused that VMs losed connectivity once dhcp lease expired. After the investigation I found out following issue/bug: 1. ipv6 metadata address of tap interface in some qdhcp-xxxx namespaces are stucked in "dadfailed tentative" state (i do not know why yet) 2. 3. root@cloud01:~# ip netns exec qdhcp-3094b264-829b-4381-9ca2-59b3a3fc1ea1 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2585: tap1797d9b1-e1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:77:64:0d brd ff:ff:ff:ff:ff:ff inet 169.254.169.254/32 brd 169.254.169.254 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet 192.168.0.2/24 brd 192.168.0.255 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet6 fe80::a9fe:a9fe/64 scope link dadfailed tentative valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe77:640d/64 scope link valid_lft forever preferred_lft forever 4. 5. This blocked dhcp agent to finish sync_state function, and NetworkCache was not updated with subnets of such neutron network 6. During creation of VM assigned to such network, agent does not detect any subnets (see point 2), so he thinks (reload_allocations()) there is no dhcp needed and deletes qdhcp-xxxx namespace, so no DHCP and no Metadata are working on such network since that moment, and after 24h we see connectivity issues. 7. Restart of DHCP agent recreates missing qdhcp-xxxx namespaces, but NetworkCache in dhcp agent is again empty, so creation of VM deletes the qdhcp-xxxx namespace again 🙁 Workaround is to remove dhcp agent from that network and add it again. Interestingly, sometimes I need to do it multiple times, because in few cases tap interface in new qdhcp finishes again in dadfailed tentative state. After year in production we have 20 networks out of 60 in such state. We are using kolla-ansible deployment on Ubuntu 20.04, kernel 5.4.0-65-generic. Openstack version Victoria and neutron is in version 17.2.2.dev70. Is that bug in neutron, or is it misconfiguration of OS on our side? I'm locally testing patch which disables ipv6 dad in qdhcp-xxxx namespace (net.ipv6.conf.default.accept_dad = 1), but I'm not sure it is good solution when it comes to other neutron features? Kamil Madáč Slovensko IT a.s.

3 3

[horizon] Bump XStatic-Angular-FileUpload to 12.2.13
by Thomas Goirand 06 Jan '22

06 Jan '22

Hi, After someone unrelated to OpenStack maintenance uploaded libjs-angular-file-upload 12.2.13, I tested it, and it didn't break Horizon (at least, when I manually uploaded a file, it worked...). So IMO, it would be fine to just bump to that version. Cheers, Thomas Goirand (zigo)

1 0

[keystone][requirements] keystone holding back pysaml2-7.1.x update
by Matthew Thode 05 Jan '22

05 Jan '22

Hi again, pysaml2===7.1.0 has been breaking updates for a while now. https://review.opendev.org/818612 -- Matthew Thode

1 0

[horizon][requirements] falling behind on requirements updates
by Matthew Thode 05 Jan '22

05 Jan '22

Hi, The following requirements updates have been stalled. XStatic-Angular===1.8.2.1 Has been held back for at least 7 months, but I think closer to a year now. Some review history is here: https://review.opendev.org/794258 django-compressor===2.4.1 rcssmin===1.1.0 rjsmin===1.1.0 These come as a group and have been holding things back for about a month. I'm not sure what's holding things back here on the horizon side. Review bundled with XStatic-Angular here: https://review.opendev.org/823449 -- Matthew Thode

1 0

[all][tc] Technical Committee next weekly meeting on Jan 6th at 1500 UTC
by Ghanshyam Mann 05 Jan '22

05 Jan '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Jan 6th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Jan 5th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[infra] Missing releases from opendev.org/opendev/git-review/tags
by Pete Zaitcev 05 Jan '22

05 Jan '22

Greetings: I noticed that the list of tags for git-review in the website does not include the 2.2.x tags, which exist in git: [zaitcev@niphredil git-review-0]$ grep url .git/config url = https://opendev.org/opendev/git-review.git [zaitcev@niphredil git-review-0]$ git tag -l --format='%(objectname) %(objecttype) %(refname)'| grep 2\\.2 bb81051c2481d4ac983ec0b28bd62b590d361141 tag refs/tags/2.2.0 [zaitcev@niphredil git-review-0]$ git show bb81051c2481d4ac983ec0b28bd62b590d361141 | head -5 tag 2.2.0 Tagger: Jeremy Stanley <fungi(a)yuggoth.org> Date: Wed Nov 24 02:20:05 2021 +0000 Release 2.2.0 [zaitcev@niphredil git-review-0]$ The 2.2.0 is missing from https://opendev.org/opendev/git-review/tags Coincidentally, it is also missing from https://tarballs.opendev.org/openstack/git-review/ Is this something that the infrastructure team did on purpose? Or is this just a bug to be reported? -- Pete

3 7

RE: [nova][dev] Revisiting qemu emulation where guest arch != host arch
by Race, Jonathan 05 Jan '22

05 Jan '22

That makes sense which is the best method I saw as well. For your example "use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated", I actually implemented a new field called hw_emulation_architecture as to not conflict with any existing nova operations and to eliminate confusion. This allows for setting this specific value as an image meta property in glance, and if it is set then it will execute emulation via qemu for the designated architecture. If it is not set then operations will occur as normal. https://review.opendev.org/c/openstack/nova/+/822053 is really just an initial response for the bug, that was submitted. And our long-term goal is to collab on this existing blueprint https://blueprints.launchpad.net/nova/+spec/pick-guest-arch-based-on-host-a… for a more full set of capabilities. Jonathan Race Cyber Range Engineer | Georgia Cyber Range GEORGIA CYBER CENTER On Wed, 2020-07-15 at 14:17 +0000, Apsey, Christopher wrote: > All, > > A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. > > I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? > yes, i cant really speak to how much use it would get or how useful it woudl be to the majoriy fo user but i would be supportive of adding this capablity. We have to be a little carful to get the design wright for example we might want to differnciate between the native architecture and emulated architectures e.g. use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated with the new "in" suppot being added to placment we can use required=in:HW_ARCH_X86,COMPUTE_ARCH_X86 in cases where you dont care and by default if you wanted native only you could use the HW_ARCH_* traits in the image and we can have a prefileter add the both triats by default if the architrue is set in the iamge and there is not arch trait in the flavor or image. i will certenly review a spec if you proporse one but you might now have time to get it approved this cycle the spec deadlien woudl have been thursday btu it has been moved to next week. > Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. > > Thoughts? > > [1] > http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653…<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.open…> > > Chris Apsey > Director | Georgia Cyber Range > GEORGIA CYBER CENTER > > 100 Grace Hopper Lane | Augusta, Georgia | 30901 > https://www.gacybercenter.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gacyb…> >

1 0

[largescale-sig] Next meeting: Jan 5th, 15utc
by Thierry Carrez 05 Jan '22

05 Jan '22

Hi everyone, and happy new year! To kick off 2022, the Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220105T15 We will be discussing our upcoming activities and our next OpenInfra Live episode, as well as any topic you may add to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

openstack-kolla with GlusterFS integration
by Satish Patel 05 Jan '22

05 Jan '22

Folks, Recently I have started playing with the Openstack Kolla Project because of some requirements. I want to integrate kolla with GlusterFS for nova vm backend storage. I have functional Glsuter storage and want to mount on compute node to use for vm backend but not sure how do i do that because i am new to containers I can see kolla use following to bind volume with nova_compute container { "Type": "volume", "Name": "nova_compute", "Source": "/var/lib/docker/volumes/nova_compute/_data", "Destination": "/var/lib/nova", "Driver": "local", "Mode": "rw", "RW": true, "Propagation": "" } If I can mount GlusterFS in /mnt directory then how do I tell docker to use /mnt to create volume for nova_compute?

2 6

Logical Volume migration to a New Openstack environment
by KK CHN 05 Jan '22

05 Jan '22

List, I am in need to migrate a Virtual machine ( running in an old OpenStack environment with only one controller). This VM has its own disk file + a logical volume attached to it with application data on it. Only Cinder backend( No rbd/ceph backend configured ) for this environment. Now I am migrating this Virtual machine to another OpenStack(ussuri with three controllers, three compute nodes and three storage nodes) environment with ceph/rbd backend. I am able to export the VM with its disk file and import it to the other openstack environment and able to boot the machine. But How to export the attached logical volume from the old VM and attach to the VM in the other environment ? what is the methodology to follow to export this logical volume in the old openstack VM and import to the new VM running in the other openstack environment ? kindly share your suggestions/expertise to perform this Thanks in advance for your valuable guidance. Krish

3 2

[cinder] Bug deputy report for week of 01-05-2022
by Sofia Enriquez 05 Jan '22

05 Jan '22

No meeting today. This is a bug report from 12-29-2021 to 01-05-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- No bugs in this period :P 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

[nova][placement] Spec approval freeze punted to Jan13st
by Sylvain Bauza 05 Jan '22

05 Jan '22

Hi folks, As agreed on yesterday's nova meeting [1], we accepted to punt the spec approval freeze for one week, ie. at January 13st. That said, we won't accept any exception for a spec approval after this day as we will only have 6 weeks after Jan 13st until FeatureFreeze. Thanks (and happy new 2022 by the way), -Sylvain [1] https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-04-16.00.log.h…

1 0

OpenInfra Live - January 6 at 9am CT
by Allison Price 04 Jan '22

04 Jan '22

Hi everyone, This week, I will be hosting the first OpenInfra Live <http://openinfra.live/> episode of 2022, brought to you by the OpenStack, Kata Containers, Zuul, and StarlingX communities! It's been one year since the formation of the OpenInfra Foundation and the global community has produced more software, more production use cases, more collaboration than ever before. Join us as we look back at 2021, the software milestones, production growth, and momentum across the OpenInfra landscape. Episode: A Year in Review: OpenInfra Highlights from 2021 Date and time: Thursday, January 6 at 9am CT (1500 UTC) You can watch us live on: YouTube <https://www.youtube.com/watch?v=MhAK2efrl9I> LinkedIn <https://www.linkedin.com/video/event/urn:li:ugcPost:6884201840976764928/> Facebook <https://www.facebook.com/104139126308032/posts/4704702346251664/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Ghanshyam Mann, OpenStack TC Chair Tao Peng, Kata Containers Architecture Committee Member James Blair, Zuul Maintainer Greg Waines, StarlingX Technical Steering Committee Member Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Have you heard that the OpenInfra Summit is going back to Berlin, June 7-9? Registration and sponsorship opportunities are now available here: https://openinfra.dev/summit/ <https://openinfra.dev/summit/>. Thanks, Allison

1 0

[charms] nominate Hemanth Nakkina for charms-core
by Edward Hope-Morley 04 Jan '22

04 Jan '22

I would like propose Hemanth Nakkina for charms-core. Hemanth has really stepped up his efforts to provide invaluable contributions both in code and reviews and I beleive he is in a good position to be considered for core where he will be able to provide additional value to the project. Hemanth has demonstrated rigour for quality through his contributions and is always keen to help others with his deep knowledge of the charms and Openstack. Here is a list of all his contributions: patches: https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonical.com I hope you will join me in voting for Hemanth. - Ed

6 5

Subject: [kolla] Updating libvirt container images without VM downtime
by CHALANSONNET Stéphane (Acoss) 04 Jan '22

04 Jan '22

Hello, When you update or restart libvirt container , the instances aren't restart . The qemu process /usr/libexec/qemu-kvm is executed outside the container. However for the lastest functionality you need to restart your instances later Regards, stephane.chalansonnet(a)acoss.fr -----Message d'origine----- De : openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Envoyé : mardi 4 janvier 2022 20:18 À : openstack-discuss(a)lists.openstack.org Objet : openstack-discuss Digest, Vol 39, Issue 11 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [charms] nominate Hemanth Nakkina for charms-core (Frode Nordahl) 2. Re: [TripleO] Douglas Viroel for tripleo-ci core (Jason Poulin) 3. Re: [TripleO] Douglas Viroel for tripleo-ci core (Ade Lee) 4. Re: [TripleO] Douglas Viroel for tripleo-ci core (Jeremy Stanley) 5. [kolla] Updating libvirt container images without VM downtime (J-P Methot) ---------------------------------------------------------------------- Message: 1 Date: Tue, 4 Jan 2022 17:33:34 +0100 From: Frode Nordahl <frode.nordahl(a)canonical.com> To: Billy Olsen <billy.olsen(a)canonical.com> Cc: Alex Kavanagh <alex.kavanagh(a)canonical.com>, openstack-discuss(a)lists.openstack.org Subject: Re: [charms] nominate Hemanth Nakkina for charms-core Message-ID: <CAKpbOATbKOH1116UUxAWjQoyRiE-9u8CiHjTcTashb6tcvQ1yg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Fri, Dec 10, 2021 at 6:12 PM Billy Olsen <billy.olsen(a)canonical.com> wrote: > > > > On Fri, Dec 10, 2021 at 7:08 AM Alex Kavanagh <alex.kavanagh(a)canonical.com> wrote: >> >> >> >> On Fri, Dec 10, 2021 at 1:24 PM Edward Hope-Morley <opentastic(a)gmail.com> wrote: >>> >>> I would like propose Hemanth Nakkina for charms-core. Hemanth has >>> really stepped up his efforts to provide invaluable contributions >>> both in code and reviews and I beleive he is in a good position to >>> be considered for core where he will be able to provide additional value to the project. >>> Hemanth has demonstrated rigour for quality through his >>> contributions and is always keen to help others with his deep >>> knowledge of the charms and Openstack. Here is a list of all his contributions: >>> >>> patches: >>> https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com >>> reviews: >>> https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonica >>> l.com >>> >>> I hope you will join me in voting for Hemanth. >> >> >> +1 from me; Hemanth has submitted good patches and thoughtful reviews in my experience. He would be a good member of charms-core. >> >> Cheers >> Alex. >> > > I concur with Alex here. +1 from me as well. I concur with Alex and Billy here. I would like to add that it has been a pleasure to work with Hemanth to resolve some really hard problems and I look forward to what he can bring to the team and project in the capacity of being a charms core. -- Frode Nordahl > - Billy > >>> >>> >>> - Ed >>> >>> >> >> >> -- >> Alex Kavanagh - Software Engineer >> OpenStack Engineering - Data Centre Development - Canonical Ltd ------------------------------ Message: 2 Date: Tue, 4 Jan 2022 12:00:53 -0500 From: Jason Poulin <corellianimports(a)aol.com> To: Ronelle Landy <rlandy(a)redhat.com> Cc: Amol Kahat <akahat(a)redhat.com>, Marios Andreou <marios(a)redhat.com>, openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: [TripleO] Douglas Viroel for tripleo-ci core Message-ID: <C5A32FC3-0DB1-4190-9A10-6D8288B95F88(a)aol.com> Content-Type: text/plain; charset="utf-8" Can someone take me off this list. I don?t know why I?m on it. Please. > On Jan 4, 2022, at 11:32 AM, Ronelle Landy <rlandy(a)redhat.com> wrote: > > ? > +1 absolutely > >> On Tue, Jan 4, 2022 at 11:25 AM Amol Kahat <akahat(a)redhat.com> wrote: >> +1 >> >>> On Tue, Jan 4, 2022 at 6:40 PM Marios Andreou <marios(a)redhat.com> wrote: >>> Hello TripleO ( & happy new year :) \o/ ) >>> >>> I'd like to propose Douglas Viroel [1] for core on the tripleo-ci >>> repos (openstack/tripleo-ci, openstack/tripleo-quickstart-extras, >>> openstack/tripleo-quickstart, openstack/tripleo-repos). >>> >>> Doug joined the team last year and besides his code contributions he >>> has also been consistently providing many very useful and thoughtful >>> code reviews. I think he will be an excellent addition to the ci >>> core team. >>> >>> As is customary, let's leave this thread open for a week and if >>> there are no objections or other concerns then we add Doug to the >>> core group next week. >>> >>> thanks, marios >>> >>> [1] https://review.opendev.org/q/owner:viroel%2540gmail.com >>> >>> >> >> >> -- >> Amol Kahat >> Software Engineer >> Red Hat India Pvt. Ltd. Pune, India. >> akahat(a)redhat.com >> B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

1 0

[neutron] Bug deputy December 27
by Rodolfo Alonso Hernandez 04 Jan '22

04 Jan '22

Hello: These are the bugs opened during the last week: https://bugs.launchpad.net/neutron/+bug/1956034: "ovn load balancer health monitor cause mac address conflict". Unassigned. https://bugs.launchpad.net/neutron/+bug/1956035: "ovn load balancer member failover not working when accessed from floating ip". Unassigned. https://bugs.launchpad.net/neutron/+bug/1955799: "Not changing floatingip status while deleting instance that had floatingip assocciate (Showing ACTIVE)". Patch: https://review.opendev.org/c/openstack/neutron/+/822091 Regards.

1 0

[neutron] CI meeting agenda - 4.01.2022
by Slawek Kaplonski 04 Jan '22

04 Jan '22

Hi, It's just reminder that we will today have Neutron CI meeting. It will be at 3pm UTC time. Meeting will be on the #openstack-neutron channel and on jiitsi: https://meetpad.opendev.org/neutron-ci-meetings Agenda is in the etherpad https://etherpad.opendev.org/p/neutron-ci-meetings See You there :) -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[nova] Getting away from cdrkit / genisoimage
by Thomas Goirand 04 Jan '22

04 Jan '22

Hi, Please see: https://bugs.debian.org/982241 It looks like cdrkit / genisoimage wont be available in the next Debian 12 (and therefore probably it will also be dropped in Ubuntu). As per the bug report: "I'm told xorriso and libburnia are alternatives and are alive and doing well." Would it be possible to switch to that? Cheers, Thomas Goirand (zigo)

2 1

cpu pinning
by open infra 04 Jan '22

04 Jan '22

3 7

[all][qa][triplo] Help need to maintain OpenStack health dashboard
by Ghanshyam Mann 04 Jan '22

04 Jan '22

Hello Everyone, In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that is the case, can we collaborate on maintaining the existing dashboard? OpenStack health dashboard: https://opendev.org/openstack/openstack-health Repo: http://status.openstack.org/openstack-health/#/ [1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#… -gmann

5 7

[tempest] Extending tempest for mixed-architecture stacks
by James LaBarre 03 Jan '22

03 Jan '22

Recently I had been running Tempest on my setup testing a mixed-architecture deployment (x86_64 ans ppc64le compute nodes at the same time). It seems that some of the migration and affinity tests will check if there's more than one Compute node before they run. However, it would seem that's as far as they check, without checking if they are in fact compatible or even of the same architecture. (my test cluster is very small, and normally includes two ppc64le Compute nodes, and sometimes one x86_64 Compute node. Currently one ppc64le machine is down for repair). Because the two compute nodes are different architectures, I am getting failures in various migration and affinity tests, maybe more if I tested a larger subset. Now granted my particular setup is a special case, but it does bring to mind some extensions that may be needed for Tempest in the future. I could see it being possible to have x86_64 and ARM mixed together in one stack, maybe even tossing in RISC-v someday. I'm thinking we need to start adding in extra test images, flavors, etc into the Tempest configurations (as in defining multiple options so that each architecture can have test images, etc assigned to it, rather than the current primary and alt image for just one architecture) Additionally, there should be testcases taking into account the architectures involved (such as seeing that an instance on one arch cannot be migrated to the other, as an example). I know this involves a bit of refactoring, I didn't know if it had even been considered yet. -- James LaBarre Software Engineer, OpenStack MultiArch Red Hat <https://www.redhat.com> jlabarre(a)redhat.com <mailto:jlabarre@redhat.com> <https://www.redhat.com>

3 2

[tc][all] Follow up pain point discussion
by Rico Lin 03 Jan '22

03 Jan '22

Dear all The pain point collection etherpad [1] seems to get good attention from teams. We plan to host a one-hour video meeting to keep the discussion going. Please fill in the doodle to select your preferred time if you can join us: https://doodle.com/poll/kur2mfywceerqcvh?utm_source=poll&utm_medium=link The discussion will be hosted in video format. Here are some items (but not limited to) I expect we will discuss and hopefully put some actions/efforts on. - General Pain point: RabbitMQ - General Pain point: OpenStackClient support - General project pain point discussion: How to encourage teams to work/reply on pain points. Meanwhile, we encourage all to check the etherpad and provide your feedback. Also if teams can help to answer questions/concerns on etherpad (like Nova team does) will be greatly appreciated. [1] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin*

7 11

[octavia] Management Network Issue
by Ammad Syed 03 Jan '22

03 Jan '22

Hi, I am using octavia 9.0. I have created a neutron vlan based management network of octavia. I am creating a loadbalancer with a subnet in the tenant network, its getting created successfully. Then added a listener and created a pool, both created successfully. Now a weird situation is happening. Now when I add a member in the pool, the management network interface get detached automatically from the AMPHORA instance and amphora keeps in PENDING_UPDATE state. I have created a dedicated service-project for octavia and management network and subnet resides there. Any advise how to fix it ? Ammad

2 2

[Diversity] D&I WG Meeting Cancellation and Poll Reminder
by Amy Marrich 02 Jan '22

02 Jan '22

Just a reminder that tomorrow's meeting is canceled and to participate in the Meeting Time and IRC vs Video Poll! https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link Thanks, Amy (spotz)

1 0