HA router priority should be according to configurable priority of L3-agent

[Yair Fried]

Currently all instances have the same priority (hard coded 50)
Admin should be able to assign priority to l3-agents so that Master will be chosen accordingly (suppose that you have an agent with smaller bandwidth than others, you would like it to have the least amount possible of active (Master) instances.
This will require extending the L3-agent API

This is blocked by bug: https://bugs.launchpad.net/neutron/+bug/1365429

[Isaku Yamahata (yamahata)]

If we are going to add a parameter, we should allow not only prioirty, but also other vrrp parameters to be set via API.
vrrp version, advertisement interval, preempt mode/delay, accept mode,

[Assaf Muller (amuller)]

I think adding more sophisticated router schedulers is more appropriate, instead of the admin manually setting priorities on agents. For example, we could create a 'network bandwidth' scheduler, by (For example) adding currently used external network network bandwidth to the agent heartbeats and aggregating that over a time period on the controller. Continuing this train of thought, this bug could be closed in favor of a blueprint, if the reporter would like to take this task on himself.

[yalei wang (yalei-wang)]

Hi Yair Fried, and amuller, if you agree, I want to write this bp, maybe we could realize it in the next 'L' cycle.

[Yair Fried (yfried)]

Yalei Wang,
You have my blessing

[Assaf Muller (amuller)]

I have *a lot* of reservations and concerns regarding what's being suggested in this bug report. Yalei, do you want to post a summary of what you had in mind?

[Armando Migliaccio (armando-migliaccio)]

If Assaf says 'nay', I think this can't go ahead. Please pick it up, and elaborate more.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]