Madhu Venugopal 5217602776 Create vxlan-id space from 0 instead of starting from 1 ...

With the introduction of GetIDInRange function in IDM and using it in
ovmanager, the idm.New was modified to start from 1. But that causes
issues when the network is removed which results in releasing the
vxlan-id from IDM. With the offset of 1, the Release call incorrectly
releases a bit which could be in use by another network and this results
in the infamous "error creating vxlan interface: file exists" errors
when another network is created with this freed bit.

Signed-off-by: Madhu Venugopal <madhu@docker.com>

2016-11-25 13:02:03 -08:00

..

bridge

Merge pull request #1526 from sanimej/policy

2016-11-10 10:12:26 -08:00

host

Add driver api enhancements for gossip

2016-04-18 19:55:39 -07:00

ipvlan

Remove driver endpoints on network deleting

2016-10-14 10:05:20 +08:00

macvlan

Merge pull request #1477 from allencloud/fix-nits-in-comments

2016-11-02 09:58:18 -07:00

null

Add driver api enhancements for gossip

2016-04-18 19:55:39 -07:00

overlay

Create vxlan-id space from 0 instead of starting from 1

2016-11-25 13:02:03 -08:00

remote

Refactoring logrus import and formatting

2016-11-08 12:42:41 -07:00

solaris

Fix new golint reported errors

2016-11-14 16:41:54 -08:00

windows

Merge pull request #1541 from msabansal/defaultgw

2016-11-08 14:34:26 -08:00