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