<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">1/ make this a topic for next call?<div><br></div><div>2/ tomorrow is holiday, then many of us will be traveling on Wednesday. Did we say we canceled both calls this week?<br><br><div id="AppleMailSignature" dir="ltr">Lixia (from my iPhone)<div><br></div></div><div dir="ltr"><br>On Aug 30, 2019, at 10:48 AM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">Dear folks<br><br>Right now, all Jenkins slaves hosted at UCLA are down. UCLA hosts all macOS 10.13 slaves. Therefore, none of the build jobs can complete.<br><br>This is not the first time that all slaves of a certain OS are failing at the same time, and most likely this would not be the last.<br><br>How about deploying the nodes in a more resilient way?<br><b>For each OS version, there should be slaves in at least two different sites.</b><br>This ensures the build jobs can proceed when there is at most one failure.<br><br>Yours, Junxiao<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 3, 2018 at 11:03 AM Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>20180402 NFD call discussed this issue.<br></div><div><br></div><div>Beichuan reveals that Ashiq is going to take over Jenkins in May 2018. During the transition, he is going to learn how to deploy macOS slaves, and then he can start swapping nodes to be more resilient.</div><div><br></div><div>There were also concerns about the Jenkins master being deployed at only one site, but there isn't a good solution yet.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 31, 2018 at 10:04 PM, Junxiao Shi <span dir="ltr"><<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Dear folks</div><div dir="auto"><br></div><div dir="auto">Right now, all Jenkins slaves hosted at CSU are down. CSU hosts all OSX 10.12 and 10.13 slaves. Therefore, none of the build jobs can complete.</div><div dir="auto">This is not the first time that all slaves of a certain OS are failing at the same time, and most likely this would not be the last.</div><div dir="auto"><br></div><div dir="auto">How about deploying the nodes in a more resilient way?</div><div dir="auto"><b>For each OS version, there should be slaves in at least two different sites</b>.</div><div dir="auto">This ensures the build jobs can proceed when there is at most one failure.</div><div dir="auto"><br></div><div dir="auto">Yours, Junxiao</div></blockquote></div><br></div>
</blockquote></div></div>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>Nfd-dev mailing list</span><br><span><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a></span><br><span><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a></span><br></div></blockquote></div></body></html>