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)
24 lines
664 B
Django/Jinja
24 lines
664 B
Django/Jinja
{# Append DHCPv6 agents #}
|
|
{# Create a program entry for each DHCPv6 relay agent instance #}
|
|
{% for vlan_name in vlan_list %}
|
|
{% if DHCP_RELAY and vlan_name in DHCP_RELAY and 'dhcpv6_servers' in DHCP_RELAY[vlan_name] %}
|
|
{% for dhcpv6_server in DHCP_RELAY[vlan_name]['dhcpv6_servers'] %}
|
|
{% if dhcpv6_server | ipv6 %}
|
|
{% set _dummy = relay_for_ipv6.update({'flag': True}) %}
|
|
{% endif %}
|
|
{% endfor %}
|
|
{% if relay_for_ipv6.flag %}
|
|
{% set _dummy = relay_for_ipv6.update({'flag': False}) %}
|
|
[program:dhcp6relay]
|
|
command=/usr/sbin/dhcp6relay
|
|
|
|
priority=3
|
|
autostart=false
|
|
autorestart=false
|
|
stdout_logfile=syslog
|
|
stderr_logfile=syslog
|
|
|
|
{% endif %}
|
|
{% endif %}
|
|
{% endfor %}
|