Bug 827870 - VM network name should be limited to 15 chars
Summary: VM network name should be limited to 15 chars
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Yaniv Lavi
QA Contact: David Botzer
URL:
Whiteboard: network
Depends On: 821172
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-03 11:37 UTC by Yaniv Lavi
Modified: 2016-02-10 19:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 821172
Environment:
Last Closed: 2013-01-06 07:44:44 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yaniv Lavi 2012-06-03 11:37:18 UTC
+++ This bug was initially created as a clone of Bug #821172 +++

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:

--- Additional comment from ykaul on 2012-05-13 01:02:41 EDT ---

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).

Comment 1 Itamar Heim 2012-06-10 16:06:35 UTC
backend limitation is a higher priority than the history db one

Comment 2 Itamar Heim 2013-01-06 07:44:44 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


Note You need to log in before you can comment on or make changes to this bug.