[network] use new nova_admin_tenant_name instead of nova_admin_tenant_id

[Mark Vanderwiel]

Based upon this enhancement in Kilo:
Community bug: https://bugs.launchpad.net/neutron/+bug/1331566
Community patch (merged into Kilo on 10/6/2014): https://review.openstack.org/#/c/103978/

We can use the tenant name instead of getting the id.

The base openstack neutron patch added the following to the conf file:

The patch made the following change to /etc/neutron/neutron.conf:

# The name of the admin nova tenant. If the uuid of the admin nova tenant
# is set, this is optional. Useful for cases where the uuid of the admin
# nova tenant is not available when configuration is being done.
# nova_admin_tenant_name =

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/160971
Committed: https://git.openstack.org/cgit/stackforge/cookbook-openstack-network/commit/?id=48d3cafe4f5f787d3faf9b6652fa46c23dd34655
Submitter: Jenkins
Branch: master

commit 48d3cafe4f5f787d3faf9b6652fa46c23dd34655
Author: Mark Vanderwiel <email address hidden>
Date: Tue Mar 3 14:24:10 2015 -0600

    Use new nova_admin_tenant_name

    Patches in base neutron allow for use of just the nova tenant name
    instead of having to make an ugly cli call into keystone to get the
    uuid. This is much much cleaner way to do it.
    Kept the old admin_tenant_id attribute, added a new
    admin_tenant_name one. This should come directly from the Compute
    cookbook attribute, service_tenant_name, but since Network does
    not depend upon Compute cookbook, I simply added the default here.
    I don't think we want to introduce a depends between Network and
    Compute, that would be a circular dependency.

    Change-Id: I88948b6ad300192cb00b07f10d29dc7ec19d4ba2
    Closes-Bug: #1427817