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

2017-07-30 Thread Hari Gowtham
On Fri, Jul 28, 2017 at 8:40 PM, Shyam Ranganathan  wrote:
> 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.
>> I would like us to push the changes for 'tiering' which Hari was working
>> on as an experimental enhancements (They seem to be feature enhancements in
>> glusterd to enable extra options for add-brick and remove-brick). Mainly
>> because with glusterfs 4.0 we will have glusterd2, and all those efforts
>> would be gone. By the looks of it, most of the patches are not causing any
>> regression failures at least.
>> I would recommend to mark them experimental features of 3.12 branch.
>> Any feedback? Left to release branch maintainers I guess.
> Considering the fact that glusterd2 would be a the way forward in 4.0, the
> patches that you mention are good candidates to get into 3.12, as this is
> possibly the last release where we should be working on glusterd related
> major feature changes.
> The patch in question looks to be:
> (experimental) and (in master with a
> merge conflict).
> @hari, can you address the patch merge issue on master, and also @glusterd
> team, can we get this reviewed in time?

I'll address the merge conflicts and update the patch on master.

> Are there other patches that are in line for the same?

the other patch is

> Shyam
> ___
> Gluster-devel mailing list

Hari Gowtham.
Gluster-devel mailing list

[Gluster-devel] Weekly Untriaged Bugs

2017-07-30 Thread jenkins
[...truncated 6 lines...] / build: Need NetBSD VM to debug / core: implementation of fallocate call in 
read-only xlator / core: non-atomic file move operation on 
same volume / core: sys_xxx() functions should guard 
against bad return values from fs / distribute: inodelk in dht_migrate_file 
is ineffective for hardlink migration / fuse: File Corruption Occurs with 
upgraded Client / fuse: storage.owner-uid and owner-gid 
parameters not working / glusterd: glusterd: code lacks clarity of 
logic in glusterd_get_quorum_cluster_counts() / glusterd: glusterd crash / glusterfind: Glusterfind : Move 
Operations performed in the Filesystem are not reported correctly / io-cache: [Scale] : Client logs flooded 
with "inode context is NULL" error messages / io-cache: [Scale] : Client logs flooded 
with "inode context is NULL" error messages / io-cache: [Scale] : Client logs flooded 
with "inode context is NULL" error messages / locks: [GNFS+EC] lock is being granted to 
2 different client for the same data range at a time after performing lock 
acquire/release from the clients1 / md-cache: md-cache uses incorrect xattr 
keynames for GF_POSIX_ACL keys / md-cache: md-cache: xattr values should 
not be checked with string functions / project-infrastructure: Need a way to get 
logs for aborted regression runs / project-infrastructure: Smoke test 
failing with insufficient disk space / unclassified: Trying to use user:glfs 
with vmware / website: IP address
[...truncated 2 lines...]

Description: Binary data
Gluster-devel mailing list