On 2016-04-29 08:41:46 -0600 (-0600), Mark Carlson wrote:
> OpenStack could request a port number be assigned for default use:
> https://tools.ietf.org/html/rfc6335
As discovered when Keystone did this several years ago, the port
numbers being assigned at this stage have tipped over into the
defau
...and we just landed a patch to use the 6200 range for examples.
https://review.openstack.org/#/c/274840/
--John
On 29 Apr 2016, at 9:26, John Dickinson wrote:
> The "bind_port" setting in Swift's config files is required to be explicitly
> set. It doesn't matter what the number is. If yo
OpenStack could request a port number be assigned for default use:
https://tools.ietf.org/html/rfc6335
-- mark
> On Apr 29, 2016, at 8:26 AM, John Dickinson wrote:
>
> The "bind_port" setting in Swift's config files is required to be explicitly
> set. It doesn't matter what the number is. If y
The "bind_port" setting in Swift's config files is required to be explicitly
set. It doesn't matter what the number is. If you have a port conflict with
another service, feel free to change it.
As to why port 6000 was used initially... The truth is probably lost to the
mists of time. However, I
On 29/04/2016 10:12, Peter Brouwer wrote:
Hello All,
When looking at the ports used by the system I noticed port 6000 is
already in use before starting the swift services.
In the swift object-server.conf file the default port setting is 6000
to, so yes when starting the swift object serve
