<p dir="ltr">On Feb 12, 2016 10:50 PM, "Kaushal M" <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>
><br>
> On Fri, Feb 12, 2016 at 10:47 PM, Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br>
> > Le vendredi 12 février 2016 à 12:16 +0100, Michael Scherer a écrit :<br>
> >> Le mercredi 10 février 2016 à 19:18 +0530, Kaushal M a écrit :<br>
> >> > On Wed, Feb 10, 2016 at 1:53 PM, Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br>
> >> > > Le mercredi 10 février 2016 à 11:44 +0530, Kaushal M a écrit :<br>
> >> > >> On Sun, Feb 7, 2016 at 2:34 PM, Michael Scherer <<a href="mailto:mscherer@redhat.com">mscherer@redhat.com</a>> wrote:<br>
> >> > >> > Le samedi 06 février 2016 à 18:17 -0500, Vijay Bellur a écrit :<br>
> >> > >> >> I think starting around 0900 UTC on Friday of next week (12th Feb)<br>
> >> > >> >> should be possible. We should be done with 3.7.8 before that and can<br>
> >> > >> >> afford a bit of downtime then. In case any assistance is needed post the<br>
> >> > >> >> migration, we can have folks around the clock to help.<br>
> >> > >> >><br>
> >> > >> >> If migration fails for an unforeseen reason, would we be able to<br>
> >> > >> >> rollback and maintain status quo?<br>
> >> > >> ><br>
> >> > >> > Yes. Worst case, I think people would just redo a few reviews or push<br>
> >> > >> > again patch.<br>
> >> > >> ><br>
> >> > >> > Also, since gerrit is critical, I wonder what is the support of gerrit<br>
> >> > >> > for slaves and replication.<br>
> >> > >><br>
> >> > >> Michael are you okay with the time? If you are, I think we should<br>
> >> > >> announce the migration.<br>
> >> > ><br>
> >> > > I am ok.<br>
> >> ><br>
> >> > So as discussed in the community meeting, we will be announcing the<br>
> >> > migration and downtime. Vijay, you said you required the exact<br>
> >> > schedule? This is what I expect<br>
> >> ><br>
> >> > Friday 12th Feb 2016<br>
> >> ><br>
> >> > 0900 UTC : <a href="http://build.gluster.org">build.gluster.org</a> and <a href="http://review.gluster.org">review.gluster.org</a> are taken down and<br>
> >> > migration begins.<br>
> >> > <1-2 hrs?>: Michael copies over data onto the RH community infra and<br>
> >> > sets up the VMs.<br>
> >> > <? hrs>: The DNS records are updated, and some time is for it to propogate.<br>
> >> > <3hr?>: Verify everything is working well (I can help with this). We'd<br>
> >> > possibly need to run a regression job, so this will take longest I<br>
> >> > think.<br>
> >> ><br>
> >> > 1700UTC <or earlier>: We announce the finish of the migration and open<br>
> >> > the services back up. If migration failed, we bring the existing<br>
> >> > servers back on, and continue on.<br>
> >><br>
> >> So, for people wanting to know, the migration has started.<br>
> >><br>
> >> 1) gerrit<br>
> >> ----------<br>
> >> gerrit seems to be ok, it has a new IP 66.187.224.201<br>
> >><br>
> >> people who used to have access there need to contact me so I can<br>
> >> explain/create required account on the new virt host.<br>
> >><br>
> >> the old VM is shutdown for now. I will make a backup copy of the disk.<br>
> >><br>
> >> 2) jenkins<br>
> >> ----------<br>
> >><br>
> >> so the preparation of the migration didn't worked as well, so we have to<br>
> >> copy the VM when offline, and then prepare it later ( ie, import in<br>
> >> libvirt, adjust network, etc). So jenkins master is offline (sorry manu<br>
> >> for your tcpdump monitoring), we are making a copy of the disk that is<br>
> >> gonna take between 3 and 14h (most likely < 4h, but rsync estimation is<br>
> >> moving a lot), and then restart like before.<br>
> ><br>
> > So turn out I was wrong, and the copy is taking a much longer time.<br>
> > Despites me trying to investigate why, it didn't copied everything.<br>
> ><br>
> > So the new plan is to stop the VM, make a local copy of the disk, start<br>
> > the VM, and then copy that one over the new server, prepare for the new<br>
> > host (firewall, public ip, etc), and sync from the old VM to the new<br>
> > host.<br>
> ><br>
> > All is ok with this plan ?<br>
><br>
> Sounds good to me. No need to wait for the copy to happen and the<br>
> downtime should be minimal like with gerrit.<br>
></p>
<p dir="ltr">Can we schedule this minimal downtime sometime tomorrow? Or if possible tonight itself. Since we don't require a long downtime we can do this anytime we like. </p>
<p dir="ltr">I'd like to get the migration done by the end of this week (if possible) before Michael goes on vacation. <br><br></p>
<p dir="ltr">> > --<br>
> > Michael Scherer<br>
> > Sysadmin, Community Infrastructure and Platform, OSAS<br>
> ><br>
> ><br>
</p>