<div dir="ltr"><div>Timothy<br><br></div>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.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 23 March 2015 at 15:15, ClaytonLuce, Timothy <span dir="ltr"><<a href="mailto:Timothy.ClaytonLuce@netapp.com" target="_blank">Timothy.ClaytonLuce@netapp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mike,<br>
<br>
Did not see a response to this request. Please respond, we can discuss in the Cinder Core meeting this week.<br>
<span class="im HOEnZb"><br>
-----Original Message-----<br>
From: ClaytonLuce, Timothy [mailto:<a href="mailto:Timothy.ClaytonLuce@netapp.com">Timothy.ClaytonLuce@netapp.com</a>]<br>
</span><div class="HOEnZb"><div class="h5">Sent: Friday, March 20, 2015 5:27 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)<br>
<br>
Mike,<br>
<br>
I request the same consideration being given to the Oracle driver team:<br>
<br>
> The tag for Kilo in Cinder has already happened, so it's too late to revert. We<br>
> may be able to revisit this in Kilo RC, but I want to see your CI reporting<br>
> reliably now to then to Cinder reviews.<br>
<br>
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.<br>
<br>
Tim<br>
________________________________________<br>
From: Mike Perez <<a href="mailto:thingee@gmail.com">thingee@gmail.com</a>><br>
Sent: Friday, March 20, 2015 2:55 PM<br>
To: OpenStack Development Mailing List (not for usage questions)<br>
Subject: Re: [openstack-dev] [cinder] Request exemption for removal of NetApp FC drivers (no voting CI)<br>
<br>
On 12:33 Fri 20 Mar , ClaytonLuce, Timothy wrote:<br>
> I'd like to point out that for NetApp FC drivers NetApp has been in<br>
> discussions and updating progress on these drivers since their submission.<br>
><br>
> I will point out a discussion in the Nov Core meeting where I brought up the<br>
> challenge around FC environments and the response I received:<br>
<br>
<snip><br>
<br>
> NetApp has in good faith been working toward implementing a CI for FC,<br>
> I won't go into the challenges of spending $$ for lab equipment to build out<br>
> a scalable quality CI system but suffice it to say the lab equipment is on<br>
> order and scheduled for arrival the first part of April, at which point we<br>
> can put in place the CI for FC.<br>
<br>
1) We've been talking about CI's since Feburary 2014. That's really too bad<br>
this took so long. The deadline itself has been overly announced on the<br>
mailing list and Cinder IRC meetings. [1][2][3][4][5][6][7][8]<br>
<br>
2) We have a number of FC drivers today that had no problem meeting this<br>
deadline that was expressed in November 2014.<br>
<br>
3) I've barely received updates from Netapp folks on progress here. I'm the<br>
only point of contact, so if you weren't talking to me, then it's unknown.<br>
I've expressed this to a number of your engineers and in my announcements<br>
about the CI deadline [8]<br>
<br>
I had to engage with Netapp to get updates, no one came to me with updates. The<br>
last update I heard from one of your engineers was, we bought the hardware,<br>
but it's just sitting there. That is not acceptable with us being past the<br>
deadline, and shows a clear sign of this not being a priority.<br>
<br>
> NetApp has been very forthcoming in our progress and have gotten all our<br>
> other CI systems in place for 7-mode iSCSI/NFS, cDOT iSCSI/NFS and E-Series.<br>
><br>
> I respectfully request that NetApp FC be removed from this list of drivers to<br>
> be removed for Kilo and placed back in the releaes and we can negotiate an<br>
> agreed upon time as to when the CI system for these drivers will be in place.<br>
<br>
There will be no negotiating on what is an acceptable timeline for Netapp. What<br>
we all agreed to as a *community* back at the summit and Cinder IRC meeting<br>
was it.<br>
<br>
<br>
[1] - <a href="https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers" target="_blank">https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers</a><br>
[2] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-21-16.00.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-21-16.00.log.html</a><br>
[3] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-04-16.04.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-04-16.04.log.html</a><br>
[4] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-18-16.00.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-18-16.00.log.html</a><br>
[5] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-25-16.00.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-25-16.00.log.html</a><br>
[6] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html</a><br>
[7] - <a href="http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-18-16.00.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-18-16.00.log.html</a><br>
[8] - <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html</a><br>
<br>
--<br>
Mike Perez<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Duncan Thomas</div>
</div>