Skip to content

Moving IPAM initalization out of drvRegistry into libnetwork core#1310

Merged
aboch merged 1 commit intomoby:masterfrom
mavenugo:drvRegIpam
Jul 6, 2016
Merged

Moving IPAM initalization out of drvRegistry into libnetwork core#1310
aboch merged 1 commit intomoby:masterfrom
mavenugo:drvRegIpam

Conversation

@mavenugo
Copy link
Contributor

@mavenugo mavenugo commented Jul 5, 2016

Signed-off-by: Madhu Venugopal [email protected]

return i.defaultLocalAddressSpace, i.defaultGlobalAddressSpace, nil
}

func (r *DrvRegistry) initIPAMs(lDs, gDs interface{}) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we instead make this method exported so that in controller.go we just call it as

drvRegistry.InitIPAMDrivers(nil, c.getStore(datastore.GlobalScope));

we'd achieve the same thing I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The point of this change is to remove the IPAM driver dependancy from drvRegistry.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so the point is to allow the creator of DrvRegistry to control which ipam drivers needs to be registered.

@aboch
Copy link
Contributor

aboch commented Jul 6, 2016

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants