Description of problem: The name of a VM network is limited to 20 chars today but should be limited to 15 characters. The current implementation creates Linux bridge (which is limited to 15 chars) using the name of the network. I would add validation for the input but not change the DB scheme,mostly because not all networks require bridge. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I think the limitation should be that the first 15 chars string should be unique, not limited so much in length. (see example in Bugzilla, with its annoying 20 chars limitation for a bug alias). Example: vlan161_office-and-it-network vlan162_qa-and-rnd-network would be ok with my suggestion, truncated in yours (or disallowed).
We are not sure if the right solution for this bug is to make the 15 first characters unique or differentiate between the Linux bridge name (which is the reason for this limitation) and the network name.
This bug won't make it to 3.1, and since the required behaviour is not clear, closing it for now.