Bug 1282799 - Import all-in-one plugins from ovirt-engine into ovirt-live
Summary: Import all-in-one plugins from ovirt-engine into ovirt-live
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-live
Classification: Retired
Component: General
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Sandro Bonazzola
QA Contact: Sandro Bonazzola
URL:
Whiteboard:
Depends On: 1282798
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-17 13:09 UTC by Sandro Bonazzola
Modified: 2016-08-11 07:58 UTC (History)
7 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-11 07:58:28 UTC
oVirt Team: Integration
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 48670 0 master MERGED All-In-One import 2016-03-07 15:18:04 UTC

Description Sandro Bonazzola 2015-11-17 13:09:06 UTC 
Description of problem:
All in one support has been dropped in 4.0 but we still need it to some extent in ovirt-live.
Comment 1 Yedidyah Bar David 2015-11-17 13:24:11 UTC 
No chance of basing ovirt-live on hosted-engine too? This would be really cool.

Another option is to use nested kvm for the host.

Otherwise, if we have to support it in ovirt-live, not sure why we should deprecate it in engine. Workarounds that we'll need to apply there can probably be applied, even if less easily, on a normal allinone engine machine.
Comment 2 Pavel Stehlik 2016-06-27 11:32:09 UTC 
QE just sanity - Live should work.
Comment 3 Gil Klein 2016-08-11 07:58:28 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Note You need to log in before you can comment on or make changes to this bug.