Re: [openstack-dev] [Ironic] Third-party drivers and testing

2014-01-21 Thread Devananda van der Veen
On Sun, Jan 19, 2014 at 7:47 PM, Christopher Yeoh cbky...@gmail.com wrote: On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen devananda@gmail.com wrote: 1. each driver must adhere to the existing driver interfaces. 2. each driver must have comprehensive unit test coverage and

Re: [openstack-dev] [Ironic] Third-party drivers and testing

2014-01-21 Thread Devananda van der Veen
On Mon, Jan 20, 2014 at 8:29 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, Jan 19, 2014 at 2:47 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all, I've been thinking about how we should treat third-party drivers in Ironic for a while, and had several discussions at the

Re: [openstack-dev] [Ironic] Third-party drivers and testing

2014-01-20 Thread Jay Pipes
On Sun, Jan 19, 2014 at 2:47 PM, Devananda van der Veen devananda@gmail.com wrote: Hi all, I've been thinking about how we should treat third-party drivers in Ironic for a while, and had several discussions at the Hong Kong summit and last week at LCA. Cinder, Nova, Neutron, and TripleO

[openstack-dev] [Ironic] Third-party drivers and testing

2014-01-19 Thread Devananda van der Veen
Hi all, I've been thinking about how we should treat third-party drivers in Ironic for a while, and had several discussions at the Hong Kong summit and last week at LCA. Cinder, Nova, Neutron, and TripleO are all having similar discussions, too. What follows is a summary of my thoughts and a

Re: [openstack-dev] [Ironic] Third-party drivers and testing

2014-01-19 Thread Christopher Yeoh
On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen devananda@gmail.com wrote: 1. each driver must adhere to the existing driver interfaces. 2. each driver must have comprehensive unit test coverage and sufficient inline documentation. 3. vendors are responsible for fixing bugs in