（→） |
（→） |
| （未显示同一用户的1个中间版本） |
| 第7行： |
第7行： |
| | ** April 3rd: | | ** April 3rd: |
| | *** (nick): topic | | *** (nick): topic |
| − | *** (cardoe) Stop Binding - next steps | + | *** (cardoe) retiring networking-bgpvpn? |
| − | **** https://review.opendev.org/c/openstack/neutron/+/985732 | + | **** With the plan of https://specs.openstack.org/openstack/neutron-specs/specs/2026.2/bgp_evpn_type_5_route_support.html and the spec authors mentioning adding Type-2 in the future this replaces the functionality of networking-bgpvpn from a database standpoint / object modeling |
| − | *** (cardoe) EVPN VXLAN updates with OVN BGP EVPN and networking-bgpvpn
| + | **** https://specs.openstack.org/openstack/neutron-specs/specs/2026.2/bgp_evpn_type_5_route_support.html#changes-to-cli-and-rest-api |
| − | **** ML thread for this topic: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GIDECROTNN2SOF3QXIDKYNJNLDZJRKV6/ | + | **** router create with VNI or auto-allocate requires admin operation which is what "openstack bgpvn create --route-target $VNI --project $PROJECT mybgpvpn" is which requires admin but then delegates that BGPVPN object to members of that project |
| − | **** https://review.opendev.org/c/openstack/neutron-specs/+/982256 | + | **** router attachment as an extra step "openstack bgpvpn router assocation create --advertise_extra_routes mybgpvpn myrouter" as a member |
| − | **** https://review.opendev.org/c/openstack/neutron-specs/+/952166 | + | **** the "openstack router add subnet --advertise-host myrouter mysubnet" is equal to "openstack router add subnet myrouter mysubnet" using the bgpnvpn associated router with "--advertise_extra_routes". |
| − | **** https://review.opendev.org/c/openstack/neutron/+/985837 | + | **** This all has the added flexibility of allowing multiple backends so that telco routers can have different bgpvpn backends to service this workload but since we're now moving this into neutron itself for OVN, will networking-bgpvpn be considered deprecated or retired? |
| | * Ongoing discussions: | | * Ongoing discussions: |
| | * To be vetted for discussion: | | * To be vetted for discussion: |
2026年5月20日 (三) 16:29的最新版本
The Neutron Drivers Team (Neutron Drivers) holds public meetings as advertised on OpenStack IRC Meetings Calendar. If you are unable to attend, please check the most recent logs.
Ping list: ykarel, mlavalle, mtomaska, slaweq, tobias-urdin, lajoskatona, haleyb, ralonsoh, cardoe
Agenda
- On Demand agenda. Use this section to add your proposal to this meeting; do not use any other section (keep this template, please):
- April 3rd:
- (nick): topic
- (cardoe) retiring networking-bgpvpn?
- With the plan of https://specs.openstack.org/openstack/neutron-specs/specs/2026.2/bgp_evpn_type_5_route_support.html and the spec authors mentioning adding Type-2 in the future this replaces the functionality of networking-bgpvpn from a database standpoint / object modeling
- https://specs.openstack.org/openstack/neutron-specs/specs/2026.2/bgp_evpn_type_5_route_support.html#changes-to-cli-and-rest-api
- router create with VNI or auto-allocate requires admin operation which is what "openstack bgpvn create --route-target $VNI --project $PROJECT mybgpvpn" is which requires admin but then delegates that BGPVPN object to members of that project
- router attachment as an extra step "openstack bgpvpn router assocation create --advertise_extra_routes mybgpvpn myrouter" as a member
- the "openstack router add subnet --advertise-host myrouter mysubnet" is equal to "openstack router add subnet myrouter mysubnet" using the bgpnvpn associated router with "--advertise_extra_routes".
- This all has the added flexibility of allowing multiple backends so that telco routers can have different bgpvpn backends to service this workload but since we're now moving this into neutron itself for OVN, will networking-bgpvpn be considered deprecated or retired?
- Ongoing discussions:
- To be vetted for discussion:
- To be screened:
- Ready for discussion:
- Approved RFE's:
- Other RFE's:
Previous meeting logs
- Previous meetings, with their notes and logs, can be found here.
