Open Stack

I request the same consideration for Huawei 18000 iSCSI driver and 18000 FC driver. May I also add it to the meeting agenda?

·         I promise Huawei Volume CI will become stable and reporting stably  before March 31. Our CI will be moved to a more better environment tomorrow<app:ds:tomorrow> or the day after tomorrow<app:ds:the%20day%20after%20tomorrow>.
·         And we also have find out why some times the job will failed. It is because that Jenkins allow the job builds concurrently on the same node by default and this will cause the job building fails. We have changed this to not to build job concurrently on the same node.

So I request the same exemption or FFE for Huawei 18000 iSCSI driver and Huawei 18000 FC driver.

Thanks and best regards,
Liu
·

________________________________
新国刘
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]

Phone:
Fax:
Mobile:
Email:
地址：深圳市龙岗区坂田华为基地 邮编：518129
Huawei Technologies Co., Ltd.
Bantian, Longgang District,Shenzhen 518129, P.R.China
http://www.huawei.com
________________________________
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
发件人: Duncan Thomas [mailto:duncan.thomas at gmail.com]
发送时间: 2015年3月23日 21:28
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

Timothy
You are very welcome to add it to the meeting agenda if you feel it should be discussed - the agenda is open and managed on the wiki.

On 23 March 2015 at 15:15, ClaytonLuce, Timothy <Timothy.ClaytonLuce at netapp.com<mailto:Timothy.ClaytonLuce at netapp.com>> wrote:
Mike,

Did not see a response to this request.  Please respond, we can discuss in the Cinder Core meeting this week.

-----Original Message-----
From: ClaytonLuce, Timothy [mailto:Timothy.ClaytonLuce at netapp.com<mailto:Timothy.ClaytonLuce at netapp.com>]
Sent: Friday, March 20, 2015 5:27 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

Mike,

I request the same consideration being given to the Oracle driver team:

> The tag for Kilo in Cinder has already happened, so it's too late to revert. We
> may be able to revisit this in Kilo RC, but I want to see your CI reporting
> reliably now to then to Cinder reviews.

We are going to try by hook or crook to scrounge/borrow equipment to put a quick and dirty CI together and get it reliably reporting.

Tim
________________________________________
From: Mike Perez <thingee at gmail.com<mailto:thingee at gmail.com>>
Sent: Friday, March 20, 2015 2:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)

On 12:33 Fri 20 Mar     , ClaytonLuce, Timothy wrote:
> I'd like to point out that for NetApp FC drivers NetApp has been in
> discussions and updating progress on these drivers since their submission.
>
> I will point out a discussion in the Nov Core meeting where I brought up the
> challenge around FC environments and the response I received:

<snip>

> NetApp has in good faith been working toward implementing a CI for FC,
> I won't go into the challenges of spending $$ for lab equipment to build out
> a scalable quality CI system but suffice it to say the lab equipment is on
> order and scheduled for arrival the first part of April, at which point we
> can put in place the CI for FC.

1) We've been talking about CI's since Feburary 2014. That's really too bad
   this took so long. The deadline itself has been overly announced on the
   mailing list and Cinder IRC meetings. [1][2][3][4][5][6][7][8]

2) We have a number of FC drivers today that had no problem meeting this
   deadline that was expressed in November 2014.

3) I've barely received updates from Netapp folks on progress here. I'm the
   only point of contact, so if you weren't talking to me, then it's unknown.
   I've expressed this to a number of your engineers and in my announcements
   about the CI deadline [8]

I had to engage with Netapp to get updates, no one came to me with updates. The
last update I heard from one of your engineers was, we bought the hardware,
but it's just sitting there. That is not acceptable with us being past the
deadline, and shows a clear sign of this not being a priority.

> NetApp has been very forthcoming in our progress and have gotten all our
> other CI systems in place for 7-mode iSCSI/NFS, cDOT iSCSI/NFS and E-Series.
>
> I respectfully request that NetApp FC be removed from this list of drivers to
> be removed for Kilo and placed back in the releaes and we can negotiate an
> agreed upon time as to when the CI system for these drivers will be in place.

There will be no negotiating on what is an acceptable timeline for Netapp. What
we all agreed to as a *community* back at the summit and Cinder IRC meeting
was it.


[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
[2] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-21-16.00.log.html
[3] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-04-16.04.log.html
[4] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-18-16.00.log.html
[5] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-25-16.00.log.html
[6] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html
[7] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-18-16.00.log.html
[8] - http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html

--
Mike Perez

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Duncan Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150323/3d3d34a6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6737 bytes
Desc: image001.jpg
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150323/3d3d34a6/attachment.jpg>