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.claytonl...@netapp.com]
Sent: Friday, March 20, 2015 5:27 PM
To: OpenStack Development Mailing List (not for
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.claytonl...@netapp.com wrote:
Mike,
Did not see a response to this request. Please respond,
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
tomorrowapp:ds:tomorrow
On 13:15 Mon 23 Mar , ClaytonLuce, Timothy wrote:
Mike,
Did not see a response to this request. Please respond, we can discuss in
the Cinder Core meeting this week.
Which request? I already responded to your message:
I disagree with your assertion that NetApp has ignored this for a year and we
are being inconsiderate of the community. The specific drivers (FC) we are
discussing were added in the Kilo-1 period, so since Dec. and are net new
drivers. All other NetApp drivers have had corresponding CI in
On 17:23 Mon 23 Mar , ClaytonLuce, Timothy wrote:
I disagree with your assertion that NetApp has ignored this for a year and we
are being inconsiderate of the community. The specific drivers (FC) we are
discussing were added in the Kilo-1 period, so since Dec. and are net new
drivers.
Hi Mike,
I think what we are talking is huawei-volume-ci, not huawei-ci. It is
huawei-volume-ci that is on behalf of huawei 18000 iSCSI and huawei 18000 FC
driver.
Regarding to only report failures when a patch really does break your
integration, I think huawei-volume-ci probaly should be
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:
16:10:44
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
Ditto for Huawei.
While we are not *reliably* reporting, we are reporting and the necessary steps
have already been taken (and more importantly, approved) to get this reliably
working ASAP.
We respectfully request the same consideration for our cinder drivers.
--Rocky (as proxy for Liu
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
On 21:53 Fri 20 Mar , Rochelle Grober wrote:
Ditto for Huawei.
While we are not *reliably* reporting, we are reporting and the necessary
steps have already been taken (and more importantly, approved) to get this
reliably working ASAP.
We respectfully request the same consideration
12 matches
Mail list logo
