John Kung 3f4a439109 Fix socket growth on system application operations
There is an issue whereby docker exec_run commands do not close the TCP socket.
Thus on each kube application operation, such as application-apply, the docker
exec_run consumes 4 TCP sockets per iteration.  Thus, when it hits limit
of 1024 sockets, system can no longer perform application operations.

This updates the python-docker package. The source code was already in the
cengn mirror; and this update adds a patch to finally close socket in
docker client.

Tests performed:
Install AIO, Storage labs.
system application-upload stx-openstack, apply, remove
system application apply stress test of over 300 iterations
and verify no growth in sockets held by sysinv-conductor.

Change-Id: I21b9e486af1e3bb3b82fd79c3e3662c97b53b732
Closes-Bug: 1838088
Depends-On: https://review.opendev.org/#/c/675686/
Signed-off-by: John Kung <john.kung@windriver.com>
2019-08-09 15:45:35 -04:00
2019-07-05 01:22:19 +00:00
2019-04-03 22:30:59 -04:00
2019-07-03 09:17:48 -04:00
2019-06-14 15:09:09 -07:00
2019-05-03 14:48:56 -04:00
2019-01-30 16:40:20 -08:00
2019-07-05 13:42:52 -04:00
2019-01-08 11:42:04 -05:00
2019-04-19 19:52:31 +00:00
2019-05-16 17:22:59 -05:00
2018-05-31 07:36:35 -07:00

integ

StarlingX Integration

Description
StarlingX Integration and packaging
Readme 52 MiB
Languages
Shell 33.1%
JavaScript 24.1%
Perl 14.3%
Python 10.3%
Makefile 6.6%
Other 11.5%