Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Sam,
The use cases where pretty complete the last time I checked so let's move them
to gerrit so we can all vote.
Echoing Kyle I would love to see us focusing on getting things
us focusing on getting things ready for
>> the summit.
>>
>> German
>>
>> -Original Message-
>> From: Samuel Bercovici [mailto:samu...@radware.com]
>> Sent: Monday, April 28, 2014 11:44 AM
>> To: OpenStack Development Mailing List (not for usage q
Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Hi,
I was just working to push the use cases into the new format .rst but I agree
that using google doc would be more intuitive.
Let me know what you prefer to do with the use cases document:
1. leave it at google docs at -
https:
On Apr 27, 2014, at 8:35 AM, Eugene Nikanorov
mailto:enikano...@mirantis.com>> wrote:
On Fri, Apr 25, 2014 at 4:03 AM, Eugene Nikanorov
mailto:enikano...@mirantis.com>> wrote:
Speaking of SSL - we have a few few project-wise issues such as lack of secure
storage, lack of secure messaging, req
an
>
>
>
> *From:* Vijay B [mailto:os.v...@gmail.com]
> *Sent:* Tuesday, April 29, 2014 2:30 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API
> proposal
>
>
>
&
OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
>
> On Mon, Apr 28, 2014 at 6:23 PM, Stephen Balukoff
> wrote:
> > Hi guys,
> >
> > Sorry for all the drama on the list lately.
>
: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Also, a section for the API specification for the newly created SSL extensions
needs to be added to https://wiki.openstack.org/wiki/Neutron/LBaaS/SSL.
Regards,
Vijay
On Tue, Apr 29, 2014 at 1:55 PM, Vijay B
mailto:os.v...@gmail.com
---
From: Samuel Bercovici [mailto:samu...@radware.com<mailto:samu...@radware.com>]
Sent: Monday, April 28, 2014 11:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Hi,
I was just working to push the
; German
>>
>> -Original Message-
>> From: Samuel Bercovici [mailto:samu...@radware.com]
>> Sent: Monday, April 28, 2014 11:44 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of n
---Original Message-
> From: Samuel Bercovici [mailto:samu...@radware.com]
> Sent: Monday, April 28, 2014 11:44 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
>
> Hi,
>
> I was
time I checked so let's
>> move them to gerrit so we can all vote.
>>
>> Echoing Kyle I would love to see us focusing on getting things ready
>> for the summit.
>>
>> German
>>
>> -Original Message-
>> From: Samuel Bercovici [mailto:
>>
>> Echoing Kyle I would love to see us focusing on getting things ready for
>> the summit.
>>
>> German
>>
>> -Original Message-
>> From: Samuel Bercovici [mailto:samu...@radware.com]
>> Sent: Monday, April 28, 2014 11:44 AM
>> To: O
rcovici [mailto:samu...@radware.com]
> Sent: Monday, April 28, 2014 11:44 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
>
> Hi,
>
> I was just working to push the use cases i
Sent: Monday, April 28, 2014 11:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Hi,
I was just working to push the use cases into the new format .rst but I agree
that using google doc would be
.
-Original Message-
From: Kyle Mestery [mailto:mest...@noironetworks.com]
Sent: Monday, April 28, 2014 4:33 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
Folks, sorry for the top post here, but I wanted to
Folks, sorry for the top post here, but I wanted to make sure to
gather people's attention in this thread.
I'm very happy to see all the passion around LBaaS in Neutron for this
cycle. As I've told a few people, seeing all the interest from
operators and providers is fantastic, as it gives us valu
Hi,
> You knew from the action items that came out of the IRC meeting of April
> 17 that my team would be working on an API revision proposal. You also knew
> that this proposal was to be accompanied by an object model diagram and
> glossary, in order to clear up confusion. You were in that meeti
>
> On Fri, Apr 25, 2014 at 4:03 AM, Eugene Nikanorov > wrote:
>
>> Hi Stephen,
>>
>> Thanks for the great document. As I promised, I'll try to make a few
>> action items out if it.
>> First of all, I'd like to say that the API you have proposed is very
>> close to what is proposed in the blueprin
Hi Eugene,
Apologies for the delay in my response. It took me a while to figure out
how to say what I wanted to say here as diplomatically as possible. In the
end, I decided I couldn't be diplomatic about some of the things that I
think needed to be said. I don't play games of politics very well a
Hi Stephen,
Thanks for the great document. As I promised, I'll try to make a few action
items out if it.
First of all, I'd like to say that the API you have proposed is very close
to what is proposed in the blueprint
https://review.openstack.org/#/c/89903/with several differences I'd
like to addre
Hi Brandon!
Thanks for the questions. Responses inline:
On Wed, Apr 23, 2014 at 2:51 PM, Brandon Logan
wrote:
> Hey Stephen!
> Thanks for the proposal and spending time on it (I know it is a large time
> investment). This is actually very similar in structure to something I had
> started on e
Hey Stephen!
Thanks for the proposal and spending time on it (I know it is a large
time investment). This is actually very similar in structure to
something I had started on except a load balancer object was the root
and it had a one-to-many relationship to VIPs and each VIP had a
one-to-many
Hi y'all!
As discussed in last week's IRC meeting, my team members and I have
produced a revised draft of the API v2.0 proposal started last week by the
Rackspace crew. (Thanks again for this, y'all-- this helped us get a heck
of a head start on our revised proposal.)
Our v2.0 API proposal revisi
23 matches
Mail list logo
