On Fri, Oct 11, 2013 at 04:56:23PM -0700, Justin Pettit wrote:
> From: Bruce Davie <bda...@vmware.com>
> 
> The hardware VTEP OVSDB schema specifies relations that a VTEP can use
> to integrate physical ports into logical switches maintained by a
> network virtualization controller such as NVP.
> 
> Co-authored-by: Ben Pfaff <b...@nicira.com>
> Co-authored-by: Kenneth Duda <kd...@aristanetworks.com>
> Co-authored-by: Justin Pettit <jpet...@nicira.com>
> Signed-off-by: Justin Pettit <jpet...@nicira.com>

This commit and change log has a few references to NVP.  I think that
NVP is now marketed under the name NSX, so perhaps we should update the
references.

This week we changed how we generate the E-R diagrams for the vswitchd
schema.  Can you update the commit to use the same pattern for the vtep
schema?  (That means that the commit would no longer include vtep.gv or
vtep.pic.)

vtep.xml still talks about port 6632 as the default OVSDB port.  Do we
have a plan for transitioning vtep to use the IETF standardized port?

vtep.xml has a few references to Open vSwitch (rather that to the Open
vSwitch database or database server) that seem a little out of line,
since VTEP doesn't involve Open vSwitch proper.

Thanks,

Ben.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to