Ask Your Question

Wrong port number on Nova's Controller install instruction filter:authtoken ?

asked 2013-11-29 20:48:09 -0500

guido-extras gravatar image
  • Distribution : CentOS 6.4
  • OpenStack Release : Havana

I am installting both a Nova Controller and a Nova Node on the SAME host and there appears to be a conflict where the filter:authtoken ports of both Controller and Node cannot co-exist on the same host, as one has a port as 5000 and another one as 35357.

The Nova CONTROLLER install instructions ( step 8 of ( ) require the configuration of the /etc/nova/api-paste.ini file as such:

[filter:authtoken] paste.filter_factory=keystoneclient.middleware.auth_token:filter_factory auth_host=localhost auth_port=5000 auth_protocol=http auth_uri=http://localhost:5000/v2.0 admin_tenant_name=service admin_user=nova admin_password=NOVA_PASS

But the Nova Compute NODE install instructions ( step 8 of ( ) requires the same file's [filter:authtoken] section to be configured as such:

[filter:authtoken] paste.filter_factory=keystoneclient.middleware.auth_token:filter_factory auth_host=localhost auth_port = 35357 auth_protocol = http admin_user=nova admin_tenant_name=service admin_password=NOVA_PASS

NOTICE the auth_port is 5000 on the Controller and 34357 on the Node. This indicates that both cannot co-exist in this type of installation. I believe the Controller instruction is incorrect and should also be 34357, which is Keystone's endpoint port.

Please clarify how these two configurations can co-exist on the same file or if, as I suspect, the port 5000 is incorrectly pointed out in the configuration.


edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-12-03 20:38:45 -0500

guido-extras gravatar image

Thanks. I did not test on 35357, but I left the configuration just as the instructions for the Nova Controller and it worked, since my install was on a single node.

edit flag offensive delete link more

answered 2013-12-03 14:24:13 -0500

demontie gravatar image


the "filter:authtoken" section is used to specify the Keystone information. It's used by Nova to validate a token that you passed when you made some request to the API. So I think there's no problem on using the port 35357 in both files, since it's Keystone's admin port (which is used by the services internally).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-11-29 20:48:09 -0500

Seen: 23 times

Last updated: Dec 03 '13