February 2025 - openstack-discuss

[Glance]Cancelling Weekly Meeting (Feb 13)
by Mridula Joshi 12 Feb '25

12 Feb '25

Hello, Cancelling this week's weekly meeting, As most of the members are not around. Thanks, Mridula Joshi

1 0

openstack instances unable to reach the internet
by collinl＠churchofjesuschrist.org 12 Feb '25

12 Feb '25

I have been banging my head on this issue for quite some time now. I am hoping that somebody can help me see what I have misconfigured. Here is the situation. I have tried setting up several openstack installs, and in none of them am I able to reach the internet from the instances running inside of openstack. All of them are on Rocky Linux 9.5, running the dalmatian version of openstack, installed using packstack. (I have tried an all-in-one, with everything on a single node, and a cluster with the controller/networking on one node, and the compute running on separate nodes). I can get the cirros instances running on the backend network within openstack, and can ssh to them via the floating ip from the host without issues. The cirros instance can ping other cirros instances in the openstack controlled network (both on the backend network(subnet is in the 192.168.100.0/24 range, or on the external public network(subnet is in the 172.24.4.024 range) Even trying the simplest configuration, where everything is all on a single node (compute/networking/controller/etc), Everything from instance creation to VM migration/etc all seems to work just fine. However, the cirros instances cannot ping anything on the internet -- for example, I am unable to ping 8.8.8.8 or even the gateway that the host can reach (The host has an ip used to reach horizon on the 10.61.157.0/24 subnet on our internal lan) I can ping all interfaces from the cirros interface through the backend_network (192.168.100.0/24) through the public interface (172.24.4.0/24), and can even ping the host ip address (10.61.157.59) . . .However, I can't ping anything beyond that (i.e. the 10.61.147.1 gateway does not ping from the cirros instance) From the host commandline, it is able to reach everything external just fine (i.e. it can ping it's gateway 10.61.147.1 and 8.8.8.8 or anything else external) Here is the ip addr output from the host: 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet6 fe80::21d:d8ff:feb7:1edf/64 scope link valid_lft forever preferred_lft forever 3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 56:d8:51:53:10:b0 brd ff:ff:ff:ff:ff:ff 4: br-int: <BROADCAST,MULTICAST> mtu 1442 qdisc noop state DOWN group default qlen 1000 link/ether 62:8c:b0:c2:3e:5a brd ff:ff:ff:ff:ff:ff 5: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:1d:d8:b7:1e:df brd ff:ff:ff:ff:ff:ff inet 10.61.157.59/24 brd 10.61.157.255 scope global br-ex valid_lft forever preferred_lft forever inet 172.24.4.1/24 brd 172.24.4.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::2446:29ff:fe58:6541/64 scope link valid_lft forever preferred_lft forever 6: tapeffe7cc1-56: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue master ovs-system state UNKNOWN group default qlen 1000 link/ether fe:16:3e:e2:66:5d brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fee2:665d/64 scope link valid_lft forever preferred_lft forever 7: tap65170f1f-e0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 3a:26:09:cf:3d:4f brd ff:ff:ff:ff:ff:ff link-netns ovnmeta-65170f1f-e837-4b5e-a471-13e783e6b48e inet6 fe80::3826:9ff:fecf:3d4f/64 scope link valid_lft forever preferred_lft forever And the output from the ovs-vsctl show command: 46294eda-8a39-4775-875d-ef6ec9929346 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int fail_mode: secure datapath_type: system Port tap65170f1f-e0 Interface tap65170f1f-e0 Port patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 Interface patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24 type: patch options: {peer=patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int} Port tapeffe7cc1-56 Interface tapeffe7cc1-56 Port br-int Interface br-int type: internal Bridge br-ex fail_mode: standalone Port patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int Interface patch-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24-to-br-int type: patch options: {peer=patch-br-int-to-provnet-371bdb7c-d2f3-4e70-aca9-1c4838c57e24} Port br-ex Interface br-ex type: internal Port eth0 Interface eth0 ovs_version: "3.3.1" Here is the info for the networks/subnets currently configured: From "openstack network list --long" +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | ID | Name | Status | Project | State | Shared | Subnets | Network Type | Router Type | Availability Zones | Tags | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ | 65170f1f-e837-4b5e-a47 | backend_network | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | b1e5aef4-77da-4b0b-9b9 | geneve | Internal | | | | 1-13e783e6b48e | | | 4fa039fe26 | | | 4-5aaf395484e0 | | | | | | b8e7a305-65f0-44ea-93a | public | ACTIVE | c5f408c4daed4fb2afefa4 | UP | False | 6cff8f70-9dc8-4f17-b78 | flat | External | | | | a-cc6ec741d408 | | | 4fa039fe26 | | | 0-32cf2aedb017 | | | | | | c0c67da4-22bf-4dd2-b4c | private | ACTIVE | 2967b1fe70794fa88cbb3d | UP | False | caed16ae-22ff-427a-a37 | geneve | Internal | | | | 2-2edcb41ffb97 | | | e7227cec77 | | | 0-6b891755bfa7 | | | | | +------------------------+-----------------+--------+------------------------+-------+--------+------------------------+--------------+-------------+--------------------+------+ From "openstack subnet list --long" +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | ID | Name | Network | Subnet | Project | DHCP | Name Servers | Allocation Pools | Host Routes | IP Version | Gateway | Service Types | Tags | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ | 6cff8f70-9dc8 | public_subnet | b8e7a305-65f0 | 172.24.4.0/24 | c5f408c4daed4 | False | | 172.24.4.2-172.2 | | 4 | 172.24.4.1 | | | | -4f17-b780-32 | | -44ea-93aa- | | fb2afefa44fa0 | | | 4.4.254 | | | | | | | cf2aedb017 | | cc6ec741d408 | | 39fe26 | | | | | | | | | | b1e5aef4-77da | backend_subne | 65170f1f-e837 | 192.168.100.0 | c5f408c4daed4 | True | | 192.168.100.100- | | 4 | 192.168.100.1 | | | | -4b0b-9b94-5a | t | -4b5e-a471-13 | /24 | fb2afefa44fa0 | | | 192.168.100.250 | | | | | | | af395484e0 | | e783e6b48e | | 39fe26 | | | | | | | | | | caed16ae-22ff | private_subne | c0c67da4-22bf | 10.0.0.0/24 | 2967b1fe70794 | True | | 10.0.0.2-10.0.0. | | 4 | 10.0.0.1 | | | | -427a-a370-6b | t | -4dd2-b4c2-2e | | fa88cbb3de722 | | | 254 | | | | | | | 891755bfa7 | | dcb41ffb97 | | 7cec77 | | | | | | | | | +---------------+---------------+---------------+---------------+---------------+-------+--------------+------------------+-------------+------------+---------------+---------------+------+ From "openstack floating ip list" +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | ID | Floating IP Address | Fixed IP Address | Port | Floating Network | Project | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ | 61d98a1c-f19a-451f-9353-6cb8305a0c | 172.24.4.175 | 192.168.100.128 | effe7cc1-566d-4574-b4e3-d9f440b776 | b8e7a305-65f0-44ea-93aa- | c5f408c4daed4fb2afefa44fa039fe26 | | 2f | | | 5e | cc6ec741d408 | | +------------------------------------+---------------------+------------------+------------------------------------+------------------------------------+----------------------------------+ From "openstack server list" +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ | e42372d2-946d-4c90-bf2d-1e36cda80e2f | test3 | ACTIVE | backend_network=172.24.4.175, 192.168.100.128 | N/A (booted from volume) | m1.tiny | +--------------------------------------+-------+--------+-----------------------------------------------+--------------------------+---------+ Any assistance in helping me figure out what I am missing to get external access would be greatly appreciated. Thank you!

4 14

Flat openstack network
by Mateusz Woźniakowski 12 Feb '25

12 Feb '25

Good day, I have a question, how to configure neutron in openstack kolla, so as not to make a vrouter but to make a flat network and pass vlans to openstack and make a public network directly in openstack kolla. at the moment I have it on vrouter but it is not a good solution for me. and I would need to set up several networks in openstack Could someone suggest where to find it and how to set it up?

2 3

Building kolla-ansible in china region
by Satish Patel 12 Feb '25

12 Feb '25

Folks, I am trying to build kolla-ansible in China but somehow my docker repository not accessible. I understand geo location and the great firewall. Does anyone know if there is any local china repo or docker hub which I can use in that region to build the openstack. # docker run -d --network host --name registry --restart=always -e REGISTRY_HTTP_ADDR=0.0.0.0:4000 -v registry:/var/lib/registry registry:2 Unable to find image 'registry:2' locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). See 'docker run --help'.

4 4

[kolla-ansible] why swift deployment support has been deprecated for removal in 2025.2?
by Sara khosravi 12 Feb '25

12 Feb '25

Hello everyone, I’m new to Kolla-Ansible. I have used Swift with a simple Ansible playbook and have tested with GitLab CI. But now I’m following the CI/CD procedures in Kolla-Ansible. I’m trying to understand why swift deployment support has been deprecated for removal in 2025.2. I’m having trouble finding the exact failure points in the CI pipeline related to the Swift role, and I can’t seem to find any clues about failures that occurred in the CI process. I really appreciate any help you can provide.

2 1

Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack
by 文相吴 11 Feb '25

11 Feb '25

Hello, Please check if cinder service_type == block-storage or volumev3 in your environment. If your cinder service_type == block-storage, adding a volumev3 service_type & related endpoints, to check if it works. If yes, that is a bug, will fix in soon. Thanks Best Regrads Wu Wenxiang Original: From：zhang.jingwei(a)99cloud.net<zhang.jingwei(a)99cloud.net> Date：2025-02-06 09:50:15(中国 (GMT+08:00)) To：shubham.kumar.yadav369<shubham.kumar.yadav369(a)gmail.com> Cc：wu.wenxiang<wu.wenxiang(a)99cloud.net> , zhu.boxiang<zhu.boxiang(a)99cloud.net> Subject：Re: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack We are preparing the environment you mentioned. After the environment is ready, we will check the corresponding problems and give you feedback in time. Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Best Regrads Zhang Jingwei From: 吴文相 Date: 2025-02-04 10:18 To: Shubham Kumar Yadav CC: 张菁WEI; 朱博祥 Subject: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack Sorry for late，we are in Chinese New Year vacation(Spring Festival)，will back in 1 week Thanks Best Regrads Wu Wenxiang Original: From: Shubham Kumar Yadav<shubham.kumar.yadav369(a)gmail.com> Date: 2025-01-22 18:26:46 To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack Dear Support Team, I hope this message finds you well. I am reaching out to report an issue I am experiencing with the Skyline console in the Dalmatian version of OpenStack. Issue Description: I am unable to list volumes and instances, as well as access volume-related services like Manila. This functionality is critical for my operations. Version Details: I have successfully set up the Skyline console for the Zed version of OpenStack, where everything is functioning as expected. However, the same cannot be said for the Dalmatian version. Troubleshooting Steps Taken: I have checked the service status and confirmed that all necessary services are running. I have attempted to refresh the console and clear the cache, but the issue persists. Request for Assistance: I would appreciate any guidance or troubleshooting steps you could provide to resolve this issue. If there are any logs or additional information you need from my end, please let me know. Also im using same image for both the openstack version - 99cloud/skyline:latest These are the versions of nova-api & cinder-api Zed version nova-manage version 26.2.2 cinder-manage version list 21.1.0 Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Thank you for your attention to this matter. I look forward to your prompt response. Best regards, Shubham

1 0

Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack
by 吴文相 11 Feb '25

11 Feb '25

Hello, Please check if cinder service_type == block-storage or volumev3 in your environment. If your cinder service_type == block-storage, adding a volumev3 service_type & related endpoints, to check if it works. If yes, that is a bug, will fix in soon. Thanks Best Regrads Wu Wenxiang Original: From：zhang.jingwei(a)99cloud.net<zhang.jingwei(a)99cloud.net>Date：2025-02-06 09:50:15(中国 (GMT+08:00))To：shubham.kumar.yadav369<shubham.kumar.yadav369(a)gmail.com>Cc：wu.wenxiang<wu.wenxiang(a)99cloud.net> , zhu.boxiang<zhu.boxiang(a)99cloud.net>Subject：Re: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStackWe are preparing the environment you mentioned. After the environment is ready, we will check the corresponding problems and give you feedback in time. Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Best Regrads Zhang Jingwei 张菁韡产品部邮箱(Email)：zhang.jingwei(a)99cloud.net 地址(Addr)：无锡市新吴区菱湖大道200号中国传感网国际创新园G10-1010 From: 吴文相 Date: 2025-02-04 10:18 To: Shubham Kumar Yadav CC: 张菁WEI; 朱博祥 Subject: Re:[skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStack Sorry for late，we are in Chinese New Year vacation(Spring Festival)，will back in 1 week Thanks Best Regrads Wu Wenxiang Original: From: Shubham Kumar Yadav<shubham.kumar.yadav369(a)gmail.com> Date: 2025-01-22 18:26:46 To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [skyline-console] Issue with Skyline Console in Dalmatian Version of OpenStackDear Support Team, I hope this message finds you well. I am reaching out to report an issue I am experiencing with the Skyline console in the Dalmatian version of OpenStack. Issue Description: I am unable to list volumes and instances, as well as access volume-related services like Manila. This functionality is critical for my operations. Version Details: I have successfully set up the Skyline console for the Zed version of OpenStack, where everything is functioning as expected. However, the same cannot be said for the Dalmatian version. Troubleshooting Steps Taken: I have checked the service status and confirmed that all necessary services are running. I have attempted to refresh the console and clear the cache, but the issue persists. Request for Assistance: I would appreciate any guidance or troubleshooting steps you could provide to resolve this issue. If there are any logs or additional information you need from my end, please let me know. Also im using same image for both the openstack version - 99cloud/skyline:latest These are the versions of nova-api & cinder-api Zed version nova-manage version 26.2.2 cinder-manage version list 21.1.0 Dalmation version nova-manage version 30.0.1 cinder-manage version list 25.0.0 Thank you for your attention to this matter. I look forward to your prompt response. Best regards, Shubham

1 0

[ovn][neutron] How to change chassis priority
by Satish Patel 11 Feb '25

11 Feb '25

Folks, I have the following 4 chassis and I would like to change priority so I can decide which one will be active one. I want to make os-chn-gen-comp-002 highest priority. How do I change priority? I don't have any L3 routers. All I have are subnets because I am using a vlan tenant provider. $ ovn-nbctl list HA_Chassis 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 c75de7ab-b346-4aa5-886b-31b0fd12401e d8ecd5fe-af56-45ac-a4c5-a35b6ea8f5cc dd6ce2d4-9746-4429-862a-e78750bb4909 _uuid : 784ec6e9-9af8-45c6-86e0-75ae7ccf9278 chassis_name : os-chn-ctrl03 external_ids : {} priority : 32767 _uuid : c75de7ab-b346-4aa5-886b-31b0fd12401e chassis_name : os-chn-ctrl01 external_ids : {} priority : 32765 _uuid : d8ecd5fe-af56-45ac-a4c5-a35b6ea8f5cc chassis_name : os-chn-gen-comp-002 external_ids : {} priority : 32764 _uuid : dd6ce2d4-9746-4429-862a-e78750bb4909 chassis_name : os-chn-ctrl02 external_ids : {} priority : 32766

2 3

[openstack][neutron]advice for centralized routing model or DVR
by Nguyễn Hữu Khôi 11 Feb '25

11 Feb '25

Hello. I am planning to deploy l3 agent and I see that article: https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/ht… but could I have some experiences from you? In my environment, I use 100gbps for network nodes and 25gbps for compute nodes. Nguyen Huu Khoi

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-7)
by Goutham Pacha Ravi 11 Feb '25

11 Feb '25

Hello Stackers, We're 7 weeks from the coordinated 2025.1 ("Epoxy") release [1]. Perhaps more importantly, we have three weeks until Feature Freeze, a code merge deadline for project teams with deliverables as part of that coordinated release. I'd recommend reading through the great summary of release deadlines and activities that Thierry Carrez (ttx) from the OpenStack Release Team sent to this list [2]. If you'd like to be a Project Team Lead or a member of the OpenStack TC, now is a great time to nominate yourself. Nominations are accepted until 23:45 UTC on 2025-02-19 [3]. In TC news this week, a couple of governance changes were merged, where we retired a redundant Ansible role project and added the OpenStack Libraries (Oslo) project team to the list of project teams requiring a PTL election. There are several governance changes open for the community's review. A number of contributors and operators participated in FOSDEM 2025 and met up at a Birds of a Feather session hosted by Amy Marrich (spotz). The meeting gathered some interesting thoughts [4] that we'll dive into during our weekly meeting this week. The OpenInfra Foundation is hosting two open community feedback meetings to discuss a proposal to join the Linux Foundation. One of these calls is today, 2025-02-11, at 16:00 UTC [5]. === Weekly Meeting === The OpenStack TC met over IRC [6] and video (Zoom) [7] last week. The meeting was well attended. We reviewed the state of participation of project liaisons in Oslo. The team behind Oslo has a tough job maintaining many disparate code repositories that aid service project teams. Members of the TC felt that the project might see more traction if they re-evaluated their leadership model. After the meeting, we added Oslo to the list of projects requiring a PTL election. The TC expressed that resetting the DPL model every cycle has been beneficial in identifying inactive maintainers and ensuring project continuity. A new release of PBR was made earlier in the day, and project maintainers were advised to report any packaging or obscure issues that may have arisen as a result in the #opendev channel on OFTC. We went on to discuss the state of the CI. Concerns were raised about heavy test loads and project teams running a large number of jobs on every change, which can impact the overall quota and cause other jobs to wait or be queued. Some projects are running upwards of 60 jobs on a single change, with many being multi-node jobs that can consume 10-20% of the overall quota. The TC is concerned about the high number of node hours being consumed by projects and encourages teams to review their test jobs to identify redundant or unnecessary tests. Some strategies to do this include identifying jobs that have remained non-voting for a long time and considering moving them to a periodic pipeline. Project teams should also be mindful of perma-failing test jobs and ensure these are removed until the underlying issue is fixed. The next meeting of the OpenStack TC is today, 2025-02-11, and will be held on the #openstack-tc IRC channel on OFTC at 18:00 UTC. Please find the agenda within the meeting wiki [8]. I hope you're able to join us. === Governance Proposals === ==== Merged ==== - Retire qdrouterd role | https://review.opendev.org/c/openstack/governance/+/938193 - Reset the DPL model for the Oslo project | https://review.opendev.org/c/openstack/governance/+/939485 ==== Open for Review ==== - Define testing runtime for the 2025.2 release | https://review.opendev.org/c/openstack/governance/+/941141 - Cleanup policy popup leads list | https://review.opendev.org/c/openstack/governance/+/941148 - Add Watcher project update liaison | https://review.opendev.org/c/openstack/governance/+/940168 - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 18:00 UTC [8]. === Upcoming Events === - 2025-02-19: Nominations submission deadline for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) - 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] Release countdown for week R-7: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] How to submit your candidacy in OpenStack elections: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] OpenStack BoF @ FOSDEM '25 Etherpad: https://etherpad.opendev.org/p/r.f28603feec88c9e91ff1ced894af35c9 [5] Join the discussion regarding OpenInfra Foundation joining the Linux Foundation: https://board.openinfra.org/strategic-consideration [6] TC Meeting IRC Log 2025-02-04: https://meetings.opendev.org/meetings/tc/2025/tc.2025-02-04-18.00.log.html [7] TC Meeting Video Recording, 2025-02-04: https://youtu.be/92afQSmLk08 [8] TC Meeting Agenda, 2025-02-11: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0