<html><body><p>Hi,<br><br>I think out docker all call, use docker_for_bay, which use <br><br>CONF.docker.default_timeout.<br><br>And default_timeout can be changed any value. User can customized it per case.<br><br><br>For why set 10, maybe it was because someone local test OK. So use that value.<br><br>I think for jenkins, it can use CONF override value to make it work.<br><br><br><br><br>Thanks<br><br>Best Wishes,<br>--------------------------------------------------------------------------------<br>Kai Qiang Wu (Î⿪ǿ Kennan£©<br>IBM China System and Technology Lab, Beijing<br><br>E-mail: wkqwu@cn.ibm.com<br>Tel: 86-10-82451647<br>Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br> No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>--------------------------------------------------------------------------------<br>Follow your heart. You are miracle! <br><br><img width="16" height="16" src="cid:1__=8FBBF59BDFA473538f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for "Qiao,Liyong" ---25/11/2015 03:24:49 pm---hi all In Magnum code, we hardcode it as DEFAULT_DOCKER_TIM"><font color="#424282">"Qiao,Liyong" ---25/11/2015 03:24:49 pm---hi all In Magnum code, we hardcode it as DEFAULT_DOCKER_TIMEOUT = 10</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Qiao,Liyong" <liyong.qiao@intel.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">25/11/2015 03:24 pm</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[openstack-dev] [Magnum] Why set DEFAULT_DOCKER_TIMEOUT = 10 in docker client?</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>hi all<br>In Magnum code, we hardcode it as DEFAULT_DOCKER_TIMEOUT = 10<br>This bring troubles in some bad networking environment (or bad <br>performance swarm master)<br>At least it doesn't work on our gate.<br><br>Here is the test patch on gate </tt><tt><a href="https://review.openstack.org/249522">https://review.openstack.org/249522</a></tt><tt> , I <br>set it as 180 to make sure<br>the failure it due to time_out parameter passed to docker client, but we <br>need to chose a suitble one<br><br>I check docker client's default value,<br>DEFAULT_TIMEOUT_SECONDS = 60 , I wonder why we overwrite it as 10?<br><br>Please let me know what's your though? My suggestion is we set <br>DEFAULT_DOCKER_TIMEOUT<br>as long as our rpc time_out.<br><br>-- <br>BR, Eli(Li Yong)Qiao<br><br>[attachment "liyong_qiao.vcf" deleted by Kai Qiang Wu/China/IBM] __________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br></tt><br><br><BR>
</body></html>