On Mon, Jul 13, 2015 at 9:40 AM, Russell Bryant <rbry...@redhat.com> wrote:
> On 07/05/2015 01:38 AM, Alex Wang wrote: > > This commit lays down the foundation for a new controller in OVN, the > > ovn-controller-vtep, for controlling the vtep enabled physical switches. > > What do you think about OVN NB db integration for this? I see in the > code how the gateways are treated like logical ports with special names. > Is that all that's needed? It might be helpful to me at least to run > through some examples of how this would be used. > > Based on the discussion offline, we do not need to associate each physical port vlan pair to a logical port. Will send out a new series with simplification. > > Limitation: > > > > - How to make controller-vtep connect to OVN_SB? > > > > my understanding is that vtep should not know the location of ovnsb. > > but there is no "external_ids" column in vtep schema. and the > manager > > for vtep should be the controller-gw. so, the implementation > requires > > user to specify both vtep, and ovnsb location from command line. > > That seems fine to me. Having to specify the OVN_SB db location doesn't > seem like much of a burden. > > -- > Russell Bryant > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
