linbit/openstack-cinder

Openstack Cinder, with DRBD driver included

OpenStack Cinder

OpenStack Cinder is a storage service for an open cloud computing service.

You can learn more about Cinder at:

• Wiki
• Developer Docs
• Blueprints
• Release notes
• Design specifications

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://opendev.org/openstack/cinder

If you'd like to contribute, please see the information in CONTRIBUTING.rst

You can raise bugs on Launchpad

Python client

Python Cinderclient

openstack-cinder's Issues

cinder-volume uses default URI of localhost despite specific URI in cinder.conf

We are currently using LINSTOR controllers in a HA configuration accessible from a floating IP managed by Corosync+Pacemaker.

Our cinder.conf uses the following configuration (organization specific data obfuscated) for the LINSTOR backend:

. . .
[KALMYK]
iscsi_helper = tgtadm
linstor_controller_diskless = False
linstor_default_resource_size = 1
linstor_default_storage_pool_name = KalmykLINSTOR
linstor_default_uri = linstor://XXX.XXX.XXX.6
linstor_default_volume_group = vg_kalmyk_linstor
linstor_volume_downsize_factor = 4096
volume_backend_name = LINSTOR
volume_driver = cinder.volume.drivers.linstordrv.LinstorDrbdDriver
. . .

However, the cinder-volume service ignores the linstor_default_uri specified and defaults to using linstor://localhost, errors-out when unable to do so, and goes into a crash-backoff loop.

We've identified the code responsible for this behavior and prepared a patch/diff file:

linstor.txt

After applying this patch/diff, the cinder-volume service accepts the specified URI and works properly in sending API requests to our controller.

Can these changes be verified?

in-use volume extend support

Hi, it seems that the in-use volume extension doesn't work even though it should work according to docs https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#_using_drbd_as_the_transport_protocol ("Resizing of attached and in-use volumes does not fully work. While the resize itself is successful, the compute service will not propagate it to the VM until after a restart.").

After some digging, it seems it is because you use LocalConnector https://github.com/openstack/os-brick/blob/master/os_brick/initiator/connectors/local.py that doesn't support volume extend.

Are you planning to implement a live extension - possibly in a new connector?

Typo "asssert_called_once_with"