On 01/27/2016 10:04 AM, Na Zhu wrote: > Hi Russell, > > Yes, OVN supports provider network type flat and vlan, if use provider > network, the traffic between compute nodes are not encapsulated with STT or > Geneve header, and the provider network is not used for connecting external > in neutron, I think need external network to connect openstack to external. > > I am not clear why you said using provide network to connect external, can > the external you mentioned be public network?
In OpenStack, "provider networks" (networks created in the system that map directly to a physical network in your environment) are the most common way we provide connectivity to outside of OpenStack (usually your route out to the Internet). OVN has enough support for this to support an environment that exclusively uses "provider networks". Using the traditional Neutron OVS support, that model looks like this: http://docs.openstack.org/liberty/networking-guide/scenario-provider-ovs.html The most common way of deploying OpenStack is using a combination of tenant overlay networks + a virtual router that implements NAT and connectivity to a provider network. Again, using the traditional OVS support in Neutron, that model is: http://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.html I'd like to support this model for OVN deployments, but we're still missing a few things to make it work. Yet another method of providing connectivity between logical and physical networks is using vtep gateways (TOR switches or software that implements in the hardware_vtep ovsdb schema). There's not really an equivalent in the existing OVS support, and I don't think this is feature complete enough yet anyway except for more limited use cases. -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
