, March 26, 2014 22:47
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to
support other iSCSI transports besides TCP
On Wed, Mar 26, 2014 at 12:18 PM, Eric Harney ehar...@redhat.com wrote:
On 03/25/2014 11
Hello, Shlomi.
On Tue, Mar 25, 2014 at 7:07 PM, Shlomi Sasson shlo...@mellanox.com wrote:
I want to share with the community the following challenge:
Currently, Vendors who have their iSCSI driver, and want to add RDMA
transport (iSER), cannot leverage their existing plug-in which inherit
)
Subject: Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support
other iSCSI transports besides TCP
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach to handle this, I already have
the code, should I open a bug or blueprint to track this issue
: Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support
other iSCSI transports besides TCP
On Wed, Mar 26, 2014 at 12:18 PM, Eric Harney
ehar...@redhat.commailto:ehar...@redhat.com wrote:
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach
, Ramy [mailto:ramy.asse...@hp.com]
Sent: Tuesday, March 25, 2014 17:55
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][cinder] Refactor ISCSIDriver to support
other iSCSI transports besides TCP
Hi Shlomi,
Another solution to consider is to create
This all makes sense to me. I would suggest a blueprint and a pull request as
soon as Juno opens.
Vish
On Mar 25, 2014, at 8:07 AM, Shlomi Sasson shlo...@mellanox.com wrote:
Hi,
I want to share with the community the following challenge:
Currently, Vendors who have their iSCSI driver,
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach to handle this, I already have
the code, should I open a bug or blueprint to track this issue?
Best Regards,
Shlomi
A blueprint around this would be appreciated. I have had similar
thoughts
On Wed, Mar 26, 2014 at 12:18 PM, Eric Harney ehar...@redhat.com wrote:
On 03/25/2014 11:07 AM, Shlomi Sasson wrote:
I am not sure what will be the right approach to handle this, I already
have the code, should I open a bug or blueprint to track this issue?
Best Regards,
Shlomi
A
Hi Shlomi,
Another solution to consider is to create a subclass per transport (iSCSI,
iSER) which reference the same shared common code.
This is the solution used for the 3PAR iSCSI FC transports. See these for
reference:
cinder/volume/drivers/san/hp/hp_3par_common.py
