How to make the fips used for dvr l3 routing on the compute nodes be persistent on boot? [closed]

asked 2014-12-04 06:08:45 -0600

capsali gravatar image

updated 2014-12-04 10:37:39 -0600

smaffulli gravatar image

I just finished setting up neutron dvr after a looong battle!

It works nearly as expected except i have a question about fips. As i understand, because now l3 agent is in dvr mode it will eat up an extra external ip just for routing purposes on the compute nodes. So i have 3 nodes, i get 3 public ips taken by each compute node. Those ip's dont appear in my floating ip pool.

The problem is that if i restart any of the compute nodes, the fip on the node is cleaned up on boot. So when i associate a fip on an instance that resides on that compute node it gets another ip for routing.

Is there any way of making the fips used for dvr l3 routing on the compute nodes be persistent on boot? Or even if it gets cleaned on boot can it take the same ip when i associate a fip on an instance on that compute node?

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by capsali
close date 2015-09-29 06:35:37.784460