DHCP agent scheduler API extension should be supported by ML2/OVN backend

[Slawek Kaplonski]

Neutron DHCP agent can work perfectly fine with ML2/OVN backend and there are some use cases, like Baremetal provisioning over IPv6 which requires that. Because of that dhcpagentscheduler API extension should be added to the list of the extensions supported by the OVN driver so it's not disabled during start of the Neutron server.
Adding it there will allow users to use API to add/removed networks to/from DHCP agents as well as check what networks are hosted on which DHCP agent.

[Slawek Kaplonski (slaweq)]

Patch proposed https://review.opendev.org/c/openstack/neutron/+/897528

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/897528
Committed: https://opendev.org/openstack/neutron/commit/f006d29251abe3c138ee0dea5b549496b66b8fa7
Submitter: "Zuul (22348)"
Branch: master

commit f006d29251abe3c138ee0dea5b549496b66b8fa7
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/2023.2
Review: https://review.opendev.org/c/openstack/neutron/+/898292

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/2023.1
Review: https://review.opendev.org/c/openstack/neutron/+/898293

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/zed
Review: https://review.opendev.org/c/openstack/neutron/+/898294

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/neutron/+/898295

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/neutron/+/898296

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/neutron/+/898297

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/898293
Committed: https://opendev.org/openstack/neutron/commit/3123df2672dac33edb22742bba2b6a0812fdd1a0
Submitter: "Zuul (22348)"
Branch: stable/2023.1

commit 3123df2672dac33edb22742bba2b6a0812fdd1a0
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01
    (cherry picked from commit f006d29251abe3c138ee0dea5b549496b66b8fa7)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/898294
Committed: https://opendev.org/openstack/neutron/commit/6476edc9861b8b6e147333e613ada4210a950480
Submitter: "Zuul (22348)"
Branch: stable/zed

commit 6476edc9861b8b6e147333e613ada4210a950480
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01
    (cherry picked from commit f006d29251abe3c138ee0dea5b549496b66b8fa7)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/898295
Committed: https://opendev.org/openstack/neutron/commit/9d4638071f86c7f366d9b19b4a2bcd36121f117b
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 9d4638071f86c7f366d9b19b4a2bcd36121f117b
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01
    (cherry picked from commit f006d29251abe3c138ee0dea5b549496b66b8fa7)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/898296
Committed: https://opendev.org/openstack/neutron/commit/efc3ff75a4ec89dc2d5cc4d27fe4c7fc6139cd54
Submitter: "Zuul (22348)"
Branch: stable/xena

commit efc3ff75a4ec89dc2d5cc4d27fe4c7fc6139cd54
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01
    (cherry picked from commit f006d29251abe3c138ee0dea5b549496b66b8fa7)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/898292
Committed: https://opendev.org/openstack/neutron/commit/f797f8bc2eb259eb74b751c4e37cb94cb0a2da1e
Submitter: "Zuul (22348)"
Branch: stable/2023.2

commit f797f8bc2eb259eb74b751c4e37cb94cb0a2da1e
Author: Slawek Kaplonski <email address hidden>
Date: Fri Oct 6 10:58:57 2023 +0200

    Add dhcpagentscheduler API extension to the ML2/OVN extensions

    In most typical use cases ML2/OVN backend don't needs to run DHCP agent
    as OVN provides DHCP functionality natively. But there are some use
    cases like Baremetal provisioning over IPv6 or Spine Leaf architecture
    with DHCP relays where DHCP agent is necessary and it can work perfectly
    fine with ML2/OVN backend.
    The problem was that dhcpagentscheduler API extension wasn't listed as
    supported by the OVN backend so it was filtered out from the list of
    supported extensions during start of the neutron server. This caused
    problems with API to get/set/delete networks to/from DHCP agent.

    This patch adds this API extension to the list of the extensions
    supported by the OVN driver to fix that issue.

    Depends-On: https://review.opendev.org/c/openstack/tempest/+/898090

    Closes-bug: #2038655

    Change-Id: I09a37ca451d44607b7dde344c93ace060c7bda01
    (cherry picked from commit f006d29251abe3c138ee0dea5b549496b66b8fa7)

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Slawek Kaplonski <email address hidden>" on branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/neutron/+/898297
Reason: it requires changes in tempest and we have already pinned tempest in this branch so it's not possible to backport it

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 22.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 23.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 20.5.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 21.2.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 24.0.0.0b1 development milestone.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron xena-eom release.