Hi Duncan,
We totally understand that CI is not a box ticking exercise, it actually
serves a purpose, and we are fully on board with the need for CI. We
have resources monitoring the CI results and handling failures on daily
basis.
As far as the failures, we have resolved all issues related to our
drivers that occur during the weekend (hence the failures). My
understanding is that some time due to instability of devstack, there
might be intermittent failures not related to out drivers at all, such
as this:
https://review.openstack.org/#/c/168177/
Thanks,
Diem.
On 04/21/2015 03:40 PM, Duncan Thomas wrote:
Can you please investigate and comment here on this thread as to why
your CI is failing for all patches? If this is not resolved, your
driver will not be re-added, and ignoring requests to investigate CI
failures will increase the chances of your driver being removed in
future, without notice. Setting up a CI system is not a box ticking
exercise, it requires monitoring and maintenance. If that is not
possible then you are not yet in a position to be added back into cinder.
On 21 Apr 2015 19:32, "Diem Tran" <[email protected]
<mailto:[email protected]>> wrote:
On 04/21/2015 01:01 PM, Mike Perez wrote:
On 09:57 Apr 21, Mike Perez wrote:
On 15:47 Apr 20, Diem Tran wrote:
Hi Mike,
Oracle ZFSSA iSCSI CI is now reporting test results.
It is configured
to run against the ZFSSA iSCSI driver. You can see the
results here:
https://review.openstack.org/#/q/reviewer:%22Oracle+ZFSSA+CI%22,n,z
Below are some patchsets that the CI reports:
https://review.openstack.org/#/c/168424/
https://review.openstack.org/#/c/168419/
https://review.openstack.org/#/c/175247/
https://review.openstack.org/#/c/175077/
https://review.openstack.org/#/c/163706/
I would like to kindly request you and the core team
to get the
Oracle ZFSSA iSCSI driver re-integrated back to the
Cinder code base.
If there is anything else you need from the CI and the
driver, please
do let me know.
This was done on 4/8:
https://review.openstack.org/#/c/170770/
My mistake this was only the NFS driver. The window to have
drivers readded in
Kilo has long past. Please see:
http://lists.openstack.org/pipermail/openstack-dev/2015-March/059990.html
This will have to be readded in Liberty only at this point.
Thank you for your reply. Could you please let me know the
procedure needed for the driver to be readded to Liberty?
Specifically, will you be the one who upload the revert patchset,
or it is the driver maintainer's responsibility?
Diem.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
[email protected]?subject:unsubscribe
<http://[email protected]?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
