OpenStack Compute (nova)

nova's usage of cinderclient url should be configurable

Bug #1047033 reported by Vish Ishaya on 2012-09-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	High	Vish Ishaya	OpenStack Compute (nova) 2012.2 "folsom"

Bug Description

When nova parses the service catalog to talk to cinder, it attempts to connect to cinder using publicURL. This should be configurable.

Vish Ishaya (vishvananda) on 2012-09-06

Changed in nova:
status:	New → In Progress
importance:	Undecided → High
assignee:	nobody → Vish Ishaya (vishvananda)
milestone:	none → folsom-rc1

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-09-06: Fix proposed to nova (master)

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

Vish Ishaya (vishvananda) on 2012-09-06

summary:

- nova's usage of cinderclient should use internalURL
+ nova's usage of cinderclient url should be configurable

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-09-06: Fix merged to nova (master)

Reviewed: https://review.openstack.org/12524
Committed: http://github.com/openstack/nova/commit/25b0b58c9595f8600664aa5c49504e44eed80859
Submitter: Jenkins
Branch: master

commit 25b0b58c9595f8600664aa5c49504e44eed80859
Author: Vishvananda Ishaya <email address hidden>
Date: Thu Sep 6 13:46:27 2012 -0700

Allow cinder catalog match values to be configured

    Depending on how a deployments keystone catalog is set up, the
    default values passed in to the cinder client may be incorrect.
    This adds a configuration option to specify exactly where to look
    for the cinder endpoint in the service catalog.

Fixes bug 1047033

Change-Id: I93324b6930f384306311b0bbac375a9224283fbc