March 2021 - openstack-discuss - lists.openstack.org

[Manila ] Bug squash happening next week starting Monday March 15th
by Vida Haririan 09 Mar '21

09 Mar '21

Hi all, We are planning a new Bug Squash event for next week. The event will be held from 15th through 18th March, 2021, providing plenty of time for all interested to participate. There will be a synchronous bug triage/review call held simultaneously on our Freenode channel #openstack-manila on 18th March, 2021 at 15:00 UTC and on this Jitsi bridge [1]. A list of selected bugs will be provided in advance here [2]. As always, please feel free to update the list with any bugs that you would like us to focus on during this period. Looking forward to you joining us for this event and many thanks in advance for your participation. :) Regards, Vida [1] https://meetpad.opendev.org/ManilaW-ReleaseBugSquash-II [2] https://ethercalc.openstack.org/hrs8m6sqpmaz

1 0

[election][tacker] PTL candidacy for Xena
by Yasufumi Ogawa 08 Mar '21

08 Mar '21

Hi, I'd like to propose my candidacy for Tacker PTL in Xena cycle. In Wallaby release, we have released several features for the latest ETSI NFV standard while largely updating infras, such as moving to Ubuntu 20.04, supporting redhat distros again and dropping python2 completely for not only Tacker but also related projects such as tosca-parser or heat-translator or so [1]. In addition, we have fixed instability in unit and functional tests for which we have troubles several times. As Tacker PTL, I've led the team by proposing not only new features, but also things for driving the team such as documentation or bug tracking. In Xena cycle, I would like to continue to make Tacker be more useful product for users interested in NFV. I believe Tacker will be a good reference implementation for NFV standard. We have planed to make Tacker more feasible not only for VM environment, but also container to meet requirements from industries. - Continue to implement the latest container technology with ETSI NFV standard. - Introduce multi API versions to meet the requirements for operators enable to deploy mixed environment of multi-vendor products in which some products provide a stable version APIs while other products adopt move advanced ones. - Proceed to design and implement test framework under development in ETSI NFV TST to improve the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. [1] https://docs.openstack.org/releasenotes/tacker/unreleased.html Regards, Yasufumi Ogawa

1 0

[election][kuryr] PTL Candidacy for Xena
by Maysa De Macedo Souza 08 Mar '21

08 Mar '21

Greetings, I would like to continue serving as Kuryr PTL for the Xena cycle. I have been contributing to the OpenStack community since the Queens release and started serving as Kuryr PTL in the Wallaby cycle. It was a great opportunity to contribute back to the community as PTL and I would like to continue doing that. In wallaby we achieved the following goals: * Improved CI stability and fixed broken gates e.g. Network Policy e2e and OVN gates. * Added new testing scenarios for Services without selectors and Services with sctp. * Extended Kuryr functionalities - we started the dual-stack support and included the support for SCTP and Service without selectors. * Increased the contributor base with new contributors from the Outreachy program. For the next cycle, I propose the following goals for Kuryr: * Improve and extend CI: we already did great improvements, but we must continuously work on it to provide better and quicker feedback during the development process. As part of that, we plan to: update gates to start using Kubeadm and include a new cri-o gate. * Extend Kuryr functionalities: Support dual stack and Kubeadm for DevStack installations, and move Pools management to CRDs. * Continue growing the contributor base. Thanks, Maysa Macedo. IRC: maysams

1 0

Openstack Cinder support matrix
by DANILO PAOLO DELL'ORTO 08 Mar '21

08 Mar '21

Hi, The Openstack Cinder driver support matrix (see link-1 below) lists the supported features for each storage and in the IBM Virtualize Family (SVC) section lacks support for 3 important features: Thin provisioning, Volume migration (storage assisted) and Active -Active high availability support. In the same site in section IBM Spectrum Virtualize volume driver (link-2 below), the functions described above seem to be supported and explained in more detail. Which of the two parts is true? Maybe the support matrix is out of date? best regards link-1 https://docs.openstack.org/cinder/latest/reference/support-matrix.html link-2 https://docs.openstack.org/cinder/latest/configuration/block-storage/driver…

2 1

[election][Octavia] PTL candidacy for Xena
by Gregory Thiemonge 08 Mar '21

08 Mar '21

Hi everyone, I would like to propose my candidacy for Octavia PTL during the Xena cycle. I have been an Octavia contributor for 2 years, and a core reviewer for 2 releases. Since then, I have been working in many areas in Octavia: adding support for new protocols (SCTP), fixing CI jobs, improving the octavia-dashboard. My focus will be to continue the work that the team has accomplished these last years, particularly adding many new features in Octavia (active/active load balancers, leveraging features provided by HAProxy 2.0) and improving our CI coverage (restoring CentOS jobs). Thanks for your consideration, Gregory

1 0

[neutron] Bug deputy report - week of March 1st
by Slawek Kaplonski 08 Mar '21

08 Mar '21

Hi, I was Neutron's bug deputy last week. Below is my summary. **critical** https://bugs.launchpad.net/neutron/+bug/1917487 - [FT] "IpNetnsCommand.add" command fails frequently - Assigned to Rodolfo https://bugs.launchpad.net/nova/+bug/1917610 - Migration and resize tests from tempest.scenario.test_minbw_allocation_placement.MinBwAllocationPlacementTest failing in neutron-tempest-dvr-ha-multinode-full - fix done in tempest https://review.opendev.org/c/openstack/tempest/+/778451 https://bugs.launchpad.net/neutron/+bug/1917793 - [HA] keepalived_state_change does not finish "handle_initial_state"execution - gate failure, assigned to Rodolfo **high** https://bugs.launchpad.net/neutron/+bug/1917409 - neutron-l3-agents won't become active - needs assignment https://bugs.launchpad.net/neutron/+bug/1917508 - Router create fails when router with same name already exists - related to ovn l3 plugin, needs assignment https://bugs.launchpad.net/neutron/+bug/1917370 - [functional] ovn maintenance worker isn't mocked in functional tests - **High** as it's causing gate failures or timeouts, assigned, patch: https://review.opendev.org/c/openstack/neutron/+/778080 - already merged https://bugs.launchpad.net/neutron/+bug/1917393 - [L3][Port forwarding] admin state DOWN/UP router will lose all pf-floating-ips and nat rules - assigned, In progress, Patch: https://review.opendev.org/c/openstack/neutron/+/778126 https://bugs.launchpad.net/neutron/+bug/1918108 - [OVN] IGMP snooping traps IGMP messages - assigned to Lucas already, **medium** https://bugs.launchpad.net/neutron/+bug/1917448 - GRE tunnels over IPv6 have wrong packet_type set in OVS - set as **Medium**, assigned, patch: https://review.opendev.org/c/openstack/neutron/+/778178, already merged **Wishlist** https://bugs.launchpad.net/neutron/+bug/1917437 - Enable querier for multicast (IGMP) in OVN, Assigned, In progress https://bugs.launchpad.net/neutron/+bug/1917866 - No need to fetch whole network object on port create - assigned to Oleg, patch proposed already https://review.opendev.org/c/openstack/neutron/+/778881 https://bugs.launchpad.net/neutron/+bug/1904559 - Designate driver: allow_reverse_dns_lookup doesn't works if dns_domain zone wasn't created - Switched to be RFE - please, especially drivers team members, check and triage it so we can discuss that on the drivers meeting, **undecided** https://bugs.launchpad.net/networking-ovn/+bug/1914857 - AttributeError: 'NoneType' object has no attribute 'db_find_rows' - Rodolfo and Lucas are triaging it, **Old bugs which needs attention** https://bugs.launchpad.net/neutron/+bug/1752903 - Floating IPs should not allocate IPv6 addresses - L3 subteam should take a look at it. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[election][neutron] PTL Candidacy for Xena
by Slawek Kaplonski 08 Mar '21

08 Mar '21

Hi, I want to propose my candidacy for Neutron PTL in the Xena cycle. Wallaby was my third cycle serving as Neutron PTL. I think I helped to keep the project in a healthy state and I would like to continue serving as the PTL and keep Neutron running well in the Xena cycle. In Wallaby we accomplished many important goals like e.g.: * finished migration to the engine facade, * improve our CI jobs and its overall stability, * and close of many feature parity gaps between OVN and OVS backends. But we also didn't finish some of the goals which were set for that cycle, like e.g. switching OVN to be the default Neutron backend in Devstack. If I will be elected, I would like to set it as my main goal for Xena cycle. We did a lot of work on adoption of the OVN backend in Neutron already and I think that we are now ready to move on and switch it to be the default backend in the Devstack. I want to focus on couple of things in the Xena cycle: * reduce our bug backlog as it is huge now, * maintenance and continue improvements of our CI, as this is "never ending story", * keep Neutron running in a smooth way. As I mentioned above, if I will be elected, Xena will be my 4th cycle as Neutron PTL and I would like to find some potential successors for the next cycles to help them onboard and understand what are the duties and responsibilities of the PTL. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] Inflated version dependency in os-brick
by Thomas Goirand 08 Mar '21

08 Mar '21

Hi, As I've started packaging Wallaby for Debian, I noticed that os-brick has very inflated version dependencies: $ diff -u ../requirements.txt requirements.txt --- ../requirements.txt 2021-03-08 10:54:44.896134101 +0100 +++ requirements.txt 2021-03-08 10:54:48.848127942 +0100 @@ -2,17 +2,16 @@ # of appearance. Changing the order has an impact on the overall integration # process, which may cause wedges in the gate later. -pbr!=2.1.0,>=5.4.1 # Apache-2.0 -eventlet>=0.25.1 # MIT -oslo.concurrency>=3.26.0 # Apache-2.0 -oslo.context>=2.23.0 # Apache-2.0 -oslo.log>=3.44.0 # Apache-2.0 -oslo.i18n>=3.24.0 # Apache-2.0 -oslo.privsep>=1.32.0 # Apache-2.0 -oslo.serialization>=2.29.0 # Apache-2.0 -oslo.service!=1.28.1,>=1.24.0 # Apache-2.0 -oslo.utils>=3.34.0 # Apache-2.0 -requests>=2.14.2 # Apache-2.0 -six>=1.10.0 # MIT -tenacity>=6.0.0 # Apache-2.0 -os-win>=3.0.0 # Apache-2.0 +pbr>=5.5.1 # Apache-2.0 +eventlet>=0.30.1 # MIT +oslo.concurrency>=4.4.0 # Apache-2.0 +oslo.context>=3.1.1 # Apache-2.0 +oslo.log>=4.4.0 # Apache-2.0 +oslo.i18n>=5.0.1 # Apache-2.0 +oslo.privsep>=2.4.0 # Apache-2.0 +oslo.serialization>=4.1.0 # Apache-2.0 +oslo.service>=2.5.0 # Apache-2.0 +oslo.utils>=4.8.0 # Apache-2.0 +requests>=2.25.1 # Apache-2.0 +tenacity>=6.3.1 # Apache-2.0 +os-win>=5.4.0 # Apache-2.0 Some of the above is clearly abusing. For example, I don't think Cinder really needs version 5.5.1 of PBR, and 5.5.0 should really be enough. I've traced it back to: https://review.opendev.org/c/openstack/os-brick/+/778807 If this is a consequence of the project stopping to test lower bounds of requirements, then this has gone really insane, and the bad practice must stop immediately to restore sanity, and we must revert. We're back 5 years ago where each projects was uselessly requiring the latest version of everything for no reason... From a downstream package maintainer perspective, this is a disaster move. Haven't we learned from our mistakes? Cheers, Thomas Goirand (zigo)

1 0

[infra][qe][nova] Would it be possible to host a custom cirros image somewhere for the nova-next job?
by Lee Yarwood 08 Mar '21

08 Mar '21

Hello all, I recently landed a fix in Cirros [1] to allow it to be used by the nova-next job when it is configured to use the q35 machine type [2], something that we would like to make the default sometime in the future. With no release of Cirros on the horizon I was wondering if I could instead host a build of the image somewhere for use solely by the nova-next job? If this isn't possible I'll go back to the Cirros folks upstream and ask for a release but given my change is the only one to land there in almost a year I wanted to ask about this approach first. Many thanks in advance, Lee [1] https://github.com/cirros-dev/cirros/pull/65 [2] https://review.opendev.org/c/openstack/nova/+/708701

4 9

Post to Openstack mail list
by DANILO PAOLO DELL'ORTO 08 Mar '21

08 Mar '21

Hi, I would like to post questions on the openstack mail lists, can you authorize me? best regards

1 0