sum up:
[bug description: neutron-vpn-agent hostname for ha]
There are two ways for neutron-vpn-agent HA with pacemaker/corosync working: 1) all quantum-gateway node hostname should be same. 2)router-migration, currently we try to use hostname since if there are bunches of virtual routers it may consume much more time for router migration, hostname seems more easy and simple.
[bug description: pacemaker report errors if all quantum-gateway node use same hostname]
To fix this problem, we will set hostname to united name "neutron-gateway" in function "neutron-l3-agent start()" of ocf, and set hostname back to the original one assigned by juju in function "neutron-l3-agent stop()" of ocf, this may solved the problem that no quantum-gateway node has the same hostname "neutron-gateway" in the same time.
sum up:
[bug description: neutron-vpn-agent hostname for ha]
There are two ways for neutron-vpn-agent HA with pacemaker/corosync working: 1) all quantum-gateway node hostname should be same. 2)router-migration, currently we try to use hostname since if there are bunches of virtual routers it may consume much more time for router migration, hostname seems more easy and simple.
[bug description: pacemaker report errors if all quantum-gateway node use same hostname]
To fix this problem, we will set hostname to united name "neutron-gateway" in function "neutron-l3-agent start()" of ocf, and set hostname back to the original one assigned by juju in function "neutron-l3-agent stop()" of ocf, this may solved the problem that no quantum-gateway node has the same hostname "neutron-gateway" in the same time.