Comment 2 for bug 1800417

Thanks much for the review. This is a different issue with #1800599 (which is caused by multiple long lived clients which use up neutron processing threads).

This issue is special for create_network as this operation will query then update segment allocation table which will cause confliction during concurrency access scenarios. as workaround, we add a global InterProcessLock to make the create_network operation in sequence but we would like to see whether community has better solution/suggestion for such cases. Thanks!