ck Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS] Thoughts on current process
Hi,
On Thu, May 1, 2014 at 10:46 PM, Jorge Miramontes
mailto:jorge.miramon...@rackspace.com>> wrote:
Hey
>
>
> We wanted a discussion to happen on whether the existing object model
> would work with both API proposals. That blueprint being pushed to
> gerrit the same time as Stephen mailing out his proposal made it seem
> like this was not going to happen.
>
I'm sorry about that. In fact I was just p
Hi Eugene,
On Fri, 2014-05-02 at 00:10 +0400, Eugene Nikanorov wrote:
> Hi,
>
>
> On Thu, May 1, 2014 at 10:46 PM, Jorge Miramontes
> wrote:
> Hey Eugene,
>
>
> I think there is a misunderstanding on what iterative
> development means to you and me and
Hi,
On Thu, May 1, 2014 at 10:46 PM, Jorge Miramontes <
jorge.miramon...@rackspace.com> wrote:
> Hey Eugene,
>
> I think there is a misunderstanding on what iterative development means
> to you and me and I want to make sure we are on the same page. First of
> all, I'll try not to use the ter
t (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS] Thoughts on current process
Hi Jorge,
A couple of inline comments:
Now that we have a set of requirements the next question to ask is, "How
doe we priorit
nikano...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 1, 2014 8:12 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@li
Sorry, missed the phrase ending:
> It's not because developers of lbaas have not thought about it, it's
> because we were limited in dev and core reviewing
> resources, so implement
>
so implementing some of the operators requirements was always in our plans.
Eugene.
_
Hi Jorge,
A couple of inline comments:
>
> Now that we have a set of requirements the next question to ask is, "How
> doe we prioritize requirements so that we can start designing and
> implementing them"?
Prioritization basically means that we want to support everything and only
choose what is
: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Thoughts on current process
Hi Jorge!
+1 to everything you just said. In fact, I think you said essentially what I
was trying to last week with 100% less drama.
I'll work to add workflows
Jorge,
In looking over your API proposal linked above, have things significantly
changed there since you sent it out two weeks ago? (And if so, which parts
should I take a look at again?)
Thanks,
Stephen
On Wed, Apr 30, 2014 at 5:07 PM, Stephen Balukoff wrote:
> Hi Jorge!
>
> +1 to everything
Hi Jorge!
+1 to everything you just said. In fact, I think you said essentially what
I was trying to last week with 100% less drama.
I'll work to add workflows to my proposal, but please note it's late on a
Wednesday and tomorrow's IRC meeting is awfully early in my time zone. I
probably won't ha
Oops! Everywhere I said Samuel I meant Stephen. Sorry you both have SB as
you initials so I got confused. :)
Cheers,
--Jorge
On 4/30/14 5:17 PM, "Jorge Miramontes"
wrote:
>Hey everyone,
>
>I agree that we need to be preparing for the summit. Using Google docs
>mixed with Openstack wiki works
Hey everyone,
I agree that we need to be preparing for the summit. Using Google docs
mixed with Openstack wiki works for me right now. I need to become more
familiar the gerrit process and I agree with Samuel that it is not
conducive to "large" design discussions. That being said I'd like to add
m
13 matches
Mail list logo
