Feature #3292
Import KVM/Xen running VMs
| Status: | Closed | Start date: | 11/04/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | CLI | |||
| Target version: | Release 4.14 | |||
| Resolution: | fixed | Pull request: |
Description
Currently, VMs created manually outside of OpenNebula are detected, and stored in the host resource as a list of "wild" VMs.
These VMs could be included as a VM resource, and be monitored.
Since the VMs were not created by OpenNebula, the actions should be limited to a small set, or even to none.
Related issues
History
#1
Updated by Carlos Martín over 6 years ago
This was also requested during the OpenNebulaConf.
The specific use case was to deploy ONE inside a VM, add the physical host to ONE, and then make ONE be aware of its own VM.
This would allow, for instance, to live-migrate the frontend to another host.
#2
Updated by Ruben S. Montero over 6 years ago
- Subject changed from Include "wild" VMs in the VM pool to Import KVM/Xen running VMs
- Category changed from Core & System to CLI
- Target version set to Release 4.14
This is currently done for vCenter and all the functionality needed is in place. This is to build user-space tools to import the VMs in the same way onevcenter vms does.
#3
Updated by Ruben S. Montero over 6 years ago
- Related to Feature #3532: Add more information on WILD VMs added
#4
Updated by Ruben S. Montero over 6 years ago
- Tracker changed from Backlog to Feature
#5
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to New
#6
Updated by Ruben S. Montero about 6 years ago
- Assignee set to Javi Fontan
#7
Updated by Ruben S. Montero about 6 years ago
- Status changed from New to Closed
- Resolution set to fixed
#8
Updated by Carlos Martín almost 6 years ago
- Related to Backlog #3908: Consider the use case of a frontend VM sef-import in HA docs added