* Use right keyword in invoke to _floating_ip_pool_delete (bug 2866)
    * Don't assume name of fip pool when router:external is reset, walk and
      delete all fip pool children
Don't throw 500 if FIP pool is still associated to project. Use right keywork for NetworkInUse exception
Merge pull request #39 from Juniper/hajay_fip_pool_delete_c_h

Handle floating ip pool deletes without assuming name and raise right exceptions on failure