Feature #5247

Wild VMs should import NICs and Disks

Added by Tino Vázquez 3 months ago. Updated 12 days ago.

Status:AssignedStart date:07/14/2017
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:

0%

Category:vCenter
Target version:Release 5.4.3
Resolution: Pull request:

Description

In both vCenter and KVM. They should import these resources WITHOUT any association with existing resources in OpenNebula.

Associated revisions

Revision b0eaefe6
Added by Tino Vázquez about 1 month ago

Feature #5247: Enable disc and nic import for wild vms

Revision 419193e4
Added by Tino Vázquez about 1 month ago

Feature #5247: Enable disc and nic import for wild vms

(cherry picked from commit b0eaefe61e1faf6d2b8d9c31129651f715bb9421)

Revision 5f5bc646
Added by Tino Vázquez about 1 month ago

Feature #5247: Add wait loop for image registering on wild VM import

Revision f1fbc569
Added by Tino Vázquez about 1 month ago

Feature #5247: Add wait loop for image registering on wild VM import

(cherry picked from commit 5f5bc646edb660b44e0c4d7d19318a8c56c84e1b)

Revision 9db35f31
Added by Sergio Semedi about 1 month ago

F #5247 imported vnets now retrieves mac addr from wild (#475)

Revision 8589b57a
Added by Sergio Semedi about 1 month ago

F #5247 imported vnets now retrieves mac addr from wild (#475)

(cherry picked from commit 9db35f318a99cbb8e6fb042fc05c535d8bc144f2)

History

#1 Updated by Tino Vázquez 3 months ago

  • Subject changed from Wild VMs import ignore discs and NICs to Wild VMs should import NICs and Disks
  • Category changed from Drivers - VM to vCenter
  • Target version changed from Release 5.6 to Release 5.4.1

NICs pointing to existing networks.

DISKs do not need an image in the datastore, but rather being not backed by any image

Needs to solve the following issues:

  • import distributed nics
  • allow spaces in the VMDK names and paths

#2 Updated by Tino Vázquez 3 months ago

Also, control rollback

#3 Updated by Tino Vázquez about 1 month ago

  • Status changed from New to Assigned
  • Assignee set to Tino Vázquez

#4 Updated by Sergio Semedi about 1 month ago

Issues to solve:

  • imported NICS from VM now keep the same mac address but when u have more than 1 NIC in your machine pointing to the same network opennebula will force the second one to belong to the same AR MAC RANGE defined earlier. Vcenter does not respect this limitation.
  • Vnets are duplicated when u try to import machines in the same vcenter_network

#5 Updated by Ruben S. Montero 12 days ago

  • Target version changed from Release 5.4.1 to Release 5.4.3

Also available in: Atom PDF