Feature #1750
[Self-service] Prevent creation of vm without at least one disk and one network
| Status: | Closed | Start date: | 01/31/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | - | |||
| Resolution: | wontfix | Pull request: |
Description
Because, I think that creating a VM without disk or without network is a mistake.
compute.js-issue1750.patch 
(774 Bytes)
History
#1
Updated by Nicolas AGIUS over 8 years ago
- File compute.js-issue1750.patch added
This patch has only been tested with Opennebula 1.8.1
Thank Mathieu Alorent for this code.
#2
Updated by Carlo Daffara over 8 years ago
Nicolas AGIUS wrote:
This patch has only been tested with Opennebula 1.8.1
Thank Mathieu Alorent for this code.
There are actually quite good reasons for having VMs without a disk or without network:
- if the VM boots from the network via PXE ( <boot dev='network'/> ), that is a fast way to bring inside of OpenNebula some common educational environments like LTSP;
- if the VM is imported from another environment (Pys, VMware, etc.) and no previous adaptation of the network configuration is possible, we usually start the VM with no network, change the configuration and then modify the template to add one or more nics.
I would say that eventually we can assume that at least 1 disk OR 1 network must be present.
#3
Updated by Carlos MartÃn about 8 years ago
- Status changed from New to Closed
- Resolution set to wontfix
I'm closing this one, Self-service was discontinued in favor of the Sunstone views. With the new wizards, it's really easy to see when no disks or networks were added.