Juniper Openstack

config: Synchronously allocate virtual network ID

Bug #1601919 reported by Édouard Thuleau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
Medium
Édouard Thuleau
Juniper Openstack r3.2.0.0-fcs "r3.2.0.0"

Bug Description

Synchronously allocate virtual network ID

Tags: config
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/21819
Submitter: ?douard Thuleau (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/21819
Committed: http://github.org/Juniper/contrail-controller/commit/9df622900687df4ebc812ad6ea60243311529151
Submitter: Zuul
Branch: master

commit 9df622900687df4ebc812ad6ea60243311529151
Author: Édouard Thuleau <email address hidden>
Date: Mon Jul 11 19:50:09 2016 +0200

[config] Synchronously allocate virtual network ID

To improve config node scalability, that patch move the virtual network
ID allocation from the schema to the vnc API server.
To prevent any issue during the upgrade from version where vni is
allocated by the schema to the version where it's allocated by the vnc
API, that patch also sets the vni if it not sets when the vnc API
received a virtual network create notification. That update will need to
be removed for the future release 3.2.

Change-Id: I53098c36315169035e1a9c2b8474b777eb7f362a
Closes-Bug: #1601919

Nischal Sheth (nsheth)
no longer affects: opencontrail
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.