That is for admin, 5000 is for normal usage.

Personally, I'd like to see all of the custom ports go away and we use an URL scheme as proposed:

http://wiki.openstack.org/URLs

On 06/20/2012 08:56 PM, Mellquist, Peter wrote:
What happened to 35357?

In general, new port #s should be applied through IANA and when approved then 
made public.

Peter.

-----Original Message-----
From: openstack-bounces+peter.mellquist=hp....@lists.launchpad.net 
[mailto:openstack-bounces+peter.mellquist=hp....@lists.launchpad.net] On Behalf 
Of Joseph Heck
Sent: Wednesday, June 20, 2012 4:16 PM
To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: [Openstack] [keystone] Keystone on port 5000 - proposing change 
default port to 8770

At the risk of a terrible public tar and feathering...

I've learned that port 5000 (which Keystone is using for it's default 
public-token-auth stuff) is commonly blocked by many firewalls, as it's been 
registered as a Microsoft uPnP port.

I thought I'd go ahead and propose changing the default to 8770. I picked this 
number because it's close to the Nova ports in common use (8773, 8774, 8775, 
and 8776).

And yes, I'll submit updates to all REST docs, XML docs, devstack, and the code.

So... how many people do I need to worry about murdering me for this next 
design summit?

-joe

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to