Re: [Gluster-devel] Network outage in the datacneter in Raleigh
Le vendredi 13 avril 2018 à 14:21 +0200, Michael Scherer a écrit : > Le vendredi 13 avril 2018 à 14:03 +0200, Michael Scherer a écrit : > > Hi, > > > > seems the internet link is down in the community cage that host our > > servers. RH IT is looking at the issue, but in the mean time, > > Jenkins > > and gerrit are down. > > > > Also Centos CI and others co hosted things are affected. > > > > I will post update when I will get more information (or when this > > is > > back) > > So this is back. IT told me this was a issue on the router and is > investigating. So far, we suspect a error when recabling something in > the DC. Following that incident, we have to apply a rather urgent security fix, so the network will be down on the 17th April, around 12h UTC (so 17h30 for Bangalore, 8h on Boston timezone, 5h on Portland one, and 14h Amsterdam one). Downtime would be around 10 minutes, no services would be rebooted, but jobs running might fail, depending where/what they are using. They would just have to be restarted however. Only services in the cage would be impacted: - gerrit - jenkins - builders in the cage Download server should not be impacted, among others. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Coverity covscan for 2018-04-16-7438f1f2 (master branch)
GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-04-16-7438f1f2 ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 4.1: Schedule, scope and review focus
- Original Message - From: "Shyam Ranganathan" To: "Gluster Devel" , "GlusterFS Maintainers" Sent: Wednesday, April 11, 2018 6:37:58 PM Subject: Re: [Gluster-devel] Release 4.1: Schedule, scope and review focus On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > Hi, > > As we have completed potential scope for 4.1 release (reflected here [1] > and also here [2]), it's time to talk about the schedule. > > - Branching date (and hence feature exception date): Apr 16th We are about 5 days away from branching, now would be a good time to think which features are slipping and call them out sooner than later! I need two more weeks time, planning to complete feature by EOD April. Can u please consider it as exception ? -- Jiffin > - Week of Apr 16th release notes updated for all features in the release > - RC0 tagging: Apr 23rd > - Week of Apr 23rd, upgrade and other testing > - RCNext: May 7th (if critical failures, or exception features arrive late) > - RCNext: May 21st > - Week of May 21st, final upgrade and testing > - GA readiness call out: May, 28th > - GA tagging: May, 30th > - +2-4 days release announcement > > and, review focus. As in older releases, I am starring reviews that are > submitted against features, this should help if you are looking to help > accelerate feature commits for the release (IOW, this list is the watch > list for reviews). This can be found handy here [3]. > > So, branching is in about 4 weeks! > > Thanks, > Shyam > > [1] Issues marked against release 4.1: > https://github.com/gluster/glusterfs/milestone/5 > > [2] github project lane for 4.1: > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > [3] Review focus dashboard: > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Unplanned Jenkins restart
Hello folks, I've just restarted Jenkins for an security update to a plugin. There was one running centos-regression job that I had to cancel. -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Regression with brick multiplex on demand
Hello folks, In the past if you had a patch that was fixing a brick multiplex failure, you couldn't test whether it actually fixed brick multiplex failures easily. You had two options: * Create a new review where you turn on brick multiplex via the code and also apply your patch. Mark a -1 for this review and iterate until tests passed. * Merge the patch and pray. Now on any patch that you want brick multiplex triggered, just add comment "run brick-mux regression" and it will trigger a run and post results to the review. This is a non-voting job. This should not mess up any votes. Please file a bug if it does. -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel