Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1486712 - [RFE] Display external libvirt VMs
[RFE] Display external libvirt VMs
Status: CLOSED CURRENTRELEASE
Product: vdsm
Classification: oVirt
Component: RFEs (Show other bugs)
4.20.0
Unspecified Unspecified
low Severity low (vote)
: ovirt-4.2.0
: 4.20.9.1
Assigned To: Milan Zamazal
Vladimir
: FutureFeature
Depends On:
Blocks: 1506206
  Show dependency tree / graph
 
Reported: 2017-08-30 08:00 EDT by Milan Zamazal
Modified: 2018-01-16 08:00 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, there was no way to identify external virtual machines in the Administration Portal. Only basic operations can be performed on external machines as they are not managed by the Manager. In this release, external machines can be identified by the prefix "external".
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-12 07:53:15 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
michal.skrivanek: ovirt‑4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
mavital: testing_ack+

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


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 79907 None None None 2017-08-30 08:02 EDT
oVirt gerrit 81192 None None None 2017-08-30 08:03 EDT

  None (edit)
Description Milan Zamazal 2017-08-30 08:00:18 EDT 
External VMs, i.e. those not created by current oVirt instance, managed by libvirt should be displayed in Engine UI among regular oVirt VMs. Engine may permit very basic operations on them such as Power Off while refusing to run operations that are not meaningful or safe to perform on external VMs.
Comment 1 Red Hat Bugzilla Rules Engine 2017-08-30 08:00:23 EDT 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 Yaniv Kaul 2017-09-01 05:38:21 EDT 
I don't see a reason to support this. We can have it in Cockpit. We currently do not wish to mix and match libvirt and oVirt VMs.
Comment 3 Michal Skrivanek 2017-09-01 07:05:00 EDT 
I suppose it's done already?
Comment 4 Milan Zamazal 2017-09-01 08:07:35 EDT 
Yes, although the VMs may still not show up in Engine due to some bug.
Comment 5 Michal Skrivanek 2017-09-01 08:17:49 EDT 
it's low prio, so whatever is done now is good enough. Moving to MODIFIED
Comment 6 Emma Heftman 2017-10-24 07:10:04 EDT 
Hi Milan
I'm reviewing the doc text and also trying to work out the impact of this feature on the documentation. Can you please clarify what is meant by external VMs. Where were the created? Also, where exactly in the UI will I see the word External?

Thanks
Emma
Comment 7 Milan Zamazal 2017-10-24 07:39:47 EDT 
(In reply to Emma Heftman from comment #6)

> Can you please clarify what is meant by external VMs.

External VMs are VMs created outside oVirt.

> Where were the created? 

They can (this doesn't mean they should!) be created for instance by a user manually or by software other than oVirt.

> Also, where exactly in the UI will I see the word External?

External VMs can be recognized by their names in the UI: The names have "external-" prefix.
Comment 9 Vladimir 2017-11-09 05:06:20 EST 
Hi, Milan

As discussed via e-mail there are some minor issues with this RFE:

1. Reboot external VM - Reboot action is successful, but nothing really happens
2. Migration - Migration action is not blocked
3. Shutdown action destoys VM - this one might mislead users. E.g. they might think that VM will be paused, but in fact it will be gone from the libvirt
Comment 10 Milan Zamazal 2017-11-09 07:59:40 EST 
(In reply to Vladimir from comment #9)

> 1. Reboot external VM - Reboot action is successful, but nothing really
> happens
> 2. Migration - Migration action is not blocked

Yes, those are minor faults in Engine. Not part of the implemented functionality, you may file a separate bug if you want to report it.

> 3. Shutdown action destoys VM - this one might mislead users. E.g. they
> might think that VM will be paused, but in fact it will be gone from the
> libvirt

Actually the VM is shown as Down, not Paused, in Engine; it must be removed to completely disappear from Engine. I think this an intended behavior.
Comment 11 Vladimir 2018-01-16 08:00:44 EST 
Verified on 
RHEVM version : 4.2.0.2-0.1.el7
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.