<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</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>I agree we need to separate out the different CI jobs into their own accounts. We'll start on that and I’ll get back to you </div>
<div><br>
</div>
<div>Thanks,</div>
<div>Rich</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>Edgar Magana <<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"Announcements for third party CI operators." <<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, November 20, 2014 at 4:45 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>" <<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Third-party-announce] Cisco CSR1KV CI Failing and recheck commands<br>
</div>
<div><br>
</div>
<div>
<div 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>
<div>Rich,</div>
<div><br>
</div>
<div>My strong suggestion is to separate Cisco CI into multiple accounts. You can request new accounts for these different jobs/technologies:</div>
<div><a href="http://ci.openstack.org/third_party.html#requesting-a-service-account">http://ci.openstack.org/third_party.html#requesting-a-service-account</a></div>
<div><br>
</div>
<div>It will provide a more granular visibility for everybody as well as a easier management when one of those jobs got broken again (hopefully not very often).</div>
<div><br>
</div>
<div>On the recheck commands, please update the wiki page with the corresponding strings:</div>
<div><a href="https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin_and_Drivers">https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin_and_Drivers</a></div>
<div><br>
</div>
<div>Unfortunately, I feel uncomfortable to re-enable a CI system that is incomplete at this moment. I believe that the above suggestion will help in many ways avoiding this situation again.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Edgar</div>
</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>"Richard Winters (riwinter)" <<a href="mailto:riwinter@cisco.com">riwinter@cisco.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>" <<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, November 20, 2014 at 1:04 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>" <<a href="mailto:third-party-announce@lists.openstack.org">third-party-announce@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Third-party-announce] Cisco CSR1KV CI Failing and recheck commands<br>
</div>
<div><br>
</div>
<div>
<div 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>Hello Anita, Edgar</div>
<div><br>
</div>
<div>I’m working with Nikolay and Dane on Cisco’s CI stability problem. </div>
<div><br>
</div>
<div>We are currently evaluating the failures on the CSR1KV CI and implementing corrective actions to stabilize it. While this activity is progressing we have internally disabled both the CSR1KV as well as the VPNaaS jobs from running. </div>
<div><br>
</div>
<div>At this time you could reenable the Cisco CI to pick up the remaining jobs (apic-nexus, ml2-multinode-nexus, ml2-nexus and n1kv_neutron) which we feel have been running reliably. Once we have identified and corrected all the problems with the CSR1KV/VPNaaS
jobs we’ll go through any necessary procedures to reintroduce them. </div>
<div><br>
</div>
<div>Also, AFAIK the Cisco recheck command is available and hasn’t changed since it was first implemented. Let me know if your looking for a change in the way it currently works.</div>
<div><br>
</div>
<div>Thanks</div>
<div>Rich</div>
<div><br>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>