FloatingIP PTR should have managed_tenant_id enforced

[Endre Karlson]

If you set a FIP PTR atm the reverse zone will be created as teh context tenant if no config option is set. We should blow up with a ConfigurationError if the managed_tenant_id is not set and disallow the set operation

[Endre Karlson (endre-karlson)]

We'll set the default for the option instead to 00000000-0000-0000-0000-000000000000 and log a warning on central startup.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit bdab598b6a58c37473c45602d2d8a92a78bed3f3
Author: Endre Karlson <email address hidden>
Date: Fri Mar 27 12:45:43 2015 +0100

    Fix ownership issue with Zone's created on set fip

    When a user sets a FloatingIP a Reverse Zone is created that's owned by the
    system but if no managed_resource_tenant_id option was set then the Zone would
    get owned by the context.tenant_id when create_domain() is called in
    set_floatingip.

    We fix it by changing the default managed_resource_tenant_id to
    "00000000-0000-0000-0000-000000000000".

    Closes-Bug: #1437060

    Change-Id: I491309d92a9e3fba2f42af1ae85372b6258d53f3