Open Stack

Hi Mike,

This is just a gentle status check from our team:

We are aware of the requirements where the CI needs to report in a 
stable fashion for at least 5 days prior to 4/6/2015. Hence we'd like to 
know if you and the Cinder team have any issue with the current state of 
Oracle ZFSSA CI. We want to handle it immediately and stay complied with 
the requirements.

Thank you,
Diem.


On 03/26/2015 01:28 PM, Diem Tran wrote:
> Hi Mike, The CI has been adjusted to run 304 tests since 3/24/2015 
> evening: 
> https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z
>
> Here are examples of recent success runs:
> https://review.openstack.org/#/c/167080/
> https://review.openstack.org/#/c/165763/
> https://review.openstack.org/#/c/166823/
> https://review.openstack.org/#/c/166689/
> https://review.openstack.org/#/c/167366/
> https://review.openstack.org/#/c/166164/
>
> We delayed our response until now because we want to get proofs of 
> success runs and make sure our CI complies with the requirements. We 
> believe it does now.
>
> Thank you for your contribution and effort in keeping us updated on 
> this matter.
>
> Diem.
> On 03/24/2015 05:28 PM, Mike Perez wrote:
>> On 18:20 Mon 23 Mar     , Diem Tran wrote:
>>> Hello Cinder team,
>>>
>>> Oracle ZFSSA CI has been reporting since March 20th. Below is a link
>>> to the list of results the CI already posted:
>>>
>>> https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z
>>>
>>> Our CI system will be running and reporting results from now on,
>>> hence I kindly request that you accept our CI results and consider
>>> re-integrating our drivers back in Kilo RC.
>>>
>>> If there is any concern, please let us know.
>> Diem,
>>
>> I appreciate your team getting back to us on the CI. It appears your 
>> CI is
>> running 247 tests, when it should be running 304. Please verify 
>> you're running
>> tempest as followed in the instructions here:
>>
>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_tests_do_I_use.3F 
>>
>>
>> Once this issue is resolved, I'll continue to monitor the stability, 
>> and based
>> on that make a decision for readding the driver.
>>
>