Backlog #4740
Allow creation of "Empty disk image" for type OS
| Status: | Pending | Start date: | 08/23/2016 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.6 |
Description
Currently it's only allowed to create a "Empty disk image" for type "Generic storage datablock". I would like to allow for the creation of "Empty disk image" for type OS as well. It's perfectly possible to create a (empty) OS disk which will be installed later based on an ISO / network install, etc. It's not clear for me why this restriction is in place.
History
#1
Updated by Yannick MOLINET almost 5 years ago
You can use datablock to install your OS and change the type after (it's what I done).
#2
Updated by Stefan Kooman almost 5 years ago
@Yannick Molinet: I know, that's what I do as well. But I don't know why this restriction is in place. I want to eliminate this step.
#3
Updated by EOLE Team almost 5 years ago
Stefan Kooman wrote:
@Yannick Molinet: I know, that's what I do as well. But I don't know why this restriction is in place. I want to eliminate this step.
+1
It's quite disturbing for now comers to OpenNebula, I explained the procedure several times.
Regards.
#4
Updated by Ruben S. Montero almost 5 years ago
- Tracker changed from Request to Backlog
- Category set to Core & System
- Priority changed from Normal to High
- Target version set to Release 5.4
#5
Updated by Guillaume Oberlé almost 5 years ago
Since we can easily change the boot order of VMs (introduced with 5.0) the difference between an OS and a DATABLOCK image is at best informative. Maybe we should consider removing the OS data block type and consider to keep only the traditional data block and the CDROM type ?
#6
Updated by Ruben S. Montero about 4 years ago
- Target version changed from Release 5.4 to Release 5.6