Fixing the gate

A recent patch in devstack [1] forces the use of path access instead
of port for Keystone authentication, leading to connection error in CK
when launching the devstack.

Now CK devstack plugin uses $KEYSTONE_SERVICE_URI to support now and
future keystone devstack modification.

[1] https://review.openstack.org/#/c/456344/

Change-Id: I7ef964185b029036e7ea7abfb555162e9f2d6ec6
This commit is contained in:
Maxime Cottret 2017-04-19 14:08:18 +02:00
parent f9364192cf
commit 27a50b4354
1 changed files with 2 additions and 2 deletions

View File

@ -107,8 +107,8 @@ function configure_cloudkitty {
# auth
iniset $CLOUDKITTY_CONF authinfos auth_type v3password
iniset $CLOUDKITTY_CONF authinfos auth_protocol http
iniset $CLOUDKITTY_CONF authinfos auth_url "$KEYSTONE_SERVICE_PROTOCOL://$KEYSTONE_SERVICE_HOST:5000/v3"
iniset $CLOUDKITTY_CONF authinfos identity_uri "$KEYSTONE_SERVICE_PROTOCOL://$KEYSTONE_SERVICE_HOST:5000/v3"
iniset $CLOUDKITTY_CONF authinfos auth_url "$KEYSTONE_SERVICE_URI/v3"
iniset $CLOUDKITTY_CONF authinfos identity_uri "$KEYSTONE_SERVICE_URI/v3"
iniset $CLOUDKITTY_CONF authinfos username cloudkitty
iniset $CLOUDKITTY_CONF authinfos password $SERVICE_PASSWORD
iniset $CLOUDKITTY_CONF authinfos project_name $SERVICE_TENANT_NAME