[Third-party-announce] Freescale CI is disabled

Edgar Magana edgar.magana at workday.com
Fri Dec 5 05:14:54 UTC 2014


+1 vote to re-enable Freescale CI. 
Thanks Trinath for all the hard work. 

Edgar


> On Dec 4, 2014, at 8:56 PM, "trinath.somanchi at freescale.com" <trinath.somanchi at freescale.com> wrote:
> 
> Hi-
> 
> I have updated the CI setup and ran two jobs, 
> 
> Please find our CI logs for the commits suggested.
> 
> For Negative Testing:   http://git.freescale.com/openstack_logs/Freescale-ML2-Mechanism-Driver/114629_7_8
> 
> For Normal Testing:  http://git.freescale.com/openstack_logs/Freescale-ML2-Mechanism-Driver/114393_7_9/
> 
> For the Second Job, Freescale-FWaaS-Plugin, Due the improvements to Neutron till date, I'm improving the code to submit. And the Spec for the same is pending at Advances Services split from neutron. I will enable the job once the Spec is approved.
> 
> Kindly help me enable the CI.
> 
> Thanking you all.
> 
> --
> Trinath Somanchi - B39208
> trinath.somanchi at freescale.com | extn: 4048
> 
> -----Original Message-----
> From: trinath.somanchi at freescale.com [mailto:trinath.somanchi at freescale.com] 
> Sent: Wednesday, November 19, 2014 10:29 AM
> To: Announcements for third party CI operators.
> Subject: Re: [Third-party-announce] Freescale CI is disabled
> 
> Hi-
> 
> I have upgraded my CI setup. This time The past errors will not be repeated. We made a monitoring system to review the complete CRD setup and Zuul.
> 
> I'm working on Scenario Tests in CI currently. 
> 
> Kindly help me enable the CI. 
> 
> Will work on sandbox initially and then promote to neutron.
> 
> --
> Trinath Somanchi - B39208
> trinath.somanchi at freescale.com | extn: 4048
> 
> -----Original Message-----
> From: Edgar Magana [mailto:edgar.magana at workday.com]
> Sent: Tuesday, October 28, 2014 9:57 PM
> To: Announcements for third party CI operators.
> Subject: Re: [Third-party-announce] [fslosci] Freescale CI is disabled
> 
> Are you guys considering to include some kind of monitoring system to at least find out those issues before they become really hard to fix.
> Just a suggestion.
> 
> Thanks,
> 
> Edgar
> 
> On 10/27/14, 10:03 PM, "trinath.somanchi at freescale.com"
> <trinath.somanchi at freescale.com> wrote:
> 
>> Hi Kyle, Anita-
>> 
>> With respect to the CI setup , we have a Jenkins Master,  2 Slave nodes 
>> for ML2 MD and another Slave Node for FWaaS Plugin.
>> 
>> I see that one of the Slave nodes is down (Jenkins is unable to reach 
>> the
>> same) But this change is assigned to it to test.
>> 
>> Zuul tried to check the same for  more attempts and was failed.
>> 
>> But I see that, there can be a configuration where the number of 
>> attempts can be configured rather than a irregular one.
>> 
>> Also, In the Jenkins master, I have seen a Zuul-Server crash where it 
>> reported 'Out of Memory' error. The Jenkins master is active with 4GB 
>> RAM. Now (Today) its updated to 8GB RAM.
>> 
>> Now that, I have replaced the faulty slave node with a new once with 
>> 8GB RAM and 500 GB HDD.  I think, it might not cause this issue again 
>> in near future.
>> 
>> Kindly vote me to enable the CI account.
>> 
>> --
>> Trinath Somanchi - B39208
>> trinath.somanchi at freescale.com | extn: 4048
>> 
>> -----Original Message-----
>> From: OpenStack Freescale CI [mailto:fslosci at freescale.com]
>> Sent: Monday, October 27, 2014 7:00 PM
>> To: Announcements for third party CI operators.
>> Subject: Re:[fslosci] [Third-party-announce] Freescale CI is disabled
>> 
>> *******************************************************
>> This Message was Posted by:
>> third-party-announce-bounces+fslosci=freescale.com at lists.openstack.org
>> *******************************************************
>> 
>> 
>>> On Sat, Oct 25, 2014 at 11:27 AM, Anita Kuno <anteaya at anteaya.info> wrote:
>>> https://review.openstack.org/#/c/99522/8
>>> 
>>> I am at a loss for words.
>>> 
>>> I am going to need a fairly large contingent of Neutron as 
>>> ambassadors  on this account's behalf before it gets any privileges 
>>> with gerrit again.
>> Yikes, that looks like a catastrophic failure. I'll see if Trinaths 
>> reaches out and try to understand what's happening here.
>> 
>> Thanks,
>> Kyle
>> 
>>> Anita.
>>> 
>>> _______________________________________________
>>> Third-party-announce mailing list
>>> Third-party-announce at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-annou
>>> n
>>> ce
>> 
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announc
>> e
>> 
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announc
>> e
> 
> 
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
> 
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
> 
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce



More information about the Third-party-announce mailing list