commit f661e06e4ac3b906e1d9591ac101bcbb1f077f72
Author: Naveen Joy <email address hidden>
Date: Fri Feb 8 12:54:28 2019 -0800
Optimize GPE VNI allocation & train release support
GPE networks have a large pool of allocatable
Virtual Network Identifiers (VNIs) - 16+ Million. The prior
implementation stores each unallocated VNI in the specified
range, for allocation in the Neutron DB.
This patch optimizes VNI allocation in the DB, by dynamically
computing a valid VNI for allocation at network creation time,
thereby storing only the allocated VNIs in Neutron DB.
Mypy code added; couple of method signatures changes; removed
some hard work that previously generated a log about whether
a released segment was a tenant segment or not.
Also, provides GPE type driver support for the Train
release.
Reviewed: https:/ /review. opendev. org/638307 /git.openstack. org/cgit/ x/networking- vpp/commit/ ?id=f661e06e4ac 3b906e1d9591ac1 01bcbb1f077f72
Committed: https:/
Submitter: Zuul
Branch: master
commit f661e06e4ac3b90 6e1d9591ac101bc bb1f077f72
Author: Naveen Joy <email address hidden>
Date: Fri Feb 8 12:54:28 2019 -0800
Optimize GPE VNI allocation & train release support
GPE networks have a large pool of allocatable
Virtual Network Identifiers (VNIs) - 16+ Million. The prior
implementation stores each unallocated VNI in the specified
range, for allocation in the Neutron DB.
This patch optimizes VNI allocation in the DB, by dynamically
computing a valid VNI for allocation at network creation time,
thereby storing only the allocated VNIs in Neutron DB.
Mypy code added; couple of method signatures changes; removed
some hard work that previously generated a log about whether
a released segment was a tenant segment or not.
Also, provides GPE type driver support for the Train
release.
Closes-bug: #1817218 ad031fc19a65b4f 0aa85cf5c72
Change-Id: I5413c130103431