<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>+1</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Eric Windisch <<a href="mailto:ewindisch@docker.com">ewindisch@docker.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Friday, August 15, 2014 at 9:45 PM<br>
<span style="font-weight:bold">To: </span>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] Enabling silent Docker tests for Nova?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">I have proposed a _silent_ check for Nova for integration of the Docker driver:
<div><br>
</div>
<div> <a href="https://review.openstack.org/#/c/114547/">https://review.openstack.org/#/c/114547/</a><br clear="all">
<div><br>
</div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif">It has been established that this code cannot move back into Nova until the tests are running and have a solid history of success. That cannot happen unless we're allowed to run the tests. Running a
silent check on changes to Nova is the first step in establishing that history.</span><br>
</div>
<div><br>
</div>
<div>Joe Gordon suggests we need a spec to bring the driver back into Nova. Besides the fact that specs are closed and there is no intention of reintegrating the driver for Juno, I'm uncertain of proposing a spec without first having solid history of successful
testing, especially given the historical context of this driver's relationship with Nova.</div>
<div><br>
</div>
<div>If we could enable silent checks, we could help minimize API skew and branch breakages, improving driver quality and reducing maintenance while we prepare for the Kilo spec + merge windows. Furthermore, by having a history of testing, we can seek faster
inclusion into Kilo.</div>
<div><br>
</div>
<div>Finally, I acknowledge that we may be entering a window of significant load on the CI servers and I'm sensitive to the needs of the infrastructure team to remain both focused and to conserve precious compute resources. If this is an issue, then I'd like
to plot a timeline, however rough, with the infrastructure team. </div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif"><br>
</span></div>
-- <br>
<div dir="ltr">Regards,
<div>Eric Windisch</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>