f18911ea14
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
15 lines
811 B
Plaintext
15 lines
811 B
Plaintext
# config for templated.Catalog, using camelCase because I don't want to do
|
|
# translations for keystone compat
|
|
catalog.RegionOne.identity.publicURL = http://localhost:$(public_port)s/v2.0
|
|
catalog.RegionOne.identity.adminURL = http://localhost:$(admin_port)s/v2.0
|
|
catalog.RegionOne.identity.internalURL = http://localhost:$(admin_port)s/v2.0
|
|
catalog.RegionOne.identity.name = 'Identity Service'
|
|
catalog.RegionOne.identity.id = 1
|
|
|
|
# fake compute service for now to help novaclient tests work
|
|
catalog.RegionOne.compute.publicURL = http://localhost:8774/v1.1/$(tenant_id)s
|
|
catalog.RegionOne.compute.adminURL = http://localhost:8774/v1.1/$(tenant_id)s
|
|
catalog.RegionOne.compute.internalURL = http://localhost:8774/v1.1/$(tenant_id)s
|
|
catalog.RegionOne.compute.name = 'Compute Service'
|
|
catalog.RegionOne.compute.id = 2
|