How do ScaleIO storage pools work with cinder?

asked 2017-06-07 16:28:19 -0500

mchlumsky gravatar image

From the documentation: https://docs.openstack.org/ocata/config-reference/block-storage/drivers/emc-scaleio-driver.html (https://docs.openstack.org/ocata/conf...)

[scaleio]
volume_driver = cinder.volume.drivers.dell_emc.scaleio.driver.ScaleIODriver
volume_backend_name = scaleio
san_ip = GATEWAY_IP
sio_protection_domain_name = Default_domain
sio_storage_pool_name = Default_pool
sio_storage_pools = Domain1:Pool1,Domain2:Pool2
san_login = SIO_USER
san_password = SIO_PASSWD
san_thin_provision = false

Given the configuration above, all volumes get created in the storage pool Default_pool.

In fact, if Default_pool fills up, volume creation begins to fail with

2017-06-07 20:30:33.508 15819 INFO cinder.volume.drivers.emc.scaleio [req-95dd5ac5-8a9f-4b8f-b4e2-b19b306283a4 6c20cdc6afb344deb2a47ad9b55969a4 c92e2cc91312478db83a753477be715a - default default] Add volume response: {u'errorCode': 67, u'message': u'Insufficient resources', u'httpStatusCode': 500}

What is the purpose of sio_storage_pools ? It seems they are unused.

Is there a way to configure storage pools so that pools that are full are skipped and pools with available capacity are used (when creating volumes)?

edit retag flag offensive close merge delete