Bug 1458407

Summary:	[RFE] Logical Network name length needs to be 256 bytes
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	nenduri
Component:	ovirt-engine	Assignee:	Leon Goldberg <lgoldber>
Status:	CLOSED ERRATA	QA Contact:	Michael Burman <mburman>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	danken, devdatta, fgarciad, jdonohue, lsurette, myakove, nenduri, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ycui, yibyang, ykaul
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature, ZStream
Target Release:	---	Flags:	gklein: testing_plan_complete+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1477204 (view as bug list)		Environment:
Last Closed:	2018-05-15 17:43:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1477161, 1477569, 1478717, 1478790, 1483295
Bug Blocks:	1477204

Description nenduri 2017-06-02 18:50:01 UTC

Description of problem:

Current maximum logical network name length is 15 characters.

Typical Cisco ACI logical network names are much longer than 15 characters. 
It consists of tenant name, application name, and end point group name.
We need to support 256 characters long.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Lavi 2017-06-07 15:14:33 UTC

Is this for external network or any network?

Comment 2 nenduri 2017-06-07 17:56:16 UTC

(In reply to Yaniv Lavi from comment #1)
> Is this for external network or any network?

We need this change for any network. 

we use internal networks in phase 1 and we plan to use external networks (without any network plumbing on rhev host) in phase 2.

Comment 3 Dan Kenigsberg 2017-06-18 12:40:38 UTC

Can you provide a sample network name? We consider whether we want to support unrestricted network names or to keep our current limitations on character types. (keeping the limitation may simplify and haste our implementation a bit)

Comment 4 nenduri 2017-06-20 00:02:16 UTC

(In reply to Dan Kenigsberg from comment #3)
> Can you provide a sample network name? We consider whether we want to
> support unrestricted network names or to keep our current limitations on
> character types. (keeping the limitation may simplify and haste our
> implementation a bit)

The ACI network names (EPG names) are in the following format.

TenantName|ApplicationName|EPGName

For example:

Coke|HumanResource|Epg1

The default delimiter is "|". But we do allow configuring delimiter too.

Comment 7 Michael Burman 2017-11-21 08:42:36 UTC

Verified on - 4.2.0-0.5.master.el7

Comment 10 errata-xmlrpc 2018-05-15 17:43:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1488

Comment 11 Franta Kust 2019-05-16 13:06:09 UTC

BZ<2>Jira Resync