Bug #4124

vCenter VMs within resource pool cannot be monitor nor imported

Added by Tino Vázquez over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:11/02/2015
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:

0%

Category:vCenter
Target version:Release 4.14.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Associated revisions

Revision 74cb1564
Added by Tino Vázquez over 5 years ago

Bug #4124: Add support for VMs in Resource Pools

Various small fixes

Revision 132bee03
Added by Tino Vázquez over 5 years ago

Bug #4124: Add support for VMs in Resource Pools

Various small fixes
(cherry picked from commit 74cb15642a50f36de175400249968f3aeee6cf5c)

Revision fffcc62d
Added by Tino Vázquez over 5 years ago

Bug #4124: Add comments for resource pool code and minor refactor

Revision b5be1631
Added by Tino Vázquez over 5 years ago

Bug #4124: Add comments for resource pool code and minor refactor
(cherry picked from commit fffcc62d0a36cc8a2c85b9f91e2a080dda11a309)

Revision b421b113
Added by Tino Vázquez over 5 years ago

Bug #4124: Fix bug in default resource pool in vCenter driver

Revision b3a02589
Added by Tino Vázquez over 5 years ago

Bug #4124: Fix bug in default resource pool in vCenter driver
(cherry picked from commit b421b113dc021d4a92282406e3296b522bc9f744)

History

#1 Updated by Tino Vázquez over 5 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF