#179 Support "Datacenter" locations for IP addresses and Sub/Supernets

[Four Eighteen]

Just as VMWare vCenter allows you to create multiple "Datacenters" object containers which are generally physical locations, and can each contian multiple clusters, hosts, and differing policies, can you allow for "Datacenters" to be a grouping object with which to place subnets and addresses within them? This would make tracking subnets easier, especially with addresses ranges that may not be networked together, but independently use the same address space. (ie, Isolated networks in both locations that happen to both share the same address space but are not networked together and therefore don't collide). For example, I may be given a private subnet from Amazon AWS that is 10.11.12.0/24, and is in use there, but I may also oversee and use that same subnet at a SoftLayer datacenter in Dallas Texas, on a separate isolated network, and the networks may not be tied together. But the easiest way to organize the address space would be to palce them in different "Datacenter" containers.

[alexjhart]

I like this idea, but would like to consider how it incorporates with sections, rather than creating another grouping. Thoughts?

[Four Eighteen]

Perhaps it could be an attribute? Maybe I'm not aware of something like this that already exists, but if subnets can be assigned to a grouping such as a "Site" aka "Location", I would like to be able to limit admins access to the interface so that they can only edit IP addresses within their own "Site". We have multiple offices. I work at the corporate office, and we oversee everything, but we have offices in Japan, where I want them to be able to edit their own "Site" and subnets they use there, but not edit the subnets we use else where, but only view the subnets at our USA office, Korea office, etc.

[alexjhart]

That seems reasonable. I would support that idea.