Skip to content

Conversation

@wangzhizheng
Copy link

add the terminate_connection in iSCSIDriver for checking if the last
volume is removed. If so, delete the initiator group which mapped with
the volume

add the terminate_connection in iSCSIDriver for checking if the last
volume is removed. If so, delete the initiator group which mapped with
the volume
if return the whole snapshot the snapshot.name will not be able to be
saved and cinder db will not be updated correctly.
Only id and status need to be returned
@wangzhizheng
Copy link
Author

the second commit is for bugfix #5

Copy link
Contributor

@shayh shayh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This flow is problematic,

  1. it will add more command sent to XMS.
  2. not sure what will happen if the last IG volumes terminates the connection and at the same time a new connection get's initialized.

.num_of_mapped_volumes(self._get_ig_name(connector)))
if num_vols > 0:
return
else:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be simpler
if num_vols == 0:
...

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, but if we want to delete the initiator group, there is no other way but send the request to XMS.
It is not an error issue but how XtremIO driver should work.
By the way other storage vendor working like this, this is why I think that we should also work as so. Users maybe use multiple backend storage and keep all the storage have the same work will be friendly to user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants