On Wed, Feb 4, 2015 at 6:40 AM, brian mullan wrote:
> I've read through this thread and although there was a lot of discussion
> about OVN and
> integration with OpenStack I'd like to ask if there has been any discussion
> about what
> considerations might need to be made tomake OVN easy to utiliz
I've read through this thread and although there was a lot of discussion
about OVN and
integration with OpenStack I'd like to ask if there has been any discussion
about what
considerations might need to be made tomake OVN easy to utilize with Linux
Containers/Namespaces?
Use of container technolog
On Tue, Jan 20, 2015 at 12:18:59AM +0100, Thomas Graf wrote:
> On 01/19/15 at 09:19am, Ben Pfaff wrote:
> > I really prefer feature negotiation in any case, because it means that
> > OVN can work with OVS that has custom version numbers or backports of
> > individual features.
>
> You are absolute
On 01/19/15 at 03:13pm, Ben Pfaff wrote:
> I think that this can be simply tested for with an OFPT_PACKET_OUT whose
> packet is an ARP and whose actions modify ARP header fields and then
> send the packet back to the controller. If the packet comes back in an
> OFPT_PACKET_IN, with the requested A
On 01/19/15 at 09:19am, Ben Pfaff wrote:
> I really prefer feature negotiation in any case, because it means that
> OVN can work with OVS that has custom version numbers or backports of
> individual features.
You are absolutely right. Thinking about this more, I guess we don't
even have a choice a
On 01/19/15 at 09:58am, Ben Pfaff wrote:
> To keep the discussion going, let's talk about each of those features.
>
> These days, OVS allows an ARP responder can be implemented in the
> OpenFlow flow table (since all ARP fields are modifiable), but that has
> only been true for a few versions. Be
On Tue, Jan 20, 2015 at 12:07:52AM +0100, Thomas Graf wrote:
> On 01/19/15 at 09:58am, Ben Pfaff wrote:
> > To keep the discussion going, let's talk about each of those features.
> >
> > These days, OVS allows an ARP responder can be implemented in the
> > OpenFlow flow table (since all ARP fields
On Mon, Jan 19, 2015 at 11:38:48PM +0100, Thomas Graf wrote:
> On 01/19/15 at 10:01am, Ben Pfaff wrote:
> > I realize that a shared library was mentioned elsethread as having some
> > importance, but I don't understand why. ovn-controller and the other C
> > components of OVN will be just as usefu
On 01/19/15 at 10:01am, Ben Pfaff wrote:
> I realize that a shared library was mentioned elsethread as having some
> importance, but I don't understand why. ovn-controller and the other C
> components of OVN will be just as useful whether they are statically or
> dynamically linked to the OVS libr
On Mon, Jan 19, 2015 at 05:25:22PM +, Dave Tucker wrote:
>
> On 19 Jan 2015, at 16:56, Miguel Ángel Ajo wrote:
>
> >Wasn’t OVN to be developed in C too?
>
> That's what was being discussed here based on a comment earlier in the
> thread.
> I'm just exploring whether there is a reason to cons
On Mon, Jan 19, 2015 at 05:56:30PM +0100, Miguel Ángel Ajo wrote:
>
> On Monday, 19 de January de 2015 at 15:32, Dave Tucker wrote:
> >
> > On 19 Jan 2015, at 13:04, Thomas Graf wrote:
> >
> > > Agreed. I would expect that OVN might lead to more frequent releases
> > > of OVS with a more "st
On Mon, Jan 19, 2015 at 02:32:02PM +, Dave Tucker wrote:
>
> On 19 Jan 2015, at 13:04, Thomas Graf wrote:
>
> >Agreed. I would expect that OVN might lead to more frequent releases
> >of OVS with a more "stable at all times attitude" as OVN will depend on
> >specific OVS features.
>
> This is
On 19 Jan 2015, at 16:56, Miguel Ángel Ajo wrote:
Wasn’t OVN to be developed in C too?
That's what was being discussed here based on a comment earlier in the
thread.
I'm just exploring whether there is a reason to consider using Python
instead.
I guess it really comes down to what version
On Mon, Jan 19, 2015 at 02:04:42PM +0100, Thomas Graf wrote:
> On 01/16/15 at 04:28pm, Ben Pfaff wrote:
> > We have not yet contemplated that, but it could be possible.
> >
> > In my opinion, OVS is not releasing often enough in any case. I think
> > that 3 or 4 releases a year is about right (bu
On Monday, 19 de January de 2015 at 15:32, Dave Tucker wrote:
>
> On 19 Jan 2015, at 13:04, Thomas Graf wrote:
>
> > Agreed. I would expect that OVN might lead to more frequent releases
> > of OVS with a more "stable at all times attitude" as OVN will depend
> > on
> > specific OVS feature
On 19 Jan 2015, at 13:04, Thomas Graf wrote:
Agreed. I would expect that OVN might lead to more frequent releases
of OVS with a more "stable at all times attitude" as OVN will depend
on
specific OVS features.
This is my concern. For OVN to be useful in the context of OpenStack, we
should b
On 01/16/15 at 04:28pm, Ben Pfaff wrote:
> We have not yet contemplated that, but it could be possible.
>
> In my opinion, OVS is not releasing often enough in any case. I think
> that 3 or 4 releases a year is about right (but that's off the cuff, not
> some kind of official policy or anything).
On Fri, Jan 16, 2015 at 01:49:42PM +, Dave Tucker wrote:
> Quoting from the blog post:
>
> "OVN will not require a special build of OVS or OVN-specific changes to
> ovs-vswitchd or ovsdb-server"
>
> Does choosing C prevent us packaging and versioning OVN separately from OVS?
No. Any
On 15 Jan 2015, at 5:17, Ben Pfaff wrote:
On Wed, Jan 14, 2015 at 10:12:39AM -0600, Kyle Mestery wrote:
On Tue, Jan 13, 2015 at 2:43 PM, Thomas Graf
wrote:
On 01/13/15 at 11:29am, Ben Pfaff wrote:
Open Virtual Network (OVN) Proposed Architecture
==
...@nicira.com]
Sent: Thursday, January 15, 2015 9:07 AM
To: Eitan Eliahu
Cc: Thomas Graf; dev; YAMAMOTO Takashi
Subject: Re: [ovs-dev] OVN architecture
On Thu, Jan 15, 2015 at 8:55 AM, Eitan Eliahu wrote:
> Shared libraries on Windows could be implemented as DLLs (Dynamic Link
> Libraries) wit
-boun...@openvswitch.org] On Behalf Of Thomas Graf
> Sent: Thursday, January 15, 2015 7:19 AM
> To: Gurucharan Shetty
> Cc: dev; YAMAMOTO Takashi
> Subject: Re: [ovs-dev] OVN architecture
>
> On 01/15/15 at 07:04am, Gurucharan Shetty wrote:
>> On Thu, Jan 15, 2015 at 4:06 AM,
] On Behalf Of Thomas Graf
Sent: Thursday, January 15, 2015 7:19 AM
To: Gurucharan Shetty
Cc: dev; YAMAMOTO Takashi
Subject: Re: [ovs-dev] OVN architecture
On 01/15/15 at 07:04am, Gurucharan Shetty wrote:
> On Thu, Jan 15, 2015 at 4:06 AM, Thomas Graf wrote:
> > On 01/15/15 at 03:36pm,
On 01/15/15 at 07:04am, Gurucharan Shetty wrote:
> On Thu, Jan 15, 2015 at 4:06 AM, Thomas Graf wrote:
> > On 01/15/15 at 03:36pm, YAMAMOTO Takashi wrote:
> >> > On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote:
> >> >> > ovn-controller
> >> >> > --
> >> >>
> >> >> neut
On Thu, Jan 15, 2015 at 4:06 AM, Thomas Graf wrote:
> On 01/15/15 at 03:36pm, YAMAMOTO Takashi wrote:
>> > On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote:
>> >> > ovn-controller
>> >> > --
>> >>
>> >> neutron "ofagent" agent has a similar design to ovn-controller.
>>
On 01/15/15 at 03:36pm, YAMAMOTO Takashi wrote:
> > On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote:
> >> > ovn-controller
> >> > --
> >>
> >> neutron "ofagent" agent has a similar design to ovn-controller.
> >> you might be able to reuse at least some of code if pytho
> On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote:
>> > ovn-controller
>> > --
>>
>> neutron "ofagent" agent has a similar design to ovn-controller.
>> you might be able to reuse at least some of code if python+ryu
>> is acceptable.
>>
>> https://github.com/openstack/n
On Tue, Jan 13, 2015 at 09:43:58PM +0100, Thomas Graf wrote:
> I obviously absolutely love this. I will provide my thoughts over
> the next days.
Great, looking forward to the discussion.
> On 01/13/15 at 11:29am, Ben Pfaff wrote:
> > Following are not well thought out:
> >
> > learn
> >
On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote:
> > ovn-controller
> > --
>
> neutron "ofagent" agent has a similar design to ovn-controller.
> you might be able to reuse at least some of code if python+ryu
> is acceptable.
>
> https://github.com/openstack/neutron/tre
On Wed, Jan 14, 2015 at 10:12:39AM -0600, Kyle Mestery wrote:
> On Tue, Jan 13, 2015 at 2:43 PM, Thomas Graf
> wrote:
>
> > On 01/13/15 at 11:29am, Ben Pfaff wrote:
> > > Open Virtual Network (OVN) Proposed Architecture
> > >
> > >
> > > The Open v
> ovn-controller
> --
neutron "ofagent" agent has a similar design to ovn-controller.
you might be able to reuse at least some of code if python+ryu
is acceptable.
https://github.com/openstack/neutron/tree/stable/juno/neutron/plugins/ofagent
> OVN database
>
midonet use
On Tue, Jan 13, 2015 at 2:43 PM, Thomas Graf
wrote:
> On 01/13/15 at 11:29am, Ben Pfaff wrote:
> > Open Virtual Network (OVN) Proposed Architecture
> >
> >
> > The Open vSwitch team is pleased to announce OVN, a new subproject in
> > development wi
On 01/13/15 at 11:29am, Ben Pfaff wrote:
> Open Virtual Network (OVN) Proposed Architecture
>
>
> The Open vSwitch team is pleased to announce OVN, a new subproject in
> development within the Open vSwitch. The full project announcement is
> at Net
Open Virtual Network (OVN) Proposed Architecture
The Open vSwitch team is pleased to announce OVN, a new subproject in
development within the Open vSwitch. The full project announcement is
at Network Heresy and reproduced at:
http://openvs
33 matches
Mail list logo
