[Gluster-infra] Migrating Gerrit and Jenkins out of iWeb
mscherer at redhat.com
Wed Feb 10 13:52:41 UTC 2016
Le mercredi 10 février 2016 à 19:18 +0530, Kaushal M a écrit :
> On Wed, Feb 10, 2016 at 1:53 PM, Michael Scherer <mscherer at redhat.com> wrote:
> > Le mercredi 10 février 2016 à 11:44 +0530, Kaushal M a écrit :
> >> On Sun, Feb 7, 2016 at 2:34 PM, Michael Scherer <mscherer at redhat.com> wrote:
> >> > Le samedi 06 février 2016 à 18:17 -0500, Vijay Bellur a écrit :
> >> >> I think starting around 0900 UTC on Friday of next week (12th Feb)
> >> >> should be possible. We should be done with 3.7.8 before that and can
> >> >> afford a bit of downtime then. In case any assistance is needed post the
> >> >> migration, we can have folks around the clock to help.
> >> >>
> >> >> If migration fails for an unforeseen reason, would we be able to
> >> >> rollback and maintain status quo?
> >> >
> >> > Yes. Worst case, I think people would just redo a few reviews or push
> >> > again patch.
> >> >
> >> > Also, since gerrit is critical, I wonder what is the support of gerrit
> >> > for slaves and replication.
> >> Michael are you okay with the time? If you are, I think we should
> >> announce the migration.
> > I am ok.
> So as discussed in the community meeting, we will be announcing the
> migration and downtime. Vijay, you said you required the exact
> schedule? This is what I expect
> Friday 12th Feb 2016
> 0900 UTC : build.gluster.org and review.gluster.org are taken down and
> migration begins.
> <1-2 hrs?>: Michael copies over data onto the RH community infra and
> sets up the VMs.
> <? hrs>: The DNS records are updated, and some time is for it to propogate.
> <3hr?>: Verify everything is working well (I can help with this). We'd
> possibly need to run a regression job, so this will take longest I
> 1700UTC <or earlier>: We announce the finish of the migration and open
> the services back up. If migration failed, we bring the existing
> servers back on, and continue on.
> Also, Michael are you happy migrating just one server or both?
ideally, I would prefer both, but as i had trouble to move the jenkins
VM while it was running, I couldn't prepare the network setup. I would
need to open a few ports, etc, so that requires tickets to IT.
> I case
> you can only do one server we'd like Jenkins to migrated out.
The problem is that this requires tome network changes, unlike the
gerrit one, where the work was already done.
Sysadmin, Community Infrastructure and Platform, OSAS
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Gluster-infra