[resending to the ovs-dev as I sent my original reply to Russell only]
Comments inline
Salvatore
On 24 June 2015 at 16:15, Russell Bryant wrote:
> On 06/23/2015 06:56 PM, Ben Pfaff wrote:
> > On Tue, Jun 23, 2015 at 11:58:25PM +0200, Salvatore Orlando wrote:
> >> I'm afraid I have to start bik
On 06/23/2015 06:56 PM, Ben Pfaff wrote:
> On Tue, Jun 23, 2015 at 11:58:25PM +0200, Salvatore Orlando wrote:
>> I'm afraid I have to start bike shedding on this thread too.
>> Apparently that's what I do best.
>
> These are important clarifications, not bikeshedding.
>
> More below (with lots of
On Tue, Jun 23, 2015 at 11:58:25PM +0200, Salvatore Orlando wrote:
> I'm afraid I have to start bike shedding on this thread too.
> Apparently that's what I do best.
These are important clarifications, not bikeshedding.
More below (with lots of trimming and reflowing for clarity):
> On 06/23/201
I'm afraid I have to start bike shedding on this thread too.
Apparently that's what I do best.
More inline,
Salvatore
On 23 June 2015 at 23:23, Russell Bryant wrote:
> On 06/23/2015 05:10 PM, Ben Pfaff wrote:
> > On Tue, Jun 23, 2015 at 04:54:20PM -0400, Russell Bryant wrote:
> >> On 06/23/2015
On 06/23/2015 05:10 PM, Ben Pfaff wrote:
> On Tue, Jun 23, 2015 at 04:54:20PM -0400, Russell Bryant wrote:
>> On 06/23/2015 04:17 PM, Ben Pfaff wrote:
>>> On Mon, Jun 22, 2015 at 02:34:07PM -0400, Russell Bryant wrote:
On 06/15/2015 08:00 PM, Ben Pfaff wrote:
> On Wed, Jun 10, 2015 at 03:1
On Tue, Jun 23, 2015 at 04:54:20PM -0400, Russell Bryant wrote:
> On 06/23/2015 04:17 PM, Ben Pfaff wrote:
> > On Mon, Jun 22, 2015 at 02:34:07PM -0400, Russell Bryant wrote:
> >> On 06/15/2015 08:00 PM, Ben Pfaff wrote:
> >>> On Wed, Jun 10, 2015 at 03:13:54PM -0400, Russell Bryant wrote:
> P
On 06/23/2015 04:17 PM, Ben Pfaff wrote:
> On Mon, Jun 22, 2015 at 02:34:07PM -0400, Russell Bryant wrote:
>> On 06/15/2015 08:00 PM, Ben Pfaff wrote:
>>> On Wed, Jun 10, 2015 at 03:13:54PM -0400, Russell Bryant wrote:
Provider Networks
=
OpenStack Neutron curren
On Mon, Jun 22, 2015 at 02:34:07PM -0400, Russell Bryant wrote:
> On 06/15/2015 08:00 PM, Ben Pfaff wrote:
> > On Wed, Jun 10, 2015 at 03:13:54PM -0400, Russell Bryant wrote:
> >> Provider Networks
> >> =
> >>
> >> OpenStack Neutron currently has a feature referred to as "provider
>
On 06/13/2015 06:12 PM, Salvatore Orlando wrote:
> Second, much of the flows currently programmed by ovn-controller
> would be useful for provider networks. We still want to implement port
> security and ACLs (security groups). The major difference is that
> unless the packet is d
(Apologies for the slow follow-up to the responses on this thread. I've
been on vacation.)
On 06/15/2015 08:00 PM, Ben Pfaff wrote:
> On Wed, Jun 10, 2015 at 03:13:54PM -0400, Russell Bryant wrote:
>> Provider Networks
>> =
>>
>> OpenStack Neutron currently has a feature referred
On Wed, Jun 10, 2015 at 03:13:54PM -0400, Russell Bryant wrote:
> Provider Networks
> =
>
> OpenStack Neutron currently has a feature referred to as "provider
> networks". This is used as a way to define existing physical networks
> that you would like to integrate into your envir
On Sat, Jun 13, 2015 at 5:12 PM, Salvatore Orlando
wrote:
> Hi Russel,
>
> thanks for sharing these thoughts. I was indeed thinking as well we need to
> support this in OVN as the provider networks are a fairly basic neutron
> feature - despite being an "extensions".
> I have some comments inlin
Hi Russel,
thanks for sharing these thoughts. I was indeed thinking as well we need to
support this in OVN as the provider networks are a fairly basic neutron
feature - despite being an "extensions".
I have some comments inline. I apologise in advance for their dumbness as
I'm still getting up to
I've been doing some thinking about OpenStack Neutron's provider
networks and how we might be able to support that with OVN as the
backend for Neutron. Here is a start. I'd love to hear what others think.
Provider Networks
=
OpenStack Neutron currently has a feature referred to
14 matches
Mail list logo
