Public bug reported: Currently, neutron does not utilize oslo.messaging namespaces for RPC layers. All namespaces are set to None [1]. This can cause issues as more methods are added and can start clashing with each other. For example, in this patch[2] we wanted to add a get_ports method to the dhcp agent but that method already exists in the metadata agent RPC layer[3]
This RFE is to cover the work needed to introduce unique namespaces in the RPC layer. Special consideration has to be taken for upgrade scenarios and SLURP releases. One way how to implement this RFE was discussed in the neutron meeting[4]. That is, 1. Give unique names to all RPC namespaces and test it with grenade jobs to see how it works 2. If that works fine we can go with this approach, if there will be problem with upgrades, we will need to: 3(migration path) 3. The migration path would be to setup two listeners on the server side, one in None namespace and the other with the new namespace name. This would have to happen over 4 releases due to SLURP. Start in release C(Caracal) until release E. See more info here [5] [1] https://opendev.org/openstack/neutron-lib/src/commit/9e3a3a608670d2d7bc0ae98fd39551920e563efe/neutron_lib/constants.py#L566-L581 [2] https://review.opendev.org/c/openstack/neutron/+/903572 [3] https://opendev.org/openstack/neutron/src/commit/de58c1b99523104a471420ef0468147f13c9e98d/neutron/agent/metadata/agent.py#L70 [4] https://meetings.opendev.org/meetings/networking/2024/networking.2024-01-02-14.00.log.html#l-89 [5] https://meetings.opendev.org/meetings/networking/2024/networking.2024-01-02-14.00.log.html#l-130 ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2047849 Title: [RFE] Start using oslo messaging namespaces Status in neutron: New Bug description: Currently, neutron does not utilize oslo.messaging namespaces for RPC layers. All namespaces are set to None [1]. This can cause issues as more methods are added and can start clashing with each other. For example, in this patch[2] we wanted to add a get_ports method to the dhcp agent but that method already exists in the metadata agent RPC layer[3] This RFE is to cover the work needed to introduce unique namespaces in the RPC layer. Special consideration has to be taken for upgrade scenarios and SLURP releases. One way how to implement this RFE was discussed in the neutron meeting[4]. That is, 1. Give unique names to all RPC namespaces and test it with grenade jobs to see how it works 2. If that works fine we can go with this approach, if there will be problem with upgrades, we will need to: 3(migration path) 3. The migration path would be to setup two listeners on the server side, one in None namespace and the other with the new namespace name. This would have to happen over 4 releases due to SLURP. Start in release C(Caracal) until release E. See more info here [5] [1] https://opendev.org/openstack/neutron-lib/src/commit/9e3a3a608670d2d7bc0ae98fd39551920e563efe/neutron_lib/constants.py#L566-L581 [2] https://review.opendev.org/c/openstack/neutron/+/903572 [3] https://opendev.org/openstack/neutron/src/commit/de58c1b99523104a471420ef0468147f13c9e98d/neutron/agent/metadata/agent.py#L70 [4] https://meetings.opendev.org/meetings/networking/2024/networking.2024-01-02-14.00.log.html#l-89 [5] https://meetings.opendev.org/meetings/networking/2024/networking.2024-01-02-14.00.log.html#l-130 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2047849/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
