fication later this week to
>> propose a list of capabilities.
>>
>>
>>
>> -Sam.
>>
>>
>>
>>
>>
>> *From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
>> *Sent:* Saturday, May 03, 2014 1:33 AM
>>
>> *To:* O
>
>
> I plan to look deeper into L7 content modification later this week to
> propose a list of capabilities.
>
>
>
> -Sam.
>
>
>
>
>
> *From:* Stephen Balukoff [mailto:sbaluk...@bluebox.net]
> *Sent:* Saturday, May 03, 2014 1:33 AM
>
> *To
AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS]L7 conent switching APIs
Hi Adam and Samuel!
Thanks for the questions / comments! Reactions in-line:
On Thu, May 1, 2014 at 8:14 PM, Adam Harwell
mailto:adam.harw...@rackspace.com
Hi Adam and Samuel!
Thanks for the questions / comments! Reactions in-line:
On Thu, May 1, 2014 at 8:14 PM, Adam Harwell wrote:
>
> Stephen, the way I understood your API proposal, I thought you could
> essentially combine L7Rules in an L7Policy, and have multiple L7Policies,
> implying that
ions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS]L7 conent switching APIs
Hi Samuel,
We talked a bit in chat about this, but I wanted to reiterate a few things here
for the rest of the group. Comments in-line:
On Wed, Apr 30, 2014 at 6:10 A
v@lists.openstack.org>>
Date: Thursday, May 1, 2014 6:52 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS]L7 conent switching APIs
Hi Samuel,
We talked a bit in chat
Hi Samuel,
We talked a bit in chat about this, but I wanted to reiterate a few things
here for the rest of the group. Comments in-line:
On Wed, Apr 30, 2014 at 6:10 AM, Samuel Bercovici wrote:
> Hi,
>
>
>
> We have compared the API the is in the blue print to the one described in
> Stephen do
Hi,
We have compared the API the is in the blue print to the one described in
Stephen documents.
Follows the differences we have found:
1) L7PolicyVipAssoc is gone, this means that L7 policy reuse is not
possible. I have added use cases 42 and 43 to show where such reuse makes sense.
2)