; [mailto:openstack-
>> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
>> Nguyen, Liem Manh
>> Sent: Thursday, June 21, 2012 10:40 AM
>> To: Joseph Heck; Vaze, Mandar
>> Cc: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] [keystone]
[mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> Nguyen, Liem Manh
> Sent: Thursday, June 21, 2012 10:40 AM
> To: Joseph Heck; Vaze, Mandar
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [keystone] Keystone on port 5000 - proposing
&g
Behalf
Of Joseph Heck
Sent: Thursday, June 21, 2012 1:28 AM
To: Vaze, Mandar
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [keystone] Keystone on port 5000 - proposing change
default port to 8770
Honestly the only reason is that I've heard some fairly direct feedback that
port
On 21/06/12 09:27, Joseph Heck wrote:
> 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
Makes sense to me honestly.Will sed live its hours of glory ?Regards,Razique
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 21 juin 2012 à 10:27, Joseph Heck a écrit :Honestly the only reason is that I've heard some fairly direct feedback that port 5000 is that MS uPnP port and hence bl
vaze=nttdata@lists.launchpad.net] On
> Behalf Of Joseph Heck
> Sent: Thursday, June 21, 2012 4:46 AM
> To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
> Subject: [Openstack] [keystone] Keystone on port 5000 - proposing change
> default port to 8770
>
> At
[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
As an operator, I can say we have had issues with the fact that keystone
is on port 5000, and wouldn't mind if it changed to something else :)
Regards,
Tom
On 21/06/12 11:19, Dolph Mathews wrote:
Alternatively, if anyone would like to tar and feather me for picking
port 5000 in the first plac
I would recommend keeping a clear separation of administrative APIs from
user APIs. Some policy restrictions in environments require them. EX:
FISMA
On Wed, Jun 20, 2012 at 6:19 PM, Dolph Mathews wrote:
> Alternatively, if anyone would like to tar and feather me for picking port
> 5000 in the f
Alternatively, if anyone would like to tar and feather me for picking port
5000 in the first place, I'm available. That said, I have no attachment to
port 5000... but I'm curious, are people experiencing real issues trying to
use port 5000?
-Dolph
On Wed, Jun 20, 2012 at 6:16 PM, Joseph Heck wro
stack@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-t
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
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
13 matches
Mail list logo
