I know I'm arriving late to this thread, but I want to chime in with a
resounding yes! to this approach.
We've held to a fairly strict policy around maintaining compatibility
within the driver API since early on, and we'll continue to do that as
we add new interfaces (see the new
On Sun, Mar 1, 2015 at 8:45 AM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Gary Kotton's message of 2015-03-01 02:32:37 -0800:
Hi,
I am just relaying pain-points that we encountered in neutron. As I have
said below it makes the development process a lot quicker for people
working on
@lists.openstack.orgmailto:
openstack-dev@lists.openstack.o
rg
Date: Saturday, February 28, 2015 at 8:28 AM
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:
openstack-dev@lists.openstack.o
rg
Subject: [openstack-dev] [Ironic] Adding vendor drivers in Ironic
Hello All,
This is about adding
On 02/28/2015 09:36 PM, Ramakrishnan G wrote:
You may not realize you do a disservice to those reading this post and
those reviewing future patches if you set unreasonable expectations.
Telling others that they can expect a patch merged in the same day is
not reasonable, even if that has
On 02/28/2015 07:28 AM, Ramakrishnan G wrote:
Hello All,
Hi!
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers getting added in Ironic which is a
very good thing. But something I noticed is that, most of these reviews
have lots of hardware-specific code
, February 28, 2015 at 8:28 AM
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.o
rg
Subject: [openstack-dev] [Ironic] Adding vendor drivers in Ironic
Hello All,
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers
Excerpts from Gary Kotton's message of 2015-03-01 02:32:37 -0800:
Hi,
I am just relaying pain-points that we encountered in neutron. As I have
said below it makes the development process a lot quicker for people
working on external drivers. I personally believe that it fragments the
community
On 02/28/2015 01:28 AM, Ramakrishnan G wrote:
Hello All,
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers getting added in Ironic which is a
very good thing. But something I noticed is that, most of these reviews
have lots of hardware-specific code in
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Ironic] Adding vendor drivers in Ironic
Hello All,
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers getting added in Ironic which is a very
good thing. But something I
...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Saturday, February 28, 2015 at 8:28 AM
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Ironic] Adding vendor drivers
You may not realize you do a disservice to those reading this post and
those reviewing future patches if you set unreasonable expectations.
Telling others that they can expect a patch merged in the same day is
not reasonable, even if that has been your experience. While we do our
best to
Hello All,
This is about adding vendor drivers in Ironic.
In Kilo, we have many vendor drivers getting added in Ironic which is a
very good thing. But something I noticed is that, most of these reviews
have lots of hardware-specific code in them. This is something most of the
other Ironic
12 matches
Mail list logo
