multiple-backends configured hit the storwize ssh limitation

Bug #1335722 reported by TaoBai
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
TaoBai

Bug Description

The storwize has a limitation that within 1 second can't burst more than 3 ssh connection to avoid hacker attack.
If configure more than 3 backends(pools) from the same storwize, each backend will start a new cinder-volume service and create new ssh connection. Then it will hit the storwize limiation.

I know is a feature in progress may solve this problem.
https://etherpad.openstack.org/p/cinder-pool-impl-comparison

I create this to see what we can do before this feature be finished

Revision history for this message
Huang Zhiteng (zhiteng-huang) wrote :

This doesn't seem like a Cinder bug. I'd call it a Storwize bug/issue/limitation instead.

Changed in cinder:
status: New → Invalid
Revision history for this message
Jakub Pavlik (pavlk-jakub) wrote :

Is there posibillity how to start each ssh session into storwize with 1 sec delay?

Revision history for this message
Jay Bryant (jsbryant) wrote :

Tao,

Wasn't that a workaround that had been tried was to put a 1 second sleep in? I think that it taking that approach for now is acceptable. Shouldn't be a notable performance impact.

Revision history for this message
TaoBai (baitao2020) wrote :

Hi Jay
Thanks for your comments, that's also what I thought. I will do it.

Revision history for this message
Jason Ni (jason-ni-py) wrote :

As it's a workaround, I think it would be good to expose a switch in conf file that enable users to have the choice.

Revision history for this message
TaoBai (baitao2020) wrote :

Hi ZhiTeng
After consideration, I will change the status from In progress to new. Because I will use this ticket to follow storwize driver change. let me know, if you still can't agree. You are also welcome to review the code change
Thanks.

Changed in cinder:
assignee: nobody → TaoBai (baitao2020)
status: Invalid → In Progress
Revision history for this message
TaoBai (baitao2020) wrote :

Hi Jason

I don't think we need change the cinder.conf. It affect every storwize driver user when setup more than 3 backend. And the change will only influence storwize driver

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/104137

tags: added: drivers storwize-svc
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/104137
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=776c94a8a3f49370a519e4ca92fb3071fc86e262
Submitter: Jenkins
Branch: master

commit 776c94a8a3f49370a519e4ca92fb3071fc86e262
Author: Tao Bai <email address hidden>
Date: Wed Jul 2 03:17:50 2014 -0700

    Slow down Storwize driver initialization

    Storwize has the limitation that can not burst more than
    3 new ssh connection within 1 second.So slow down storwize
    driver initialization.

    Closes-Bug: #1335722
    Change-Id: Id442cd6421ef23b953a3cb45a5f6dd6969064a6e

Changed in cinder:
status: In Progress → Fix Committed
Changed in cinder:
milestone: none → juno-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: juno-2 → 2014.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (master)

Change abandoned by Mike Perez (<email address hidden>) on branch: master
Review: https://review.openstack.org/134147
Reason: No activity for over a month.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.