Assign IP to Multiple Interfaces: Prototype M2M Change

[bryanculver]

Investigate how other aspects need to be changed/improved (potentially create some one-off stories for future follow-on in 2.0)

• Primary IP on Device is a 1-to-1 enforcement, this likely can be derived
• What additional fields should live on the through table
• Primary IP of interface vs Primary IP of device
  • Add 'Primary' IP role #1099

This should be the master issue and branch to go into next. Other subsequent PRs will target this (as it likely won't be mergable initially, forms and filters will be broken).

Since a spike of this nature will almost certainly be a "draw the rest of the owl" problem, it will build on #3190. It will help size the following story in #2403.

[gsnider2195]

Through table fields

field	type	choices	constraints/comments
source1	BooleanField	True/False
destination1	BooleanField	True/False
default2	BooleanField	True/False
preferred2	BooleanField	True/False
primary2	BooleanField	True/False
secondary3	BooleanField	True/False
standby4	BooleanField	True/False	Probably covered by InterfaceRedundancyGroup(#2621)?
primary_for_device	BooleanField	True/False	Limited to one per address family per device

Footnotes

1. Cisco tunnel configuration ↩ ↩²

2. JunOS interface configuration ↩ ↩² ↩³

3. Cisco IOS configuration ↩

4. Cisco ASA configuration ↩

[lampwins]

One point of clarification on primary IP, it needs to be zero or one of each family type (v4, and v6) per device. I.e. a device may have both a primary v4 and v6 address at the same time.

[gsnider2195]

One point of clarification on primary IP, it needs to be zero or one of each family type (v4, and v6) per device. I.e. a device may have both a primary v4 and v6 address at the same time.

Thanks for the reminder. I probably would have forgotten to account for different address families!

[bryanculver]

Completed with #3399