Bug 1318626 - Mark export domain as clearly deprecated in UI\REST.
Summary: Mark export domain as clearly deprecated in UI\REST.
Keywords:
Status: CLOSED DUPLICATE of bug 1318628
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Documentation
Version: 4.0.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ovirt-4.0.4
: ---
Assignee: bugs@ovirt.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1039606 1318628
TreeView+ depends on / blocked
 
Reported: 2016-03-17 11:53 UTC by Yaniv Lavi
Modified: 2016-08-31 22:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Deprecated Functionality
Doc Text:
Red Hat Virtualization will drop support for export domains in future versions.
Clone Of:
: 1318628 (view as bug list)
Environment:
Last Closed: 2016-08-31 22:11:36 UTC
oVirt Team: Docs
Embargoed:
ylavi: ovirt-4.0.z?
ylavi: planning_ack+
ylavi: devel_ack?
ylavi: testing_ack?

Attachments (Terms of Use)

Description Yaniv Lavi 2016-03-17 11:53:15 UTC 
Description of problem:
We will be looking to replace export domain functions with different flows in 4.x. We need to clear deprecate the domain type to start deferring users to other flows that provide the same functions.
Comment 1 Sandro Bonazzola 2016-05-02 10:01:20 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 2 Yaniv Lavi 2016-05-23 13:17:20 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 3 Yaniv Lavi 2016-05-23 13:21:05 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 4 Yaniv Kaul 2016-05-29 13:31:21 UTC 
I don't think the requirements are clear enough. 
- Where do you want to display and what in the UI?
- What exactly do we wish to do in the API?
Comment 5 Yaniv Lavi 2016-06-02 12:03:13 UTC 
Moving to docs where we will have deprecation notes.
Comment 6 Yaniv Lavi 2016-06-14 16:18:22 UTC 
It's still there in 4.0. We just telling user is might not be in 4.1.
Comment 7 Byron Gravenorst 2016-06-15 23:58:01 UTC 
Thanks for that explanation. I will keep the doc text fairly vague then.
Comment 8 Yaniv Lavi 2016-08-10 15:59:02 UTC 
Can we please make sure the documentation is reviewed and any flow with export domain is clearly replaced with the replacement flow?
Example moving VM from DC to DC and from RHEV to RHEV should be done with import storage domain and LSM. Not with export domain.
Comment 10 Lucy Bopf 2016-08-31 22:11:36 UTC 
Closing this as duplicate to avoid confusion. This work was completed in bug 1318628.

*** This bug has been marked as a duplicate of bug 1318628 ***
Note You need to log in before you can comment on or make changes to this bug.