Bug 1402700

Summary:	[RFE] - Attach imported external provider networks the correct cluster (the one with the hosts that have external provider support)
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED WONTFIX	QA Contact:	Gil Klein <gklein>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	bugs, mburman, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-13 08:41:48 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:

Description Michael Burman 2016-12-08 08:20:31 UTC

Description of problem:
[RFE] -  Attach imported external provider networks the correct cluster (the one with the hosts that have external provider support).

- We should attach networks that imported from external provider to the cluster with host/s that have external provider support.
We should do the same for networks that created on the external provider via the rhv-m ui as well.

Currently we handling this by attaching the external networks to all clusters for both scenarios.
https://bugzilla.redhat.com/show_bug.cgi?id=1383449
https://bugzilla.redhat.com/show_bug.cgi?id=1373477

And we would like to improve it by attaching such networks only to correct clusters.

Comment 1 Yaniv Lavi 2017-06-13 08:41:48 UTC

This seems like the correct behavior since the provider will most likely manage all of the clusters. I think we should wait for a partner request to change this behavior. 
For OVN this is the correct path in any case.

Comment 2 Michael Burman 2017-06-13 08:59:50 UTC

(In reply to Yaniv Lavi from comment #1)
> This seems like the correct behavior since the provider will most likely
> manage all of the clusters. I think we should wait for a partner request to
> change this behavior. 
> For OVN this is the correct path in any case.

ACK