Feature #5048

When importing resources in vCenter, they should be assigned to the OpenNebula cluster where the host is located

Added by OpenNebula Systems Support Team over 3 years ago. Updated over 3 years ago.

Status:ClosedStart date:03/02/2017
Priority:SponsoredDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:vCenter
Target version:Release 5.4
Resolution:fixed Pull request:

Description

Currently all the resources are always created in OpenNebula Cluster 0.

History

#1 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

  • Tracker changed from Feature to Backlog

#2 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

  • Tracker changed from Backlog to Feature
  • Target version set to Release 5.4

#3 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

  • Status changed from Pending to Assigned
  • Assignee set to Miguel Ángel Álvarez Cabrerizo

The import tool's behavior is coherent with the onevnet, onedatastore CLI commands and Sunstone for networks and datastores. Networks and datastores when they are created are assigned to the default cluster so that's what the importer does, if that behavior changes in the future the importer will reflect this change.

In next release the importer CLI for hosts will allow to select the OpenNebula cluster where the host will be assigned to.

#4 Updated by Tino Vázquez over 3 years ago

  • Status changed from Assigned to New
  • Assignee changed from Miguel Ángel Álvarez Cabrerizo to Ruben S. Montero

#5 Updated by Ruben S. Montero over 3 years ago

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

Also available in: Atom PDF