Feature Request: Replicate TAP in-use status across multiple cloud nodes. #3721
Description
Is your feature request related to a problem? Please describe.
So I run very large GNS3 topologies, and I get overwhelmed by convoluted, rats-nests of connection on my screen. To deal with this, I seperate my topology into distinct sections, and then use bridges w/ TAP interfaces to connect the two. I'll bridge in linux using BRCTL, assign taps to the bridges, then plop them into GNS3 via the cloud node. I've created custom Cloud nodes pre-populated with the TAPs I need. The thing is... I have several instances of these cloud nodes all over my environment, and it's very easy to accidentally connect stuff to a tap that in already in use. If I connected them to the same cloud node, GNS3 would recognize it and stop me. But since multiple cloud nodes have the same TAPs... GNS3 doesn't recognize this. I end up having to keep a spreadsheet as to which taps are in use, and it becomes a pain-in-the-butt to manage.
Describe the solution you'd like
I'd love to TAP in-use status to be replicated across all cloud nodes that TAP is added to. i.e. If I have "tap-wan-1" added to both Cloud1 and Cloud2, and then I connect it to something on Cloud1, I'd like Cloud2 to be aware that it's in use, so that I know to connect the next thing (on the other end) to "tap-wan-2".
Describe alternatives you've considered
There really is no alternative to this, other than continuing to deal with the issue.
Additional context
Nothing additional to add.