Problems with the "creation of new sizes" feature

[john-kheir]

Scenario to test feature https://github.com/0-complexity/openvcloud/issues/421

1- Create a new size with Mem=32768 MB, vcpu:16 GB and Boot_disk_sizes=[10,20,30,50,100]

Actual results

1- Sizes that we can select , for Mem=32768 MB, vcpu:16 GB, are [10,20,..250,500,...]

2- VM has been created although the environment doesn't provide such a RAM and CORE capacity

3- The newly created size can be deleted

Expected Results

1- Only Bootdisk_sizes defined during the creation of the new size should be selected during creating a new VM. 2- VM shouldn't be created in an environment that doesn't provide such size.. Instead 503 should be returned 3- We shouldn't be able to delete a size for a created vm that uses that size

Environment

du-conv-2

Software Version

JumpScale

Core: branch: 7.1.5 (4a461ad) 10/18/2016, 8:59:37 AM
Portal: branch: 7.1.5 (d9a418a) 10/17/2016, 12:43:41 PM

OpenvCloud

Core: branch: 2.1.5 (21d31c9) 10/18/2016, 5:41:00 PM
G8VDC: branch: 2.1 (76cdafb) 10/18/2016, 9:21:58 PM
Selfhealing: branch: master (21c05da) 10/16/2016, 8:18:04 AM

OpenvStorage:

openvstorage-backend-core: 1.7.3-rev.713.f2fab03-1
openvstorage-health-check: 2.0.0-rev.134.9ef41c0-1
alba: 0.9.20
openvstorage-webapps: 2.7.3-rev.4029.63e298f-1
openvstorage-backend-webapps: 1.7.3-rev.713.f2fab03-1
openvstorage-core: 2.7.3-rev.4029.63e298f-1
openvstorage-hc: 1.7.3-rev.713.f2fab03-1
openvstorage-cinder-plugin: 1.2.2-rev.38.dcc3b76-1
openvstorage: 2.7.3-rev.4029.63e298f-1
openvstorage-backend: 1.7.3-rev.713.f2fab03-1
openvstorage-sdm: 1.6.3-rev.372.0cfe8a2-1

[ahsayde]

Tested on du-cov-2

steps:

• I created a new VM with size as shown:

• Form cloudspace page click new VM

Issue 1

Expected Result

• Only 50, 100, 125 disk sizes are available

Actual Result

• Disk sizes not defined during creating a new size still appear in the list.

• when selecting one of them this error message appears

Issue 2

• Still possible creating a new size that the environment doesn't provide it.. So for example any cpu has (16 core) , and still a VM with this size (18 core) can be created

Software version

JumpScale

Core: branch: master (ba74149) 12/12/2016, 11:58:33 AM
Portal: branch: master (f112ae1) 12/12/2016, 12:46:19 PM

OpenvCloud

Core: branch: master (5b1ea6e) 12/12/2016, 3:49:35 PM
G8VDC: branch: master (9a53d52) 11/27/2016, 11:03:39 AM
Selfhealing: branch: master (cdb50c8) 12/12/2016, 3:50:11 PM

OpenvStorage:

openvstorage-backend-core: 1.7.6-rev.817.91abb7c-1
openvstorage-health-check: 3.1.2-rev.227.f50ebb6-1
alba: 1.1.0
openvstorage-webapps: 2.7.6-rev.4320.8c4fb99-1
openvstorage-backend-webapps: 1.7.6-rev.817.91abb7c-1
openvstorage-core: 2.7.6-rev.4320.8c4fb99-1
openvstorage-hc: 1.7.6-rev.817.91abb7c-1
openvstorage: 2.7.6-rev.4320.8c4fb99-1
openvstorage-backend: 1.7.6-rev.817.91abb7c-1
openvstorage-sdm: 1.6.6-rev.445.4216f7e-1

[grimpy]

Issue1 is not a real issue, but a limitation of the UI used for admin portal this will not be possible from the End User UI.

Issue2 is somehow irrelevant its the operators responsibility to enter valid sizes.

[ahsayde]

@john-kheir