Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1458407 - [RFE] Logical Network name length needs to be 256 bytes
[RFE] Logical Network name length needs to be 256 bytes
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
4.1.0
Unspecified Unspecified
high Severity urgent
: ovirt-4.2.0
: ---
Assigned To: Leon Goldberg
Michael Burman
: FutureFeature, ZStream
Depends On: 1477161 1477569 1478717 1478790 1483295
Blocks: 1477204
  Show dependency treegraph
 
Reported: 2017-06-02 14:50 EDT by nenduri
Modified: 2018-05-15 13:45 EDT (History)
15 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1477204 (view as bug list)
Environment:
Last Closed: 2018-05-15 13:43:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
gklein: testing_plan_complete+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 79116 None None None 2017-07-30 14:28 EDT
oVirt gerrit 79459 None None None 2017-07-30 14:30 EDT
oVirt gerrit 79971 None None None 2017-07-30 14:30 EDT
Red Hat Product Errata RHEA-2018:1488 None None None 2018-05-15 13:45 EDT

  None (edit)
Description nenduri 2017-06-02 14:50:01 EDT
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 11:14:33 EDT
Is this for external network or any network?
Comment 2 nenduri 2017-06-07 13:56:16 EDT
(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 08:40:38 EDT
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-19 20:02:16 EDT
(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 03:42:36 EST
Verified on - 4.2.0-0.5.master.el7
Comment 10 errata-xmlrpc 2018-05-15 13:43:21 EDT
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

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