Open shan-wan opened 8 years ago
This is determined by ScaleIO architecture. Not a Cinder bug.
If you set sio_round_volume_capacity = False in cinder.conf, it should fail at creation.
Extend volume will succeed regardless and a warning will be logged if sio_round_volume_capacity is set to False.
Description:
cinder create/extend should follow the storage properties. Scaleio volume must be a positive number in granularity of 8 GB. But 'cinder create 1' creates a 1G volume although it uses 8G backend lun. And to extend this 1GB volume, at least 16G grow-to size must be specified.
Project:
Openstack
Project Area:
Openstack cinder
Release:
Openstack master branch
Severity:
S1
Full Details:
Test Environment and PreCondtion:
Devstack deployed Openstack environment
Detailed Test Steps:
In this case, user only need <= 8G space, but cinder extend at least 16. This way to use storage is wasty, we should follow the scaleio storage lun size maybe.
cinder log:
Expected Results:
'cinder create 1' on ScaleIO backend should:
Actual results:
'cinder create 1' on ScaleIO creates a 1G volume but uses 8G backend storage.
Problem details:
Support Materials: