Calico-Libnetwork should fail on unusable opts

[ozdanborne]

From @djosborne on June 8, 2016 20:43

Docker network creation supports passing --opt (as we explain in our documentation). We accept --opt ipip and --opt nat-outgoing as possible options, but they are only used if not using calico-ipam.

From the user's perspective, they might create a network using calico-ipam and pass those two parameters, but Calico will never modify the pool to use them.

Two possible solutions for this issue:

1. Fail with an error if they use default ipam and still pass one of those two options
2. Actually apply those options to the pool when they are using Calico IPAM.

We may also want to widen the scope of this issue to fail on all unknown/unused opts passed during creation.

Copied from original issue: projectcalico/calico-containers#1017

[tomdee]

We no longer support non-Calico IPAM. So let's fix this by throwing an error when creating a network when any unknown options are passed in (including nat-outgoing or ipip)