Bug 1402700 - [RFE] - Attach imported external provider networks the correct cluster (the one with the hosts that have external provider support)
Summary: [RFE] - Attach imported external provider networks the correct cluster (the ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.1.0
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-08 08:20 UTC by Michael Burman
Modified: 2017-06-13 08:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-13 08:41:48 UTC
oVirt Team: Network
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.