OK, that's well-motivated enough. We've had requests like this from other groups for the same reason. So feel free to submit a patch that removes the requirement.
On Fri, Aug 02, 2013 at 09:57:01PM +0400, Igor Ryzhov wrote: > I am creating my own datapath module and I don't want to implement > internal type devices creating. But daemon sends me a command to > create such a port. So I have to remove it from database to stop > daemon sending me internal port add requests. > > Best regards, > Igor Ryzhov > > 02.08.2013, ? 21:11, Ben Pfaff <[email protected]> ???????(?): > > > Why do you want to remove it? > > > > On Fri, Aug 02, 2013 at 08:10:42PM +0400, Igor Ryzhov wrote: > >> OpenFlow specification says that LOCAL port is optional and used for > >> implementing in-band management. Why can't I remove this port? > >> > >> Best regards, > >> Igor Ryzhov > >> > >> 02.08.2013, ? 19:43, Ben Pfaff <[email protected]> ???????(?): > >> > >>> On Fri, Aug 02, 2013 at 05:35:01PM +0400, Igor Ryzhov wrote: > >>>> When I create a new bridge using ovs-vsctl, default port named as a > >>>> bridge > >>>> of type "internal" is created too. > >>>> > >>>> Please, explain to me, for what purpose and why can't I remove it? > >>> > >>> OpenFlow always has a "local" port. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
