Re: [openstack-dev] [Neutron] New plug-ins requirements

2013-11-15 Thread Mark McClain 

On Nov 14, 2013, at 2:02 AM, Edgar Magana emag...@plumgrid.com wrote:
 
 I do agree with you. When I said in my first email little bit of guidance I 
 mean the policy for Icehouse and moving forward. I do not want to make our 
 PTL angry  :-)

I wouldn’t worry about making me angry.  I officiated football (soccer) for 
many years.  It takes a lot to make me angry :)


 
 Mark,
 
 I hope you can commend on this thread, otherwise I will bring this topic on 
 our next IRC meeting.
 
 Thanks,
 

I’ve posted the policy in a separate thread.  If there are any questions, feel 
free to ask in that thread and we’ll be able to  clarify and additional details 
to the wiki version so that they documented for everyone in the community. This 
already a planned agenda item for Monday’s team meeting too.

mark



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

Re: [openstack-dev] [Neutron] New plug-ins requirements

2013-11-15 Thread Russell Bryant 
On 11/12/2013 10:15 AM, Kyle Mestery (kmestery) wrote:
 On Nov 12, 2013, at 2:46 AM, Robert Collins robe...@robertcollins.net wrote:
 On 12 November 2013 21:15, Edgar Magana emag...@plumgrid.com wrote:
 Team,

 It has been decided during the Icehouse summit that all vendor specific
 plug-ins should enforce remote tempest tests:
 http://ci.openstack.org/third_party.html

 I would like to understand if we will apply this rule for any new plug-in
 during Icehouse or we will start applying this new requirement until J
 timeframe.

 I can't comment on when - thats a Neutron dev decision, but I heartily
 endorse getting all code paths tested asap :).

 My personal opinion is if we are going to require all existing Neutron 
 plugins to
 have valid smokestack tests by Icehouse-2, then any new plugins should not
 be allowed into the tree without those tests. This includes new Modular Layer 
 2
 MechanismDrivers as well.

A bit of a terminology nit ... SmokeStack is a specific system that runs
tests and reports results back to gerrit.  Presumably the requirement is
to be *like* SmokeStack, but not be integrated with SmokeStack itself.

-- 
Russell Bryant

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

Re: [openstack-dev] [Neutron] New plug-ins requirements

2013-11-13 Thread Salvatore Orlando 
I reckon we should wait a little for the PTL to propose a draft of the
policy we can comment on.

'thirdy paty test' probably was meant as integration with gerrit (
http://ci.openstack.org/third_party.html); the test suite to be executed
is, obviously, the tempest test suite.
In my opinion, the policy will define criteria for acceptability of skipped
tests and ability of adding plugin-specific tests.

Regards,
Salvatore


On 12 November 2013 15:15, Kyle Mestery (kmestery) kmest...@cisco.comwrote:

 On Nov 12, 2013, at 2:46 AM, Robert Collins robe...@robertcollins.net
 wrote:
  On 12 November 2013 21:15, Edgar Magana emag...@plumgrid.com wrote:
  Team,
 
  It has been decided during the Icehouse summit that all vendor specific
  plug-ins should enforce remote tempest tests:
  http://ci.openstack.org/third_party.html
 
  I would like to understand if we will apply this rule for any new
 plug-in
  during Icehouse or we will start applying this new requirement until J
  timeframe.
 
  I can't comment on when - thats a Neutron dev decision, but I heartily
  endorse getting all code paths tested asap :).
 
 My personal opinion is if we are going to require all existing Neutron
 plugins to
 have valid smokestack tests by Icehouse-2, then any new plugins should not
 be allowed into the tree without those tests. This includes new Modular
 Layer 2
 MechanismDrivers as well.

  I do believe that should enforce this new requirement ASAP but I also
  believe that we need to provide a little bit more of guidance on this
  process.
  So, Besides the above mentioned wiki, is there any more information
 that we
  can provide about this new requirement? I think we should update Neutron
  wiki with this information.
  If somebody is very familiar with the process will be interested in
 posting
  their input on this thread.
 
  I think the requirement of 'use third party tests' is confusing goal
  with implementation: the goal should be that 'all vendor plugins be CI
  tested at verification level at minimum'. This leaves room for gate
  based testing of such plugins too, if the vendor steps up and meets
  the requirements to have their plugin be gate checked - which is
  superior to merely doing verification checks.
 
  -Rob




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

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