So, to summarise, here is what I'll do, and the order in which I plan to do it:
1) Take fast models offline 2) Take snapshots of dogfood, staging and fastmodels01/03 (can't do 02 as it's broken) 3) update/upgrade all cloud nodes 4) reboot the cloud 5) Work on fastmodels02 Thanks Dave On 17 Oct 2012, at 15:19, Dave Pigott <[email protected]> wrote: > > On 17 Oct 2012, at 15:10, Andy Doan <[email protected]> wrote: > >> On 10/17/2012 08:51 AM, Dave Pigott wrote: >>>>>>> Obviously, if I do this, it will disrupt staging, dogfood and >>>>>>> fastmodels, so this is a warning that absent from any dissent, I will >>>>>>> reboot the cloud tomorrow morning. If you would rather defer this >>>>>>> let's discuss when it should be deferred to. Obviously, to get the v8 >>>>>>> fast model instance up is paramount. >>>>> >>>>> Interrupting staging and dogfood is fine, I think. For fastmodels, if >>>>> you put the devices offline in the scheduler before the interruption and >>>>> put >>>>> them back online after it's done (i.e. control will still be accepting >>>>> jobs and queuing them), it should be OK. >>>>> >>> Of course. Was planning on that, but good to be reminded, and I should have >>> listed it in my e-mail. >> >> Also - can we make sure that we do a snapshot of each system so that we >> don't have to re-create the instance? > > Good idea, although the way things should work is that the instances will > come up exactly as they were when the nodes were closed down. I'm not > proposing to delete the nodes and re-create them. > > Dave _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
