Honestly the only reason is that I've heard some fairly direct feedback that 
port 5000 is that MS uPnP port and hence blocked by many corporate entities, so 
it's just a matter of a PITA and a slight bump in setup for those groups. 
Thought to honestly register another port with IANA like 35357 and put it in 
place - wanted to see if anyone screamed first.

-joe

On Jun 20, 2012, at 8:49 PM, Vaze, Mandar wrote:
> "public_port" is configurable via keystone.conf - so if port 5000 is blocked 
> in specific setup, it is trivial to change it to some other port.
> 
> why make so many changes (REST docs, XML docs, devstack, and the code) for a 
> parameter that can be easily tweaked ?
> 
> -Mandar
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of Joseph Heck
> Sent: Thursday, June 21, 2012 4:46 AM
> To: [email protected] ([email protected])
> 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     : [email protected]
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> ______________________________________________________________________
> Disclaimer:This email and any attachments are sent in strictest confidence 
> for the sole use of the addressee and may contain legally privileged, 
> confidential, and proprietary data.  If you are not the intended recipient, 
> please advise the sender by replying promptly to this email and then delete 
> and destroy this email and any attachments without any further use, copying 
> or forwarding


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to