The control-network charm option is used as a netmask to determine which IPs the API services should bind to. Requiring an operator to provide such information seems however unnecessary (and error-prone) given that the same information could be obtained via the charm bindings.
As an example, the contrail controller could simply bind its listener services to the IPs that lie in the juju space bound to the contrail-controller endpoint, removing the need to provide that same information via the charm config.
The control-network charm option is used as a netmask to determine which IPs the API services should bind to. Requiring an operator to provide such information seems however unnecessary (and error-prone) given that the same information could be obtained via the charm bindings.
As an example, the contrail controller could simply bind its listener services to the IPs that lie in the juju space bound to the contrail-controller endpoint, removing the need to provide that same information via the charm config.