Marcus, Prachi would be the best person to answer this question as she added the constraint to create-schema.sql:
8836a08e (prachi 2011-11-08 11:23:37 -0800 658) CONSTRAINT `fk_op_dc_vnet_alloc__physical_network_id` FOREIGN KEY (`physical_network_id`) REFERENCES `physical_network' Commit id is 8836a08e. -Alena. On 11/15/12 7:40 AM, "Marcus Sorensen" <[email protected]> wrote: >https://issues.apache.org/jira/browse/CLOUDSTACK-226 > >It looks like this was fixed (11fe086adab8e790018343252ed08aac9a27b1c6) by >making sure that a particular vlan range can only exist on one physical >network. Is there any technical reason for this? It looks like the fix >worked around the unique key restriction in the database schema, is that >the only limiting factor? We recently changed the naming scheme of KVM >bridges to allow the same vlan to be used on different physical networks, >so I can make the solution KVM specific. > >I'm just not sure why this limitation was created in the first place (the >schema, not the fix) and want to gather some info before doing too much. >I'd rather just make the key unique to vlan on physical network and let >the >individual doing the implementation decide if they want to do multiple >layer2 domains to their boxes or not. >
