Open Stack

>Network names are not guaranteed to be unique. This could cause >problems. If I recall correctly we had a similar discussion about one of the >plugins (One of the IBM ones?) where they ran into the issue of network >names and uniqueness.
My proposal is to use network-uuid as the key, and send the network name in the body, as shown below.
{ "network-1-uuid": { "total-ips" : 256
                       "available-ips" : count1,
                       "name" : test-network,
                    }}
 == Aihua Edward Li == 


     On Friday, October 9, 2015 1:27 PM, Sean M. Collins <sean at coreitpro.com> wrote:
   

 On Fri, Oct 09, 2015 at 02:38:03PM EDT, Aihua Li wrote:
>  For this use-case, we need to return network name in the response.We also have the implementation and accompanying tempest test scripts.The issue 1457986 is currently assigned to Mike Dorman. I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations.

Network names are not guaranteed to be unique. This could cause problems. If I recall correctly we had a similar discussion about one of the plugins (One of the IBM ones?) where they ran into the issue of network names and uniqueness.

-- 
Sean M. Collins


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151009/772e22aa/attachment-0001.html>