Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb
On 02/06/2016 07:37 AM, Michael Scherer wrote: Le samedi 06 février 2016 à 05:41 -0500, Kaleb Keithley a écrit : - Original Message - From: "Kaushal M" Hi Vijay. I spoke with Michael about migrating off of iWeb. Another option we discussed yesterday (sorry, should have thought to have you join us) with Karanbir, in the context of using more of CentOS CI, was moving gerrit to gerrithub. (Keeping our own jenkins master on Rackspace, but using slaves in CentOS CI.) The advantage is that gerrithub is then responsible for keeping gerrit up to date (and up). KB and Amye will be sending email about this soon. Watch this space. So as I suspect that gerrithub is gonna take some time before we do evaluate everything, I will proceed with the migration of gerrit to RH DC for now. We would be likely in a better shape for a migration anywhere from here. And when I say "8h", that's a worst case. I suspect it would be better, but I propose to schedule a documentation day or something where we can put developpers to good use when gerrit is down and copied. 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? Thanks, Vijay ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1291537] [RFE] Provide mechanism to spin up reproducible test environment for all developers
https://bugzilla.redhat.com/show_bug.cgi?id=1291537 --- Comment #10 from Vijay Bellur --- COMMIT: http://review.gluster.org/13355 committed in master by Niels de Vos (nde...@redhat.com) -- commit c7d2037b8c6293663280a759a2e447d5aef130bd Author: Raghavendra Talur Date: Thu Feb 4 14:33:54 2016 +0530 vagrant-tests: Fix bug when git branch name has a / It is possible for a git branch to have a / in it. Source copy from host to VM used relative path on the assumption that VM vagrant dir will always be three levels down the topdir of repo. This assumption breaks when git branch has a / in it. Of the two solutions to fix it: a. Mangle the git branch name to not have a / b. Accomodate the possibility of have a / in git branch name. I have chosen b) because that looks cleaner. Change-Id: I6b71c31da2f5f7c349d6d6882767768b2534d14f BUG: 1291537 Signed-off-by: Raghavendra Talur Reviewed-on: http://review.gluster.org/13355 Smoke: Gluster Build System NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Niels de Vos -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xN15TSsvcv&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb
Le samedi 06 février 2016 à 05:41 -0500, Kaleb Keithley a écrit : > > - Original Message - > > From: "Kaushal M" > > > > Hi Vijay. > > > > I spoke with Michael about migrating off of iWeb. > > Another option we discussed yesterday (sorry, should have thought to have you > join us) with Karanbir, in the context of using more of CentOS CI, was moving > gerrit to gerrithub. > > (Keeping our own jenkins master on Rackspace, but using slaves in CentOS CI.) > > The advantage is that gerrithub is then responsible for keeping gerrit up to > date (and up). > > KB and Amye will be sending email about this soon. Watch this space. So as I suspect that gerrithub is gonna take some time before we do evaluate everything, I will proceed with the migration of gerrit to RH DC for now. We would be likely in a better shape for a migration anywhere from here. And when I say "8h", that's a worst case. I suspect it would be better, but I propose to schedule a documentation day or something where we can put developpers to good use when gerrit is down and copied. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Using software-factory for our infra
On Sat, Feb 06, 2016 at 04:10:01PM +0530, Kaushal M wrote: > Thanks misc for letting me know of this. > > So software-factory[1][2] is a collection of tools (gerrit, jenkins, > etherpad, pastebin etc.) that help build and test software. It > provides all these tools in a well integrated manner with > single-signon to all. > > I think using this for our infra would be very useful. What do other > people feel? Would you be interested in getting this set up for the > Gluster project? Setting up things is the easy part. We need a group of people that are accountable for maintaining any of the infrastructure components. Unless we get a whole team of globally distributed and engaged sysadmins, I would not like to see more software components in our infra. Niels > > ~kaushal > > > [1]: http://softwarefactory-project.io/docs/ > [2]: http://softwarefactory-project.io/ > ___ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra signature.asc Description: PGP signature ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Migrating Gerrit and Jenkins out of iWeb
- Original Message - > From: "Kaushal M" > > Hi Vijay. > > I spoke with Michael about migrating off of iWeb. Another option we discussed yesterday (sorry, should have thought to have you join us) with Karanbir, in the context of using more of CentOS CI, was moving gerrit to gerrithub. (Keeping our own jenkins master on Rackspace, but using slaves in CentOS CI.) The advantage is that gerrithub is then responsible for keeping gerrit up to date (and up). KB and Amye will be sending email about this soon. Watch this space. > > He's already done trial runs of migrating the b.g.o and r.g.o VMs into > the community hardware we have lying around. It's easier to migrate > these VMs into the community cage, than into rackspace. > > We know we can do this migration. But this migration would require a > downtime of about 8 hours for both Gerrit and Jenkins. If we can come > up with a time for this downtime, we can get the migration done by the > end of the upcoming week. One way we could do this (credit to misc) > would be to spend a day as a documentation day, when all developers > instead of developing work on getting documentation fixed up. > > We also need to update Gerrit, but Michael suggested doing it after > the migration. That would possibly also require some downtime later. > > In any case, what we want now is a time set for doing the migration. > Can you help us set this time? > > Thanks, > Kaushal > ___ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra > ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] Using software-factory for our infra
Thanks misc for letting me know of this. So software-factory[1][2] is a collection of tools (gerrit, jenkins, etherpad, pastebin etc.) that help build and test software. It provides all these tools in a well integrated manner with single-signon to all. I think using this for our infra would be very useful. What do other people feel? Would you be interested in getting this set up for the Gluster project? ~kaushal [1]: http://softwarefactory-project.io/docs/ [2]: http://softwarefactory-project.io/ ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] Migrating Gerrit and Jenkins out of iWeb
Hi Vijay. I spoke with Michael about migrating off of iWeb. He's already done trial runs of migrating the b.g.o and r.g.o VMs into the community hardware we have lying around. It's easier to migrate these VMs into the community cage, than into rackspace. We know we can do this migration. But this migration would require a downtime of about 8 hours for both Gerrit and Jenkins. If we can come up with a time for this downtime, we can get the migration done by the end of the upcoming week. One way we could do this (credit to misc) would be to spend a day as a documentation day, when all developers instead of developing work on getting documentation fixed up. We also need to update Gerrit, but Michael suggested doing it after the migration. That would possibly also require some downtime later. In any case, what we want now is a time set for doing the migration. Can you help us set this time? Thanks, Kaushal ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
