Pool Manager Instance Should Only Be Called For Domains in Instance

[Ron Rickard]

Rather than check to see if the domain is in the pool instance in Pool Manager, only call the Pool Manager instance for the domain. This can be done by having each Pool Manager instance listen on their own topic, 'pool_manager.<pool_id>', and having the client call the pool manager instance for that topic.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/148390

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/148390
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=679c420878245fbb142f17f179aeae0640fb422c
Submitter: Jenkins
Branch: master

commit 679c420878245fbb142f17f179aeae0640fb422c
Author: rjrjr <email address hidden>
Date: Mon Jan 19 17:29:05 2015 -0700

    Call the Correct Pool Manager Instance for the Domain

    Rather than check to see if the domain is in the Pool Manager instance in
    the Pool Manager service, call the correct Pool Manager instance for the
    domain. This is done by:

    - Having each Pool Manager instance listen on it's own topic
    - Client calls the Pool Manager instance by topic

    The topic per instance is 'pool_manager.<pool_id>'.

    Change-Id: I4211601305670c6b972fb778dd68fe511a34c777
    Closes-Bug: #1412605