Backlog #5053
Differentiate created templates on vCenter
| Status: | Pending | Start date: | 03/09/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | vCenter | |||
| Target version: | - |
Description
When create a template making a vm persistent, add an attribute to know if has alredy been created on vCenter (vm has been deleted) or is still only in OpenNebula. Another option is to add an attribute while is waiting and delete it when it's created, so all of the created templates have the same attributes and the only different ones are those who has been created making a vm as persistent.
History
#1
Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Tracker changed from Request to Backlog
- Category changed from Core & System to vCenter
#2
Updated by Jaime Melis about 4 years ago
Can you please elaborate? We are having difficulties understanding this issue.
#3
Updated by Adrian Menendez about 4 years ago
When a vm is deployed as persistent, OpenNebula creates a template too. Meanwhile the vm is up and running, the template is only on OpenNebula, just a registry, not a real vCenter template. It would be interesting to be able to differentiate which of them really exists on vCenter.