9fe70f45f3
As neutron-vpnaas-agent has been loaded just inside of the existing l3 agent rather than requiring operators to run a completely different binary with a subclass of the existing L3 agent[1]. We need restructure this role to fit with this new feature. [1] https://review.openstack.org/488247 Depends-On: I47cd8ba5a14da3c76d5b1eb0b4c0cf0c729eb2ff Change-Id: Id690a652bc9facf1c3e39358f548ab7ddd967d80 Implements: blueprint restructure-neutron-vpnaas Closes-Bug: #1731498
17 lines
577 B
Django/Jinja
17 lines
577 B
Django/Jinja
#!/bin/bash
|
|
|
|
set -o errexit
|
|
|
|
# NOTE(jeffrey4l): Remove all l3 related netns in case of multiple active routers in l3 high available mode.
|
|
neutron-netns-cleanup \
|
|
--config-file /etc/neutron/neutron.conf \
|
|
--config-file /etc/neutron/l3_agent.ini \
|
|
--config-file /etc/neutron/fwaas_driver.ini \
|
|
--force --agent-type l3
|
|
|
|
neutron-l3-agent \
|
|
--config-file /etc/neutron/neutron.conf \
|
|
--config-file /etc/neutron/neutron_vpnaas.conf \
|
|
--config-file /etc/neutron/l3_agent.ini \
|
|
--config-file /etc/neutron/fwaas_driver.ini
|