aa323e435e
Why I did it DHCPv6 Relay information will be stored in DHCP_RELAY table instead of VLAN table in the future. How I did it Change dhcp_relay docker files to parse through DHCP_RELAY to check for dhcpv6 status How to verify it Build dhcp_relay docker and check all dhcp_relay and dhcpmon are running properly Which release branch to backport (provide reason below if selected)
17 lines
605 B
Django/Jinja
17 lines
605 B
Django/Jinja
[group:dhcp-relay]
|
|
programs=
|
|
{%- set add_preceding_comma = { 'flag': False } %}
|
|
{% for vlan_name in vlan_list %}
|
|
{% if VLAN and vlan_name in VLAN and VLAN[vlan_name]['dhcp_servers'] %}
|
|
{% if add_preceding_comma.flag %},{% endif %}
|
|
{% set _dummy = add_preceding_comma.update({'flag': True}) %}
|
|
isc-dhcpv4-relay-{{ vlan_name }}
|
|
{%- endif %}
|
|
{# Append DHCPv6 agents #}
|
|
{% if DHCP_RELAY and vlan_name in DHCP_RELAY and 'dhcpv6_servers' in DHCP_RELAY[vlan_name] %}
|
|
{% if add_preceding_comma.flag %},{% endif %}
|
|
{% set _dummy = add_preceding_comma.update({'flag': True}) %}
|
|
dhcp6relay
|
|
{%- endif %}
|
|
{% endfor %}
|