Re: [Gluster-devel] Release 3.12: Status of features (Require responses!)

Hi, Here is an updated status: RC0 tagging date moved to 2nd August (awaiting 3 more feature backports before tagging RC0 and also some release notes for delivered features). This is a quick link for patches awaiting reviews and closure [2] Features awaiting backports (as these have enough

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

On 07/24/2017 09:56 PM, Pranith Kumar Karampuri wrote: On Sat, Jul 22, 2017 at 1:36 AM, Shyam > wrote: - Implement parallel writes feature on EC volume - https://github.com/gluster/glusterfs/issues/251

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

On 07/25/2017 02:56 AM, Amar Tumballi wrote: Further changes: - No new milestone assigned, IOW not moved to 4.0 by default, hence contributors working on these features would need to rekindle conversations on including the same in 4.0 on the ML or on the issue itself.

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

On 07/24/2017 03:56 AM, Niels de Vos wrote: - Decide what to do with glfs_ipc() in libgfapi -https://github.com/gluster/glusterfs/issues/269 - @nixpanic I assume there is more than just test case disabling for this, is this expected to happen by 3.12? https://review.gluster.org/17854 has

Re: [Gluster-devel] Release 3.12: Status of features (Require responses!)

On 07/24/2017 06:54 AM, Kotresh Hiremath Ravishankar wrote: - gfid-path by default - https://github.com/gluster/glusterfs/issues/139 Following patches needs to be merged. It would be back ported to 3.12 branch Once it is merged.

Re: [Gluster-devel] Question regarding to gluster and vfs

On 08/17/2017 07:36 AM, Amar Tumballi wrote: On Thu, Aug 17, 2017 at 1:21 PM, Raghavendra Talur > wrote: On Wed, Aug 16, 2017 at 5:52 PM, Ilan Schwarts > wrote: > Hi, > So this is a bit

[Gluster-devel] (was: Release 3.12: RC0 tagging date (Jul-31st-2017)) Release 3.12: RC0 Tagged!

Finally! RC0 is tagged and sent for packaging (to make it easier for users to test and provide feedback). With this we will not accept any more feature backports to 3.12, and only bug fixes will be merged (as per the stability phase guidelines [1]). This brings us to the testing/stability

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

On 07/23/2017 01:01 PM, Amar Tumballi wrote: Responses inline. On Sat, Jul 22, 2017 at 1:36 AM, Shyam > wrote: - posix: provide option to handle 'statfs()' properly when more than 1 brick is exported from 1 node -

[Gluster-devel] RIO-Distribution: Status update

Hi, Here is a detailed (and lengthy, considering it is been a while) status update on RIO. As the mail is long, you maybe interested in subsections of the same, so here are a list of sections and their numbers, 1) General information 2) What does the graph look like 3) What works 4) What

[Gluster-devel] Release 3.10.7: Tracker and dates

Hi, Release 3.10.6 is announced [1] and fixed bugs are now closed. In preparation for the 3.10.7 release, here are the required details, 1) Tracker bug to mark blockers against: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.7 2) Release tagging would be on(around) the 30th of

Re: [Gluster-devel] Locating blocker bugs for a release (and what is a blocker anyway)

On 10/12/2017 12:58 AM, Nithya Balachandran wrote: > - When to mark the blocker bug as dependent on another bug: > > Blockers are meant to track *just* blockers for a major or minor release, > not all bugs that are a part of the release. Hence when a bug is actually a

Re: [Gluster-devel] [Gluster-Maintainers] Changing Submit Type on review.gluster.org

On 09/07/2017 02:20 AM, Nigel Babu wrote: Hello folks, A few times, we've merged dependent patches out of order because the Submit type[1] did not block us from doing so. The last few times we've talked about this, we didn't actually take a strong decision either way. In yesterday's maintainers

[Gluster-devel] Release 3.13: (STM release) Details

Hi, The next community release of Gluster is 3.13, which is a short term maintenance release is slated for release on 30th Nov [1] [2]. Thus giving a 2 month head room to get to 4.0 work done, while maintaining the cadence of releasing every 3 months. This mail is to announce the scope,

[Gluster-devel] Release 3.12: Announced 3.12.0 and 3.12.1 in 5 days!

Hi, Release 3.12.0 has been announced [1] and tracker bug for 3.12.1 is now open [2]. 3.12.1 will be tagged on the 10th of Sep, which is about 5 days away, so do update the tracker bug with any blockers that are identified. Thanks, Shyam [1] Announce:

[Gluster-devel] Release 3.10.6: Preparing for the release on 30th-September 2017

Hi, Here is a quick health check on 3.10.6 and also a request for any pending patches to be backported as needed (based on the backport guidelines [1]). If there are any identified blockers, mark them against the blocker bug [2]. Major issue to be addressed: We still carry in our release

Re: [Gluster-devel] Patch backport request

Hi, This patch is not a target for a backport for the following reasons, - Addresses a performance issue - Is a large patch, and hence backport guidelines would essentially not allow it unless it is a crash or a corruption issue that is being fixed - Is available in 3.12 for consumption We

[Gluster-devel] Release 3.12: Readiness for release (request attention)

Hi, Here is a status of 3.12 from a release readiness perspective. Most importantly, if there are any known blockers for the release, please shout out ASAP. Final release tagging would be slated (around) 30th Aug, 2017 1) YELLOW: Release notes are in, but need a review by feature owners

[Gluster-devel] Release 3.12: Glusto run status

Nigel was kind enough to kick off a glusto run on 3.12 head a couple of days back. The status can be seen here [1]. The run failed, but managed to get past what Glusto does on master (see [2]). Not that this is a consolation, but just stating the fact. The run [1] failed at, 17:05:57

Re: [Gluster-devel] Release 3.12: Glusto run status

o/377/ [b] analysis of the failure: https://paste.fedoraproject.org/paste/mk6ynJ0B9AH6H9ncbyru5w On 08/25/2017 04:29 PM, Shyam Ranganathan wrote: Nigel was kind enough to kick off a glusto run on 3.12 head a couple of days back. The status can be seen here [1]. The run failed, but managed to get

Re: [Gluster-devel] Release 3.12: Readiness for release (request attention)

On 08/25/2017 04:48 PM, Shyam Ranganathan wrote: Hi, Here is a status of 3.12 from a release readiness perspective. Most importantly, if there are any known blockers for the release, please shout out ASAP. Final release tagging would be slated (around) 30th Aug, 2017 1) YELLOW: Release

[Gluster-devel] Release 3.12: Release tagged and packaged

her *STM* release - 4.1: Will be the next LTM release around April-2018 Changes to the web content for all of the above can be seen here: https://github.com/gluster/glusterweb/pull/149 Get cracking on those 4.0 features!!! Thanks, Shyam and Jiffin On 08/29/2017 04:16 PM, Shyam Ranganathan wr

Re: [Gluster-devel] Release 3.12: Readiness for release (request attention)

On 08/29/2017 06:45 AM, Amar Tumballi wrote: On Tue, Aug 29, 2017 at 3:03 AM, Shyam Ranganathan <srang...@redhat.com <mailto:srang...@redhat.com>> wrote: On 08/25/2017 04:48 PM, Shyam Ranganathan wrote: Hi, Here is a status of 3.12 from a release readiness

Re: [Gluster-devel] Release 3.12: Glusto run status

On 08/29/2017 09:31 AM, Atin Mukherjee wrote: On Tue, Aug 29, 2017 at 4:13 AM, Shyam Ranganathan <srang...@redhat.com <mailto:srang...@redhat.com>> wrote: Nigel, Shwetha, The latest Glusto run [a] that was started by Nigel, post fixing the prior timeout issue,

Re: [Gluster-devel] Gluster documentation search

On 08/28/2017 07:14 AM, Nigel Babu wrote: Hello folks, I spend some time today mucking about trying to figure out how to make our documentation search a better experience. The short answer is, search kind of works now. Awesome! thank you. Long answer: mkdocs creates a client side file

[Gluster-devel] Release 3.12: Release tagging tomorrow @ 12:00PM UTC

Hi, All patches and tests as required for the release are done, we will be tagging the release tomorrow at the time in subject. Shyam ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Note on github issue updates from gluster-ant

Hi, Currently, when a new change is posted referencing a github issue, an automated message is posted on the issue by gluster-ant. Further, if the patch is refreshed for any reason, another message with the same content is posted on the issue by gluster-ant. The above causes noise, and also

[Gluster-devel] Locating blocker bugs for a release (and what is a blocker anyway)

Hi, Recently I was in some conversations that mentioned having to hunt for the mail that announced the blocker bug for a release, when there is a need to mark a bug as a blocker for that release. This need not be done as here is the shortcut (if you did not know) on how to find the blocker,

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

On 09/27/2017 05:12 AM, Soumya Koduri wrote: Hi Shyam, On 09/11/2017 07:51 PM, Shyam Ranganathan wrote: - Feature proposal:    - Contributors need to request for features that will be a part of the 3.13 release, sending a mail to the devel list, and including the github issue

Re: [Gluster-devel] [Gluster-Maintainers] Client Server incompatibility with Gluster 4.0

On 10/12/2017 04:25 AM, Ric Wheeler wrote: I worry about having to update all of the clients when we have new code on servers. Typically, for example with NFS, the client negotiates the protocol version it understands and we default to the highest version the clients and servers both

Re: [Gluster-devel] [Gluster-Maintainers] [Gluster-users] Release 3.12.2 : Scheduled for the 10th of October

On 10/12/2017 08:09 AM, Jiffin Tony Thottan wrote: [2] : https://review.gluster.org/#/c/18489/ [1] : https://review.gluster.org/18506 Hi, Both issues looks like a regression. Master patch [2] got merged in master but [1] is still pending. @Rafi :

Re: [Gluster-devel] [Gluster-Maintainers] Client Server incompatibility with Gluster 4.0

On 10/12/2017 11:03 AM, Vijay Bellur wrote: Further, rolling upgrades of the server becomes a moot point, as some would be a higher version in the interim and hence prevent existing clients to talk to the same, as our upgrade process is servers first and then clients. I do not

Re: [Gluster-devel] Release 3.10.8: Planned for 30th of Nov, 2017

On 11/01/2017 09:04 AM, Shyam Ranganathan wrote: Hi, As release 3.10.6 is announced, here is are the needed details for 3.10.8 Release date: 30th Nov, 2017 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.8 It would be good to fix the outstanding sharding

Re: [Gluster-devel] Tests failing on Centos 7

As we are testing on Cent7 and for analyzing failures need a cent7 instance to debug, here is a way to do this using a cent7 container on your machine [1]. All tests do not pass or work, things that hang are noted. Post first setup, this becomes easier ;) There is still some work to ensure

[Gluster-devel] Release 3.13: Release notes (Please read and contribute)

Hi, 3.13 RC0 is around the corner (possibly tomorrow). Towards this and the final 3.13.0 release, I was compiling the features that are a part of 3.13 and also attempted to write out the release notes for the same [1]. Some features have data and other do not (either in the commit message

Re: [Gluster-devel] IPC test is failing due to Segmentation Fault

On 11/15/2017 10:47 AM, Shyam Ranganathan wrote: On 11/14/2017 01:57 AM, Vaibhav Vaingankar wrote: Hi I am building GlusterFS from source on s390x, while testing it is seen *features/ipc.t *is failing cause of segmentation fault. here is the bt log: Please let me know if the issue is caused

[Gluster-devel] Release 4.0: Schedule and scope clarity (responses needed)

Hi, As this is a longish mail, there are a few asks below, that I request folks to focus and answer. 4.0 is a STM release (Short Term Maintenance), further, 4.1 is also slated as a STM release (although the web pages read differently and will be corrected shortly). Finally 4.2 would be the

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

On 10/31/2017 02:52 PM, Atin Mukherjee wrote: @maintainers on the patch review, please ensure that we have a github reference for features, else there is a lot we will miss for the same! This was a miss from my end where I should have checked the

Re: [Gluster-devel] [Gluster-users] BoF - Gluster for VM store use case

On 10/31/2017 08:36 PM, Ben Turner wrote: * Erasure coded volumes with sharding - seen as a good fit for VM disk storage I am working on this with a customer, we have been able to do 400-500 MB / sec writes! Normally things max out at ~150-250. The trick is to use multiple files, create the

[Gluster-devel] Release 3.10.8: Planned for 30th of Nov, 2017

Hi, As release 3.10.6 is announced, here is are the needed details for 3.10.8 Release date: 30th Nov, 2017 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.8 It would be good to fix the outstanding sharding+rebalance bug that is being carried over in the

[Gluster-devel] RIO scope in release 4.0 (Was: Request for Comments: Upgrades from 3.x to 4.0+)

On 11/02/2017 08:10 AM, Kotresh Hiremath Ravishankar wrote: Hi Amudhan, Please go through the following that would clarify up-gradation concerns from DHT to RIO in 4.0 1. RIO would not deprecate DHT. Both DHT and RIO would co-exist. 2. DHT volumes would not be migrated to RIO. DHT volumes

[Gluster-devel] Release 3.10.9: Planned for 03rd of Jan, 2018

Hi, As release 3.10.8 is announced, here is are the needed details for 3.10.9 Release date: 03rd Jan, 2018 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.9 Shyam ___ Gluster-devel mailing list

[Gluster-devel] Release 3.13.1: Planned for 20th of Dec, 2017

Hi, As release 3.13.0 is announced, here is are the needed details for 3.13.1 Release date: 20th Dec, 2017 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.13.1 Shyam ___ Gluster-devel mailing list

[Gluster-devel] Announcing GlusterFS release 3.13.0 (Short Term Maintenance)

This is a major release that includes a range of features enhancing usability; enhancements to GFAPI for developers and a set of bug fixes. * Addition of summary option to the heal info CLI * Addition of checks for allowing lookups in AFR and removal of 'cluster.quorum-reads' volume option

[Gluster-devel] Announcing Gluster release 3.10.8 (Long Term Maintenance)

The Gluster community is pleased to announce the release of Gluster 3.10.8 (packages available at [1]). Release notes for the release can be found at [2]. We are still working on a further fix for the corruption issue when sharded volumes are rebalanced, details as below. * Expanding a

[Gluster-devel] Release 3.13 and 3.10.8

Heads up! Both releases are tagged, and off to packaging (3.10.8 packages are also available for testing prior to announcement of the release). Further release announcements will be made to the users and other lists as we close on package testing and also publishing the release notes. I

[Gluster-devel] Release 3.10.7: Preparing for the release on 30th October

Hi, Here is a status check on 3.10.7 and related work, in lieu of the impending 30th release of the next minor version. 1) Major issues in release notes: - Expanding a gluster volume that is sharded may cause file corruption - Tracked bug: https://bugzilla.redhat.com/show_bug.cgi?id=1498081 -

Re: [Gluster-devel] Test Case execution is failing

On 10/27/2017 09:15 AM, Vaibhav Vaingankar wrote: Hello, We are building GlusterFS from source. The build and installation is successful, but while running `run-tests.sh` script we have encountered the following error Result: FAIL ./tests/basic/0symbol-check.t: bad status 1

Re: [Gluster-devel] Release 3.13: (STM release) Details

On 10/31/2017 08:11 AM, Karthik Subrahmanya wrote: Hey Shyam, Can we also have the heal info summary feature [1], which is merged upstream [2]. I haven't raised an issue for this yet, I can do that by tomorrow and I need to write a doc for that. Thanks for bringing this to my notice, it

Re: [Gluster-devel] Test Case execution is failing

On 10/31/2017 09:39 AM, Shyam Ranganathan wrote: On 10/27/2017 09:15 AM, Vaibhav Vaingankar wrote: Hello, We are building GlusterFS from source. The build and installation is successful, but while running `run-tests.sh` script we have encountered the following error     Result: FAIL

Re: [Gluster-devel] Release 3.13: (STM release) Details

On 09/11/2017 10:21 AM, Shyam Ranganathan wrote: Hi, The next community release of Gluster is 3.13, which is a short term maintenance release is slated for release on 30th Nov [1] [2]. Thus giving a 2 month head room to get to 4.0 work done, while maintaining the cadence of releasing every 3

Re: [Gluster-devel] Release 3.10.7: Preparing for the release on 30th October

] release notes: https://github.com/gluster/glusterfs/blob/release-3.10/doc/release-notes/3.10.7.md On 10/25/2017 10:06 AM, Shyam Ranganathan wrote: Hi, Here is a status check on 3.10.7 and related work, in lieu of the impending 30th release of the next minor version. 1) Major issues in release

Re: [Gluster-devel] Release 4.0: Schedule and scope clarity

the primary target for the release. Thanks, Shyam P.S: Github milestones for these releases are updated accordingly On 11/20/2017 04:04 PM, Shyam Ranganathan wrote: > Hi, > > As this is a longish mail, there are a few asks below, that I request > folks to focus and answer. > > 4.

Re: [Gluster-devel] Moving Regressions to Centos 7

On 12/20/2017 04:30 AM, Nigel Babu wrote: > Hello folks, > > We've been using Centos 6 for our regressions for a long time. I believe > it's time that we moved to Centos 7. It's causing us minor issues. For > example, tests run fine on the regression boxes but don't work on local > machines or

Re: [Gluster-devel] Builds failing regularly in various jobs (Jenkins, Smoke, other)

.com/gluster/glusterfs-patch-acceptance-tests/pull/130> > > However, this will soon become more than just a warning. We should > either fix this or completely get rid of bd xlator unless someone > owns it up. > > On Mon, May 14, 2018 at 2:51 AM, Shyam Ranganat

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

. We also used gdb to inspect glusterd pmap registry and found that older stale port map data is present (in function pmap_registry_search as clients invoke a connection). Thanks, Shyam On 05/13/2018 06:56 PM, Shyam Ranganathan wrote: > Hi, > > Nigel pointed out that the nightly bric

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

to possible glusterd issue again). This does not seem to correlate to the other glusterd stale port map information (as glusterd is restarted in this case), so we possibly need to narrow this down further. Help appreciated! Thanks, Shyam On 05/13/2018 06:56 PM, Shyam Ranganathan wrote: > Hi, > &

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

On 05/14/2018 08:35 PM, Shyam Ranganathan wrote: > Further to the mail below, > > 1. Test bug-1559004-EMLINK-handling.t possibly just needs a larger > script timeout in mux based testing. I can see no errors in the 2-3 > times that it has failed, other than taking over 1000 s

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched

announcement Thanks, Shyam On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > Hi, > > Release 4.1 has been branched, as it was done later than anticipated the > calendar of tasks below would be reworked accordingly this week and > posted to the lists. > > Thanks, > Shyam >

[Gluster-devel] Brick-Mux tests failing for over 11+ weeks

Hi, Nigel pointed out that the nightly brick-mux tests are now failing for about 11 weeks and we do not have a clear run of the same. Spent some time on Friday collecting what tests failed and to an extent why, and filed bug https://bugzilla.redhat.com/show_bug.cgi?id=1577672 Asks: Whoever has

[Gluster-devel] Builds failing regularly in various jobs (Jenkins, Smoke, other)

Hi, The builds are failing due to the following, https://bugzilla.redhat.com/show_bug.cgi?id=1577668 Nigel/Misc, can you take a stab at finding out what is new that is causing these warnings to appear? Failing a quick resolution there, anyone from maintainers, could you look at supressing the

[Gluster-devel] Release 4.1: Branched

Hi, Release 4.1 has been branched, as it was done later than anticipated the calendar of tasks below would be reworked accordingly this week and posted to the lists. Thanks, Shyam On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > Hi, > > As we have completed potential scope for 4.

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

on these issues, request that the data/analysis be posted to the lists, reduces rework! On 05/15/2018 09:10 PM, Shyam Ranganathan wrote: > Hi, > > After the fix provided by Atin here [1] for the issue reported below, we > ran 7-8 runs of brick mux regressions against this fix, and we have ha

[Gluster-devel] Test case tests/bugs/fuse/bug-1309462.t is marked bad!

Recent regressions are failing due to this test case, and details on the failure are in the bug used in the patch: https://review.gluster.org/#/c/20069/1 This will be backported to 3.12 and 4.1 as needed. Shyam ___ Gluster-devel mailing list

Re: [Gluster-devel] Test case tests/bugs/fuse/bug-1309462.t is marked bad!

On 05/23/2018 10:19 AM, Shyam Ranganathan wrote: > Recent regressions are failing due to this test case, and details on the > failure are in the bug used in the patch: > https://review.gluster.org/#/c/20069/1 Patch merged against master, if your patch was failing regression in this tes

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

for the release. `master` branch still has issues, jFYI. Shyam [1] New patch to test mux only: https://review.gluster.org/#/c/20087/1 On 05/24/2018 03:08 PM, Shyam Ranganathan wrote: > After various analysis and fixes here is the current state, > > - Reverted 3 patches aimed at proper cleanup

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

After various analysis and fixes here is the current state, - Reverted 3 patches aimed at proper cleanup sequence when a mux'd brick is detached [2] - Fixed a core within the same patch, for a lookup before brick is ready case - Fixed an replicate test case, that was partly failing due to cleanup

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

On 05/16/2018 10:34 AM, Shyam Ranganathan wrote: > Some further analysis based on what Mohit commented on the patch: > > 1) gf_attach used to kill a brick is taking more time, causing timeouts > in tests, mainly br-state-check.t. Usually when there are back to back > kill_bri

Re: [Gluster-devel] Brick-Mux tests failing for over 11+ weeks

and the regression run links for logs: https://review.gluster.org/#/c/20022/3 [2] Test with core: https://build.gluster.org/job/regression-on-demand-multiplex/20/ On 05/14/2018 08:31 PM, Shyam Ranganathan wrote: > *** Calling out to Glusterd folks to take a look at this ASAP and > provide

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched

On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched

On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched

(and non-mux related): https://review.gluster.org/#/c/20109/1 On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > Here is the current release activity calendar, > > - RC0 tagging: May 14th > - RC0 builds: May 15th > - May 15th - 25th > - Upgrade testing > - General testin

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Schedule, scope and review focus

On 04/30/2018 01:02 PM, Shyam Ranganathan wrote: > On 04/18/2018 01:56 PM, Shyam Ranganathan wrote: >> On 04/11/2018 09:07 AM, Shyam Ranganathan wrote: >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: >>>> Hi, >>>> >>>> As we have comple

Re: [Gluster-devel] Release 4.1: Schedule, scope and review focus

On 04/18/2018 01:56 PM, Shyam Ranganathan wrote: > On 04/11/2018 09:07 AM, Shyam Ranganathan wrote: >> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: >>> Hi, >>> >>> As we have completed potential scope for 4.1 release (reflected here [1] >>>

Re: [Gluster-devel] [gluster-packaging] Release 4.0: Making it happen! (GlusterD2)

On 01/11/2018 02:01 AM, Kaushal M wrote: >> - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs >> will not build GD2 (as the source is not available) and will continue as >> is (which means there is enough spec file magic here that we can specify >> during release packaging

[Gluster-devel] Release 3.10.10: Planned for the 30th of Jan, 2018

Hi, As release 3.10.9 is announced, here is are the needed details for 3.10.10 Release date: 30th Jan, 2018 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.10 Shyam ___ Gluster-devel mailing list

[Gluster-devel] Release 4.0: Making it happen!

Hi, 4.0 branching date is slated on the 16th of Jan 2018 and release is slated for the end of Feb (28th), 2018. We are at the phase when we need to ensure our release scope is correct and *must* release features are landing. Towards this we need the following information for all contributors.

[Gluster-devel] Release 4.0: Making it happen! (Protocol changes and wireshark)

Hi, As we are introducing a new protocol version, the existing gluster wireshark plugin [1] needs to be updated. Further this needs to get released to wireshark users in some fashion, which looks like a need to follow wireshark roadmap [2] (not sure if this can be part of a maintenance release,

[Gluster-devel] Release 4.0: Making it happen! (GlusterD2)

Hi, (GD2 team, packaging team, please read) Here are some things we need to settle so that we can ship/release GD2 along with Gluster 4.0 release (considering this is a separate repository as of now). 1) Generating release package (read as RPM for now) to go with Gluster 4.0 release Proposal:

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

On 01/02/2018 11:08 AM, Shyam Ranganathan wrote: > Hi, > > As release 3.13.1 is announced, here is are the needed details for 3.13.2 > > Release date: 19th Jan, 2018 (20th is a Saturday) Heads up, this is tomorrow. > Tracker bug for blockers: > https://bugzilla.redha

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: Making it happen!

On 01/17/2018 10:35 PM, Amar Tumballi wrote: > 220 > I1cccb304a I6e25dbb69 > If13913fa9 > “[Cleanup]

Re: [Gluster-devel] Release 4.0: Making it happen!

On 01/10/2018 01:14 PM, Shyam Ranganathan wrote: > Hi, > > 4.0 branching date is slated on the 16th of Jan 2018 and release is > slated for the end of Feb (28th), 2018. This is today! So read on... Short update: I am going to wait a couple more days before branching, to settle rel

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13.2: Tagged and off to packaging

On 01/19/2018 07:24 PM, Shyam Ranganathan wrote: > On 01/18/2018 01:23 PM, Shyam Ranganathan wrote: >> On 01/02/2018 11:08 AM, Shyam Ranganathan wrote: >>> Hi, >>> >>> As release 3.13.1 is announced, here is are the needed details for 3.13.2 >>> >>

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

On 01/19/2018 03:18 AM, Pranith Kumar Karampuri wrote: > > 2. I'm also backporting https://review.gluster.org/#/c/18571/ > . Please > > consider merging it too today if it is ready. > > > Let's take this one in 3.13.3, I think we need to test a

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

On 01/18/2018 07:56 PM, Ravishankar N wrote: >>> 1. There is one patch https://review.gluster.org/#/c/19218/ which >>> introduces full locks for afr writevs. We're introducing this as a >>> GD_OP_VERSION_3_13_2 option. Please wait for it to be merged on 3.13 >>> branch today. Karthik, please back

Re: [Gluster-devel] Release 3.13.2: Planned for 19th of Jan, 2018

On 01/18/2018 01:23 PM, Shyam Ranganathan wrote: > On 01/02/2018 11:08 AM, Shyam Ranganathan wrote: >> Hi, >> >> As release 3.13.1 is announced, here is are the needed details for 3.13.2 >> >> Release date: 19th Jan, 2018 (20th is a Saturday) > > Heads

Re: [Gluster-devel] Release 4.0: Branched

On 01/23/2018 03:17 PM, Shyam Ranganathan wrote: > 4.0 release has been branched! > > I will follow this up with a more detailed schedule for the release, and > also the granted feature backport exceptions that we are waiting. > > Feature backports would need to make it in b

[Gluster-devel] IMP: Release 4.0: CentOS 6 packages will not be made available

Gluster Users, This is to inform you that from the 4.0 release onward, packages for CentOS 6 will not be built by the gluster community. This also means that the CentOS SIG will not receive updates for 4.0 gluster packages. Gluster release 3.12 and its predecessors will receive CentOS 6 updates

[Gluster-devel] Community NetBSD regression tests EOL'd

Gluster Users, Gluster community is deprecating running regression tests for every commit on NetBSD, and in the future continue only build sanity (and handling any build breakages) on FreeBSD. We lack contributors that can help us keep the *BSD infrastructure and functionality up to date and

Re: [Gluster-devel] Release 4.0: Release notes (please read and contribute)

Hi, I have posted an initial draft version of the release notes here [1]. I would like to *suggest* the following contributors to help improve and finish the release notes by 06th Feb, 2017. As you read this mail, if you feel you cannot contribute, do let us know, so that we can find the

[Gluster-devel] Release 3.10.11: Planned for the 28th of Feb, 2018

Hi, As release 3.10.10 is tagged and off to packaging, here are the needed details for 3.10.11 Release date: 28th Feb, 2018 Tracker bug for blockers: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.10.11 Shyam ___ Gluster-devel mailing list

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: RC0 build tomorrow (at risk)

Hi Packaging team, Preparation for RC0 is ongoing, I am waiting on scores for this patch [1] (removing experimental code from the release branch) to go through, and the following items to be resolved before tagging RC0. Devel/maintainers, 1) https://review.gluster.org/#/c/18785/ needs a

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: Branched

On 01/26/2018 06:41 AM, Raghavendra G wrote: > > > On Fri, Jan 26, 2018 at 4:49 PM, Raghavendra Gowdappa > <rgowd...@redhat.com <mailto:rgowd...@redhat.com>> wrote: > > > > - Original Message ----- > > From: "Shyam Ranganathan"

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: Branched

tps://review.gluster.org/19364  (Waiting for centos regression) > > Please merge the patches. Thanks Thanks for letting me know, one patch is merged, waiting on regression tests for the other. > > > On Thursday 25 January 2018 09:49 PM, Shyam Ranganathan wrote: >> On 01/23/20

Re: [Gluster-devel] Release 4.0: Tracker bug and release version

Hi, We now have the bugzilla release version created for 4.0, apologies for the delay. As a result here is the tracker for the release 4.0.0: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-4.0.0 Thanks, Shyam ___ Gluster-devel mailing list

Re: [Gluster-devel] Race in protocol/client and RPC

On 02/01/2018 08:25 AM, Xavi Hernandez wrote: > After having tried several things, it seems that it will be complex to > solve these races. All attempts to fix them have caused failures in > other connections. Since I've other work to do and it doesn't seem to be > causing serious failures in

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: RC0 Tagged

All pending actions as noted in the mail are complete, and 4.0.0rc0 has been tagged. This brings us to the most important phase of 4.0 which is testing out things that are not covered in our automated regression runs and such. For now, let's get some packages (as soon as I trigger the release

Re: [Gluster-devel] Release 4.0: Release notes (please read and contribute)

On 01/29/2018 05:10 PM, Shyam Ranganathan wrote: > Hi, > > I have posted an initial draft version of the release notes here [1]. > > I would like to *suggest* the following contributors to help improve and > finish the release notes by 06th Feb, 2017. As you read this mail,

Re: [Gluster-devel] [Gluster-Maintainers] Release 4.0: RC0 build tomorrow (at risk)

On 01/30/2018 03:23 PM, Shyam Ranganathan wrote: > Hi Packaging team, > > Preparation for RC0 is ongoing, I am waiting on scores for this patch > [1] (removing experimental code from the release branch) to go through, > and the following items to be resolved before tagging RC0. H

Re: [Gluster-devel] Preview of glusterfs packaging with glusterd2 (Fedora and CentOS RPMs)

On 01/30/2018 06:33 AM, Niels de Vos wrote: > I am not sure if the advantages outweight the difficulties with > bundling two projects into one package. My personal preference would be > to have a glusterd2 package and a glusterfs one, completely separate > from each other, just with tight

Re: [Gluster-devel] update on experimental branch rebase

On 01/28/2018 08:29 AM, Amar Tumballi wrote: > As the release-4.0 version branching is now done, thought it is a good > time to refresh experimental branch too. On Friday I discovered that RIO in experimental was broken, this si fixed up in this patch: https://review.gluster.org/#/c/19354/1 So,

  1   2   3   >