Backlog #4722

Custom hypervisor names for VMs

Added by Ruben S. Montero almost 5 years ago.

Status:PendingStart date:08/18/2016
Priority:HighDue date:
Assignee:-% Done:


Category:Core & System
Target version:-


Currently VMs are named one-<id> at the hypervisor level. This is needed because oned encode the OpenNebula ID and membership in the name. When the import ability was introduced, OpenNebula keeps a hypervisor-to-OpenNebula mapping. This could be leverage to let admins set their own hypervisor naming conventions.

Also available in: Atom PDF