Update configuration files for Kilo

Bug #1439261 reported by Matt Kassawara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Invalid
High
Unassigned

Bug Description

Update the configuration files for Kilo to include changes in oslo.messaging and keystonemiddleware.auth_token. For example, RPC configuration resides in [oslo_messaging_*] and [keystone_authtoken] uses auth_plugin.

Ian Cordasco (icordasc)
Changed in glance:
assignee: nobody → Ian Cordasco (icordasc)
milestone: none → kilo-rc1
importance: Undecided → High
status: New → Triaged
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

Example of what appears to work for [keystone_authtoken] and keystone API version 3:

auth_url = http://controller:35357
auth_uri = http://controller:5000
auth_plugin = password
project_domain_id =
user_domain_id =
project_name =
username =
password =

See http://www.jamielennox.net/blog/2015/02/23/v3-authentication-with-auth-token-middleware/ for more information.

Revision history for this message
Nikhil Komawar (nikhil-komawar) wrote :

Just trying to understand this a bit more. Is this documentation change or a breaking one? Can someone add more details please?

Basically, we need to decide : Is this a blocker change, can we tag it as kilo-rc-potential and remove from RC1 list?

Ian Cordasco (icordasc)
Changed in glance:
milestone: kilo-rc1 → none
tags: added: kilo-rc-potential
Thierry Carrez (ttx)
tags: removed: kilo-rc-potential
Revision history for this message
Flavio Percoco (flaper87) wrote :

I believe this bug refers to updating the sample files.

I insist we should just get rid of them and let folks generate those files if needed.

Ian Cordasco (icordasc)
Changed in glance:
status: Triaged → Invalid
assignee: Ian Cordasco (icordasc) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.