Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

[Octavian Ciuhandu]

Thank you for your help on this,

Octavian.

From: Duncan Thomas
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, 1 September 2015 14:48
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] FW: [cinder] Microsoft CI Still Disabled

Mike is on vacation at the moment, somebody else will evaluate in his stead as 
reply here shortly

On 1 September 2015 at 14:20, Octavian Ciuhandu 
mailto:ociuha...@cloudbasesolutions.com>> 
wrote:
Hi Mike,

I think the first mail was sent only on openstack-dev. We have had already over
a week of reliable results on the Microsoft Cinder CI on all three jobs, we have
an updated set of results available at [1].

Please re-evaluate the activity of our CI and re-enable the gerrit account.

Thank you,

Octavian.

[1]: http://paste.openstack.org/show/437509/





On 24/8/15 20:19, "Octavian Ciuhandu" 
mailto:ociuha...@cloudbasesolutions.com>> 
wrote:

>Hi Mike,
>
>We have stabilised the Microsoft Cinder CI and ensured dry-runs testing over
>the past days.
>
>The reason why we didnt report earlier on the status is that we were waiting
>for the completion of a series of hardware maintenance activities performed in
>the Microsoft datacenter where the CI is running, as metioned by Hashir in the
>previous email.
>
>In the meantime we also improved the CI software infrastructure, including:
>
>1. Adding local pip and deb cache servers to reduce transient package download
>issues 2. Improved resiliency in the under and overcloud deployment scripts [1]
>3. Improved monitoring to reduce the respose time on transient issues,
>especially for undercloud networking which was the source of a significant
>amount of failures due to a switch misconfiguration in the datacenter, recently
>identified and solved.
>
>We have a list of recent runs for all 3 drivers available at [2].
>
>Please let us know if there’s anything else that prevents re-enabling the
>Microsoft Cinder CI account.
>
>Thank you,
>
>Octavian.
>
>[1]: https://github.com/cloudbase/cinder-ci
>[2]: http://paste.openstack.org/show/426144/
>
>
>
>
>
>
>On 24/8/15 16:48, "Hashir Abdi" 
>mailto:ha...@microsoft.com>> wrote:
>
>>Mike:
>>
>>Apologies for the delayed response.
>>
>>We have been addressing bug-fixes and infrastructure changes for our CI, 
>>while working through vacation schedules.
>>
>>We have now been able to conduct successful dry runs of our CI, and I'll let 
>>Octavian follow up here with those latest successful results.
>>
>>Sincerely
>>
>>Hashir Abdi
>>
>>Principal Software Engineering Manager
>>Microsoft
>>
>>
>>
>>
>>
>>
>>
>>-Original Message-
>>From: Mike Perez [mailto:thin...@gmail.com<mailto:thin...@gmail.com>]
>>Sent: Friday, August 21, 2015 8:39 PM
>>To: OpenStack Development Mailing List 
>>mailto:openstack-dev@lists.openstack.org>>
>>Cc: Microsoft Cinder CI 
>>mailto:microsoft_cinder...@microsoft.com>>;
>> Octavian Ciuhandu 
>>mailto:ociuha...@cloudbasesolutions.com>>
>>Subject: [cinder] Microsoft CI Still Disabled
>>
>>The Microsoft CI has been disabled since July 22nd [1].
>>
>>Last I heard from the Cinder midcycle sprint, this CI was still not ready and 
>>it hasn't been for 30 days now.
>>
>>Where are we with things, and why has communication been so poor with the 
>>Cloud Base solutions team?
>>
>>[1] - 
>>https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.openstack.org%2fpipermail%2fthird-party-announce%2f2015-July%2f000249.html&data=01%7c01%7chabdi%40exchange.microsoft.com%7c33ba5a82486e4dc6d06508d2aa8a115d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mPalAeUjUVBu9sVn6fDnehA4TN3uZOUB4DAKS6qcFaU%3d
>>
>>--
>>Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
--
Duncan Thomas
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] FW: [cinder] Microsoft CI Still Disabled

[Octavian Ciuhandu]

Hi Mike,

I think the first mail was sent only on openstack-dev. We have had already over 
a week of reliable results on the Microsoft Cinder CI on all three jobs, we 
have 
an updated set of results available at [1].

Please re-evaluate the activity of our CI and re-enable the gerrit account.

Thank you,

Octavian.

[1]: http://paste.openstack.org/show/437509/





On 24/8/15 20:19, "Octavian Ciuhandu"  wrote:

>Hi Mike,
>
>We have stabilised the Microsoft Cinder CI and ensured dry-runs testing over
>the past days.
>
>The reason why we didnt report earlier on the status is that we were waiting 
>for the completion of a series of hardware maintenance activities performed in 
>the Microsoft datacenter where the CI is running, as metioned by Hashir in the
>previous email.
>
>In the meantime we also improved the CI software infrastructure, including:
>
>1. Adding local pip and deb cache servers to reduce transient package download
>issues 2. Improved resiliency in the under and overcloud deployment scripts [1]
>3. Improved monitoring to reduce the respose time on transient issues,
>especially for undercloud networking which was the source of a significant
>amount of failures due to a switch misconfiguration in the datacenter, recently
>identified and solved.
>
>We have a list of recent runs for all 3 drivers available at [2].
>
>Please let us know if there’s anything else that prevents re-enabling the 
>Microsoft Cinder CI account.
>
>Thank you,
>
>Octavian.
>
>[1]: https://github.com/cloudbase/cinder-ci
>[2]: http://paste.openstack.org/show/426144/
>
>
>
>
>
>
>On 24/8/15 16:48, "Hashir Abdi"  wrote:
>
>>Mike:
>>
>>Apologies for the delayed response.
>>
>>We have been addressing bug-fixes and infrastructure changes for our CI, 
>>while working through vacation schedules.
>>
>>We have now been able to conduct successful dry runs of our CI, and I'll let 
>>Octavian follow up here with those latest successful results.
>>
>>Sincerely
>>
>>Hashir Abdi
>>
>>Principal Software Engineering Manager
>>Microsoft
>>
>>
>>
>>
>>
>>
>>
>>-Original Message-
>>From: Mike Perez [mailto:thin...@gmail.com]
>>Sent: Friday, August 21, 2015 8:39 PM
>>To: OpenStack Development Mailing List 
>>Cc: Microsoft Cinder CI ; Octavian 
>>Ciuhandu 
>>Subject: [cinder] Microsoft CI Still Disabled
>>
>>The Microsoft CI has been disabled since July 22nd [1].
>>
>>Last I heard from the Cinder midcycle sprint, this CI was still not ready and 
>>it hasn't been for 30 days now.
>>
>>Where are we with things, and why has communication been so poor with the 
>>Cloud Base solutions team?
>>
>>[1] - 
>>https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.openstack.org%2fpipermail%2fthird-party-announce%2f2015-July%2f000249.html&data=01%7c01%7chabdi%40exchange.microsoft.com%7c33ba5a82486e4dc6d06508d2aa8a115d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mPalAeUjUVBu9sVn6fDnehA4TN3uZOUB4DAKS6qcFaU%3d
>>
>>--
>>Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] Microsoft CI Still Disabled

[Octavian Ciuhandu]

Hi Mike,

We have stabilised the Microsoft Cinder CI and ensured dry-runs testing over
the past days.

The reason why we didnt report earlier on the status is that we were waiting 
for the completion of a series of hardware maintenance activities performed in 
the Microsoft datacenter where the CI is running, as metioned by Hashir in the
previous email.

In the meantime we also improved the CI software infrastructure, including:

1. Adding local pip and deb cache servers to reduce transient package download
issues 2. Improved resiliency in the under and overcloud deployment scripts [1]
3. Improved monitoring to reduce the respose time on transient issues,
especially for undercloud networking which was the source of a significant
amount of failures due to a switch misconfiguration in the datacenter, recently
identified and solved.

We have a list of recent runs for all 3 drivers available at [2].

Please let us know if there’s anything else that prevents re-enabling the 
Microsoft Cinder CI account.

Thank you,

Octavian.

[1]: https://github.com/cloudbase/cinder-ci
[2]: http://paste.openstack.org/show/426144/






On 24/8/15 16:48, "Hashir Abdi"  wrote:

>Mike:
>
>Apologies for the delayed response.
>
>We have been addressing bug-fixes and infrastructure changes for our CI, while 
>working through vacation schedules.
>
>We have now been able to conduct successful dry runs of our CI, and I'll let 
>Octavian follow up here with those latest successful results.
>
>Sincerely
>
>Hashir Abdi
>
>Principal Software Engineering Manager
>Microsoft
>
>
>
>
>
>
>
>-Original Message-
>From: Mike Perez [mailto:thin...@gmail.com]
>Sent: Friday, August 21, 2015 8:39 PM
>To: OpenStack Development Mailing List 
>Cc: Microsoft Cinder CI ; Octavian Ciuhandu 
>
>Subject: [cinder] Microsoft CI Still Disabled
>
>The Microsoft CI has been disabled since July 22nd [1].
>
>Last I heard from the Cinder midcycle sprint, this CI was still not ready and 
>it hasn't been for 30 days now.
>
>Where are we with things, and why has communication been so poor with the 
>Cloud Base solutions team?
>
>[1] - 
>https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.openstack.org%2fpipermail%2fthird-party-announce%2f2015-July%2f000249.html&data=01%7c01%7chabdi%40exchange.microsoft.com%7c33ba5a82486e4dc6d06508d2aa8a115d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mPalAeUjUVBu9sVn6fDnehA4TN3uZOUB4DAKS6qcFaU%3d
>
>--
>Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] Report Status of Microsoft iSCSI CI

[Octavian Ciuhandu]

Hello Cinder team,

Please find below CI reports for the Microsoft iSCSI CI. It executes 304 tests, 
out if which 9 are skipped and 295 successful.

https://review.openstack.org/#/c/144409/
https://review.openstack.org/#/c/144739/
https://review.openstack.org/#/c/154350/
https://review.openstack.org/#/c/155607/
https://review.openstack.org/#/c/161328/
https://review.openstack.org/#/c/161363/
https://review.openstack.org/#/c/161400/
https://review.openstack.org/#/c/162927/
https://review.openstack.org/#/c/163232/
https://review.openstack.org/#/c/163910/
https://review.openstack.org/#/c/164527/
https://review.openstack.org/#/c/166066/
https://review.openstack.org/#/c/166164/
https://review.openstack.org/#/c/167978/
https://review.openstack.org/#/c/169653/
https://review.openstack.org/#/c/169781/
https://review.openstack.org/#/c/169831/
https://review.openstack.org/#/c/169915/
https://review.openstack.org/#/c/16/
https://review.openstack.org/#/c/17/
https://review.openstack.org/#/c/170770/ 

We are constantly looking at the CI status and try to respond as soon as 
possible to any failure, to ensure the CI stability.

If there is any issue with the CI or with the reporting, please let us know.

Thank you,

Octavian.

smime.p7s
Description: S/MIME cryptographic signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Hyper-V CI missing logs

[Octavian Ciuhandu]

Hi all,

We have experienced a severe hardware failure and the storage for the logs of 
the CI runs was also being affected. We have recovered all that could be saved 
on the new dedicated server. 

If you find any patchset that has the logs missing, please issue a “check 
hyper-v” command to generate a new run and ensure that the latest logs will be 
present. 

Please let us know of any other issues you might have regarding the Hyper-V CI.

Thanks,

Octavian.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] False Positive testing for 3rd party CI

[Octavian Ciuhandu]

Hi,

On 21 Feb 2014, at 20:34, Aaron Rosen 
mailto:aaronoro...@gmail.com>> wrote:

Hi,

Yesterday, I pushed a patch to review and was surprised that several of the 
third party CI systems reported back that the patch-set worked where it 
definitely shouldn't have. Anyways, I tested out my theory a little more and it 
turns out a few of the 3rd party CI systems for neutron are just returning  
SUCCESS even if the patch set didn't run successfully 
(https://review.openstack.org/#/c/75304/).

Here's a short summery of what I found.

Hyper-V CI -- This seems like an easy fix as it's posting "build succeeded" but 
also puts to the side "test run failed". Would probably be a good idea to 
remove the "build succeeded" message to avoid any confusion.

The Hyper-V CI is non-voting (as required for new third-party CIs) and this is 
the reason why any post from it will show “build succeeded”. As published in 
other threads, AFAIK the only way to get rid of this issue is to have the CI as 
voting.

Brocade CI - From the log files it posts it shows that it tries to apply my 
patch but fails:


2014-02-20 20:23:48 + cd /opt/stack/neutron
2014-02-20 20:23:48 + git fetch 
https://review.openstack.org/openstack/neutron.git refs/changes/04/75304/1
2014-02-20 20:24:00 From https://review.openstack.org/openstack/neutron
2014-02-20 20:24:00  
* branchrefs/changes/04/75304/1 -> FETCH_HEAD
2014-02-20 20:24:00 + git checkout FETCH_HEAD
2014-02-20 20:24:00 error: Your local changes to the following files would be 
overwritten by checkout:
2014-02-20 20:24:00 etc/neutron/plugins/ml2/ml2_conf_brocade.ini
2014-02-20 20:24:00 neutron/plugins/ml2/drivers/brocade/mechanism_brocade.py
2014-02-20 20:24:00 Please, commit your changes or stash them before you can 
switch branches.
2014-02-20 20:24:00 Aborting
2014-02-20 20:24:00 + cd /opt/stack/neutron

but still continues running (without my patchset) and reports success. -- This 
actually looks like a devstack bug  (i'll check it out).

PLUMgrid CI - Seems to always vote +1 without a failure 
(https://review.openstack.org/#/dashboard/10117) though the logs are private so 
we can't really tell whats going on.

I was thinking it might be worth while or helpful to have a job that tests that 
CI is actually fails when we expect it to.

Best,

Aaron

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Thanks,

Octavian.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev