May 2022 - openstack-discuss - lists.openstack.org

[magnum] [xena] [IPv6] What is needed to make dual-stack IPv4/6 work in Magnum-managed Kubernetes 1.21+?
by Namrata Sitlani 29 May '22

29 May '22

Hello All, We run release Xena, and we have deployed Kubernetes version 1.21.10 on Magnum with Fedora CoreOS version 34 and we are trying to have IPv6 support for that Kubernetes cluster, as Kubernetes 1.21 and later versions have dual-stack(IPv4/IPv6) support enabled by default. To achieve the same, we used a network with both IPv4 and IPv6 subnets and we got a successful creation of the cluster. The compute instances of the cluster get both IPv4 and IPv6 addresses, but the master and minion nodes get IPv4 as external IP, and also the container does not get an IPv6 address. Can someone please help us with the information, what changes are required to be made at the magnum client-side to have an IPv6 supported Kubernetes Cluster? Thanks, Namrata

2 2

[all][tc] What's happening in Technical Committee: summary May 27, 2022: Reading: 5 min
by Ghanshyam Mann 27 May '22

27 May '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on May 26. Most of the meeting discussions are summarized in this email. Meeting summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-26-15.00.log.html * Next TC weekly meeting will be on June 3 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by June 2. 2. What we completed this week: ========================= * Update governance documentation to try the DPL model for leaderless projects [2]. After election, TC used to search for PTL for leaderless projects but from now onwards we will try if such projects can be moved to the DPL model. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], we have started the many items. Open Reviews ----------------- * Seven open reviews for ongoing activities[4]. Change OpenStack release naming policy proposal ----------------------------------------------------------- We had a call on Tuesday and figured out how to use the number/name in our development cycle/tooling. I am adding the agreement in resolution[5] and also the documentation about using the release number and names [6]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[7]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[8]. New ELK service dashboard: e-r service ----------------------------------------------- A small summary from dpawlik: "the opensearch cluster space seems to be stable right now (there is enough space). For the elastic search recheck, I'm working on ansible role for deploying the e-r and push it to the ci-log-processing project." TripleO team and dpawlik are working on the e-r repo merge. Consistent and Secure Default RBAC ------------------------------------------- We had call on May 24 and discussed the new defaults approach clarification for designate and octavia[9]. Takashi sent a reminder for the feedback about the 'split stack' approach[10]. We will also plan to bring it to the ops meetup in Berlin (Most of us not travelling there but we will find someone who can discuss it). I will schedule the next call and will update the timing on email and wiki[11] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[12]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[13]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14][15]. Project updates ------------------- * Add a repository for the Large Scale SIG[16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/840363 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/governance/+/843214 [6] https://review.opendev.org/c/openstack/governance/+/841800/ [7] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [8] https://review.opendev.org/c/openstack/governance/+/839880 [9] https://etherpad.opendev.org/p/rbac-zed-ptg#L97 [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028677.html [11] https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… [12] https://review.opendev.org/c/openstack/governance/+/836888 [13] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/project-config/+/843534 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron][neutron-vpnaas] retiring train/ussuri/victoria branches
by Mohammed Naser 27 May '22

27 May '22

Hi everyone, At the moment, the VPNaaS team is a bit low on people and in order to be able to handle the workload, I'd like to opt to only keeping maintained releases active. I propose retiring those branches unless someone steps up to fix and clean them up: https://review.opendev.org/c/openstack/releases/+/843167 Please respond to this email if you are running those releases and you are willing to maintain those older branches. Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

[all][oslo] Generation of sample policy files broken since oslo.policy 3.12.0
by Pierre Riteau 27 May '22

27 May '22

Hello, While updating sample policy files (those with all rules commented out and including comments) in CloudKitty, I discovered that the functionality was broken: oslo.policy generates an actual policy file instead [1]. This issue was first introduced in 3.12.0. I submitted a fix [2] which I assume will ship in the next release. I thought this was worth sharing since any project using output from oslopolicy-sample-generator in their docs or repository could be impacted. A workaround is to stick to oslo.policy 3.11.0 in your genpolicy tox environment. Cheers, Pierre Riteau (priteau) [1] https://bugs.launchpad.net/oslo.policy/+bug/1975682 [2] https://review.opendev.org/c/openstack/oslo.policy/+/843250

1 0

[cinder] festival of XS reviews 27th May 2022
by Rajat Dhasmana 27 May '22

27 May '22

Hello Argonauts, We will be having our monthly festival of XS reviews today i.e. 27th May (Friday) from 1400-1600 UTC. Following are some additional details: Date: 27th May, 2022 Time: 1400-1600 UTC Meeting link: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks and regards Rajat Dhasmana

1 0

Openstack-Ansible - Test Cluster on VirtualBox Hosts
by Dave Hall 26 May '22

26 May '22

Hello, Sorry for a beginner question. I am trying to deploy a 3-host minimal test cluster on VirtualBox hosts via OpenStack-Ansible. My purpose is to first build this test cluster and then to deploy a production cluster on physical hardware. The test cluster will be used first to learn, and then to validate changes prior to deploying them on the production cluster. I started with Vagrant-Openstack, but it is still based on Stein and not easily adaptable to Xena. Right now I'm working with Xena and OpenStack-Ansible 24.x on Debian 10 with a deployment host running Debian 11. All 4 systems are native VirtualBox VMs I've managed to deploy a couple of nearly functional clusters this way, but never fully functional and stable. Any guidelines or recommendations for this kind of deployment would be sincerely appreciated. Thanks. -Dave

2 1

[qa][requirements] Tempest Gate blocked for py3.6|7 support
by Ghanshyam Mann 26 May '22

26 May '22

Hello Everyone, As we know, in Zed cycle we have dropped the support of py3.6|7 from OpenStack which is why projects, lib like oslo started dropping it and made new releases. For example, oslo.log 5.0.0 does not support py3.6|7. Tempest being branchless and still supporting stable/victoria onwards stable branches thought of keeping the py36|7 support. But with the oslo dropped py3.6|7 and upper constraint has been updated to the oslo lib latest version made Tempest unit py3.6|7 test jobs failed. - https://bugs.launchpad.net/tempest/+bug/1975036 We have two options here: 1. requirements repo maintain different constraints for py3.6|7 and py3.8|9 which fix the Tempest py3.6| jobs and we can keep the python3.6|7 support in Tempest. Example: oslo.log which fixed the gate[1] but we might need to do the same for Tempest's other deps - https://review.opendev.org/c/openstack/requirements/+/842820 2. Drop the support of py3.6|7 from Tempest If the requirement team is not ok with the above solution then we can think of dropping the py3.6|7 support from Tempest too. This will stop Tempest to run on py3.6|7 but it will not block Tempest to test the OpenStack running on py3.6|7 as that can be done by running the Tempest in virtual env. Opinion? NOTE: Until we figure this out, I have proposed to temporarily stop running py3.6|7 on tempest gate, (especially to get c9s volume detach failure fix to merged otherwise that will block other projects gate too) - https://review.opendev.org/c/openstack/tempest/+/842821 [1] https://review.opendev.org/c/openstack/tempest/+/842819 -gmann

2 3

[neutron] Drivers meeting agenda - 27.05.2022.
by Lajos Katona 26 May '22

26 May '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have one RFE to discuss tomorrow: * [RFE] Allow setting --dst-port for all port based protocols at once (#link https://bugs.launchpad.net/neutron/+bug/1973487) On Demand agenda: * (lajoskatona): meaning of option "router_auto_schedule" is ambiguous (#link https://bugs.launchpad.net/neutron/+bug/1973656 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[neutron][neutron-vpnaas][release] dropping feature/lbaasv2 branch
by Mohammed Naser 26 May '22

26 May '22

Hi there, It looks like we've managed to track along a feature/lbaasv2 branch into neutron-vpnaas all the way from 2014 :) I'd like to request for the release team to delete that branch if possible. :) Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

5 4

openstack queens how increase dashboard threads
by Ignazio Cassano 26 May '22

26 May '22

Hello, I'd like to increase on centos queens the threads for openstack dashboard. At this time my /etc/httpd/conf.d/openstack-dashboard.conf is the following: WSGIDaemonProcess dashboard WSGIProcessGroup dashboard WSGISocketPrefix run/wsgi WSGIApplicationGroup %{GLOBAL} WSGIScriptAlias /dashboard /usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi Alias /dashboard/static /usr/share/openstack-dashboard/static <Directory /usr/share/openstack-dashboard/openstack_dashboard/wsgi> Options All AllowOverride All Require all granted </Directory> <Directory /usr/share/openstack-dashboard/static> Options All AllowOverride All Require all granted </Directory> I tired to modify the first line like this: WSGIDaemonProcess dashboard user=apache group=apache processes=3 threads=10 I restartded httpd but now I am not able to log on the the dashboard. I am sure keystone is working because I am able do execute all commands with command line. Any help, please ? Regards Ignazio

1 0