Jeremy Stretch

I'm not comfortable with the pattern used here, as it's going to be very difficult to maintain long-term. I suspect you're replicating the workflow for IP address assignment; we actually...

We specifically avoided adding discrete address fields in the early days because they are not universal. I'd be willing to introduce additional fields only if we can cite some well-defined...

> The inability to feed its address information into other systems which require separate fields complicates the overall data model around sites for larger organizations with hundreds of sites and...

> Additionally, I'd love to query Netbox sites by country, for example, which we can't currently do with the address format we have. The region model serves this function, and...

NetBox currently does not replicate _any_ related objects when cloning an object, partly because of the complex workflow that would be required to do so and partly to avoid unpleasant...

Closing this out as this FR is not actionable in its current form and there has been no effort to improve it. If anyone would like to devise and propose...

Tagging this as relevant to (but not necessarily blocked by) #7845.

Blocked by #9102

> It would be helpful for a LAG interface to record what its corresponding partner LAG interface is at the other end device. There is no concept of a connection...

> By 'multichassis' do you mean Netbox's Virtual Chassis? No, the inverse. [Juniper's MC-LAG](https://www.juniper.net/documentation/us/en/software/junos/mc-lag/topics/topic-map/examples-mc-lag.html) is one example; other vendors have different names for it (of course).