Comment 1 for bug 1557223

Revision history for this message
Liam Young (gnuoy) wrote :

I think we should take the install guide as authoritative. It says....

http://docs.openstack.org/liberty/install-guide-ubuntu/nova-controller-install.html
[DEFAULT]
...
auth_strategy = keystone

[keystone_authtoken]
...
auth_uri = http://controller:5000
auth_url = http://controller:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = NOVA_PASS

http://docs.openstack.org/kilo/install-guide/install/apt/content/ch_nova.html#nova-controller-install
[DEFAULT]
...
auth_strategy = keystone

[keystone_authtoken]
...
auth_uri = http://controller:5000
auth_url = http://controller:35357
auth_plugin = password
project_domain_id = default
user_domain_id = default
project_name = service
username = nova
password = NOVA_PASS

http://docs.openstack.org/juno/install-guide/install/apt/content/ch_nova.html#nova-controller-install
[DEFAULT]
...
auth_strategy = keystone

[keystone_authtoken]
...
auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:35357
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS

http://docs.openstack.org/icehouse/install-guide/install/apt/content/nova-controller.html
[DEFAULT]
...
auth_strategy = keystone
Add these keys to the [keystone_authtoken] section:

[keystone_authtoken]
...
auth_uri = http://controller:5000
auth_host = controller
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = nova
admin_password = NOVA_PASS

As bradm points out this does not match what our charms are doing.