December 2022 - openstack-discuss

Need assistance
by Gk Gk 06 Dec '22

06 Dec '22

Hi, We have a SR-IOV guest whose xml looks like shown below: ------ <interface type='hostdev' managed='yes'> <mac address='fa:16:3e:3d:72:18'/> <driver name='vfio'/> <source> <address type='pci' domain='0x0000' bus='0x01' slot='0x12' function='0x7'/> </source> <vlan> <tag id='2'/> </vlan> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface> ---- How to find the network statistics for the virtual function assigned to the VM above from the ethtool -S output shown below: --- ethtool -S eno12409 NIC statistics: rx_unicast: 2890507 tx_unicast: 1279755 rx_multicast: 101903131 tx_multicast: 363832 rx_broadcast: 1496406 tx_broadcast: 1052 rx_bytes: 10084560360 tx_bytes: 225469520 rx_dropped: 0 rx_unknown_protocol: 0 rx_alloc_fail: 0 rx_pg_alloc_fail: 0 tx_errors: 0 tx_linearize: 0 tx_busy: 0 tx_restart: 0 tx_queue_0_packets: 120328 tx_queue_0_bytes: 15218021 tx_queue_1_packets: 185835 tx_queue_1_bytes: 33463904 tx_queue_2_packets: 255145 tx_queue_2_bytes: 62401952 tx_queue_3_packets: 73719 tx_queue_3_bytes: 9766278 tx_queue_4_packets: 75719 tx_queue_4_bytes: 13886665 tx_queue_5_packets: 756632 tx_queue_5_bytes: 64787766 tx_queue_6_packets: 127836 tx_queue_6_bytes: 13422778 tx_queue_7_packets: 49417 tx_queue_7_bytes: 7596442 rx_queue_0_packets: 103727545 rx_queue_0_bytes: 6961254601 rx_queue_1_packets: 326249 rx_queue_1_bytes: 454984714 rx_queue_2_packets: 242553 rx_queue_2_bytes: 339238020 rx_queue_3_packets: 183649 rx_queue_3_bytes: 244280310 rx_queue_4_packets: 405611 rx_queue_4_bytes: 495795368 rx_queue_5_packets: 227854 rx_queue_5_bytes: 236190286 rx_queue_6_packets: 193401 rx_queue_6_bytes: 271337926 rx_queue_7_packets: 982683 rx_queue_7_bytes: 447042416 rx_bytes.nic: 12401182418323 tx_bytes.nic: 74986406490 rx_unicast.nic: 8485232145 tx_unicast.nic: 761643543 rx_multicast.nic: 101957596 tx_multicast.nic: 388091 rx_broadcast.nic: 1495740 tx_broadcast.nic: 1718 tx_errors.nic: 0 tx_timeout.nic: 0 rx_size_64.nic: 167990805 tx_size_64.nic: 244373395 rx_size_127.nic: 240074370 tx_size_127.nic: 466106113 rx_size_255.nic: 39290324 tx_size_255.nic: 29943862 rx_size_511.nic: 6918699 tx_size_511.nic: 4570812 rx_size_1023.nic: 22389241 tx_size_1023.nic: 15207161 rx_size_1522.nic: 8112022042 tx_size_1522.nic: 1832009 rx_size_big.nic: 0 tx_size_big.nic: 0 link_xon_rx.nic: 0 link_xon_tx.nic: 0 link_xoff_rx.nic: 0 link_xoff_tx.nic: 0 tx_dropped_link_down.nic: 0 rx_undersize.nic: 0 rx_fragments.nic: 0 rx_oversize.nic: 0 rx_jabber.nic: 0 rx_csum_bad.nic: 0 rx_length_errors.nic: 0 rx_dropped.nic: 0 rx_crc_errors.nic: 0 illegal_bytes.nic: 0 mac_local_faults.nic: 0 mac_remote_faults.nic: 0 fdir_sb_match.nic: 0 fdir_sb_status.nic: 1 tx_priority_0_xon.nic: 0 tx_priority_0_xoff.nic: 0 tx_priority_1_xon.nic: 0 tx_priority_1_xoff.nic: 0 tx_priority_2_xon.nic: 0 tx_priority_2_xoff.nic: 0 tx_priority_3_xon.nic: 0 tx_priority_3_xoff.nic: 0 tx_priority_4_xon.nic: 0 tx_priority_4_xoff.nic: 0 tx_priority_5_xon.nic: 0 tx_priority_5_xoff.nic: 0 tx_priority_6_xon.nic: 0 tx_priority_6_xoff.nic: 0 tx_priority_7_xon.nic: 0 tx_priority_7_xoff.nic: 0 rx_priority_0_xon.nic: 0 rx_priority_0_xoff.nic: 0 rx_priority_1_xon.nic: 0 rx_priority_1_xoff.nic: 0 rx_priority_2_xon.nic: 0 rx_priority_2_xoff.nic: 0 rx_priority_3_xon.nic: 0 rx_priority_3_xoff.nic: 0 rx_priority_4_xon.nic: 0 rx_priority_4_xoff.nic: 0 rx_priority_5_xon.nic: 0 rx_priority_5_xoff.nic: 0 rx_priority_6_xon.nic: 0 rx_priority_6_xoff.nic: 0 rx_priority_7_xon.nic: 0 rx_priority_7_xoff.nic: 0 ----- Please help Thanks Kumar

2 1

[nova][placement][tempest] Hold your rechecks
by Sylvain Bauza 05 Dec '22

05 Dec '22

Sorry folks, that's kind of an email I hate writing but let's be honest : our gate is busted. Until we figure out a correct path for resolution, I hereby ask you to *NOT* recheck in order to not spill our precious CI resources for tests that are certain to fail. Long story story, there are currently two problems : #1 https://launchpad.net/bugs/1940425 nova-ovs-hybrid-plug and nova-next jobs 100% fail due to a port remaining in down state. #2 https://bugs.launchpad.net/nova/+bug/1960346 nova-lvm job 100% fails due to a volume detach failure probably due to QEMU #1 is currently investigated by the Neutron team meanwhile a patch [1] has been proposed against Zuul to skip the failing tests. Unfortunately, this patch [1] is unable to merge due to #2. #2 has a Tempest patch that's being worked on [2] but the current state of this patch is WIP. We somehow need to have an agreement on the way forward during this afternoon (UTC) to identify whether we can reasonably progress on [2] or skip the failing tests on nova-lvm. Again, sorry about the bad news and I'll keep you informed. -Sylvain [1] https://review.opendev.org/c/openstack/nova/+/865658/ [2] https://review.opendev.org/c/openstack/tempest/+/842240

2 5

[ironic] Meetings cancelled Dec 26, Jan 2
by Jay Faulkner 05 Dec '22

05 Dec '22

Hey all, Ironic team decided to cancel our meetings Dec 26, 2022 and Jan 2, 2023 to allow contributors to focus on family and friends over the holiday. Thanks for the hard work in 2022. If there are any concerns for Ironic during those weeks, please email the list or ask in IRC. Thanks, Jay Faulkner

1 0

[CFP] FOSDEM 2023 Virt & IaaS DevRoom (proposal submissions date: 10Dec2022)
by Kashyap Chamarthy 05 Dec '22

05 Dec '22

(I forgot to send this earlier, but there' still 5 more days to go) tl;dr: Please submit the proposals by *10 Dec 2022*. We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2023, to be hosted on February 4th 2023. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 10th, 2022. Important Dates --------------- Submission deadline: 10th December 2022 Acceptance notifications: 15th December 2022 Final schedule announcement: 20th December 2022 Conference devroom: first half of 4th February 2023 About the Devroom ----------------- The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Submit Your Proposal -------------------- All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines --------------------- We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Submission Guidelines --------------------- Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. How to Apply ------------ In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Code of Conduct --------------- Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers ------------------- We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact devroom mailing list[2] for more information. Questions? ---------- If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission [2] iaas-virt-devroom at lists.fosdem.org PS: This is a formatted version of the official announce: https://lists.fosdem.org/pipermail/fosdem/2022q4/003473.html -- /kashyap

1 0

[neutron] Bug deputy - report from the week of Nov 28th
by Slawek Kaplonski 05 Dec '22

05 Dec '22

Hi, I was bug deputy this last week. It was pretty busy week and we had a lot of bugs reported. Here's the summary of them: Critical https://bugs.launchpad.net/neutron/+bug/1998474 - [UT] Random failure of "test_meter_manager_allocate_meter_id" - needs assignee https://bugs.launchpad.net/neutron/+bug/1998353 - Fullstack: test_packet_rate_limit_qos_policy_rule_lifecycle failing - assigned to Rodolfo, fix proposed already https://bugs.launchpad.net/neutron/+bug/1998343 - Unittest test_distributed_port_binding_deleted_by_port_deletion fails: DeprecationWarning('ssl.PROTOCOL_TLS is deprecated') - assigned to Anton Kurbatov, fix proposed already, https://bugs.launchpad.net/neutron/+bug/1995031 - [CI][periodic] neutron-functional-with-uwsgi-fips job failing - assigned to Lajos, it can be the same issue as LP#1998337 High https://bugs.launchpad.net/neutron/+bug/1998228 - [UT] Error in "test_get_vlan_device_name" with n-lib 3.2.0 - In progress, patch https://review.opendev.org/c/openstack/neutron/+/866038 https://bugs.launchpad.net/neutron/+bug/1998226 - [fullstack] Error in "test_concurrent_router_subnet_attachment_overlapping_cidr_" - seems like real issue catched by fullstack test, assigned to Fernando Royo https://bugs.launchpad.net/neutron/+bug/1998104 - dynamic-routing: address_scope calculation error - In progress, fix proposed already https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/863708 https://bugs.launchpad.net/neutron/+bug/1998621 - dnsmasq on DHCP Agent does not listen on tcp/53 after dnsmasq restart - In progress, fix already proposed https://review.opendev.org/c/openstack/neutron/+/866489 Medium https://bugs.launchpad.net/neutron/+bug/1998337 - test_dvr_router_lifecycle_ha_with_snat_with_fips fails occasionally in the gate - Needs assignee https://bugs.launchpad.net/neutron/+bug/1998751 - [L3][DVR][vlan] HA VRRP traffic flooding on physical bridges on compute nodes, needs assignee https://bugs.launchpad.net/neutron/+bug/1998749 - [L3][DVR][vlan] east-west traffic flooding on physical bridges, needs assignee Low https://bugs.launchpad.net/neutron/+bug/1998108 - Move "ChassisBandwidthConfigEvent" registration to "OvnSbIdl" class initialization - In progress, patch https://review.opendev.org/c/openstack/neutron/+/865857 https://bugs.launchpad.net/neutron/+bug/1998085 - Manual install & Configuration in Neutron incorrect vni_ranges leads to error - In progress, patch https://review.opendev.org/c/openstack/neutron/+/865960 https://bugs.launchpad.net/neutron/+bug/1998317 - CachedResourceConsumerTracker update triggered for every command - assigned to Szymon Wróblewski Whishlist (RFEs) https://bugs.launchpad.net/neutron/+bug/1998202 - [RFE] Allow shared resource providers for physical and tunnelled networks - assigned to Rodolfo https://bugs.launchpad.net/neutron/+bug/1998608 - [RFE] A new OVN monitor agent running on each compute node - assigned to Rodolfo https://bugs.launchpad.net/neutron/+bug/1998609 - [RFE] - OVN Distributed routing + IPv6 support - needs triaging from OVN and L3 teams, Others https://bugs.launchpad.net/neutron/+bug/1998235 - Allowed address pairs and dvr routers - duplicate of the old bug https://bugs.launchpad.net/neutron/+bug/1774459 which was never fixed, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder][kolla][OpenstackAnsible] Zed Cycle-Trailing Release Deadline
by Thierry Carrez 05 Dec '22

05 Dec '22

Hello teams with cycle-trailing projects, The Zed cycle-trailing release deadline[1] is next week ! All projects following the cycle-trailing release model must release their Zed deliverables by Dec 14th, 2022. [1] https://releases.openstack.org/antelope/schedule.html#a-cycle-trail The following trailing projects haven't been released yet for Zed (aside the release candidates versions if exists). Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping the release team if you have any questions or concerns. -- Thierry Carrez (ttx)

1 0

[cinder] Cinder Midcycle - 1 (R-16) Summary
by Rajat Dhasmana 05 Dec '22

05 Dec '22

Hello Argonauts, The summary for midcycle-1 held on 30th November, 2022 between 1400-1600 UTC is available here[1]. Please go through the etherpad and recordings for the discussion. [1] https://wiki.openstack.org/wiki/CinderAntelopeMidCycleSummary - Rajat Dhasmana

1 0

Upgrade Ceph 16.2.10 to 17.2.x for Openstack Wallaby RBD storage
by Zakhar Kirpichenko 05 Dec '22

05 Dec '22

Hi! I'm planning to upgrade our Ceph cluster from Pacific (16.2.10) to Quincy (17.2.x). The cluster is used for Openstack block storage (RBD), Openstack version is Wallaby built on Ubuntu 20.04. Is anyone using Ceph Quincy (17.2.x) with Openstack Wallaby? If you are, please let me know if you've encountered any issues specific to these Ceph and Openstack versions. Many thanks! Best regards, Zakhar

1 0

Re: Unable to access Internet from an instance and accessing instance using floating-point IPs from external network
by Eugen Block 04 Dec '22

04 Dec '22

Hi, if you want people to reply you should keep the mailing list in the loop. Also please don't paste pictures but terminal output as plain text so it won't get lost. >> From my controller site: >> External-internet = 192.168.1.118 >> Internal-network = 10.42.0.189 Seems like you meant it the other way around looking at the other networks. >> My external network details is shown below I don't see a segmentation ID for the external network, we create provider (external) networks with the same segmentation ID as the corresponding VLAN in our environment has. The rest of the information on the pictures is not readable to me, please paste the security-group rules as text. >> Apart from all the above information, I will briefly talk about what I >> have enabled in my global.yml file. I have set the >> kolla_internal_vip_address to "192168.1.200", kolla_external_vip_address to >> "10.42.0.200", enable_haproxy to "yes" and other core components of >> openstack was enabled. I'm not familiar with kolla so I can't really say what else could be missing or not. You could disable the port security for your instance to see if that helps, otherwise use tcpdump on control and compute node to see where the packets get lost and which vlans are in use. I'm not sure if that will resolve it but I believe your external network should have a segmentation ID. Zitat von vincent lee <vincentlee676(a)gmail.com>: > Hi, one last thing I would like to add on is the setting of my openvswitch > configuration. > [image: image.png] > [image: image.png] > > > On Wed, Nov 30, 2022 at 1:39 PM vincent lee <vincentlee676(a)gmail.com> wrote: > >> Hi Eugen, >> Sorry for causing any confusion in my previous emails and I will summarize >> the main issue here. After deploying openstack from a fresh installation, I >> have not modified the security group when working creating an instance or a >> container. >> >> From my controller site: >> External-internet = 192.168.1.118 >> Internal-network = 10.42.0.189 >> >> For my compute host 1: >> Internal-network = 192.168.1.115 >> >> For my compute host 2: >> Internal-network = 192.168.1.108 >> >> My current issue is that when I created an instance which ran >> successfully, I was not able to ping that instance from my controller via >> the external network. Besides, I was also not able to ping the internet >> (8.8.8.8) inside of the instance. >> >> However, I was able to ping to the external network (10.42.0.67) from >> inside of the newly created instance itself. In other words, the router is >> communicating correctly. I have attached an image of my network topology as >> shown below. >> [image: image.png] >> Inside of my instance >> [image: image.png] >> I have attached an image of my router details as shown below >> [image: image.png] >> My external network details is shown below >> [image: image.png] >> external network's subnet detail is shown below >> [image: image.png] >> My internal network details is shown below >> [image: image.png] >> internal network's subnet is shown below >> [image: image.png] >> My floating IPs is shown below >> [image: image.png] >> My current security group rules is shown below >> [image: image.png] >> My system information is shown below >> [image: image.png] >> Apart from all the above information, I will briefly talk about what I >> have enabled in my global.yml file. I have set the >> kolla_internal_vip_address to "192168.1.200", kolla_external_vip_address to >> "10.42.0.200", enable_haproxy to "yes" and other core components of >> openstack was enabled. >> >> Best, >> Vincent >> >> >> >> On Wed, Nov 30, 2022 at 2:30 AM Eugen Block <eblock(a)nde.ag> wrote: >> >>> So you did modify the default security-group, ports 8000 and 8080 are >>> not open by default. Anyway, can you please clarify what doesn't work >>> exactly? >>> Does the instance have an IP in the public network but the router is >>> not pingeable (but that is not necessarily an issue) and you can't >>> access it via which protocols? Does SSH work? Is the access blocked by >>> a http_proxy? >>> >>> >>> Zitat von vincent lee <vincentlee676(a)gmail.com>: >>> >>> > To add on to my previous email, I have attached an image of my security >>> > group as shown below. >>> > >>> > Best regards, >>> > Vincent >>> > >>> > On Tue, Nov 22, 2022 at 3:58 AM Eugen Block <eblock(a)nde.ag> wrote: >>> > >>> >> Just one more thing to check, did you edit the security-group rules to >>> >> allow access to the outside world? >>> >> >>> >> Zitat von Adivya Singh <adivya1.singh(a)gmail.com>: >>> >> >>> >> > it should be missing a default route most of the time. >>> >> > or check IP tables on router namespace the DNAT and SNAT are working >>> >> > properly >>> >> > >>> >> > >>> >> > >>> >> > On Tue, Nov 22, 2022 at 9:40 AM Tobias McNulty < >>> tobias(a)caktusgroup.com> >>> >> > wrote: >>> >> > >>> >> >> On Mon, Nov 21, 2022 at 7:39 PM vincent lee < >>> vincentlee676(a)gmail.com> >>> >> >> wrote: >>> >> >> >>> >> >>> After reviewing the post you shared, I believe that we have the >>> correct >>> >> >>> subnet. Besides, we did not modify anything related to the >>> cloud-init >>> >> for >>> >> >>> openstack. >>> >> >>> >>> >> >> >>> >> >> I didn't either. But I found it's a good test of the network! If >>> you are >>> >> >> using an image that doesn't rely on it you might not notice (but I >>> >> >> would not recommend that). >>> >> >> >>> >> >> >>> >> >>> After launching the instances, we are able to ping between the >>> >> instances >>> >> >>> of the same subnet. However, we are not able to receive any >>> internet >>> >> >>> connection within those instances. From the instance, we are able >>> to >>> >> ping >>> >> >>> the router IP addresses 10.42.0.56 and 10.0.0.1. >>> >> >>> >>> >> >> >>> >> >> To make sure I understand: >>> >> >> - 10.42.0.56 is the IP of the router external to OpenStack that >>> provides >>> >> >> internet access >>> >> >> - This router is tested and working for devices outside of OpenStack >>> >> >> - OpenStack compute instances can ping this router >>> >> >> - OpenStack compute instances cannot reach the internet >>> >> >> >>> >> >> If that is correct, it does not sound like an OpenStack issue >>> >> necessarily, >>> >> >> but perhaps a missing default route on your compute instances. I >>> would >>> >> >> check that DHCP is enabled on the internal subnet and that it's >>> >> providing >>> >> >> everything necessary for an internet connection to the instances. >>> >> >> >>> >> >> Tobias >>> >> >> >>> >> >> >>> >> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> > >>> > -- >>> > thanks you. >>> > vincentleezihong >>> > 2garnet >>> > form2 >>> >>> >>> >>> >>> >> >> -- >> thanks you. >> vincentleezihong >> 2garnet >> form2 >> >> > > -- > thanks you. > vincentleezihong > 2garnet > form2

2 1

[all][tc] What's happening in Technical Committee: summary 2022 Dec 02: Reading: 5 min
by Ghanshyam Mann 03 Dec '22

03 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Nov 30. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-30-16.00.log.html * Next TC weekly meeting will be on Dec 7 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 6. 2. What we completed this week: ========================= * FIPS testing on Ubuntu paid subscription We discussed it in TC meeting and after considering the currently available options, TC agreed to go for this[2]. We know it is paid subscription (given by Ubuntu as free to OpenStack upstream CI) and we should use the free open source things to test the upstream code but we do not have any other setup ready for FIPS testing (CentOSstream is not stable enough to add voting job, Debian is not tested broadly in all projects so it may take more time to add the voting job in projects) For now, testing FIPS with Ubuntu paid token is best possible go ahead and if we have any open source/free/stable version available in any distro then we can move FIPS job on that. * Added Skyline repository for OpenStack-Ansible[3] * Added the manila-infinidat charm to Openstack charms[4] * Added the cinder-infinidat charm to Openstack charms[5] 3. Activities In progress: ================== TC Tracker for 2023.1 cycle --------------------------------- * Current cycle working items and their progress are present in 2023.1 tracker etherpad[6]. Open Reviews ----------------- * Three open reviews for ongoing activities[7]. Technical Election changes (Extending Nomination and voting period) ---------------------------------------------------------------------------------- This is in review and positive response so far[8]. Renovate translation SIG i18 ---------------------------------- * No specific update for this week and it will be discussed with the Foundation staff and Board members in Dec 6th board meeting. Adjutant situation (project is not active) ----------------------------------------------- Proposal to mark Adjutant as inactive is up[9] and ready for review. I have emailed about it to current PTL also. Project updates ------------------- * Add the infinidat-tools subordinate charm to OpenStack charms[10] 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://meetings.opendev.org/meetings/tc/2022/tc.2022-11-30-16.00.log.html#… [3] https://review.opendev.org/c/openstack/governance/+/863166 [4] https://review.opendev.org/c/openstack/governance/+/864068 [5] https://review.opendev.org/c/openstack/governance/+/863958 [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/865367 [9] https://review.opendev.org/c/openstack/governance/+/849153 [10] https://review.opendev.org/c/openstack/governance/+/864067 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 02 Dec '22

02 Dec '22

Hello Neutrinos: Due to the lack of agenda, *today's meeting is cancelled*. I have one topic [1] I would like to discuss but I'll wait until I test the code and I'm sure the feature is working. Once this is done, I'll ask you to review it and vote for this RFE. Have a good weekend! [1]https://bugs.launchpad.net/neutron/+bug/1998202

1 0

[openstack-ansible] Removing support for Calico Network driver
by Dmitriy Rabotyagov 02 Dec '22

02 Dec '22

Hi everyone, Due to lack of maintainers of Calico driver support in OpenStack-Ansible we have decided to remove support for this driver. Eventually, CI was failing for Calico jobs for the last few cycles and we haven't seen any interest in further support of the feature. Patches for Calico removal are already proposed: https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/866123 https://review.opendev.org/c/openstack/openstack-ansible/+/866119 If you're interested in this driver and want to step in for fixing CI and supporting the feature, please let us know either by replying to this email or by voting accordingly for the mentioned patches. In case no negative feedback will be received we will merge them by the end of the next week, December 9 2022.

1 0

[Magnum] ls /etc/cni/net.d/ is emty
by Nguyễn Hữu Khôi 01 Dec '22

01 Dec '22

Hello guys. I use Magnum on Xena and I custom k8s cluster by labels. But My cluster is not ready and there is nothing in /etc/cni/net.d/ and my cluster said: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized And this is my labels kube_tag=v1.21.8-rancher1,container_runtime=containerd,containerd_version=1.6.10,containerd_tarball_sha256=507f47716d7b932e58aa1dc7e2b3f2b8779ee9a2988aa46ad58e09e2e47063d8,calico_tag=v3.21.2,hyperkube_prefix= docker.io/rancher/ Note: I use Fedora Core OS 31 for images. Thank you. Nguyen Huu Khoi

2 3