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

[ironic] Group Dinner in Berlin - OIS
by Iury Gregory 30 May '22

30 May '22

Hello Ironicers and fellow stackers! Since some of us will be at the Open Infrastructure Summit in Berlin, I think this would be a great opportunity to have a group dinner in Berlin with our friends (like the one we had during the Ironic Mid-Cycle at CERN). I've created an etherpad to track who would be interested in it [1] and also choose the best day. [1] https://etherpad.opendev.org/p/ironic-dinner-ois2022Berlin -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Senior Software Engineer at Red Hat Brasil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[tripleo] stable/wallaby gate blocker for centos-8 standalone - please hold recheck
by Marios Andreou 30 May '22

30 May '22

Hi folks fyi there is a wallaby gate blocker at https://bugs.launchpad.net/tripleo/+bug/1976247 Seems like ansible-role-python_venv_build is trying to install master upper constraints and that is causing a conflict for oslo-db===11.3.0 (comfing via stackviz installation) we are trying to find a workaround but please hold recheck until we do grateful for any pointers or suggestions here or on the launchpad o/ thanks, marios

1 1

[nova][stable] nova-stable-core team changes
by Sylvain Bauza 30 May '22

30 May '22

Hi, After discussing with all our Nova stable cores, we agreed the below : - Welcome Sean Mooney as a new nova-stable-core team member - Welcome Balazs Gibizer as a new nova-stable-core team member - Welcome Stephen Finucane as a new nova-stable-core team member. I would also like to take the opportunity to thank Matt Riedemann and Lee Yarwood for their important and awesome contributions to the Nova Stable Team. Without them, we saw the impact of their misses, hence the above ^. Lee, Matt, you can anytime return to the nova-stable-core team if you express so, but in the meantime, I'll remove you from the members list. Changes to https://review.opendev.org/admin/groups/540,members will occur literally seconds after I send this email. -Sylvain (on behalf of the Nova Stable team)

1 1

[ops][nova] Problems with AggregateMultiTenancyIsolation/AggregateInstanceExtraSpecsFilter after Train --> Yoga update
by Massimo Sgaravatto 30 May '22

30 May '22

Dear all We have the following use case: - reserve 3 hypervisors for VMs with "big" flavors (whatever the users of these instances are) - partition the rest of the hypervisors according to the project (so projects A1,A2..,An can use only subset S1 of hypervisors, project B1,B2,..,Bm can use only subset S2 of hypervisors) We implemented this: 1- by setting an aggregate_instance_extra_spec 'size' property (with value 'normal' or 'big') for each flavor [*] 2- by creating a BigVMs HostAggregate for size=big [**] 3- by creating an HostAggregate for size=normal for each project, such as this one [***] This used to work. A few days ago we updated our infrastructure from Train to Yoga This was an offline Fast Forward Update: we went through the intermediate releases just to do the dbsyncs. Since this update the instantiation of VMs with flavors with the size=big property doesn't work anymore This is what I see in nova-scheduler log: 2022-05-27 08:38:02.058 5273 INFO nova.filters [req-f92c0e38-262a-4d22-a7fd-8874c4265401 e237e43716fb490db5bda4b777835669 32b5d42c02b0411b8ebf2c33079eeecf - default default] Filtering removed all hosts for the request with instance ID '2412e188-9d5f-4812-ad21-195769a3c220'. Filter results: ['AggregateMultiTenancyIsolation: (start: 59, end: 10)', 'AggregateInstanceExtraSpecsFilter: (start: 10, end: 0)'] Only modifying the property of the BigVMs HA using the filter_tenant_id adding the relevant project: [root@cld-ctrl-01 ~]# openstack aggregate show BigVMs | grep prop | properties | filter_tenant_id='32b5d42c02b0411b8ebf2c33079eeecf', size='big' | the scheduling works Specifying each project and keeping the list up-to-date would be a problem. Moreover if I am not wrong there is a maximum length for the property field. Any hints ? I didn't find anything related to this issue in the nova release notes for Openstack releases > Train These are the filters that we enabled: [filter_scheduler] enabled_filters = AggregateMultiTenancyIsolation,AggregateInstanceExtraSpecsFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGro\ upAffinityFilter,PciPassthroughFilter,NUMATopologyFilter Thanks a lot, Massimo [*] E.g. [root@cld-ctrl-01 ~]# openstack flavor show cldareapd.medium | grep prope | properties | aggregate_instance_extra_specs:size='normal' |[root@cld-ctrl-01 ~]# openstack flavor show cloudvenetocloudveneto.40cores128GB25-bigunipd | grep prop | properties | aggregate_instance_extra_specs:size='big' | [**] [root@cld-ctrl-01 ~]# openstack aggregate show BigVMs +-------------------+---------------------------------------------------------------------------------------+ | Field | Value | +-------------------+---------------------------------------------------------------------------------------+ | availability_zone | nova | | created_at | 2018-06-20T06:54:51.000000 | | deleted_at | None | | hosts | cld-blu-08.cloud.pd.infn.it, cld-blu-09.cloud.pd.infn.it, cld-blu-10.cloud.pd.infn.it | | id | 135 | | is_deleted | False | | name | BigVMs | | properties |size='big' | | updated_at | None | | uuid | 4b593395-1c76-441c-9022-d421f4ea2dfb | +-------------------+---------------------------------------------------------------------------------------+ [***] [root@cld-ctrl-01 ~]# openstack aggregate show Unipd-AdminTesting-Unipd +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | availability_zone | nova | | created_at | 2018-04-12T07:31:01.000000 | | deleted_at | None | | hosts | cld-blu-01.cloud.pd.infn.it, cld-blu-02.cloud.pd.infn.it, cld-blu-05.cloud.pd.infn.it, cld-blu-06.cloud.pd.infn.it, cld-blu-07.cloud.pd.infn.it, cld-blu-11.cloud.pd.infn.it, cld-blu-12.cloud.pd.infn.it, cld-blu-13.cloud.pd.infn.it, cld-blu-14.cloud.pd.infn.it, cld-blu-15.cloud.pd.infn.it, cld-blu-16.cloud.pd.infn.it | | id | 126 | | is_deleted | False | | name | Unipd-AdminTesting-Unipd | | properties | filter_tenant_id='32b5d42c02b0411b8ebf2c33079eeecf', size='normal' | | updated_at | 2018-06-08T09:06:20.000000 | | uuid | 38f6a0d4-77ab-42e0-abeb-57e06ba13cca | +-------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ [root@cld-ctrl-01 ~]#

3 5

[Image Encryption] No meeting today
by Josephine Seifert 30 May '22

30 May '22

Hi, I have a time conflict, so there will be no meeting today. greetings Josephine (Luzi)

1 0

[neutron] Bug deputy report (week starting on 2022-05-23)
by Bernard Cafarelli 30 May '22

30 May '22

Hey neutrinos, I was the bug deputy last week, here are the reported bugs. All high/critical bugs have patches merged (and backports in progress for some), most of the other bugs have patches up for review or merged Critical * Compute tests are failing with failed to reach ACTIVE status and task state "None" within the required time. - https://bugs.launchpad.net/neutron/+bug/1964940 Revert pushed by ykarel https://review.opendev.org/c/openstack/neutron/+/843426 merged High * Open vSwitch agent - does not report to the segment plugin - https://bugs.launchpad.net/neutron/+bug/1975542 DHCP agent issue with routed provider networks, once an agent is running, new segment mappings are not added for new networks Fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843294 merged * [sqlalchemy-20] Missing DB context in L2pop methods - https://bugs.launchpad.net/neutron/+bug/1975797 Fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843413 merged * ``ovn_revision_bumbers_db._ensure_revision_row_exist`` is mixing DB contexts - https://bugs.launchpad.net/neutron/+bug/1975837 Also fix by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843478 also merged Medium * Neutron RBAC not sharing subnet - https://bugs.launchpad.net/neutron/+bug/1975603 Reported around last week's meeting time, lajos looking into it? * Neutron agent blocks during VM deletion when a remote security group is involved - https://bugs.launchpad.net/neutron/+bug/1975674 Happening with OVS firewall and large number of VMS, suggested fix for deferred https://review.opendev.org/c/openstack/neutron/+/843253 * OVN migration failed due to unhandled error in neutron_ovn_db_sync_util - https://bugs.launchpad.net/neutron/+bug/1975692 Patch by ralonsoh https://review.opendev.org/c/openstack/neutron/+/843263 merged * difference in execution time between admin/non-admin call - https://bugs.launchpad.net/neutron/+bug/1975828 Follow-up to https://bugs.launchpad.net/neutron/+bug/1973349 (that added an index to ports.network_id) Unassigned * ML2 OVN - Creating an instance with hardware offloaded port is broken - https://bugs.launchpad.net/neutron/+bug/1975743 Suggested fix by fnordahl - https://review.opendev.org/c/openstack/neutron/+/843601 Have a nice week! -- Bernard Cafarelli

1 0

[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