OK
On Thu, May 22, 2014 at 7:36 AM, Collins, Sean <
sean_colli...@cable.comcast.com> wrote:
> On Wed, May 21, 2014 at 10:47:16PM EDT, Mandeep Dhami wrote:
> > The update from Sean seem to suggest to me that we needed blueprints only
> > if the public API changes, and not for design changes that
On Wed, May 21, 2014 at 10:47:16PM EDT, Mandeep Dhami wrote:
> The update from Sean seem to suggest to me that we needed blueprints only
> if the public API changes, and not for design changes that are internal to
> neutron.
There was no statement in my e-mail that made that
suggestion. My e-mail
On 22 May 2014 03:47, Mandeep Dhami wrote:
> Hi Salvatore:
>
> Comments inline as well
>
> >
> This is a bit obscure to me. I read it as you're hinting the core team or
> part of it has double standards.
> >
> In that case I would invite you to clarify.
>
> Last week, I had requested refer
Hi Salvatore:
Comments inline as well
>
This is a bit obscure to me. I read it as you're hinting the core team or
part of it has double standards.
>
In that case I would invite you to clarify.
Last week, I had requested reference to a design document for neutron
refactoring work. As this
Some comments inline,
Salvatore
On 21 May 2014 15:23, Mandeep Dhami wrote:
> Hi Sean:
>
> While the APIs might not be changing*, I suspect that there are
> significant design decisions being made**. These changes are probably more
> significant than any new feature being discussed. As a communi
On May 21, 2014, at 10:23 AM, Mandeep Dhami
mailto:dh...@noironetworks.com>> wrote:
Hi Sean:
While the APIs might not be changing*, I suspect that there are significant
design decisions being made**. These changes are probably more significant than
any new feature being discussed. As a commun
Hi Sean:
While the APIs might not be changing*, I suspect that there are significant
design decisions being made**. These changes are probably more significant
than any new feature being discussed. As a community, are we expected to
document these design changes and review these changes as well? I
On Tue, May 20, 2014 at 05:18:57PM EDT, Mandeep Dhami wrote:
> Renewing the thread, is there a blueprint for this refactoring effort?
>
> In the email thread till now, we have just had an etherpad link. I would
> like to get more deeply involved in design/implementation and review of
> these chang
Renewing the thread, is there a blueprint for this refactoring effort?
In the email thread till now, we have just had an etherpad link. I would
like to get more deeply involved in design/implementation and review of
these changes and I get a feeling that not being able to attend the Atlanta
summit
Thanks for the link, Fawad. I had actually seen the etherpad, but I was
hoping that there was a design document backing it up.
Regards,
Mandeep
On Thu, May 15, 2014 at 10:15 AM, Fawad Khaliq wrote:
> Hi Mandeep,
>
> You can find discussion/details in the etherpad link[1].
>
> [1] https://ether
Hi Mandeep,
You can find discussion/details in the etherpad link[1].
[1] https://etherpad.openstack.org/p/refactoring-the-neutron-core
Thanks,
Fawad Khaliq
(m) +1 408.966.2214
On Thu, May 15, 2014 at 9:40 AM, Mandeep Dhami wrote:
> Hi:
>
> I am not at the conference this week, but it is my u
Hi:
I am not at the conference this week, but it is my understanding that there
was a proposal for neutron core API refactoring discussed yesterday. I am
trying to catch up with that discussion, is there a formal design
description or blueprint that I can review?
Thanks,
Mandeep
-
___
12 matches
Mail list logo
