Re: [Gluster-devel] [Gluster-infra] Gerrit and Jenkins likely unavailable most of Sunday

[Justin Clift]

On 20 Apr 2015, at 04:43, Aravinda  wrote:
> Is it not possible to view the patches if not logged in? I think public 
> access(read only) need to be enabled.

It *does* seem to be possible after all. :)

Our test instance for Gerrit (http://newgerritv2.cloud.gluster.org) is now
running the very latest release of Gerrit + the GitHub auth plugin, and
that allows anonymous read access.

So, we might be upgrading shortly. ;)

Regards and best wishes,

Justin Clift

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Rebalance improvement design

[Nithya Balachandran]

That sounds great. Thanks.

Regards,
Nithya

- Original Message -
From: "Benjamin Turner" 
To: "Nithya Balachandran" 
Cc: "Susant Palai" , "Gluster Devel" 

Sent: Wednesday, 22 April, 2015 12:14:14 AM
Subject: Re: [Gluster-devel] Rebalance improvement design

I am setting up a test env now, I'll have some feedback for you this week.

-b

On Tue, Apr 21, 2015 at 11:36 AM, Nithya Balachandran 
wrote:

> Hi Ben,
>
> Did you get a chance to try this out?
>
> Regards,
> Nithya
>
> - Original Message -
> From: "Susant Palai" 
> To: "Benjamin Turner" 
> Cc: "Gluster Devel" 
> Sent: Monday, April 13, 2015 9:55:07 AM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
> Hi Ben,
>   Uploaded a new patch here: http://review.gluster.org/#/c/9657/. We can
> start perf test on it. :)
>
> Susant
>
> - Original Message -
> From: "Susant Palai" 
> To: "Benjamin Turner" 
> Cc: "Gluster Devel" 
> Sent: Thursday, 9 April, 2015 3:40:09 PM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
> Thanks Ben. RPM is not available and I am planning to refresh the patch in
> two days with some more regression fixes. I think we can run the tests post
> that. Any larger data-set will be good(say 3 to 5 TB).
>
> Thanks,
> Susant
>
> - Original Message -
> From: "Benjamin Turner" 
> To: "Vijay Bellur" 
> Cc: "Susant Palai" , "Gluster Devel" <
> gluster-devel@gluster.org>
> Sent: Thursday, 9 April, 2015 2:10:30 AM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
>
> I have some rebalance perf regression stuff I have been working on, is
> there an RPM with these patches anywhere so that I can try it on my
> systems? If not I'll just build from:
>
>
> git fetch git:// review.gluster.org/glusterfs refs/changes/57/9657/8 &&
> git cherry-pick FETCH_HEAD
>
>
>
> I will have _at_least_ 10TB of storage, how many TBs of data should I run
> with?
>
>
> -b
>
>
> On Tue, Apr 7, 2015 at 9:07 AM, Vijay Bellur < vbel...@redhat.com > wrote:
>
>
>
>
> On 04/07/2015 03:08 PM, Susant Palai wrote:
>
>
> Here is one test performed on a 300GB data set and around 100%(1/2 the
> time) improvement was seen.
>
> [root@gprfs031 ~]# gluster v i
>
> Volume Name: rbperf
> Type: Distribute
> Volume ID: 35562662-337e-4923-b862- d0bbb0748003
> Status: Started
> Number of Bricks: 4
> Transport-type: tcp
> Bricks:
> Brick1: gprfs029-10ge:/bricks/ gprfs029/brick1
> Brick2: gprfs030-10ge:/bricks/ gprfs030/brick1
> Brick3: gprfs031-10ge:/bricks/ gprfs031/brick1
> Brick4: gprfs032-10ge:/bricks/ gprfs032/brick1
>
>
> Added server 32 and started rebalance force.
>
> Rebalance stat for new changes:
> [root@gprfs031 ~]# gluster v rebalance rbperf status
> Node Rebalanced-files size scanned failures skipped status run time in secs
> - --- --- --- --- ---
>  --
> localhost 74639 36.1GB 297319 0 0 completed 1743.00
> 172.17.40.30 67512 33.5GB 269187 0 0 completed 1395.00
> gprfs029-10ge 79095 38.8GB 284105 0 0 completed 1559.00
> gprfs032-10ge 0 0Bytes 0 0 0 completed 402.00
> volume rebalance: rbperf: success:
>
> Rebalance stat for old model:
> [root@gprfs031 ~]# gluster v rebalance rbperf status
> Node Rebalanced-files size scanned failures skipped status run time in secs
> - --- --- --- --- ---
>  --
> localhost 86493 42.0GB 634302 0 0 completed 3329.00
> gprfs029-10ge 94115 46.2GB 687852 0 0 completed 3328.00
> gprfs030-10ge 74314 35.9GB 651943 0 0 completed 3072.00
> gprfs032-10ge 0 0Bytes 594166 0 0 completed 1943.00
> volume rebalance: rbperf: success:
>
>
> This is interesting. Thanks for sharing & well done! Maybe we should
> attempt a much larger data set and see how we fare there :).
>
> Regards,
>
>
> Vijay
>
>
> __ _
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/ mailman/listinfo/gluster-devel
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] cluster syncop framework

[Pranith Kumar Karampuri]

hi,
For implementing directory healing in ec I needed to generalize the 
cluster syncop implementation done in afr-v2 which makes things easy for 
implementing something like self-heal. The patch is at 
http://review.gluster.org/10240
Please feel free to let me know your comments. 
http://review.gluster.org/10298 uses this frame work to implement 
directory/name self-heal in ec. Re-implemented metadata self-heal in ec 
as well using this framework.


Most important things to look at are the following macros:
FOP_ONLIST - Performs the fop on the list provided in parallel
FOP_SEQ - Performs the fop on the list provided sequentially
FOP_CBK - Common cbk implementation which stores the replies from each 
of the subvolumes.


I have cced the people who I know have used barrier framework which is 
used to implement this.


One interesting thought for future is  to use this frame work in I/O 
path and measure the performance difference. If the performance 
difference is not a lot, we can probably use this heavily, because it 
makes things really easy.


Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] How to fix GITHUB_USER error when signing in

[Justin Clift]

We're still tweaking settings with the new GitHub Authenticaion
for Gerrit (and looking for a way to enable anonymous read access).

If you get this error when trying to sign in, it means you need
to clear your browser cookies:

  The HTTP server did not provide the username in the GITHUB_USER
  header when it forwarded the request to Gerrit Code Review.

I suspect it's something to do with OAuth settings being cached
in the cookie, which become invalid any time they're changed
server side.

So... once we get the bits all figured out it shouldn't happen
again.  *fingers crossed*

+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Rebalance improvement design

[Benjamin Turner]

I am setting up a test env now, I'll have some feedback for you this week.

-b

On Tue, Apr 21, 2015 at 11:36 AM, Nithya Balachandran 
wrote:

> Hi Ben,
>
> Did you get a chance to try this out?
>
> Regards,
> Nithya
>
> - Original Message -
> From: "Susant Palai" 
> To: "Benjamin Turner" 
> Cc: "Gluster Devel" 
> Sent: Monday, April 13, 2015 9:55:07 AM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
> Hi Ben,
>   Uploaded a new patch here: http://review.gluster.org/#/c/9657/. We can
> start perf test on it. :)
>
> Susant
>
> - Original Message -
> From: "Susant Palai" 
> To: "Benjamin Turner" 
> Cc: "Gluster Devel" 
> Sent: Thursday, 9 April, 2015 3:40:09 PM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
> Thanks Ben. RPM is not available and I am planning to refresh the patch in
> two days with some more regression fixes. I think we can run the tests post
> that. Any larger data-set will be good(say 3 to 5 TB).
>
> Thanks,
> Susant
>
> - Original Message -
> From: "Benjamin Turner" 
> To: "Vijay Bellur" 
> Cc: "Susant Palai" , "Gluster Devel" <
> gluster-devel@gluster.org>
> Sent: Thursday, 9 April, 2015 2:10:30 AM
> Subject: Re: [Gluster-devel] Rebalance improvement design
>
>
> I have some rebalance perf regression stuff I have been working on, is
> there an RPM with these patches anywhere so that I can try it on my
> systems? If not I'll just build from:
>
>
> git fetch git:// review.gluster.org/glusterfs refs/changes/57/9657/8 &&
> git cherry-pick FETCH_HEAD
>
>
>
> I will have _at_least_ 10TB of storage, how many TBs of data should I run
> with?
>
>
> -b
>
>
> On Tue, Apr 7, 2015 at 9:07 AM, Vijay Bellur < vbel...@redhat.com > wrote:
>
>
>
>
> On 04/07/2015 03:08 PM, Susant Palai wrote:
>
>
> Here is one test performed on a 300GB data set and around 100%(1/2 the
> time) improvement was seen.
>
> [root@gprfs031 ~]# gluster v i
>
> Volume Name: rbperf
> Type: Distribute
> Volume ID: 35562662-337e-4923-b862- d0bbb0748003
> Status: Started
> Number of Bricks: 4
> Transport-type: tcp
> Bricks:
> Brick1: gprfs029-10ge:/bricks/ gprfs029/brick1
> Brick2: gprfs030-10ge:/bricks/ gprfs030/brick1
> Brick3: gprfs031-10ge:/bricks/ gprfs031/brick1
> Brick4: gprfs032-10ge:/bricks/ gprfs032/brick1
>
>
> Added server 32 and started rebalance force.
>
> Rebalance stat for new changes:
> [root@gprfs031 ~]# gluster v rebalance rbperf status
> Node Rebalanced-files size scanned failures skipped status run time in secs
> - --- --- --- --- ---
>  --
> localhost 74639 36.1GB 297319 0 0 completed 1743.00
> 172.17.40.30 67512 33.5GB 269187 0 0 completed 1395.00
> gprfs029-10ge 79095 38.8GB 284105 0 0 completed 1559.00
> gprfs032-10ge 0 0Bytes 0 0 0 completed 402.00
> volume rebalance: rbperf: success:
>
> Rebalance stat for old model:
> [root@gprfs031 ~]# gluster v rebalance rbperf status
> Node Rebalanced-files size scanned failures skipped status run time in secs
> - --- --- --- --- ---
>  --
> localhost 86493 42.0GB 634302 0 0 completed 3329.00
> gprfs029-10ge 94115 46.2GB 687852 0 0 completed 3328.00
> gprfs030-10ge 74314 35.9GB 651943 0 0 completed 3072.00
> gprfs032-10ge 0 0Bytes 594166 0 0 completed 1943.00
> volume rebalance: rbperf: success:
>
>
> This is interesting. Thanks for sharing & well done! Maybe we should
> attempt a much larger data set and see how we fare there :).
>
> Regards,
>
>
> Vijay
>
>
> __ _
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/ mailman/listinfo/gluster-devel
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Unable to access review.gluster.org

[Aravinda]

Public access(readonly) issue is still not resolved. Github 
authentication based login is working. Update your github username in 
https://public.pad.fsfe.org/p/gluster-gerrit-migration once logged in.


~aravinda

On 04/21/2015 10:08 PM, Nagaprasad Sathyanarayana wrote:

I get a GitHub login page. Earlier this was not the case and could directly 
access review.gluster.org. Is this being resolved or this is an expected 
behaviour.

Thanks
Naga

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Fwd: [Nfs-ganesha-devel] Announce GA of Ganesha V2.2.0

[Kaleb KEITHLEY]

 Forwarded Message 
Subject: [Nfs-ganesha-devel] Announce GA of Ganesha V2.2.0
Date: Tue, 21 Apr 2015 09:30:44 -0700
From: Frank Filz 
To: 'NFS Ganesha Developers' 

Branch: Master

Tag: V2.2.0

Release Highlights:

* Ganesha supports granting delegations

* There have been numerous config changes

* Ganesha now includes systemd scripts

* Improved packaging for RPM and Debian

* Major stability improvements

* non-QT based python tools

* Support for Ganesha to be a pNFS DS only, no MDS

* SECINFO in preferred order

* LTTng support

* NFS v4.2 support

* Major improvements in 9p support

* Code cleanup (checkpatch and Coverity)

* ntirpc improvements

* FSAL_GLUSTER updated with pNFS and ACL support and more


--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
___
Nfs-ganesha-devel mailing list
nfs-ganesha-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Unable to access review.gluster.org

[Nagaprasad Sathyanarayana]

I get a GitHub login page. Earlier this was not the case and could directly 
access review.gluster.org. Is this being resolved or this is an expected 
behaviour. 

Thanks
Naga 

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] FYI, nfs-ganesha-2.2.0 GA was released today

[Kaleb KEITHLEY]

Hi,

$Subject

--

Kaleb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Rebalance improvement design

[Nithya Balachandran]

Hi Ben,

Did you get a chance to try this out?

Regards,
Nithya

- Original Message -
From: "Susant Palai" 
To: "Benjamin Turner" 
Cc: "Gluster Devel" 
Sent: Monday, April 13, 2015 9:55:07 AM
Subject: Re: [Gluster-devel] Rebalance improvement design

Hi Ben,
  Uploaded a new patch here: http://review.gluster.org/#/c/9657/. We can start 
perf test on it. :)

Susant

- Original Message -
From: "Susant Palai" 
To: "Benjamin Turner" 
Cc: "Gluster Devel" 
Sent: Thursday, 9 April, 2015 3:40:09 PM
Subject: Re: [Gluster-devel] Rebalance improvement design

Thanks Ben. RPM is not available and I am planning to refresh the patch in two 
days with some more regression fixes. I think we can run the tests post that. 
Any larger data-set will be good(say 3 to 5 TB).

Thanks,
Susant

- Original Message -
From: "Benjamin Turner" 
To: "Vijay Bellur" 
Cc: "Susant Palai" , "Gluster Devel" 

Sent: Thursday, 9 April, 2015 2:10:30 AM
Subject: Re: [Gluster-devel] Rebalance improvement design


I have some rebalance perf regression stuff I have been working on, is there an 
RPM with these patches anywhere so that I can try it on my systems? If not I'll 
just build from: 


git fetch git:// review.gluster.org/glusterfs refs/changes/57/9657/8 && git 
cherry-pick FETCH_HEAD 



I will have _at_least_ 10TB of storage, how many TBs of data should I run with? 


-b 


On Tue, Apr 7, 2015 at 9:07 AM, Vijay Bellur < vbel...@redhat.com > wrote: 




On 04/07/2015 03:08 PM, Susant Palai wrote: 


Here is one test performed on a 300GB data set and around 100%(1/2 the time) 
improvement was seen. 

[root@gprfs031 ~]# gluster v i 

Volume Name: rbperf 
Type: Distribute 
Volume ID: 35562662-337e-4923-b862- d0bbb0748003 
Status: Started 
Number of Bricks: 4 
Transport-type: tcp 
Bricks: 
Brick1: gprfs029-10ge:/bricks/ gprfs029/brick1 
Brick2: gprfs030-10ge:/bricks/ gprfs030/brick1 
Brick3: gprfs031-10ge:/bricks/ gprfs031/brick1 
Brick4: gprfs032-10ge:/bricks/ gprfs032/brick1 


Added server 32 and started rebalance force. 

Rebalance stat for new changes: 
[root@gprfs031 ~]# gluster v rebalance rbperf status 
Node Rebalanced-files size scanned failures skipped status run time in secs 
- --- --- --- --- --- 
 -- 
localhost 74639 36.1GB 297319 0 0 completed 1743.00 
172.17.40.30 67512 33.5GB 269187 0 0 completed 1395.00 
gprfs029-10ge 79095 38.8GB 284105 0 0 completed 1559.00 
gprfs032-10ge 0 0Bytes 0 0 0 completed 402.00 
volume rebalance: rbperf: success: 

Rebalance stat for old model: 
[root@gprfs031 ~]# gluster v rebalance rbperf status 
Node Rebalanced-files size scanned failures skipped status run time in secs 
- --- --- --- --- --- 
 -- 
localhost 86493 42.0GB 634302 0 0 completed 3329.00 
gprfs029-10ge 94115 46.2GB 687852 0 0 completed 3328.00 
gprfs030-10ge 74314 35.9GB 651943 0 0 completed 3072.00 
gprfs032-10ge 0 0Bytes 594166 0 0 completed 1943.00 
volume rebalance: rbperf: success: 


This is interesting. Thanks for sharing & well done! Maybe we should attempt a 
much larger data set and see how we fare there :). 

Regards, 


Vijay 


__ _ 
Gluster-devel mailing list 
Gluster-devel@gluster.org 
http://www.gluster.org/ mailman/listinfo/gluster-devel 

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Returning right ret codes in case of failure of a glusterd command

[Niels de Vos]

On Tue, Apr 21, 2015 at 06:07:00PM +0530, Atin Mukherjee wrote:
> 
> 
> On 04/21/2015 05:47 PM, Avra Sengupta wrote:
> > Hi,
> > 
> > Today whenever a gluster command fails the ret code is always 1.
> > Irrespective of the failure. I have sent the following patch which takes
> > a first step towards bringing some order to this chaos.
> Could you explain a bit more about the current problem if we do not have
> separate ret code?

Different return values for a command is quite common. One of the major
examples is documented in 'man 8 mount' in the 'RETURN CODES' chapter.

Scripts and other applications can then use the return code to inform
the users/admins and act in a more suitable way.

Cheers,
Niels

> 
> ~Atin
> > http://review.gluster.org/10313
> > 
> > It addresses the following scenarios:
> > 
> > 1. Invalid Syntax: I have incorporated this for the snapshot commands
> > only for now. In case of an invalid syntax the retcode will be 2.
> > 2. Another transaction in progress errors: In case the command fails to
> > acquire a lock, because another transaction is in progress the retcode
> > will be 3.
> > 
> > If the approach is fine, and it's fine to go with such incremental
> > retcodes, then once this patch gets accepted, I will send further
> > patches on top of this one. I would also urge other component owners to
> > block retcodes for their components in "glusterd-errno.h", and start
> > doing the same.
> > 
> > Regards,
> > Avra
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> -- 
> ~Atin
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel


pgp0hHmWtlKwe.pgp
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Request for assistance on improving bugs.cloud.gluster.org

[Niels de Vos]

On Tue, Apr 21, 2015 at 04:28:57PM +0530, Aravinda wrote:
> Cool app. Sent pull request for issue#5

Thanks! I've merged your change and pushed it to the website.

http://bugs.cloud.gluster.org/ now lists the component of the bugs, this
should make it much easier for the (sub-)maintainers and assignees to
track and correct the status of the bugs.

Niels

> 
> --
> regards
> Aravinda
> 
> On 04/20/2015 02:07 PM, Niels de Vos wrote:
> >Hey all,
> >
> >if you are not aware of its existance yet, please have a look at
> >http://bugs.cloud.gluster.org/ . This site contains a list of open bugs
> >and the status of patches posted for these bugs. The data that this page
> >displays is gathered each night, it is not real-time.
> >
> >At the moment, many bugs are in an incorrect state. Developers need to
> >be aware that release- and sub-maintainers have to keep an eye on the
> >open bugs. Bugs in a wrong state clutter the view and make it very
> >difficult to see what work is still pending. The webui is helpful
> >already, but, of course, it can be improved much more.
> >
> >I would like to make bugs.cloud.gluster.org easier to use. For this, I
> >would like some assistance from others. The code for the website is
> >located in a GitHub repository [1]. Development is rather easy. You can
> >run the data gathering script on your local system and open the
> >generated .html file with your browser.
> >
> > $ git clone https://github.com/gluster/gluster-bugs-webui.git
> > $ cd gluster-bugs-webui
> > $ bash run-report.sh
> > (or download the latest .json file from [2])
> > $ firefox gluster-bugs.html
> >
> >Several requests for feature enhancements have popped up already, you
> >can find these as "issues" [3]. If there are any other improvements you
> >can think of, do not esitate to open a new feature request [4].
> >
> >It would be much appreciated if others could share their ideas, and
> >possibly send patches or pull requests.
> >
> >Thanks,
> >Niels
> >
> >
> >1. https://github.com/gluster/gluster-bugs-webui
> >2. http://bugs.cloud.gluster.org/bugs.json
> >3. https://github.com/gluster/gluster-bugs-webui/issues
> >4. https://github.com/gluster/gluster-bugs-webui/issues/new
> >___
> >Gluster-devel mailing list
> >Gluster-devel@gluster.org
> >http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Returning right ret codes in case of failure of a glusterd command

[M S Vishwanath Bhat]

On 21 April 2015 at 17:47, Avra Sengupta  wrote:

> Hi,
>
> Today whenever a gluster command fails the ret code is always 1.
> Irrespective of the failure. I have sent the following patch which takes a
> first step towards bringing some order to this chaos.
> http://review.gluster.org/10313
>
> It addresses the following scenarios:
>
> 1. Invalid Syntax: I have incorporated this for the snapshot commands only
> for now. In case of an invalid syntax the retcode will be 2.
> 2. Another transaction in progress errors: In case the command fails to
> acquire a lock, because another transaction is in progress the retcode will
> be 3.
>
> If the approach is fine, and it's fine to go with such incremental
> retcodes, then once this patch gets accepted, I will send further patches
> on top of this one. I would also urge other component owners to block
> retcodes for their components in "glusterd-errno.h", and start doing the
> same.
>

+1. This even helps a great deal in automation, especially the "another
transaction is progress"

Best Regards,
Vishwanath


> Regards,
> Avra
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Returning right ret codes in case of failure of a glusterd command

[Niels de Vos]

On Tue, Apr 21, 2015 at 05:47:04PM +0530, Avra Sengupta wrote:
> Hi,
> 
> Today whenever a gluster command fails the ret code is always 1.
> Irrespective of the failure. I have sent the following patch which takes a
> first step towards bringing some order to this chaos.
> http://review.gluster.org/10313
> 
> It addresses the following scenarios:
> 
> 1. Invalid Syntax: I have incorporated this for the snapshot commands only
> for now. In case of an invalid syntax the retcode will be 2.
> 2. Another transaction in progress errors: In case the command fails to
> acquire a lock, because another transaction is in progress the retcode will
> be 3.
> 
> If the approach is fine, and it's fine to go with such incremental retcodes,
> then once this patch gets accepted, I will send further patches on top of
> this one. I would also urge other component owners to block retcodes for
> their components in "glusterd-errno.h", and start doing the same.

Sounds like a very useful improvement. Please document these return
codes as much as possible in "man gluster" too.

Thanks,
Niels


pgpaso8SdzGdu.pgp
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Minutes of today's Gluster Community Bug Triage meeting

[Atin Mukherjee]

On 04/21/2015 09:22 AM, Atin Mukherjee wrote:
> Hi all,
> 
> This meeting is scheduled for anyone that is interested in learning more
> about, or assisting with the Bug Triage.
> 
> Meeting details:
> - location: #gluster-meeting on Freenode IRC
> ( https://webchat.freenode.net/?channels=gluster-meeting )
> - date: every Tuesday
> - time: 12:00 UTC
> (in your terminal, run: date -d "12:00 UTC")
> - agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
> 
> Currently the following items are listed:
> * Roll Call
> * Status of last weeks action items
> * Group Triage
> * Open Floor
> 
> The last two topics have space for additions. If you have a suitable bug
> or topic to discuss, please add it to the agenda.
> 
> Appreciate your participation.
> 

Minutes:
http://meetbot.fedoraproject.org/gluster-meeting/2015-04-21/gluster-meeting.2015-04-21-12.00.html
Minutes (text):
http://meetbot.fedoraproject.org/gluster-meeting/2015-04-21/gluster-meeting.2015-04-21-12.00.txt
Log:
http://meetbot.fedoraproject.org/gluster-meeting/2015-04-21/gluster-meeting.2015-04-21-12.00.log.html


Meeting summary
---
* roll call  (atinmu, 12:01:07)

* Status of last weeks action items  (atinmu, 12:06:02)

* Group Triage  (atinmu, 12:07:48)
  * LINK: http://goo.gl/WuDQun would be it  (ndevos, 12:08:56)

* Open Floor  (atinmu, 12:31:15)

Meeting ended at 12:40:11 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* atinmu (47)
* ndevos (35)
* kkeithley_ (23)
* zodbot (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

> ~Atin
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
> 
> 

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Returning right ret codes in case of failure of a glusterd command

[Atin Mukherjee]

On 04/21/2015 05:47 PM, Avra Sengupta wrote:
> Hi,
> 
> Today whenever a gluster command fails the ret code is always 1.
> Irrespective of the failure. I have sent the following patch which takes
> a first step towards bringing some order to this chaos.
Could you explain a bit more about the current problem if we do not have
separate ret code?

~Atin
> http://review.gluster.org/10313
> 
> It addresses the following scenarios:
> 
> 1. Invalid Syntax: I have incorporated this for the snapshot commands
> only for now. In case of an invalid syntax the retcode will be 2.
> 2. Another transaction in progress errors: In case the command fails to
> acquire a lock, because another transaction is in progress the retcode
> will be 3.
> 
> If the approach is fine, and it's fine to go with such incremental
> retcodes, then once this patch gets accepted, I will send further
> patches on top of this one. I would also urge other component owners to
> block retcodes for their components in "glusterd-errno.h", and start
> doing the same.
> 
> Regards,
> Avra
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

-- 
~Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-infra] Gerrit and Jenkins likely unavailable most of Sunday

[Justin Clift]

On 21 Apr 2015, at 09:44, Vijay Bellur  wrote:

> gerrit-trigger plugin needs "Event Streaming" capability to run with Gerrit 
> 2.7+. This has been added now.
> 
> All tests (smoke, NetBSD tests) should be functional now. Please let us know 
> if you notice anything amiss.

Awesome. :)

+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Returning right ret codes in case of failure of a glusterd command

[Avra Sengupta]

Hi,

Today whenever a gluster command fails the ret code is always 1. 
Irrespective of the failure. I have sent the following patch which takes 
a first step towards bringing some order to this chaos.

http://review.gluster.org/10313

It addresses the following scenarios:

1. Invalid Syntax: I have incorporated this for the snapshot commands 
only for now. In case of an invalid syntax the retcode will be 2.
2. Another transaction in progress errors: In case the command fails to 
acquire a lock, because another transaction is in progress the retcode 
will be 3.


If the approach is fine, and it's fine to go with such incremental 
retcodes, then once this patch gets accepted, I will send further 
patches on top of this one. I would also urge other component owners to 
block retcodes for their components in "glusterd-errno.h", and start 
doing the same.


Regards,
Avra
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Request for assistance on improving bugs.cloud.gluster.org

[Aravinda]

Cool app. Sent pull request for issue#5

--
regards
Aravinda

On 04/20/2015 02:07 PM, Niels de Vos wrote:

Hey all,

if you are not aware of its existance yet, please have a look at
http://bugs.cloud.gluster.org/ . This site contains a list of open bugs
and the status of patches posted for these bugs. The data that this page
displays is gathered each night, it is not real-time.

At the moment, many bugs are in an incorrect state. Developers need to
be aware that release- and sub-maintainers have to keep an eye on the
open bugs. Bugs in a wrong state clutter the view and make it very
difficult to see what work is still pending. The webui is helpful
already, but, of course, it can be improved much more.

I would like to make bugs.cloud.gluster.org easier to use. For this, I
would like some assistance from others. The code for the website is
located in a GitHub repository [1]. Development is rather easy. You can
run the data gathering script on your local system and open the
generated .html file with your browser.

 $ git clone https://github.com/gluster/gluster-bugs-webui.git
 $ cd gluster-bugs-webui
 $ bash run-report.sh
 (or download the latest .json file from [2])
 $ firefox gluster-bugs.html

Several requests for feature enhancements have popped up already, you
can find these as "issues" [3]. If there are any other improvements you
can think of, do not esitate to open a new feature request [4].

It would be much appreciated if others could share their ideas, and
possibly send patches or pull requests.

Thanks,
Niels


1. https://github.com/gluster/gluster-bugs-webui
2. http://bugs.cloud.gluster.org/bugs.json
3. https://github.com/gluster/gluster-bugs-webui/issues
4. https://github.com/gluster/gluster-bugs-webui/issues/new
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.7 client rpms

[Niels de Vos]

On Tue, Apr 21, 2015 at 04:36:23PM +0530, Prasanth wrote:
> 
> On 04/21/2015 03:47 PM, Niels de Vos wrote:
> >On Tue, Apr 21, 2015 at 03:31:26PM +0530, Prasanth wrote:
> >>On 04/20/2015 01:25 PM, Niels de Vos wrote:
> >>>On Sun, Apr 19, 2015 at 06:00:06PM -0400, Paul Cuzner wrote:
> Hi,
> 
> Apologies for the dumb question.
> 
> I just thought I'd take a look at the nightly 3.7 build, and noticed
> that when I installed glusterfs-fuse for the client it pulls in
> glusterfs-server? Also the version is bumped to 3.8?
> >>>After the branching of release-3.7, the master branch has now been
> >>>tagged with v3.8dev. Your system is probably setup to use the nightly
> >>>builds of the master branch. You should be able to update your yum .repo
> >>>file so that these packages are used:
> >>>
> >>> 
> >>> http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/
> >>Hi Niels,
> >>
> >>I see only one slightly old nightly build
> >>(glusterfs-3.7dev-0.1009.git8b987be.autobuild) in [1]. Is that expected or
> >>is something broken?
> >This is indeed the last version available in the release-3.7 branch:
> >
> >- 3.7dev-0.1009.git8b987be.autobuild
> >- commit 8b987be
> >- https://github.com/gluster/glusterfs/commits/release-3.7
> >   -> see the commit-id on the right side next to the subject of the patch
> 
> Yea, I got it. But I see 2 newer builds mentioned below under the v3.7dev
> tag in [1]:
> 
> [DIR] glusterfs-3.7dev-0.1015.gita3578de.autobuild/ 
> 
>   17-Apr-2015 09:51   -   
> [DIR] glusterfs-3.7dev-0.1017.git7fb85e3.autobuild/ 
> 
>   18-Apr-2015 01:09   -   
> 
> 
> Could you please help me understand, what are these builds then?

These are builds from the master branch, before there was a v3.8dev tag.
For a few days, the master branch and release-3.7 both had the v3.7dev
as the lastest tag. This has now been corrected, the branches received
updated tags, v3.7.0alpha0 and v3.8dev.

Niels

> 
> [1] 
> http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/
> 
> Thanks,
> 
> -- 
> Regards,
> 
> Prasanth P
> 
> 
> >
> >HTH,
> >Niels
> >
> >>[1] 
> >>http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/
> >>
> >>Thanks,
> >>
> >>-- 
> >>Regards,
> >>
> >>Prasanth P
> >>
> >>
> >>>Cheers,
> >>>Niels
> >>>
> yum install glusterfs-fuse
> 
> 
> Dependencies Resolved
> 
> ==
>   PackageArch Version 
> Repository   Size
> ==
> Installing for dependencies:
>   glusterfs  x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   1.4 M
>   glusterfs-api  x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs64 k
>   glusterfs-cli  x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   157 k
>   glusterfs-fuse x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs88 k
>   glusterfs-libs x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   309 k
>   glusterfs-server   x86_64   
>  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   819 k
> 
> Transaction Summary
> ==
> Install ( 6 Dependent packages)
> 
> Total download size: 2.8 M
> Installed size: 10 M
> 
> 
> Just trying to play catch up :)
> 
> Cheers,
> 
> PC
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.7 client rpms

[Prasanth]

On 04/21/2015 03:47 PM, Niels de Vos wrote:

On Tue, Apr 21, 2015 at 03:31:26PM +0530, Prasanth wrote:

On 04/20/2015 01:25 PM, Niels de Vos wrote:

On Sun, Apr 19, 2015 at 06:00:06PM -0400, Paul Cuzner wrote:

Hi,

Apologies for the dumb question.

I just thought I'd take a look at the nightly 3.7 build, and noticed
that when I installed glusterfs-fuse for the client it pulls in
glusterfs-server? Also the version is bumped to 3.8?

After the branching of release-3.7, the master branch has now been
tagged with v3.8dev. Your system is probably setup to use the nightly
builds of the master branch. You should be able to update your yum .repo
file so that these packages are used:

 http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/

Hi Niels,

I see only one slightly old nightly build
(glusterfs-3.7dev-0.1009.git8b987be.autobuild) in [1]. Is that expected or
is something broken?

This is indeed the last version available in the release-3.7 branch:

- 3.7dev-0.1009.git8b987be.autobuild
- commit 8b987be
- https://github.com/gluster/glusterfs/commits/release-3.7
   -> see the commit-id on the right side next to the subject of the patch


Yea, I got it. But I see 2 newer builds mentioned below under the 
v3.7dev tag in [1]:


[DIR] 	glusterfs-3.7dev-0.1015.gita3578de.autobuild/ 
 
	17-Apr-2015 09:51 	- 	
[DIR] 	glusterfs-3.7dev-0.1017.git7fb85e3.autobuild/ 
 
	18-Apr-2015 01:09 	- 	



Could you please help me understand, what are these builds then?

[1] 
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs/epel-6-x86_64/


Thanks,

--
Regards,

Prasanth P




HTH,
Niels


[1] 
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/

Thanks,

--
Regards,

Prasanth P



Cheers,
Niels


yum install glusterfs-fuse


Dependencies Resolved

==
  PackageArch Version   
 Repository   Size
==
Installing for dependencies:
  glusterfs  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   1.4 M
  glusterfs-api  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs64 k
  glusterfs-cli  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   157 k
  glusterfs-fuse x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs88 k
  glusterfs-libs x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   309 k
  glusterfs-server   x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   819 k

Transaction Summary
==
Install ( 6 Dependent packages)

Total download size: 2.8 M
Installed size: 10 M


Just trying to play catch up :)

Cheers,

PC
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.7 client rpms

[Niels de Vos]

On Tue, Apr 21, 2015 at 03:31:26PM +0530, Prasanth wrote:
> 
> On 04/20/2015 01:25 PM, Niels de Vos wrote:
> >On Sun, Apr 19, 2015 at 06:00:06PM -0400, Paul Cuzner wrote:
> >>Hi,
> >>
> >>Apologies for the dumb question.
> >>
> >>I just thought I'd take a look at the nightly 3.7 build, and noticed
> >>that when I installed glusterfs-fuse for the client it pulls in
> >>glusterfs-server? Also the version is bumped to 3.8?
> >After the branching of release-3.7, the master branch has now been
> >tagged with v3.8dev. Your system is probably setup to use the nightly
> >builds of the master branch. You should be able to update your yum .repo
> >file so that these packages are used:
> >
> > http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/
> 
> Hi Niels,
> 
> I see only one slightly old nightly build
> (glusterfs-3.7dev-0.1009.git8b987be.autobuild) in [1]. Is that expected or
> is something broken?

This is indeed the last version available in the release-3.7 branch:

- 3.7dev-0.1009.git8b987be.autobuild
- commit 8b987be
- https://github.com/gluster/glusterfs/commits/release-3.7
  -> see the commit-id on the right side next to the subject of the patch

HTH,
Niels

> 
> [1] 
> http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/
> 
> Thanks,
> 
> -- 
> Regards,
> 
> Prasanth P
> 
> 
> >
> >Cheers,
> >Niels
> >
> >>yum install glusterfs-fuse
> >>
> >>
> >>Dependencies Resolved
> >>
> >>==
> >>  PackageArch Version   
> >>  Repository   Size
> >>==
> >>Installing for dependencies:
> >>  glusterfs  x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   1.4 M
> >>  glusterfs-api  x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs64 k
> >>  glusterfs-cli  x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   157 k
> >>  glusterfs-fuse x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs88 k
> >>  glusterfs-libs x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   309 k
> >>  glusterfs-server   x86_64   
> >> 3.8dev-0.12.gitaa87c31.el7.centos  glusterfs   819 k
> >>
> >>Transaction Summary
> >>==
> >>Install ( 6 Dependent packages)
> >>
> >>Total download size: 2.8 M
> >>Installed size: 10 M
> >>
> >>
> >>Just trying to play catch up :)
> >>
> >>Cheers,
> >>
> >>PC
> >>___
> >>Gluster-devel mailing list
> >>Gluster-devel@gluster.org
> >>http://www.gluster.org/mailman/listinfo/gluster-devel
> >>
> >>
> >>___
> >>Gluster-devel mailing list
> >>Gluster-devel@gluster.org
> >>http://www.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.7 client rpms

[Prasanth]

On 04/20/2015 01:25 PM, Niels de Vos wrote:

On Sun, Apr 19, 2015 at 06:00:06PM -0400, Paul Cuzner wrote:

Hi,

Apologies for the dumb question.

I just thought I'd take a look at the nightly 3.7 build, and noticed
that when I installed glusterfs-fuse for the client it pulls in
glusterfs-server? Also the version is bumped to 3.8?

After the branching of release-3.7, the master branch has now been
tagged with v3.8dev. Your system is probably setup to use the nightly
builds of the master branch. You should be able to update your yum .repo
file so that these packages are used:

 http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/


Hi Niels,

I see only one slightly old nightly build 
(glusterfs-3.7dev-0.1009.git8b987be.autobuild) in [1]. Is that expected 
or is something broken?


[1] 
http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/


Thanks,

--
Regards,

Prasanth P




Cheers,
Niels


yum install glusterfs-fuse


Dependencies Resolved

==
  PackageArch Version   
 Repository   Size
==
Installing for dependencies:
  glusterfs  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   1.4 M
  glusterfs-api  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs64 k
  glusterfs-cli  x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   157 k
  glusterfs-fuse x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs88 k
  glusterfs-libs x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   309 k
  glusterfs-server   x86_64   3.8dev-0.12.gitaa87c31.el7.centos 
 glusterfs   819 k

Transaction Summary
==
Install ( 6 Dependent packages)

Total download size: 2.8 M
Installed size: 10 M


Just trying to play catch up :)

Cheers,

PC
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] regressions on release-3.7 ?

[Vijay Bellur]

On 04/21/2015 01:00 AM, Jeff Darcy wrote:

Another option would be to maintain a file with this list in the tests
directory. run-tests.sh can lookup this file to determine whether it
should continue or bail out.


Alternatively^2, I could modify http://review.gluster.org/#/c/10277/ to
run such tests and ignore the results instead of skipping them entirely.
What tests should be on the list?



All tests in the "Needing investigation" and "Being investigated" 
categories of spurious-failures etherpad [1] could be a good start.


-Vijay

[1] https://public.pad.fsfe.org/p/gluster-spurious-failures


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-infra] Gerrit and Jenkins likely unavailable most of Sunday

[Vijay Bellur]

On 04/21/2015 12:30 AM, Vijay Bellur wrote:

On 04/20/2015 09:46 PM, Justin Clift wrote:

On 20 Apr 2015, at 08:11, Atin Mukherjee  wrote:

On 04/20/2015 08:35 AM, Vijay Bellur wrote:



The procedure for migration from an admin perspective is quite involved
and account migrations are better done in batches. Instead of mailing
any of us directly, can you please update the gerrit migration etherpad
[1] once you have signed in using github? This might be a slightly more
optimal way of doing this migration :). We will pick up details from
the
etherpad at a regular frequency.


There are three set of problems what we noticed in the migration
process:

1. Forbidden access when you try to sign in with github
2. Multiple accounts upon successful github signing
3. Unable to view files in patchsets - 404 error

We have the fix for 1 & 2, please do mention in the etherpad [1] if you
fall into any of these categories.

Vijay is working on point 3 and will keep posted once he finds a
solution.


Gerrit is up and running now (thanks hagarth and ndevos).  Seems to be
working
decently too. :)



Thanks a ton, Justin! It would have been difficult for us to get here
without your efforts over the weekend!



I have the process to merge new GitHub userid's into existing accounts
fairly
well optimised now too.  So, if you need your account created either add
yourself to the etherpad or email me to get it done. :)

   https://public.pad.fsfe.org/p/gluster-gerrit-migration

We're still working through Jenkins stuff at the moment... so not a
lot in
the way of smoke nor regression tests happening just yet.



Here is a quick update on Jenkins:

1. Regression tests are getting triggered for Linux.

2. NetBSD regression tests and smoke tests need to be investigated.
Initial investigation points to problems with the gerrit-trigger plugin
of Jenkins.



gerrit-trigger plugin needs "Event Streaming" capability to run with 
Gerrit 2.7+. This has been added now.


All tests (smoke, NetBSD tests) should be functional now. Please let us 
know if you notice anything amiss.


Thanks,
Vijay

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] 3.7 client rpms

[Niels de Vos]

On Mon, Apr 20, 2015 at 08:49:00PM -0400, Paul Cuzner wrote:
> 
> Thanks Niels. Any insight into the fuse rpm pulling in the server rpm?

That definitely is a bug. I thougt we solved this for the new tiering
feature, but the version you installed below already should have that
fix.

Maybe an other feature added a dependency of a library/xlator that is
only available in the server RPM. We'll need to find out where that
dependency comes from. Please file a bug for this and have it block the
'glusterfs-3.7.0' tracker (use that name in the 'blocks' field).

Thanks,
Niels

> 
> 
> 
> - Original Message -
> > From: "M S Vishwanath Bhat" 
> > To: "Niels de Vos" 
> > Cc: "Paul Cuzner" , "Gluster Devel" 
> > 
> > Sent: Tuesday, 21 April, 2015 12:36:45 AM
> > Subject: Re: [Gluster-devel] 3.7 client rpms
> > 
> > On 20 April 2015 at 17:03, Niels de Vos  wrote:
> > 
> > > On Mon, Apr 20, 2015 at 03:01:46PM +0530, M S Vishwanath Bhat wrote:
> > > > On 20 April 2015 at 13:25, Niels de Vos  wrote:
> > > >
> > > > > On Sun, Apr 19, 2015 at 06:00:06PM -0400, Paul Cuzner wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Apologies for the dumb question.
> > > > > >
> > > > > > I just thought I'd take a look at the nightly 3.7 build, and noticed
> > > > > > that when I installed glusterfs-fuse for the client it pulls in
> > > > > > glusterfs-server? Also the version is bumped to 3.8?
> > > > >
> > > > > After the branching of release-3.7, the master branch has now been
> > > > > tagged with v3.8dev. Your system is probably setup to use the nightly
> > > > > builds of the master branch. You should be able to update your yum
> > > .repo
> > > > > file so that these packages are used:
> > > > >
> > > > >
> > > > >
> > > http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/
> > > > >
> > > >
> > > > But this repo doesn't have rpms el6 for x86 architecture
> > > >
> > > >
> > > http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/
> > > >
> > > http://download.gluster.org/pub/gluster/glusterfs/nightly/glusterfs-3.7/epel-6-x86_64/glusterfs-3.7dev-0.1009.git8b987be.autobuild/
> > > >
> > > > I haven't tried with this yet, But I also don't see a repodata in there.
> > >
> > > Hmm, it seems the mirroring fails for some reason. The script uses
> > > "lftp" and that gets a segmentation fault after transferring only some
> > > of the files :-/
> > >
> > > I'm now manually (read "in a loop") running the mirror command, so the
> > > packages should be available on download.gluster.org soon.
> > >
> > > Let me know if there are any other issues.
> > >
> > 
> > Looks like we have most rpms available now, including repodata.
> > 
> > Thanks Niels.
> > 
> > Best Regards,
> > Vishwanath
> > 
> > 
> > 
> > >
> > > Thanks,
> > > Niels
> > >
> > > >
> > > > Best Regards,
> > > > Vishwanath
> > > >
> > > >
> > > > >
> > > > > Cheers,
> > > > > Niels
> > > > >
> > > > > >
> > > > > > yum install glusterfs-fuse
> > > > > > 
> > > > > >
> > > > > > Dependencies Resolved
> > > > > >
> > > > > >
> > > > >
> > > ==
> > > > > >  PackageArch Version
> > > > > Repository   Size
> > > > > >
> > > > >
> > > ==
> > > > > > Installing for dependencies:
> > > > > >  glusterfs  x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > >  1.4 M
> > > > > >  glusterfs-api  x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > > 64 k
> > > > > >  glusterfs-cli  x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > >  157 k
> > > > > >  glusterfs-fuse x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > > 88 k
> > > > > >  glusterfs-libs x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > >  309 k
> > > > > >  glusterfs-server   x86_64
> > > > >  3.8dev-0.12.gitaa87c31.el7.centos  glusterfs
> > >  819 k
> > > > > >
> > > > > > Transaction Summary
> > > > > >
> > > > >
> > > ==
> > > > > > Install ( 6 Dependent packages)
> > > > > >
> > > > > > Total download size: 2.8 M
> > > > > > Installed size: 10 M
> > > > > >
> > > > > >
> > > > > > Just trying to play catch up :)
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > PC
> > > > > > ___
> > > > > > Gluster-devel mailing list
> > > > > > Gluster-devel@gluster.org
> > > > > > http://www.gluster.org/mailman/listinfo/gluster-devel
> > > > >
> > > > > __