compute_port in config options

[Morgan Fainberg]

In ancient times keystone replaced the port for the compute service based upon it's local configuration file (templated catalog). This is silly and should not be done as it means you would need to configure the compute_port variable in keystone for it to reflect the catalog instead of updating the static data.

The keystone config should have no bearing on the nova port.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/103204
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=f18911ea148920323952fa1a154cf21a15ab31b9
Submitter: Jenkins
Branch: master

commit f18911ea148920323952fa1a154cf21a15ab31b9
Author: Morgan Fainberg <email address hidden>
Date: Fri Jun 27 11:03:34 2014 -0700

    Do not use keystone's config for nova's port

    Keystone's configuration should have no bearing on the catalog
    for nova's port. Nova's port is "static" data from the templated
    catalog perspective.

    The 'compute_port' option has been marked as deprecated and
    slated for removal in the L release. The default/sample
    templated catalog files do not rely on this option any
    longer.

    Change-Id: I51b0ec951449360f002c2e7c900ded0f40e16044
    Closes-Bug: #1335278