Hi Trinath,
I think the vendor company has many experts to review their codes. They can
do it well.
But I still have some comments inline.
Germy
On Thu, Sep 18, 2014 at 1:42 PM, trinath.soman...@freescale.com
trinath.soman...@freescale.com wrote:
Though Code reviews for vendor code takes
Hi Salvatore,
Thanks for your hyperlink. It's really a monster thread that contains
everyone's opinion. But it's useful to me.
So, Before we focus on the Neutron core itself, we should firstly release a
suite standardized APIs and a framework for vendors' codes.
About this job, I think most of it
+1
I don't think it will be seen as punitive. Vendors can write their plugins
or drivers when a deal occurs and they do not need to submit code to
community and wait for approving.
Being a third party vendor, i do not think this is punitive. OpenStack has
already established through
]
Sent: Thursday, September 18, 2014 11:01 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: tanny...@huawei.com
Subject: Re: [openstack-dev] [Neutron][Architecture]Suggestions for the third
vendors' plugin and driver
+1
I don't think it will be seen as punitive. Vendors can
Obviously, to a vendor's plugin/driver, the most important thing is API.Yes?
NB API for a monolithic plugin or a service plugin and SB API for a service
driver or agent, even MD. That's the basic.
Now we have released a set of NB APIs with relative stability. The SB APIs'
standardization are
This is a very important discussion - very closely related to the one going
on in this other thread
http://lists.openstack.org/pipermail/openstack-dev/2014-September/045768.html
.
Unfortunately it is also a discussion that tends to easily fragment and
move in a thousand different directions.
A few
: Kevin Benton [mailto:blak...@gmail.com]
Sent: Friday, September 12, 2014 12:19 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: tanny...@huawei.com
Subject: Re: [openstack-dev] [Neutron][Architecture]Suggestions for the third
vendors' plugin and driver
So my suggestion
On Fri, Sep 12, 2014 at 11:11 AM, Kevin Benton blak...@gmail.com wrote:
Maybe I missed something, but what's the solution?
There isn't one yet. That's why it's going to be discussed at the summit.
So my suggestion is remove all vendors' plugins and drivers except
opensource as built-in.
By
So my suggestion is remove all vendors' plugins and drivers except
opensource as built-in.
Yes, I think this is currently the view held by the PTL (Kyle) and some of
the other cores so what you're suggesting will definitely come up at the
summit.
Why do we need a different repo to store
This has been brought up several times already and I believe is going to be
discussed at the Kilo summit.
I agree that reviewing third party patches eats community time. However,
claiming that the community pays 46% of it's energy to maintain
vendor-specific code doesn't make any sense. LOC in
10 matches
Mail list logo
