Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 912266

Summary:	[RFE] logical networks uniqueness only per DC, same logical networks in different DCs should be possible
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	ovirt-engine	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, iheim, jkt, lpeer, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	sgrinber: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-04 08:50:13 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:

Description Jiri Belka 2013-02-18 09:02:16 UTC

Description of problem:

Split from BZ890506.

* logical networks - again different DCs can mean different clients although using same naming convention but using different physical networking.

 Simon Grinberg 2012-12-27 09:36:48 EST 
...
> rest of items should not be at DC level, rather at "tenant" level

I've argues for that on the engine-devel list if you remember the thread on networks search. There were some disagreements due to search complexity - need to check last status. But I think we've converged on tenant level.