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

[neutron] OpenStack Port Creation process
by Dhanasekar Kandasamy 17 May '22

17 May '22

Hi, I want to understand the Port Creation process in OpenStack. 1. What happens in the background when we create a Port with Security Groups? Does it create the port in the Control Plane level or is neutron involved in this? 2. How does the port obtain the IP address from DHCP and Who initiates this DHCP Process? 3. Is there any docs/links available for the same? Thanks, Dhana

3 2

[neutron] CI meeting 17.05.2022
by Slawek Kaplonski 17 May '22

17 May '22

Hi, Sorry for late notice but this week I have internal meeting on which I have to be. That meeting overlaps with Neutron CI meeting so lets cancel CI meeting this week. See You on the CI meeting next week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron][neutron-vpnaas] Reviews needed
by Mohammed Naser 17 May '22

17 May '22

Hi team, We've got a few things that need to be looked at, so appreciate reviews from the Neutron team on this: - Functional tests fixes for stable/yoga: https://review.opendev.org/c/openstack/neutron-vpnaas/+/840330 (and the rest of the chain) - TOX_CONSTRAINTS_FILE cleanup: https://review.opendev.org/c/openstack/neutron-vpnaas/+/822926 - README file cleanup: https://review.opendev.org/c/openstack/neutron-vpnaas/+/574679 - Backport of "ipsec rereadsecrets" for stable/wallaby: https://review.opendev.org/c/openstack/neutron-vpnaas/+/795884 I would appreciate if the Neutron core team can help move some of those patches since I'd like to get VPNaaS in a nice shape to make a release with those fixes :) Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

[openstack-helm] No meeting tomorrow
by Gage Hugo 17 May '22

17 May '22

Hey team, Since there's nothing on the agenda, the meeting for tomorrow is cancelled. We will meet next week at the regular time.

1 0

[puppet] Removal of novajoin support
by Takashi Kajinami 17 May '22

17 May '22

Hello, Because the novajoin project[1] has been unmaintained for a while, we deprecated support for the service during the previous Yoga cycle[2]. [1] https://opendev.org/x/novajoin [2] https://review.opendev.org/c/openstack/puppet-nova/+/833507 I've submitted the removal patch[3] so that we can drop the whole implementation from Zed release. [3] https://review.opendev.org/c/openstack/puppet-nova/+/840802 In case anyone has any concern about the removal, please share your thoughts in the above review. I'll keep WIP on the patch for one week to be open for any feedback. Thank you, Takashi

1 1

OpenTelemetry integration with OSProfiler
by Duc Truong 17 May '22

17 May '22

Hi, I'm curious if anybody has tried integrating OpenTelemetry with OSProfiler. OSProfiler has a Jaeger driver, which uses the Jaeger client. But the Jaeger client has been deprecated in favor of OpenTelemetry [1]. Related to this, is anybody currently using OSProfiler to get distributed traces in OpenStack? -- Duc [1] https://github.com/jaegertracing/jaeger-client-python

1 0

[neutron] Bug deputy report for week of May 9
by Lajos Katona 16 May '22

16 May '22

Hi Neutron Team I was bug deputy in neutron last week. Needs attention ================= * OVN revision_number infinite update loop ( https://bugs.launchpad.net/neutron/+bug/1973347 ) In Progress ============ * Slow queries after upgrade to Xena ( https://bugs.launchpad.net/neutron/+bug/1973349 ) Done ======= * [Wallaby] OVNPortForwarding._handle_lb_on_ls fails with TypeError: _handle_lb_on_ls() got an unexpected keyword argument 'context' ( https://bugs.launchpad.net/neutron/+bug/1972764) Question ======== * Does FWaaS v2 support linuxbridge-agent ? ( https://bugs.launchpad.net/neutron/+bug/1973039) Invalid / Won't fix ================= * Skip DB retry when update on "standardattributes" fails ( https://bugs.launchpad.net/neutron/+bug/1973049 ) * FWaaS rules lost on l3 agent restart ( https://bugs.launchpad.net/neutron/+bug/1973035 ) * Unable to delete FWaaS v2 firewall group stuck ACTIVE ( https://bugs.launchpad.net/neutron/+bug/1972746 ) * [neutron-dynamic-routing] Train CI is broken ( https://bugs.launchpad.net/neutron/+bug/1972854 ) ** https://review.opendev.org/c/openstack/releases/+/841292 train will be EOL-d Lajos Katona (lajoskatona)

1 0

Fwd: unable to connect instance to external network
by Vinesh N 15 May '22

15 May '22

hi, openstack - tripleo installed and was able to launch the instances. Machine has two interfaces, eth2 for external(WAN 192.168.35.0/24) and eth3 for internal(LAN 10.0.20.0/24). issue: unable to reach route interface by following command. (in this case, my route ipaddres 10.0.1.73) * openstack network create public * openstack subnet create --network public public --subnet-range 10.0.1.0/24 --allocation-pool start=10.0.1.40,end=10.0.1.80 --dns-nameserver 8.8.8.8 --gateway 10.0.1.1 --no-dhcp * openstack network create public --provider-physical-network datacentre --provider-network-type vlan --provider-segment 1 --external --share here is my ml2_conf.ini ******************************************************** [ml2] type_drivers=geneve,vlan,flat tenant_network_types=geneve mechanism_drivers=ovn path_mtu=0 extension_drivers=qos,port_security,dns [ml2_type_geneve] max_header_size=38 vni_ranges=1:65536 [ml2_type_vlan] network_vlan_ranges=datacentre:1:1000 [ml2_type_flat] flat_networks=datacentre #[linux_bridge] #physical_interface_mappings = datacentre:br-ex #physical_interface_mappings = datacentre:ens20f2 [ovn] ovn_nb_connection=tcp:10.0.1.158:6641 ovn_sb_connection=tcp:10.0.1.158:6642 ovsdb_connection_timeout=180 neutron_sync_mode=log ovn_l3_mode=True vif_type=ovs ovn_metadata_enabled=True enable_distributed_floating_ip=True dns_servers= ovn_emit_need_to_frag=False **************************************************************** here is my controller network: (ens2042 external and ens2043 internal interfaces) [root@overcloud-controller-0 ~]# ip a |more 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 2: ens20f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:25:90:fe:0f:dc brd ff:ff:ff:ff:ff:ff inet6 fe80::225:90ff:fefe:fdc/64 scope link valid_lft forever preferred_lft forever 3: ens20f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:25:90:fe:0f:dd brd ff:ff:ff:ff:ff:ff 4: ens20f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:25:90:fe:0f:de brd ff:ff:ff:ff:ff:ff inet 192.168.35.86/24 brd 192.168.35.255 scope global dynamic noprefixroute ens20f2 valid_lft 39528sec preferred_lft 39528sec inet6 fe80::f2d5:4cdf:ab4f:4f14/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: ens20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:25:90:fe:0f:df brd ff:ff:ff:ff:ff:ff inet6 fe80::225:90ff:fefe:fdf/64 scope link valid_lft forever preferred_lft forever 6: ib0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 4092 qdisc fq_codel state DOWN group default qlen 256 link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:e4:1d:2d:03:00:21:eb:51 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff 7: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether fa:8f:18:e9:44:e6 brd ff:ff:ff:ff:ff:ff 8: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:25:90:fe:0f:dc brd ff:ff:ff:ff:ff:ff inet 10.0.1.179/24 brd 10.0.1.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fefe:fdc/64 scope link valid_lft forever preferred_lft forever 9: vlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 42:f0:35:f5:cf:5f brd ff:ff:ff:ff:ff:ff inet 10.0.1.179/24 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet 10.0.1.141/32 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet 10.0.1.158/32 brd 10.0.1.255 scope global vlan1 valid_lft forever preferred_lft forever inet6 fe80::40f0:35ff:fef5:cf5f/64 scope link valid_lft forever preferred_lft forever 10: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 76:36:79:8f:4f:b7 brd ff:ff:ff:ff:ff:ff 11: genev_sys_6081: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65000 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000 link/ether 0e:59:d6:99:85:78 brd ff:ff:ff:ff:ff:ff inet6 fe80::c59:d6ff:fe99:8578/64 scope link valid_lft forever preferred_lft forever Note: I tried with 192.168.35.0/24/200.168.35.0/24 for the external network topology as well. Thanks, Vinesh ---------------

1 0

ImportError: cannot import name 'ceph_spec'" | Openstack Wallaby | Tripleo
by Swogat Pradhan 15 May '22

15 May '22

Hi Team, I am deploying openstack wallaby using the deployed ceph method. I am currently facing this issue while deploying overcloud. Can someone please check ? "2022-05-13 14:17:51.022353 | 48d539a1-1679-730f-272a-0000000000cb | TASK | Create the RGW Daemon spec definition", "An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: cannot import name 'ceph_spec'", "2022-05-13 14:17:51.669288 | 48d539a1-1679-730f-272a-0000000000cb | FATAL | Create the RGW Daemon spec definition | overcloud-controller-0 | error={\"changed\": false, \"module_stderr\": \"Traceback (most recent call last):\\n File \\\"<stdin>\\\", line 102, in <module>\\n File \\\"<stdin>\\\", line 94, in _ansiballz_main\\n File \\\"<stdin>\\\", line 40, in invoke_module\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 205, in run_module\\n return _run_module_code(code, init_globals, run_name, mod_spec)\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 96, in _run_module_code\\n mod_name, mod_spec, pkg_name, script_name)\\n File \\\"/usr/lib64/python3.6/runpy.py\\\", line 85, in _run_code\\n exec(code, run_globals)\\n File \\\"/tmp/ansible_ceph_mkspec_payload_iwqyfs7g/ansible_ceph_mkspec_payload.zip/ansible/modules/ceph_mkspec.py\\\", line 24, in <module>\\nImportError: cannot import name 'ceph_spec'\\n\", \"module_stdout\": \"\", \"msg\": \"MODULE FAILURE\\nSee stdout/stderr for the exact error\", \"rc\": 1}", With regards, Swogat Pradhan

2 6

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

14 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 12. 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-12-15.00.log.html * Next TC weekly meeting will be on May 19 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by May 18. 2. What we completed this week: ========================= * FIPS goal is selected community-wide goal now[2]. 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 ----------------- * Nine open reviews for ongoing activities[4]. Change OpenStack release naming policy proposal ----------------------------------------------------------- In today's TC meeting [5], we discussed this topic with Foundation staff and we all agreed to give the release name process handling to Foundation. TC will not be involved in the process. The release name will be mainly used for marketing purposes and we will use the release number as the primary identifier in our release scheduling, automated processes, directory structure etc. The agreed proposal is up for review[6] New release cadence open items --------------------------------------- 1. release notes strategy: Brian presented the different possible ways to reflect the tick-tock ( hoping this is the last time I am using these names as we agree to change them, see below ) release notes combination[7] and we agreed with the 'simple' approach[8]. 2. release cadence terminology With the outcome of the legal check, it is not clear to us that tick-tock words are ok to use for the new release cadence terminology and in what form/combination. In TC, we decided to use a different name and 'SLURP' (Skip Level Upgrade Release Process) is the choice of the majority. I have pushed the patch to reflect the same in the TC resolution[9]. Improve project governance --------------------------------- Slawek has the proposal the framework up and it is under review[10]. New ELK service dashboard: e-r service ----------------------------------------------- Tripleo team joined the TC meeting and we agreed to merge the master and rdo branches in the elastic-recheck repo. It is completely fine to keep both devstack-based and tripleo focus things and maintain them collaboratively. The hosting part will be investigated by the dpawlik Consistent and Secure Default RBAC ------------------------------------------- We had our weekly call on Tuesday 10 May and we agreed on the 'service' role part. I will update the spec for this. The heat open item is still in discussion and Takashi sent an email asking the feedback about the 'split stack' approach, please respond with your thought[11] While we are discussing the heat/scope things, we agreed to work on the 'new defaults' at least (separate from scope which will see later). Please find the summary/plan in etherpad L97[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. 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[14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * None 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] https://governance.openstack.org/tc/goals/selected/fips.html 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. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html#… [6] https://review.opendev.org/c/openstack/governance/+/841800 [7] https://review.opendev.org/c/openstack/cinder/+/840996 [8] https://review.opendev.org/c/openstack/cinder/+/840996/1/releasenotes/sourc… [9] https://review.opendev.org/c/openstack/governance/+/840354 [10] https://review.opendev.org/c/openstack/governance/+/839880 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028490.html [12] https://etherpad.opendev.org/p/rbac-zed-ptg#L97 [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0