Skip to content

Allow --port range for random port selection#5

Open
samrocketman wants to merge 4 commits into
naterh:masterfrom
samrocketman:horde/random-tracker-ports
Open

Allow --port range for random port selection#5
samrocketman wants to merge 4 commits into
naterh:masterfrom
samrocketman:horde/random-tracker-ports

Conversation

@samrocketman
Copy link
Copy Markdown

This way the tracker listens on a new random port each time horde is called. This allows Horde to be integrated into a continuous delivery/continuous deployment environment from the same deploy agent to multiple destination hosts (with different projects). This will allow the deployments to scale well in an automated deployment environment.

With port range, the socket is tested before port is used.

This was a cherry pick from russss#14.

This way the tracker listens on a new random port each time
herd.py is called.  This allows Herd to be integrated into a
continuous delivery/continuous deployment environment.

With port range socket is tested before port is used.

pep8 cleanup on get_random_open_port function compared to Herd
patch.
Updated gitignore so that paths created by setup.py commands are
ignored.
A random port selection from a port range has moved to
being selected at the beginning of runtime.
Within function get_random_open_port().

The socket testing interfered with the actual tracker starting a
listener.  Since no communication happens over the opened socket,
and we're just testing if it is free to bind, there should be
no timeout for the socket to expire.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant