<div dir="ltr"><div><div><div><div><div>Hi Trinath,<br><br></div>you can find more info about third party testing here [1]<br></div>Every new driver or plugin is required to provide a testing system that will test new patches and post <br>
</div>a +1/-1 to Gerrit .<br>
</div>There were meetings organized by Kyle to talk about how to set up the system [2]<br></div>It will probably help you if you read the logs of the meeting.<br><div><br><div><div><div>cheers,<br><br></div><div>Rossella<br>
</div><div><br>[1] <a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements" target="_blank">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Testing_Requirements</a><br>
[2] <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-December/021882.html">http://lists.openstack.org/pipermail/openstack-dev/2013-December/021882.html</a><br></div></div></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Jan 29, 2014 at 7:50 AM, <a href="mailto:trinath.somanchi@freescale.com">trinath.somanchi@freescale.com</a> <span dir="ltr"><<a href="mailto:trinath.somanchi@freescale.com" target="_blank">trinath.somanchi@freescale.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Akihiro-<br>
<br>
What kind of third party testing is required?<br>
<br>
I have written the driver, unit test case and checked the driver with tempest testing.<br>
<br>
Do I need to check with any other third party testing?<br>
<div class="im HOEnZb"><br>
Kindly help me in this regard.<br>
<br>
--<br>
Trinath Somanchi - B39208<br>
<a href="mailto:trinath.somanchi@freescale.com">trinath.somanchi@freescale.com</a> | extn: 4048<br>
<br>
-----Original Message-----<br>
</div><div class="HOEnZb"><div class="h5">From: Akihiro Motoki [mailto:<a href="mailto:motoki@da.jp.nec.com">motoki@da.jp.nec.com</a>]<br>
Sent: Friday, January 24, 2014 6:41 PM<br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Cc: <a href="mailto:kmestery@cisco.com">kmestery@cisco.com</a><br>
Subject: Re: [openstack-dev] [Neutron]Contributing code to Neutron (ML2)<br>
<br>
Hi Trinath,<br>
<br>
Jenkins is not directly related to proposing a new code.<br>
The process to contribute the code is described in the links Andreas pointed. There is no difference even if you are writing a new ML2 mech driver.<br>
<br>
In addition to the above, Neutron now requires a third party testing for all new/existing plugins and drivers [1].<br>
Are you talking about third party testing for your ML2 mechanism driver when you say "Jenkins"?<br>
<br>
Both two things can be done in parallel, but you need to make your third party testing ready before merging your code into the master repository.<br>
<br>
[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-November/019219.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2013-November/019219.html</a><br>
<br>
Thanks,<br>
Akihiro<br>
<br>
(2014/01/24 21:42), <a href="mailto:trinath.somanchi@freescale.com">trinath.somanchi@freescale.com</a> wrote:<br>
> Hi Andreas -<br>
><br>
> Thanks you for the reply.. It helped me understand the ground work<br>
> required.<br>
><br>
> But then, I'm writing a new Mechanism driver (FSL SDN Mechanism<br>
> driver) for ML2.<br>
><br>
> For submitting new file sets, can I go with GIT or require Jenkins for<br>
> the adding the new code for review.<br>
><br>
> Kindly help me in this regard.<br>
><br>
> --<br>
> Trinath Somanchi - B39208<br>
> <a href="mailto:trinath.somanchi@freescale.com">trinath.somanchi@freescale.com</a> | extn: 4048<br>
><br>
> -----Original Message-----<br>
> From: Andreas Jaeger [mailto:<a href="mailto:aj@suse.com">aj@suse.com</a>]<br>
> Sent: Friday, January 24, 2014 4:54 PM<br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> Cc: Kyle Mestery (kmestery)<br>
> Subject: Re: [openstack-dev] [Neutron]Contributing code to Neutron<br>
> (ML2)<br>
><br>
> On 01/24/2014 12:10 PM, <a href="mailto:trinath.somanchi@freescale.com">trinath.somanchi@freescale.com</a> wrote:<br>
>> Hi-<br>
>><br>
>><br>
>><br>
>> Need support for ways to contribute code to Neutron regarding the ML2<br>
>> Mechanism drivers.<br>
>><br>
>><br>
>><br>
>> I have installed Jenkins and created account in github and launchpad.<br>
>><br>
>><br>
>><br>
>> Kindly guide me on<br>
>><br>
>><br>
>><br>
>> [1] How to configure Jenkins to submit the code for review?<br>
>><br>
>> [2] What is the process involved in pushing the code base to the main<br>
>> stream for icehouse release?<br>
>><br>
>><br>
>><br>
>> Kindly please help me understand the same..<br>
><br>
> Please read this wiki page completely, it explains the workflow we use.<br>
><br>
> <a href="https://wiki.openstack.org/wiki/GerritWorkflow" target="_blank">https://wiki.openstack.org/wiki/GerritWorkflow</a><br>
><br>
> Please also read the general intro at<br>
> <a href="https://wiki.openstack.org/wiki/HowToContribute" target="_blank">https://wiki.openstack.org/wiki/HowToContribute</a><br>
><br>
> Btw. for submitting patches, you do not need a local Jenkins running,<br>
><br>
> Welcome to OpenStack, Kyle!<br>
><br>
> Andreas<br>
> --<br>
> Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica: jaegerandi<br>
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272<br>
> A126<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>