Comment 5 for bug 1469668

Just trying to catch the difference between this proposal and the existng get-me-a-network proposal [1][2]

So if I got it right, [2] proposes
#1 New API "get-me-a-network".
--> takes the same parameters as the network-list API. But it does not allow passing any additional parameters (like I want a network that is attached to an external network) for the user. The only control mechanism is something that the administrator has to predefine somehow.
--> returns: a network

This proposal proposes 2 things:

#2 Update to "Create Port" API:
It's a scheduler that is triggerd on "create port" when no network is specified.
--> takes additional flags or key-values (like SHARED, routed=external), which will be passed to the new scheduler, which then will continue creating the port on a matching network.
--> returns: a port on a network

#3 a new API that takes details of an existing port as argument and returns a list of hosts where this port is available
--> returns: list of hosts

So can we say that #2 replaces #1? So instead of get-me-a-network we implement get-me-a-port (hidden behind create port api) which covers the use case of [2] as well?

[1] http://specs.openstack.org/openstack/neutron-specs/specs/liberty/get-me-a-network.html
[2] https://bugs.launchpad.net/neutron/+bug/1475792