Not all EMC Cinder drivers are on the list

[Evgeniya Shumakher]

According to the list of EMC external CI systems (https://wiki.openstack.org/wiki/ThirdPartySystems):
- emc-vmax-ci
- emc-vnx-ci
- emc-vipr-ci
- emc-xio-ci

And EMC related github repos:
https://github.com/emc-openstack
https://github.com/openstack/cinder/tree/master/cinder/volume/drivers/emc

The following EMC Cinder drivers should be added:
- [in trunk] EMC XtremIO Storage (https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/emc/xtremio.py)
- [in trunk] EMC VNX direct drivers (http://docs.openstack.org/trunk/config-reference/content/emc-vnx-direct-driver.html)
   -- iSCSI Driver for EMC VNX array based on CLI
(https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/emc/emc_cli_iscsi.py)
   -- Fibre Channel Driver for EMC VNX array based on CLI (https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/emc/emc_cli_fc.py).
- [NOT in trunk] EMC ViPR Cinder Driver (https://github.com/emcvipr/controller-openstack-cinder)

Re the Ci's mapping:

Looks like both emc-vmax-ci and emc-vnx-ci test all SMI-S drivers (http://docs.openstack.org/trunk/config-reference/content/emc-smis-driver.html).
emc-vnx-ci tests both direct VNX drivers as well.
But it needs to be checked with EMC team.

[Irina Povolotskaya (ipovolotskaya)]

This issue can be discussed within this bug https://bugs.launchpad.net/driverlog/+bug/1375299

[Xing Yang (xing-yang)]

Here is the update:

emc-vmax-ci (Test EMC VMAX iSCSI and FC drivers)
emc-vnx-ci (Test EMC VNX iSCSI and FC direct drivers)
emc-xio-ci (Test EMC XtremIO iSCSI and FC drivers)

Since ViPR driver is not in the trunk yet, we don't need to add it to the driver log:
emc-vipr-ci

[Evgeniya Shumakher (eshumakher)]

Xing - thank you for the update.
One small comment here. We believe that VIPR driver can be added to DriverLog as well. The 'In trunk?' field will be empty. But as soon as the driver is upstreamed the release name will be added there.
Does it make sense?

[Xing Yang (xing-yang)]

Ok. That's fine. Does the ViPR driver log needs to match what is posted here?

https://github.com/emcvipr/controller-openstack-cinder

I'm asking because this gibhub site has ViPR FC and iSCSI drivers. We were trying to submit an ECS driver as well but that is not released yet.

[Evgeniya Shumakher (eshumakher)]

Xing -

IMO you can add all types of Cinder drivers you have to the DriverLog dashboard.

Just mark them properly:
- If they are upstreamed - list the OpenStack releases supported, if not - do not list.
- If external CI is in place - add a ref to it, it not - do not do it.

Here is the how to: https://wiki.openstack.org/wiki/DriverLog#How_To:_Add_a_new_driver_to_DriverLog

We would really appreciate if you as maintainer did it by yourself. Because you are the owner of the information about EMC Cinder drivers.
We'll be happy to help you here.

[Xing Yang (xing-yang)]

Yes, this is on my TO-DO list but just haven't got to it yet. Is Irina working on it already? If she is, I don't want to do duplicate work. Please let me know. Appreciate your help!

[Irina Povolotskaya (ipovolotskaya)]

Xing,

I believe, you are the best candidate for describing EMC drivers as you know all the details.
I can help you with adding information into the file, if you wish. Would this be useful?

[Xing Yang (xing-yang)]

Hi Irina,

Sure, I'll work on this. Thanks!

[Irina Povolotskaya (ipovolotskaya)]

Xing,

thank you for cooperation!

If you have any questions on the workflow itself, please, don't hesitate to contact me.

[Xing Yang (xing-yang)]

I updated the driver log. Removed the ViPR driver.

https://review.openstack.org/#/c/126167/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/126167
Committed: https://git.openstack.org/cgit/stackforge/driverlog/commit/?id=565b1d7084a9b6285c80119480dd98f12022964c
Submitter: Jenkins
Branch: master

commit 565b1d7084a9b6285c80119480dd98f12022964c
Author: Xing Yang <email address hidden>
Date: Sat Oct 4 16:59:32 2014 -0400

    Update EMC driver log

    Closes-Bug: #1375743
    Change-Id: I3584a633d67ee220427e6e827e78552aeaa1a255