Backlog #4722
Custom hypervisor names for VMs
| Status: | Pending | Start date: | 08/18/2016 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - |
Description
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.